I haven’t played Halo MCC for PC for about 6 weeks now, and I don’t play much online. Today, when I attempted to run Halo MCC with EAC, it gave me the error code 10022 (Unexpected Error. (0x0030004)). I don’t know why.
I decided to reset my Windows 10 (Build 20150) install via Settings > Update & Security > Recovery > “Reset this PC” - clean install, kept nothing.
I updated the system via Settings > Update & Security and get updates from the Microsoft Store.
My fresh install of Windows 10 is ready to go, I go to Microsoft Store and install Halo: Master Chief Collection (latest version 1.1619.0.0 available in Microsoft Store) icon to start the game
After it installs I click on the Halo: Master Chief Collection icon (which is still not showing an icon, just a blue square) Easy Anti-Cheat comes up and then gives me the error.
> GameID: 426 (64bit)
> Windows Version: 10.0 (Build 20150)
> Error Code: 10022
> Process Exit Code: 103h
> UUID: 1fa05fcc-8f1d-557b-7550-52d1b42c1baa
> Process list:
> <I removed all processes because I felt it was a waste of space on the forums>
I’ve looked up some solutions, most are for Steam version an not for the Microsoft Store version.
The Easy Anti-Cheat web site tells me to run the setup, the setup is not included with the Halo: Master Chief Collection install, so I can’t.
Halo Support web site doesn’t offer any assistance when it comes to Easy Anti-Cheat, Easy Anti-Cheat
Is also not useful.
I double checked my Xbox Networking in Settings > Gaming
Results:
Performance: 63ms
Packet loss: 0%
NAT Type: Open
Server Connectivity Connected
My Questions are:
Why did this happen all of a sudden? - How do I fix it? - Is anyone having issues with EAC?
I am also having this issue. I recently updated to Build 20150 of Windows 10 to use some of the developer tools. I’m guessing EAC has some sort of incompatibility with this build.
I also logged a support request with EAC. I think the issue is likely on Microsoft’s end though. Build 20152 came out yesterday and the build notes for it mention that the last build caused some games/programs to crash at launch. They found the source of the error are working on a fix for a future flight. Hopefully it gets released soon
> 2533274914473713;4:
> I also logged a support request with EAC. I think the issue is likely on Microsoft’s end though. Build 20152 came out yesterday and the build notes for it mention that the last build caused some games/programs to crash at launch. They found the source of the error are working on a fix for a future flight. Hopefully it gets released soon
I’m downloading the new build now, curious to see what happens. I’ll post my findings.
> 2631120853735429;11:
> Update: I still haven’t heard back from Easy Anti-Cheat regarding this problem. I have logged another ticket at Easy Anti-Cheat
>
> If you haven’t logged a ticket, maybe we need to make ourselves heard.
I haven’t heard back from them either. I might just end up reinstalling a production version of Windows. The features in the Insider builds for developers are cool and it’s nice to be able to do much of my work without booting into Linux, but it’s not worth me not being able to use my personal computer for both work and play. It’s probably way too much work for the developers of EAC to constantly keep their software compatible with builds that basically release weekly and are known to break functionality. I’ll go back to dual-booting for work
> 2533274914473713;12:
> > 2631120853735429;11:
> > Update: I still haven’t heard back from Easy Anti-Cheat regarding this problem. I have logged another ticket at Easy Anti-Cheat
> >
> > If you haven’t logged a ticket, maybe we need to make ourselves heard.
>
> I haven’t heard back from them either. I might just end up reinstalling a production version of Windows. The features in the Insider builds for developers are cool and it’s nice to be able to do much of my work without booting into Linux, but it’s not worth me not being able to use my personal computer for both work and play. It’s probably way too much work for the developers of EAC to constantly keep their software compatible with builds that basically release weekly and are known to break functionality. I’ll go back to dual-booting for work
Might be a good idea. Might be my plans for next weekend… or more when Halo 3 is released.
I believe I can say with some level of certainty that this issue is created by Windows 10 Build 20150+. I have cleansed my system and reinstalled Windows 10 Pro Build 18363.959 and I have no issues starting up MCC with EAC enabled.
For what its worth MS have acknowledge it as an issue in the latest Insider Build notes.
Its not solved as of yet (at least according to it) but they are working on it.
Just damn unfortunate it had to happen around Halo 3 release time…
