Application Load error 5:0000065434 after a complete fresh install

[radroachhd]

I did a complete fresh install of FNV in which I have my steam folder/s on my E drive and I cant even start up the game normally through the default .exe; I don't want to proceed with the 

Fear & Loathing in New Vegas (Fallout NV) guide until I am able to fix this as I don't want to screw anything up, I tried doing an initial start-up right after installing Mod Organizer as the linked video in the guide said it was required to start up the default NV.exe for all the features to load and work; I have also searched this problem online on multiple forums without any soulution to my personal problem. Please help.

[Greg]

You should run the game once on its own (not from Mod Organizer) so it can create the default ini files and registry settings. Once you do this, you should be able to run it from Mod Organizer.

[radroachhd]

You should run the game once on its own (not from Mod Organizer) so it can create the default ini files and registry settings. Once you do this, you should be able to run it from Mod Organizer.

Sorry if I didn't make it clear, but thats exactly what I did, I installed Mod organizer and put it in a new folder in my New vegas directory without starting it up, but did the first/initial start-up only on its own (FalloutNV.exe) which is why this is so mind boggling to me as to why I get the application load error and can't start up the game.

[GrantSP]

The error number is always associated with Steam needing to restart, either because of the reason outlined above or due to a recent Steam update.

 

I advise against installing MO anywhere inside the game installation folder. It has no need to be anywhere near the actual game as proximity to it is not a prerequisite for it to work. It also means anytime you need to do a reinstall of the game there are no extra files/folders you need to worry about.

 

Verifying your game with Steam will acquire fresh files if there is any problem with them and you should confirm that the game starts before continuing.

[radroachhd]

The error number is always associated with Steam needing to restart, either because of the reason outlined above or due to a recent Steam update.

 

I advise against installing MO anywhere inside the game installation folder. It has no need to be anywhere near the actual game as proximity to it is not a prerequisite for it to work. It also means anytime you need to do a reinstall of the game there are no extra files/folders you need to worry about.

 

Verifying your game with Steam will acquire fresh files if there is any problem with them and you should confirm that the game starts before continuing.

I moved my mod organizer folder and tools to a folder outside of my game folders and steam folders so thanks for that tip; I reinvalidated my files which I have to do everytime I try and play New Vegas, and New Vegas ONLY (for some reason), but part of the reason why I posted to this forum is because I already have been reinvalidating my files, and now even when I reinvalidate my files on steam and it says "all files are now recovered" I still get the same "

Application Load error 5:0000065434" message and the game doesn't start. I also just wanted to state that I have a legitimate legal copy of FNV and all the DLC from steam. In addition I checked to see if my steam was up to date, and running while I tried opening the original FNV.exe and it once again gave me the same load error.

Edited February 3, 2018 by radroachhd

[GrantSP]

Have you checked any of the Steam forums? This seems like a very odd behaviour. Are you also on any of the Insider buids of Windows? They may have broken something.

[radroachhd]

Have you checked any of the Steam forums? This seems like a very odd behaviour. Are you also on any of the Insider buids of Windows? They may have broken something.

I have checked about 6 steam forums (mostly outdated) for this problem but none of them address a solution to the problem i'm having as far as i've seen; and no, i'm just on regular windows 10.

Edited February 3, 2018 by radroachhd

[GrantSP]

What about any AV software? Most/all of that stuff is basically useless anyway, do you have any of that? Perhaps adding FNV as an exception or removing the AV itself. I've not heard of FNV just failing like this with no result from the actions you have currently taken.

 

Oh, one last thing. You aren't letting your system go into hibernation are you instead of shutting down? That will stop Steam updates from applying properly if I recall correctly.

[radroachhd]

What about any AV software? Most/all of that stuff is basically useless anyway, do you have any of that? Perhaps adding FNV as an exception or removing the AV itself. I've not heard of FNV just failing like this with no result from the actions you have currently taken.

 

Oh, one last thing. You aren't letting your system go into hibernation are you instead of shutting down? That will stop Steam updates from applying properly if I recall correctly.

I have 3 anti-virus softwares I believe; norton, malware bytes, and windows defender, also no I don't use hibernation on my pc, just regular shut downs at the end of the day. I will try and whitelist falloutnv somehow for each and see if it helps at all.

[radroachhd]

