Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
for some reason direct 11 doesn't work
"...you will find them here C:\Program Files (x86)\NVIDIA Corporation\PhysX\Engine\82D8704BAB07.
Copy a file called PhysXCore.dll then go to C:\Program Files (x86)\Steam\steamapps\common\The Bureau\Binaries\Win32 and find the same file. Delete the old one and paste the one you copied before. And voila! fixed!"
one other thing, turn off the nvidia physx stuff in graphic options if you are still getting crashes.
hope it works for you.
I read about this before I even installed it and did implement it, but it didn't work.
Besides, this fix was for something causing a crash in the actual game, as I understood. Not the game not launching at all.
The game wouldn't launch whether I tried either launch alternative.
I encountered a similar "0xc000007b error" on another game ("Darksiders: Warmastered Edition) and managed to find this video that solved the problem in both of these cases.
https://youtu.be/O1CkyEogN3c?si=eOI0H0HcpNpBZrDP
What I essentially did was this:
1. Use "Process Monitor" as described in the youtube video.
I discovered that the "msvcp100.dll"-files were still the culprit.
2. I manually removed the "msvcp100.dll"-files from both System32 and SysWOW64 in my Windows-folder (I'm on a 64-bit system).
3. I resinstalled "Microsoft Visual C++ 2010" using downloads I found on this page:
https://answers.microsoft.com/en-us/windows/forum/all/microsoft-visual-c-2008-and-2010/1e858d63-4c4b-46dc-86d3-03f7e8152c87
New "msvcp100.dll"-files were added by the installation to the System32 and SysWOW64-folders and after that my games with the "0xc000007b error" worked again.
Note: The most important part of this process, which I hadn't done in previous attempts, was to remove the corrupt "msvcp100.dll"-files before the reinstall!
Also be sure to use "Process Monitor" to figure out which files need replacing. It could be something other than "msvcp100.dll"-files in some cases.
Hope this fix works for those of you who are in a similar hurdle that I was in!
Now if I could just find the equivalent files for Homefront...
No, this isn't true. At least it wasn't for me.
I tried both installs from Steam and GOG (even went to the effort of buying it there) to see if either worked, and neither did.
It wasn't until I made the fix I told about in my previous post to replace a corrupt file in the Windows-folder that the game started working, and it had nothing to do with either Steam or GOG clients.
I appreciate you providing this information. It's just strange how there doesn't appear to be one fix that works for everyone.
What I did see with my own eyes, however, is that Steam is altering game code as part of their file validation process -- not their DRM wrapper files around the game, but the publisher's actual game files themselves. I have at least five different versions of the Homefront.exe file at the moment, all different in size, that I have accumulated through validation runs.