Error P:0000065432 after reinstalling OS and Vortex

[lynx64]

Greetings. After reinstalling OS (Win10) and Vortex and updating all the mods to the latest versions I get a message "Application load error P:0000065432" every time I want to start FNV. The mods I have:

NVSE, NVSR, NVAC, Collision Meshes FNV, JIP LN NVSE Plugin, NV Tick Fix, JohnyGuitar NVSE Plugin, 4Gb patcher, FPGE. All the fixes I found were from about 2015-2016 years when manual installation of mods or use of NMM were in use. So does anybody know any modern solution of such problem? BTW I tried to reinstall the game and check the integrity of the files in Steam - nothing helped. After starting the game from Steam only black screen appears so I have to shut down the game process.

[vortexposer]

Did my own research on this a few years back and determined cause is due to using a secondary installation drive vs the drive that Steam is actually installed to. E.g. C:/Steam/* with game installed to D:/SteamLibrary/*. 

The fix is to install game (Oblivion, Fallout3/NV) onto same drive as Steam's installation or move Steam's install to whichever drive is being used for install... alternatively, there's an older workaround which involves copying Steam.exe and placing its physical clone into the root folder of Fallout New Vegas. I've since remedied my own situation but if you're wanting to try the workaround "fix", I'd recommend creating as new (custom) user mod that packages the Steam.exe as its own mod, which then deploys from Vortex Staging vs manually installing physical copy of Steam.exe into game's root. Only takes a minute to create and deploy - with the appropriate Mod Type (engine Injector).

I'd also suggest not using Steam's default install path in C:/Program Files and instead choose your own custom path on C:/ that isn't "protected". Then your default game install path on C:/ will never need to be moved, in order to have basic permission to modify your own files vs some random tool that edits your registry and forces a secondary drive on the primary drive Steam already "owns".

Edited July 14 by vortexposer

[lynx64]

23 hours ago, vortexposer said:

Did my own research on this a few years back and determined cause is due to using a secondary installation drive vs the drive that Steam is actually installed to. E.g. C:/Steam/* with game installed to D:/SteamLibrary/*. 

The fix is to install game (Oblivion, Fallout3/NV) onto same drive as Steam's installation or move Steam's install to whichever drive is being used for install... alternatively, there's an older workaround which involves copying Steam.exe and placing its physical clone into the root folder of Fallout New Vegas. I've since remedied my own situation but if you're wanting to try the workaround "fix", I'd recommend creating as new (custom) user mod that packages the Steam.exe as its own mod, which then deploys from Vortex Staging vs manually installing physical copy of Steam.exe into game's root. Only takes a minute to create and deploy - with the appropriate Mod Type (engine Injector).

I'd also suggest not using Steam's default install path in C:/Program Files and instead choose your own custom path on C:/ that isn't "protected". Then your default game install path on C:/ will never need to be moved, in order to have basic permission to modify your own files vs some random tool that edits your registry and forces a secondary drive on the primary drive Steam already "owns".

As for the installation, both Steam and FNV are installed on the same drive (from the beginning) which is dedicated HDD. System is installed on the separate SSD. The installation path is the following:

H:\Games\Steam\steamapps\common\Fallout New Vegas enplczru

[vortexposer]

Hrm. That's contrary to my own test results, except for the Fallout New Vegas enplczru thing which I've seen before but forget the details of. Its a Steam regional thing iirc? Anyway, the common solution is what I previously referred to by adding copy of Steam.exe to your root folder. Check to confirm if that can still be applied as said "fix" for your particular case. If it doesn't then I'd have to suggest there's something wrong with how Steam is recognizing the installation as being "valid", since that seems to be the core issue for such an error.
 

Edited July 15 by vortexposer

[lynx64]

Yep, that's the version for Eastern Europe if I'm not mistaken (ENglish-PoLish-CZech-RUssian). I'll try to add exe now, thanks. Maybe this will help.

Edit: no, the mod with Steam exe didn't work unfortunately.

Edited July 15 by lynx64

[vortexposer]

You sure the mod was deployed to root correctly? Drop it in manually for a quick test to reconfirm while I try to research other possible causes.

Everything else points to running as Admin/basic stuff like not running game via Steam to generate documents or needing to reverify files, etc.

Edited July 15 by vortexposer

[lynx64]

I've tried both dropping and installation via Vortex. Nothing changed. BTW is there any log file that collects the dates of the game starts and maybe time played each session?

[vortexposer]

Uh, there's an appmanifest in steamapps that tracks some stuff but idk why that'd be relevant atm.
Does this apps error happen when running the vanilla launcher or jus when using xNVSE to launch?

Re-verify game files to clear manual edit and disable/use empty profile to test with no modification

Is possible issue is being compounded by region (language) when using mods for an english game but I've seen some reports about there being a direct connection between using nvse_loader.exe rather than falloutnv.exe while using 4GB patched.exe - which bypasses need to launch with nvse_loader.exe

Edited July 15 by vortexposer

[vortexposer]

If Vortex extension installed xNVSE, de-select its "Primary" status in tools bar on Dashboard tab to allow falloutnv.exe to be default launcher.

Edited July 16 by vortexposer

[lynx64]

22 hours ago, vortexposer said:

If Vortex extension installed xNVSE, de-select its "Primary" status in tools bar on Dashboard tab to allow standard falloutnv.exe to be default launcher.

Unfortunately it didn't help. I'll try to uninstall the whole Steam and reinstall it. Because after recent reinstall of OS I left the Steam untouched and just continued to use it.