0xc000007b error code for Borderlands 2 and Pre-Sequel

[santaboom2b]

Yes I know, there have been many posts about this and I have tried really.

I have tried:
-reinstalling all the vcredist stuff (used AiO Runtimes and also did it manually)
-the thing with the DLL files (to some extent, not so sure about this one tbh.)
-reinstalling the current DirectX version
-reinstalling the Game
-checking for Windows Updates
-running both Launcher and Game as Admin also ran the game in Compatibility Mode
-running "sfc /scannow" and "chkdsk c: /f /r" both as an Admin
-using Process Monitor tool (Didn't rly work maybe I used it wrong also not sure)
-updating my Nvidia Card Drivers

So yea my guess it's the .DLL files I used Dependency Walker. This gave me a ton of error messages but manually reinstalling all these files would take a while on top of that I have no idea where I would need to put all these files.

https://imgur.com/k1c2st7

Here are some error messages maybe half of them only to give a general idea.

Thank you for the help in advance :)

[Iceira]

do note i ask you again do you have any usb dongle or usb controller or device attached to system.
they have been caught in sometime prevent steam to work or a game. ( so few experince this )

if you dont know what and why this is so, do weight up the time in try fix it or maybe reset OS ( aka reinstall it) this has been done by gamers in all times, more a enough is enough, there is no shame in not can fix it, then i and other install 10 pc and one dont do right dont think we dont terminate it , because thats exatly what we do. ( and NO its about time cost and allowed to waste time in try fix it, most of the time we are not allowed to use time on it.. discard product happend every where with production. ( maybe not the right way but cost make it right.

[RiO]

İlk olarak Iceira W10 tarafından gönderildi:

do note i ask you again do you have any usb dongle or usb controller or device attached to system.
they have been caught in sometime prevent steam to work or a game. ( so few experince this )

USB devices don't raise that error code. That particular error code is only raised by an executable when a proper DLL that is binary-compatible with the DLL or header files that that exeuctable's source code was compiled and linked against, could not be loaded. Either because it could not be located; or because it was located but found to be mismatched or corrupt.

İlk olarak Iceira W10 tarafından gönderildi:

maybe reset OS ( aka reinstall it) this has been done by gamers in all times, more a enough is enough, there is no shame in not can fix it, then i and other install 10 pc and one dont do right dont think we dont terminate it , because thats exatly what we do. ( and NO its about time cost and allowed to waste time in try fix it, most of the time we are not allowed to use time on it.. discard product happend every where with production. ( maybe not the right way but cost make it right.

"IT. Have you tried turning it off and on again?" comes to mind.
Reinstalling from scratch because you don't know any better is the nuclear option.
And it's a fine time-saver for corporate environments where everything can quickly be restored off of a stock deployment image and the master copies of a user's files are all safely centrally stored on a corporate SAN with their workstation only housing mirrored working copies.

It's a poor solution for private owned systems and only a last resort.

(And for god's sake; work on your English skills a bit. I can barely parse what you're writing.)

İlk olarak santaboom2b tarafından gönderildi:

Step ahead of you already did the Dependency Walker thing here is the link again seems like I have a couple of DLL files that are "out of place."

https://imgur.com/k1c2st7

Like I mentioned before those are only a couple of screenshots the list is a lot longer my best idea is maybe getting a programm that fixes DLL files but so far I didn't have much luck with that.

The API-MS-WIN-CORE-* dlls are a red herring. You are not actually missing those. They are aliases for the actual kernel functions and are part of the Universal Windows Platform (UWP) abstraction.

These rely on a clever redirection mechanism in the DLL loader; a mechanism that Microsoft incorporated to ensure at runtime a UWP program can use the version of the kernel APIs that is available on the system without requiring direct; hard binary compatible linkage. This little trick allows such programs to work on Windows 7 - 11 on any CPU architecture supported by Windows, without needing specific builds of the program for specific OS versions or CPU architecture.

If you have a program which is actually erroring on loading those DLLs or is showing them as missing in Dependency Walker, then either that program was written wrong - in a way which bypasses that redirection mechanism, or Dependency Walker is interpreting things wrong.

The proper versions of those DLLs are part of the OS itself and are used by any UWP application on the system; including many that ship with Windows out-of-the-box. If you'd have a problem here, everything from Calculator to the Settings app would be broken.

[santaboom2b]

İlk olarak RiO tarafından gönderildi:

İlk olarak Iceira W10 tarafından gönderildi:

do note i ask you again do you have any usb dongle or usb controller or device attached to system.
they have been caught in sometime prevent steam to work or a game. ( so few experince this )

USB devices don't raise that error code. That particular error code is only raised by an executable when a proper DLL that is binary-compatible with the DLL or header files that that exeuctable's source code was compiled and linked against, could not be loaded. Either because it could not be located; or because it was located but found to be mismatched or corrupt.

İlk olarak Iceira W10 tarafından gönderildi:

maybe reset OS ( aka reinstall it) this has been done by gamers in all times, more a enough is enough, there is no shame in not can fix it, then i and other install 10 pc and one dont do right dont think we dont terminate it , because thats exatly what we do. ( and NO its about time cost and allowed to waste time in try fix it, most of the time we are not allowed to use time on it.. discard product happend every where with production. ( maybe not the right way but cost make it right.

"IT. Have you tried turning it off and on again?" comes to mind.
Reinstalling from scratch because you don't know any better is the nuclear option.
And it's a fine time-saver for corporate environments where everything can quickly be restored off of a stock deployment image and the master copies of a user's files are all safely centrally stored on a corporate SAN with their workstation only housing mirrored working copies.

It's a poor solution for private owned systems and only a last resort.

(And for god's sake; work on your English skills a bit. I can barely parse what you're writing.)

İlk olarak santaboom2b tarafından gönderildi:

Step ahead of you already did the Dependency Walker thing here is the link again seems like I have a couple of DLL files that are "out of place."

https://imgur.com/k1c2st7

Like I mentioned before those are only a couple of screenshots the list is a lot longer my best idea is maybe getting a programm that fixes DLL files but so far I didn't have much luck with that.

The API-MS-WIN-CORE-* dlls are a red herring. You are not actually missing those. They are aliases for the actual kernel functions and are part of the Universal Windows Platform (UWP) abstraction.

These rely on a clever redirection mechanism in the DLL loader; a mechanism that Microsoft incorporated to ensure at runtime a UWP program can use the version of the kernel APIs that is available on the system without requiring direct; hard binary compatible linkage. This little trick allows such programs to work on Windows 7 - 11 on any CPU architecture supported by Windows, without needing specific builds of the program for specific OS versions or CPU architecture.

If you have a program which is actually erroring on loading those DLLs or is showing them as missing in Dependency Walker, then either that program was written wrong - in a way which bypasses that redirection mechanism, or Dependency Walker is interpreting things wrong.

The proper versions of those DLLs are part of the OS itself and are used by any UWP application on the system; including many that ship with Windows out-of-the-box. If you'd have a problem here, everything from Calculator to the Settings app would be broken.

Okay that's a lot to take in I've tried a repair install with the Media Creation Tool but sadly that didn't work. I'm also guessing that I might use Dependency Walker wrong somehow? But I have no idea how or what I'm doing wrong. Yea reinstalling Windows is good but I have a lot of programs and other stuff and I'll be honest I'm not very organised so I have a genreal fear of losing important files on top of that my internet speed is questionable.

Another thing to add these 3 DLL's are at the only ones without the API-MS-WIN-CORE-* maybe that helps?

https://imgur.com/QqFMpkI

[RiO]

The ext-ms-windows-core-* dll file listed is also part of UWP.

pdmutilities.dll is afaict a delayed import that is used as part of the debugging experience for C++ with Visual Studio, through something called process debug manager (pdm). It should not matter if it's missing for normal use.

hvsifiletrust.dll I legitly don't know what it is. But it is reported as missing on more systems, where the fact that it is missing - is harmless.

ieshims.dll is an artefact from the ancient Internet Explorer Protected Mode.
It proxies several system calls in a way that is compatible with the Protected Mode sandbox.
It's a delayed import and isn't ever used if you don't use protected mode. If it's missing from your system, that's probably because MS uninstalled most of IE 11 from consumer desktops some time ago as part of a system update.
This should not matter.


I've done some digging for you and Microsoft itself will also recommend that you no longer use Dependency Walker; because it was discontinued and no longer functions properly (no longer returns correct results) in Windows 8+.

They recommend a modernized, open source variant of it instead:
https://github.com/lucasg/Dependencies

https://social.msdn.microsoft.com/Forums/en-US/8c808d5b-5fda-4870-b06c-c44280285c4b/open-sourcing-dependency-walker-dependsexe#1963b6be-d08b-4b96-af78-65f6bb340da4


Maybe try with that instead and see what it tells you.

[santaboom2b]

Ahh yes it was one file, I can't thank you enough RiO <3

For people with the same problem the file name was msvcp100.dll here is the donwload link

https://www.dll-files.com/msvcp100.dll.html

Very important tho get the 32x Version not the 64x put the file in
"C:\Program Files (x86)\Steam\steamapps\common\BorderlandsPreSequel\Binaries\Win32"
and you are ready to go.

[RiO]

If you want a comprehensive fix that doesn't rely on manually dropping DLL files:
msvcp100.dll should iirc be part of the MSVC++ 2012 Redistributable.

Yes; version number and product number don't match. That's a Microsoft thing.
(You always have to look this stuff up; I hope I got the version correct this time. :: sigh ::)

Check that you have both the X64 and the X86 version of that installed.
The former is for 64-bit executables. The latter, and the one you're probably missing, is for 32-bit executables. On a 64-bit Windows OS you should always install both.

https://www.microsoft.com/en-us/download/details.aspx?id=30679

And should you want MS's curated list of all the currently supported (and last versions of no longer supported) VC++ redistributables that you can download from their own servers:
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist

[Iceira]

OP do you have a spare disk try install it on that, more a test is the OS your are on corupted and not fixable somehow, until you know what cause this, thats how we other test for own mistake. or app or what thats is you are doing that could cause such,

most here has no doubt you cant figure how to reinstall VC++, so something drag that game down and then it throughout thats code to 2 games, if you cant see that not possible and game is well test by many steam users over many years. ( ask 2k support then ) i cant see no other choise then that or test with fresh system or you might do same mistake all over again. or device or driver do it to the game thats dont like whatever it is.


ps.
the minute that system is up and running test game before you add all own other apps and choise, because whatever it is, you should trigger it again if you do all same install as current system, if not then you did have a corrupted system.