Windows 10: error 0x82d4003 when I try to launch Halo reach

error 0x82d4003 when I try to launch Halo reach, I still have version 1909

:)

 

HALO REACH CRASH ERROR

hello guys please help me out

On launching any mode i am getting an error message UE4 MCC fatal error and it says halo mcc has stopped working and closes the window.I have no issue in navigating through the settings options the problem arises when i start any mode whether it is campaign
or multiplayer.

 

Halo PC won't launch

First of all, I hadn't played Halo PC in awhile, maybe a couple of months, yet I've had Windows 10 since about Day One. It HAS worked before. I don't know at one point it stopped working, if it was one of the latest Windows 10 updates, that, I don't know. I think it's worked since the Fall update, but I haven't really played it much since then.

Upon launching the game, I get the message: We are sorry but there was a problem accessing your personal Halo PC files which are located in your My Documents folder.

Mind you, the PC version of this game came out in 2003, so it was originally built for Windows XP, and that the Documents folder had been moved around, since. Once again, the game HAS worked fine on my machine on every version of Windows, since....well, with the exception of possibly WIndows 8/8.1, I never owned a copy of that. It worked fine on Vista, 7 and then 10.

A support link is provided in the error message, but the page cannot be found.

It looks like it's having trouble basically accessing the Documents\My Games\Halo folder.Before anyone suggests this: Re-installing did not help at all. Compatibility mode didn't help, either.

See the attachment to see the error I'm experiencing, but I did basically describe it.

 

Halo PC won't launch

EDIT: I found a workaround so I'm able to access and edit the registry. I'm currently working on it and will post another reply with results.

That doesn't even work. I cannot even create the first registry key, I end up with permission errors. See attached. I tried manually creating a reg file and that didn't work, either.