Error 0xc000007b

niles08 · 05-22-2018, 10:18 AM

Running into problems attempting to play on my work computer

The game loads fine on my home laptop, but each year I have also played on my work PC because I am so in love with the game lol.

OOTP 18 loads up fine but when I attempt to start OOTP 19, I get the following error message.

The application was unable to start correctly (0xc00000b7b). Click OK to close the application.

Side note: I am on Windows 10(just got updated).

Any advice or help would be greatly appreciated.

stealofhome · 05-22-2018, 12:57 PM

What location did the game install to? A few people have noticed the data folder in program x86 instead of my documents. This seems to cause issues where there are some administrative locks in place. I haven't seen that error though, but I'd guess try running as administrator and see if it works.

scott1964 · 05-23-2018, 10:11 PM

Maybe uninstall and the reinstall in the default location?

05-22-2018, 10:18 AM	#1
niles08 Minors (Rookie Ball) Join Date: Apr 2014 Posts: 44	Error 0xc000007b Running into problems attempting to play on my work computer The game loads fine on my home laptop, but each year I have also played on my work PC because I am so in love with the game lol. OOTP 18 loads up fine but when I attempt to start OOTP 19, I get the following error message. The application was unable to start correctly (0xc00000b7b). Click OK to close the application. Side note: I am on Windows 10(just got updated). Any advice or help would be greatly appreciated. __________________

05-23-2018, 10:11 PM	#3
scott1964 Hall Of Famer Join Date: Oct 2005 Location: Denver Posts: 5,624	Maybe uninstall and the reinstall in the default location? __________________ This just feels more like waiting in line at the Department of Motor Vehicles. PETA.....People Eating Tasty Animals.

05-22-2018, 12:57 PM	#2
stealofhome Hall Of Famer Join Date: Apr 2014 Posts: 2,282	What location did the game install to? A few people have noticed the data folder in program x86 instead of my documents. This seems to cause issues where there are some administrative locks in place. I haven't seen that error though, but I'd guess try running as administrator and see if it works.