I whitelisted the new vegas folder on the AV softwares and it did not work, still the same error.

Edited February 3, 2018 by radroachhd

[GrantSP]

Just my two cents worth but Norton may be more hassle than its worth. I just use Defender, because it's there, and MalwareBytes Anti-Malware. Even before that in more than 35 years of computing I have never been struck down by viruses. Just be sensible about what you allow on your system.

I have heard however many horro stories from Norton users that rely on it to do the right thing and end up being burnt by it.

 

Not trying to convince you otherwise, just a different viewpoint. 

[radroachhd]

Just my two cents worth but Norton may be more hassle than its worth. I just use Defender, because it's there, and MalwareBytes Anti-Malware. Even before that in more than 35 years of computing I have never been struck down by viruses. Just be sensible about what you allow on your system.

I have heard however many horro stories from Norton users that rely on it to do the right thing and end up being burnt by it.

 

Not trying to convince you otherwise, just a different viewpoint. 

I've had no issues with Norton before so I do doubt that is what's causing the problem (but yeah it is pretty subpar as far as I can tell); my thinking right now is that I should uninstall the game and everything again and this time uninstall steam as well and reinstall all that over and see if that works. Thanks for the help so far.

Edited February 3, 2018 by radroachhd

[BobboBobberson01]

I've had this issue as well, but I managed to fix it! What I ended up doing was taking the guide's wording to heart: that is, making sure neither Steam nor Fallout New Vegas was installed in Program Files (x86) on the C drive. Once I moved my Steam install to my second drive, I was able to FINALLY start the game through Mod Organizer, and can now finally continue with installing F&L. Watch the video that is referenced in the guide, it really helps!

 

All in all, I think having F:NV installed separate from the Steam install folder is the root of this problem. Moving Steam from Program Files (x86) is just an added bonus, in my eyes. Though, a part of me wonders if this is a problem that MO could have fixed by itself if it knew this kind of thing caused an error.

Edited April 5, 2018 by BobboBobberson01

[Cragnor]

Ive been having a problem with crash on startup, and with this garbage, but I found that if you move steam out of (x86) as well as runing FNV EXECUTABLE in windows 7 compatibility mode, having the LAUNCHER run as admin on startup, and copying the steam executable into your FNV folder (Not changing the location, copying and pasting the executable) it should work. Its been bugging me for a good 4 hours of trying to fix this, so if anyone is still having this problem, I hope this helps.

 

And for the record, doing all of these seperately didnt work, so I dont know if I found the golden combo to make it work, or if I did the correct thing last so heres the order I did it in:

1. Tried running as admin, didnt work

2. Tried compatability and running as admin on startup, didnt work

3. Coppying the steam exe into the folder, didnt work

4. All 3 of the previous, didnt work

5. The first two as well as moving the steam install out of (x86), didnt work

6. All of the previously mentioned methods and it worked.

 

I also have a working theory as to why it happened, after seeing that my game took up a lot of space on my drive with mods, I deleted the game from file manager and took the script extender with it, as well as other mods that did major changes. Not confirmed in the slightest, but just a hunch.

[z929669]

1 hour ago, Cragnor said:

Ive been having a problem with crash on startup, and with this garbage, but I found that if you move steam out of (x86) as well as runing FNV EXECUTABLE in windows 7 compatibility mode, having the LAUNCHER run as admin on startup, and copying the steam executable into your FNV folder (Not changing the location, copying and pasting the executable) it should work. Its been bugging me for a good 4 hours of trying to fix this, so if anyone is still having this problem, I hope this helps.

 

And for the record, doing all of these seperately didnt work, so I dont know if I found the golden combo to make it work, or if I did the correct thing last so heres the order I did it in:

1. Tried running as admin, didnt work

2. Tried compatability and running as admin on startup, didnt work

3. Coppying the steam exe into the folder, didnt work

4. All 3 of the previous, didnt work

5. The first two as well as moving the steam install out of (x86), didnt work

6. All of the previously mentioned methods and it worked.

 

I also have a working theory as to why it happened, after seeing that my game took up a lot of space on my drive with mods, I deleted the game from file manager and took the script extender with it, as well as other mods that did major changes. Not confirmed in the slightest, but just a hunch.

Try following our SSG, particularly the Steam stuff