Borderland GOTY enhanced not working

[onewombat]

get Initialisation error even after i have reinstalled and swapped drives reinstalled again can any one help

[Arid Drifter]

wow it's almost as if all these posts are 🧌 baits

[Laggy_McStutters]

Originally posted by Arid Drifter:

wow it's almost as if all these posts are 🧌 baits

just like your ♥♥♥♥ post comments you are leaving everywhere

[Arid Drifter]

Originally posted by chrisbegg93:

Originally posted by Arid Drifter:

wow it's almost as if all these posts are 🧌 baits

just like your ♥♥♥♥ post comments you are leaving everywhere

butthurt?

[THE HALF HAJI HERO]

got the same problem

[Bruurbs]

Same issue

[Ins0mn1ac]

Same here. Used to work fine.

When I use the launcher it comes up with an initialisation error. But if I launch it straight from the BorderlandsGOTY.exe file, it works fine.

[Bruurbs]

Originally posted by Ins0mn1ac:

Same here. Used to work fine.

When I use the launcher it comes up with an initialisation error. But if I launch it straight from the BorderlandsGOTY.exe file, it works fine.

You can find the launcher's logs in C:\Users\[your username]\Documents\My Games\Borderlands Game of the Year\Launcher\Logs
Near the end should show what the actual error was. It barely narrowed it down for me but it does help to know. In my case, it was:
PNPDeviceID=ROOT\DISPLAY\0000
Unable to parse PNPDeviceID in Win32_VideoController

Quick edit: It was one of the Display Adapters found in Device Manager. Likely Parsec.

[Ins0mn1ac]

Originally posted by Bruurbs:

Originally posted by Ins0mn1ac:

Same here. Used to work fine.

When I use the launcher it comes up with an initialisation error. But if I launch it straight from the BorderlandsGOTY.exe file, it works fine.

You can find the launcher's logs in C:\Users\[your username]\Documents\My Games\Borderlands Game of the Year\Launcher\Logs
Near the end should show what the actual error was. It barely narrowed it down for me but it does help to know. In my case, it was:
PNPDeviceID=ROOT\DISPLAY\0000
Unable to parse PNPDeviceID in Win32_VideoController

Quick edit: It was one of the Display Adapters found in Device Manager. Likely Parsec.

Thanks. Yeah, mine said the exact same thing.

"2024.08.24 14:25:57.861 +10:00: 000069: PNPDeviceID=ROOT\DISPLAY\0000
2024.08.24 14:25:57.861 +10:00: 000070: Unable to parse PNPDeviceID in Win32_VideoController"

[Bruurbs]

Originally posted by Ins0mn1ac:

Thanks. Yeah, mine said the exact same thing.

"2024.08.24 14:25:57.861 +10:00: 000069: PNPDeviceID=ROOT\DISPLAY\0000
2024.08.24 14:25:57.861 +10:00: 000070: Unable to parse PNPDeviceID in Win32_VideoController"

In that case, there are two options.
-Uninstall or temporarily disable the other device/driver under Device Manager (specifically under Display Adapters) that is causing the issue
-Rename the Launcher.exe under Binaries\Win64 to BorderlandsGOTY.exe and rename the original BorderlandsGOTY.exe to Launcher.exe

Additionally, apply DXVK to prevent performance issues. (found here: https://www.pcgamingwiki.com/wiki/DXVK and under Official Website)
Edit: Specifically, d3d11.dll and dxgi.dll from the x64 folder. Throw those specific files from that folder in the tar.gz file into the game folder, specifically into Binaries\Win64 - in other words, where BorderlandsGOTY.exe and Launcher.exe are

If the second option doesn't work, then you'll just have to launch the regular ol' BorderlandsGOTY.exe directly.

[Cadmeum]

Easier solution, seems like we all have a parsec issue.

Go into parsec settings, then "Host" and set virtual fallback to "no."

Device Manager. Display Adapters. Parsec Virtual. Uninstall, and check uninstall drivers for this device.

It launched immediately after doing this. Worst case scenario, if you need this driver as a host, you can just leave the exe for reinstall.


Thank you for mentioning Parsec, and so recently. I was really wanting to play, and it was parsec all along. Funny enough, I don't host on here, so it's a win-win.

[Bruurbs]

Originally posted by uh huh, yeah, sure:

Easier solution, seems like we all have a parsec issue.

Go into parsec settings, then "Host" and set virtual fallback to "no."

Device Manager. Display Adapters. Parsec Virtual. Uninstall, and check uninstall drivers for this device.

It launched immediately after doing this. Worst case scenario, if you need this driver as a host, you can just leave the exe for reinstall.


Thank you for mentioning Parsec, and so recently. I was really wanting to play, and it was parsec all along. Funny enough, I don't host on here, so it's a win-win.

It's a great solution, but sadly I rely on Parsec to play certain games in coop with my wife, as the host.
That said, thank you for that solution! I'm sure it will apply for the vast majority of people.

[Cadmeum]

Originally posted by Bruurbs:

Originally posted by uh huh, yeah, sure:

Easier solution, seems like we all have a parsec issue.

Go into parsec settings, then "Host" and set virtual fallback to "no."

Device Manager. Display Adapters. Parsec Virtual. Uninstall, and check uninstall drivers for this device.

It launched immediately after doing this. Worst case scenario, if you need this driver as a host, you can just leave the exe for reinstall.


Thank you for mentioning Parsec, and so recently. I was really wanting to play, and it was parsec all along. Funny enough, I don't host on here, so it's a win-win.

It's a great solution, but sadly I rely on Parsec to play certain games in coop with my wife, as the host.
That said, thank you for that solution! I'm sure it will apply for the vast majority of people.

If you need to play BL with it, you are likely not going to find the solution, but if this is an outlier, you can just reinstall the GPU driver. If she doesn't play BL, she can be the host. Based on the error codes over the last few years, it's these virtual gpu drivers.

Parsec gotta go, and then you can reinstall. :P