6 replies to this topic

[Giantjay]

constantly getting error code 1392 is it time to uninstall vortex? Never used to have this problem and there's NOTHING WRONG WITH MY UP TO DATE DISCS AND THERES NO ANTI VURUS EFFECTING IT

[HeyYou]

Open an elevated command prompt. Type in:

 

sfc /scannow

 

Let it complete. If it finds and fixes files, run it again, until is doesn't find any more. Reboot. See if Vortex works now.

[Giantjay]

thanks for answer it says I must be administrator  so ive done this lets see what it says

Edited by Giantjay, 18 March 2023 - 05:47 pm.

[Giantjay]

Beginning verification phase of system scan.

Verification 100% complete.

 

Windows Resource Protection did not find any integrity violations.

 

C:\WINDOWS\system32> is my answer

[HeyYou]

Hhhmmm... The 1392 error generally implies file corruption... I am not entirely sure Vortex subscribes to the same definition. Try and start vortex, let it fail, then check event viewer, and see what it has to say.

[Giantjay]

yes this happens every so often  it first started with saying things like mods not in the correct staging folder and many things like that which were incorrect been having terrible issues with messages popping up on mods such as uv tweaks and rustic clothing deleting these completly and re installing fixed the issue apart from uv tweaks I also get disc checking when starting up despite shutting down correctly its a very strange new problem currently modding using vortex is the most unstable I've ever known it to be since all the Anniversery updates especially problems with enb's its a very trying but interesting time. I think I'll get windows to go into diskchecking and let that run the whole way through that should temporarily solve the isse thank you for your quick response it wont be forgotten. I'll post any future  event checkers on here 

[HeyYou]

If you have windows do the disk check on reboot, it really doesn't tell you anything... It runs thru it, then starts windows. Bring the machine up in the 'recovery mode'.... Click on the start button, then hold the Shift key while clicking on 'restart'. Bring the machine up with command prompt only, run chkdsk from there, and you will actually be able to read if it finds anything odd. Prolly wouldn't hurt to run SFC after that as well.