Getting i/o error 1392 with vortex after restarting pc

[DarkRevenence]

I am using vortex 1.4.16 on windows 10 64Ã with 16gb of ram, I have 243 mods on skyrim vr, the game works just fine and everything runs fine I have no problems other than everytime I restart my pc and load up vortex and try to deploy mods it will give me i/o error 1392 and then ii have do chkdsk my D: drive and after restarting agian vortex will deploy mods

[AugustaCalidia]

Error 1392 is a Windows error that is widely discussed on the internet along with possible solutions to the error reported. I would advise you to do a search, if you have not done so already. Hopefully that will help you identify precisely what the source of the error is.

 

Does the error message include any details other than simply reporting an error? If so, it would be helpful to copy the entire message into your post.

[Tannin42]

First of all: Please understand that windows error codes come from the OS. Vortex doesn't come up with them, it tries to do something, that operation fails on the OS level, the error code is the explanation from windows _why_ it failed.

So these errors never happen when everything is ok.

 

In this case, here's the official description of the error code:

 

ERROR_FILE_CORRUPT 1392 (0x570)

The file or directory is corrupted and unreadable.

 

 

chkdsk is a good call for this kind of error but the fact you have to call it repeatedly would indicate it's not a fluke but something is causing this. Filesystem corruption would happen due to hardware issues (could be a defect in the drive or cables or power outage or the drive doesn't receive enough power in general) or driver-level issues - though nowadays drivers are shipped with windows and are well tested. You'd have to be doing something "unusual", e.g. using a virtual drive (something like truecrypt) and then not dismount the virtual drive correctly before the system gets powered off.

[DarkRevenence]

It only happens with vortex and it is vortex that gives me that error, it will say that it can't find a specific file until I chkdsk and restart then it works just fine

[Guest deleted34304850]

it isn't vortex giving you the error. as explained clearly above the error comes from the operating system.

then you execute chkdsk and the problem goes away....tells you that the issue is resolved (temporarily by chkdsk).

is the drive in question some sort of external drive? you've neglected to answer that, and it would help. if its not an external disk, then you've got a serious issue that you need to resolve that may result in you having to buy a new disk.