Borderlands: The Pre-Sequel

Borderlands: The Pre-Sequel

View Stats:
Cametokur Nov 1, 2016 @ 3:45am
Losing my mind trying to install this game.
So this isn't really Borderland's problem but rather the first time I've noticed it. I'm on a fresh install of Win10x64. 100% of all other games install properly and run as they should in Steam and other platforms like Origin and Uplay.

i7-6600k, ASUS ROG Strix GTX 1080, 32gb ram, installing to a SSD.

The Borderlands Pre-Sequel first-time install procedure in Steam takes an abnormal amount of time to get going- VC++ package takes forever (1-2 minutes) just to extract. It finishes OK there, but when Step 4 of 6 rolls around, .Net 4.0 installer starts up and brings this PC to a halt. After about 5 minutes of waiting it does respond to a ctrl-alt-del but it hangs immediately after. I've tested various BIOS and hardware settings and no matter what I am forced to hard-reset the machine.

Downloading all available .Net 4.0 installers from the Microsoft website results in the same freeze. I tried the "fixdotnet" package offered by Microsoft and it returns no errors. Again, I reiterate this is not this particular game's fault but rather probably a larger problem that I've been derping myself in the face for hours trying to isolate.

Anyone out there have any idea what could be going on? It's almost impossible to search for recent Win10 troubleshooting. Google has not been helpful and mostly throws results from either the Win10 preview or the Anniversary update which are no help whatsoever. The only person out there who I've found with my exact problem was told by Microsoft to run the FixDotNet tool I mentioned above, it did not solve his problem and he was asked to reinstall Windows, and he hasn't replied in 5 months so who knows if it worked or not.

TPS is working fine on my laptop and my living room PC, both running similar versions of Windows 10, latest updates, almost all of the same games installed and running fine. I'm not sure if I've run into a freak hardware problem or what. Every time this machine locks up on me and I have to hit the reset button it makes me want to get this game running on it even more.

:csgogun: :pinkteam:
< >
Showing 1-4 of 4 comments
SB Nov 1, 2016 @ 10:19am 
Several things you can try.

-verify game catche, it's possible that the installer is somehow corrupted.

-run steam as admin and run the installation again (shouldn't be required but whatever, try it anyway)

-if you're using steam beta, revert back to the normal version

-in win10 disable the xbox game dvr nonsense and try again

-uninstall it from the computer entirely and delete the files in \steamapps\common\BorderlandsPreSequel
-after this make a backup of the game using the laptop, restore the backup on the pc
Cametokur Nov 1, 2016 @ 8:31pm 
Thank you so much for your reply. I verified the game cache and it indeed had to redownload around 200mb of files, but it did not help. The only thing I can think of, since this doesn't seem to be a Borderlands problem but a Microsoft one, is to disable the XBOX stuff, which I will look into. Thank you again!
SB Nov 2, 2016 @ 5:00am 
no problem XD

also, if you're 100% sure that it's only the .net and other first time run setup things that are causing the problem, but game files aren't corrupted, you can avoid the first time setup alltogether with a regedit trick.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Valve\Steam\Apps\261640]
"vcredist2005"=dword:00000001
"vcredist2005atl"=dword:00000001
"vcredist2008"=dword:00000001
"vcredist2010"=dword:00000001
"directxredist"=dword:00000001
"net40redist"=dword:00000001


That will flag them all as "installed" XD
Cametokur Nov 2, 2016 @ 10:28am 
Ah, I'm forever in your debt. I hadn't thought of the registry for some reason. Adding the net40redist line definitely worked. Previously I'd copied the installed game from my laptop, went on MS forums, tried safe-mode, unpacked the executable, and I think I narrowed down the problem but there is no fix- has something to do with certain apps detecting that .Net 4 is not active in the "turn windows features on or off" settings. How ridiculous. I hope that this is my only instance encountering this, but for now, TPS seems to be running perfectly. :2016popsicle:
< >
Showing 1-4 of 4 comments
Per page: 1530 50

Date Posted: Nov 1, 2016 @ 3:45am
Posts: 4