It looks like Microsoft is gearing up to make their accessibility a little less than, well accessible. According to Windows Central, players are encountering a new error code dubbed “0x82d60002.” This code allegedly is only appearing when players attempt to use unauthorized third-party accessories, such as controllers, UDB drives, and other peripherals. It also displays a warning message which states that starting November 11, 2023, all unauthorized accessories will be blocked and no longer be able to be utilized with their respective Xbox console.

Microsoft has changed its policy and will no longer allow unauthorized third party Xbox accessories starting Nov 12th.

Hori, Razer, 8bitdo stuff should be safe

According to WC sources, Xbox is expanding its approval for third party wireless controllers.https://t.co/js9knadPwg pic.twitter.com/BuP7KLptod

— Knoebel (@Knoebelbroet) October 30, 2023

This is a major shift from how Microsoft usually operates, as they’ve regularly allowed several different peripherals to be used on both their Xbox consoles and Windows operating system. As you can see in the post above, there are some brands that appear to be considered safe from not being usable on an Xbox system, but that is only a small handful of companies. Thankfully Windows Central also mentioned that their sources familiar with the situation have stated that Microsoft is “expanding its program for approved third-party wireless Xbox controllers.”

This would be a most welcome change as nearly all of Microsoft’s third-party controllers are all wired, especially with those using PCs on a controller to play. It’s possible that the company will make this information known to the public once the aforementioned date passes, but as of this writing, it’s currently unknown, and the company has not made any official comment regarding the situation. Either way, as long as your third-party product has some sort of seal/official branding of Xbox on it, it’s more than likely going to be fine once the November 11 date passes. Hopefully, Microsoft further clarifies on this sooner rather than later.