Microsoft has begun implementing measures to restrict using unlicensed third-party Xbox controllers.
The rumours started when several forums like ResetEra posted that certain Xbox controllers now display a “connected accessor is not authorised” error when the device is connected to Xbox consoles, according to a report by The Verge.
As of now, the motive behind this move by Microsoft remains unclear, whether it aims to combat cheating devices or promote the Designed for Xbox partner program. Windows Central, citing sources close to Microsoft, reported that this incident may be “related to Microsoft expanding its program for approved third-party wireless Xbox controllers.”
It is important to note that Microsoft has yet to license its Xbox wireless protocol to third-party vendors. This is the reason why most of the third-party Xbox controllers are wired.
According to Microsoft Xbox support, “error 0x82d60002 occurs when you connect an unauthorised accessory to your Xbox console”. The advisory also includes a ‘Note’ explaining that “from the moment you connect an unauthorised accessory and receive error code 0x82d60002, you’ll have two to use the accessory, after which time it will then be blocked from use with the console. At that time, you’ll receive error code 0x82d60003.”
The only solution to this particular error is to connect a licensed accessory.
This restriction won’t apply to those third-party Xbox accessory developers already part of the Designed for Xbox program. Furthermore, this error will likely affect cheat devices like XIM, Cornus Zen and ReaSnow S1.
BrookGaming, a gaming accessories manufacturer, published a list of affected accessories. Another manufacturer, Cronus, will also be affected by this blockade by Microsoft.
The move could have potentially harmful consequences for the gaming world.
“This is essentially a death sentence for local fighting game events that run on Xbox, much less others that can only afford one arcade stick,” Maximilian Dood, a YouTube influencer, said on Twitter.
As of now, Microsoft has yet to comment on this whole affair.