Persistent crashing with Vortex when doing one type of thing...different from rest of posts

[BlueBearOne]

As far as I can tell, the other requests for help seem a little different. My problem actually has a workaround although it can be a nightmare when multiple small dependencies are involved.

 

Using Win 10, fully updated.

 

Whenever Vortex has to reference anything outside of itself via windows file explorer, it crashes to desktop. Period. Doesn't matter what game, what mod, etc etc. I've noticed this behavior doing the following:

1. Changing the deployment directory to match the same hard drive on which the game is installed (no, the mods are not going into the vortex directory nor the actual game directory).

solution: Hit accept QUICKLY before crash and it will be there when you open it back up, otherwise, you have to do it again (yes, this lends to infinite crashes without progress if you don't hit the "accept" button (or whatever) quickly).

2. Installing a mod from a zip file

solution: Find it on the hard drive, hit install QUICKLY (or else same crash / loop problem). Let it crash. Reopen. Go to downloads and hit install.

3. Basically anything that involves going outside of Vortex and searching for a file or a file location bombs it. But you can pick up wherever your WOULD have kept going if it hadn't crashed AS LONG AS you get to your target and hit accept in vortex fast. Otherwise you are stuck in the afore mentioned rinse and repeat loop without progress.

 

Again...independent of mod, game, profile, etc etc. It is global across Vortex. Latest Windows, Latest drivers, using chrome.

 

I *do* have the professional MS Office Business services via microsoft (sharepoint, office, etc etc). Not sure if this would have anything to do with it or not. None of it is active when this is happening.

 

Hope this helps and thanks!

[Pickysaurus]

Could be a security app of some sort? Basically when Vortex is talking to the OS it's using the standard Windows API provided to all apps. Something in your setup may be blocking that access (to the point where Vortex can't even report the error, it just gets terminated) or there's something really wrong with your Windows/Vortex install.

[rmm200]

I would suggest running hardware diagnostics on both the computer and the disk drive.

That could at least eliminate a hardware cause.

Follow up with "sfc /scannow".

(To me - it sounds like hardware. Vortex has a lot of users - and I have never seen this problem before.)

[BlueBearOne]

You guys are likely correct! I ran that command and got this message back.

 

"Windows Resource Protection found corrupt files and successfully repaired them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag."

I have no idea what you had me do but evidently I needed it ;) lol. Thanks and well done. I'll let you know if the problem persists. Thanks again!

[rmm200]

:happy: