UE4-MCC Fatal Error! (Let's try to solve this)

Halo MCC PC (Steam)
After the update of 17th November, 2020, I am getting the “UE4-MCC Fatal Error!” game crash. This error is showing up right after the small banner of “Halo: The Master Chief Collection” pops up, which comes after the Anti-Cheat initialization after we launch the game. Apparently, I’m not alone, tons of other people are getting this crash as well, and people have been getting this crash even prior to Halo 4’s launch. So instead of just reporting that “I’m having the same problem, let us know if a fix comes along” etc. let’s try to figure this thing out so we can inform 343 in a better way so as to what exactly is causing this problem.

On doing some research, I found out that the MCC main menu interface is rendered by the Unreal Engine 4(UE4) and the games are run by their separate and individual engines. So for many of us, it is the Main Menu UI that is crashing (the UE4), and for all we know the games might be just fine, as before this update all the previous games ran just fine. This may be because the update brought in crossplay along with optimizations for Xbox Series X/S, which are next gen consoles can have good system specifications. So, something optimized for the next gen console-specs might not run on certain PCs.

I will list the following fixes that I have attempted, but without any success:

  1. Uninstall and Reinstall Halo MCC and Steam more than 10 times.
  2. Repairing Anti-Cheat on Halo: MCC.
    3.Updating Windows, all of Windows features.
    4.Updating GPU drivers.
    5.Clearing out Local files on C:\Users{Username}\Appdata\LocalLow\MCC
    6.Manually taking off, cleaning, and putting back my hardware properly.
    7.Verifying file integrity from Steam.
    8.Try and search for missing files in the MCC folders.
    9.Completely wiping and resetting my PC twice and doing all the above necessary steps twice as well.
    10.Submitting a ticket in the Halo Support website.

Therefore it may be possible that the crash is being caused due to the inability of meeting minimum requirements. I will provide my system specs below:
OS: Windows 10 Pro 64-bit (10.0, Build 19042)
Processor: Intel(R) Core™ i3-4130 CPU @ 3.40GHz (4 CPUs), ~3.4GHz
RAM: 8 GB
GPU: NVIDIA GeForce GTX 750 Ti
These specs may be low, but there are way above the minimum specs that has been specified in Steam for running Halo: MCC.
Also, think of it logically, a game which is originally from 2012, no matter how much shaders you put on it, will easily run on the above specs. Reason: I can run Assassin’s Creed: Odyssey (2019) smoothly on medium/high graphic presets, which is an open world third-person RPG game with much more environmental details, and then comes Halo (2012), a Linear first-person shooter with comparatively much less environmental details. Hence, by logic, it cannot be a hardware insufficiency problem.

I have asked a few people, and for those whose game is running, they have a better GPU than me. E.g. GTX 1060, 1080, etc. And I have also spoken with someone who has the same GPU as me and his game is NOT running, just like me. So right now, this just might me a hardware reason that may be causing the crashes.

For those read the whole thing and those, whose MCC is facing crashes at launch/mid-game, PLEASE mention your system specs below. Let’s first see if this is a hardware problem or not.
Please mention your full system specs below ( or at least OS, GPU, Processor and RAM)

I don’t think its a problem with your GPU.
I have the same problem and here’s my spec:

Win 10 Pro - 1909
i7-3770T
24GB RAM
RTX 2060

Also manifested itself after the update to include Halo 4 yesterday. So its definitely something included in that update.
Reinstall of the game did not help me either.

I had this error also.
A poster in another thread suggested adding -windowed to Steam launch command and now mine is working.

My specs are:
OS: Windows 7 64-bit (6.1, Build 7601)
GPU: NVIDIA GTX 460 SE
Processor: AMD Athlon™ II X4 640 Processor
RAM: 16GB

yep, having the same problem after the update last night, hopefully 343 see’s this and gets a patch out soon

Same problem here… verry annoying come on guys…

Intel(R) Core™ i7-7820X CPU @ 3.60GHz 3.60 GHz
Windows 10 Pro 20H2 OS Build 19042.630
32.0 GB DRAM
RTX 2080

Gtx 750ti
Amd FX™-4130
8 gigs ram
Os windows 10
Should also mention I was on the insider flight this bug occurred after my first time playing the game For me deleting the app data mcc folder fixed it however after the flight received an update midway through the fix stopped working for me

I’m having the same issue.
970 GT
16GB RAM
AMD 3600X
1TB SSD.

Running gamepass version, so it’s not just a steam issue. I’ve installed twice, to 2 different drives. No go.

Happened to me as well. I am not sure if it is equipment based, as most of us played the game before Halo 4 was launched with this update. I was excited to play Halo 4, but I cant after the update. I even switched to the steam version from the game pass version and it still doesnt work. I hope a fix comes soon.

> 2535434235709530;8:
> Happened to me as well. I am not sure if it is equipment based, as most of us played the game before Halo 4 was launched with this update. I was excited to play Halo 4, but I cant after the update. I even switched to the steam version from the game pass version and it still doesnt work. I hope a fix comes soon.

There is a fix already
Just go back and I’ve explained the whole fix in another topic/section of these forums

> 2533274835453724;7:
> I’m having the same issue.
> 970 GT
> 16GB RAM
> AMD 3600X
> 1TB SSD.
>
> Running gamepass version, so it’s not just a steam issue. I’ve installed twice, to 2 different drives. No go.

There is a fix already
Just go back and I’ve explained the whole fix in another topic/section of these forums

The shortcut options for the gamepass version are normal window, minimized, and maximized. None of these options fix the problem. The option to edit the shortcut to force windowed mode does not exist for the gamepass version.

> 2535432833908437;9:
> > 2535434235709530;8:
> > Happened to me as well. I am not sure if it is equipment based, as most of us played the game before Halo 4 was launched with this update. I was excited to play Halo 4, but I cant after the update. I even switched to the steam version from the game pass version and it still doesnt work. I hope a fix comes soon.
>
> There is a fix already
> Just go back and I’ve explained the whole fix in another topic/section of these forums

I actually fixed it with the “-windowed” method, when you set it to launch in windowed mode. Hopefully this helps someone else!

same issue here

> 2535434235709530;12:
> > 2535432833908437;9:
> > > 2535434235709530;8:
> > > Happened to me as well. I am not sure if it is equipment based, as most of us played the game before Halo 4 was launched with this update. I was excited to play Halo 4, but I cant after the update. I even switched to the steam version from the game pass version and it still doesnt work. I hope a fix comes soon.
> >
> > There is a fix already
> > Just go back and I’ve explained the whole fix in another topic/section of these forums
>
> I actually fixed it with the “-windowed” method, when you set it to launch in windowed mode. Hopefully this helps someone else!

i just tried this
it launches the game so that’s a step forward, but then when i hit enter to go into the main menu, the game crashes.

but hey! two steps forward, one step back, i’ll take it as progress

also

if we’re talking hardware issues (though i don’t think it is)

ryzen 3900XT
corsair 64 GB DDR4 3200mhz
RTX 2080

If you get a fatal error when starting Halo:MCC on gamepass I found a fix. Steam users have had a lot of success forcing -windowed mode by editing the options/shortcut. This isn’t an option for the Gamepass version.So I thought I would finally install Geforce Experience. I don’t like some of their privacy policies, having to log in, etc. so I never used it. But I was desperate for a fix so I could play.You can use it to force windowed mode, change the graphic settings before you even attempt to load the game. I’ve had a lot of luck forcing windowed mode in a resolution lower than my monitor even before the game tries to load. In my case it was windowed, 1080p, graphics set to optimized.Hope this works for other people with Nvidia cards and the Gamepass version!

> 2535432833908437;10:
> > 2533274835453724;7:
> > I’m having the same issue.
> > 970 GT
> > 16GB RAM
> > AMD 3600X
> > 1TB SSD.
> >
> > Running gamepass version, so it’s not just a steam issue. I’ve installed twice, to 2 different drives. No go.
>
> There is a fix already
> Just go back and I’ve explained the whole fix in another topic/section of these forums

you didn’t explain how to fix it on gamepass though

I just encounter this very issue (GamePass) any one know the fix?

Hi Guys,
I fixed the issue, I renamed the below folder to “MCC.MCC” relaunched the game and a new folder was created.

  1. Locate folder

C:\Users\user\AppData\LocalLow\MCC

  1. Rename

C:\Users\user\AppData\LocalLow\MCC.MCC

  1. Launch Game

Hope this works for you.

> 2533274817695696;17:
> Hi Guys,
> I fixed the issue, I renamed the below folder to “MCC.MCC” relaunched the game and a new folder was created.
>
> 1. Locate folder
>
> C:\Users\user\AppData\LocalLow\MCC
>
> 2. Rename
>
> C:\Users\user\AppData\LocalLow\MCC.MCC
>
> 3. Launch Game
>
> Hope this works for you.

I can confirm that it is not your GPU. I am running a GTX 970 and this update caused the same error for me. However I can also confirm that this fix resolved the issue for me.

Originally I was using a workaround that involved adding the launch command “-windowed” in the steam launch options, but this eventually stopped working. Curious if the MCC.MCC fix will stop working. I hope this gets fixed in a future update.

have had the same error as well, had it happen twice while playing a completive matchmaking game of Halo 4, PC specs below

Ryzen 7 2700x
Asus Vega 64 Strix
MSI X370 gaming pro carbon
Team T-Force RGB 16GB Ram @3066mhz
EVGA SuperNova 850w G3
LG Ultrawide 21:9

in Microsft Store Games there isn’t this problem issues