HadToRegister Posted September 9, 2022 Share Posted September 9, 2022 This is with 1.6.7This never happened until this version of Vortex.When it reports that error, I used CHKDSK, PerfectDisk, S.M.A.R.T. and other disk checking software and they all return ZERO Errors. the only program to complain is Vortex 1.6.7I've read that "Vortex only reports what the OS is telling it", yet, the OS finds no errors, and when I run CHKDSK, the OS even tells me I don't need to run CHKDSK because the disk is fine, but I do anyway, and Windows 10 reports no errors.Just to make sure, I've run several other third party Disk Utilities and they too, report no errors, and no I/O errors, only Vortex complains. Link to comment Share on other sites More sharing options...
Pickysaurus Posted September 11, 2022 Share Posted September 11, 2022 The specific error would be helpful here. Is the path it's trying to access valid? If so, there may be something on your PC that is blocking Vortex from accessing it. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 11, 2022 Author Share Posted September 11, 2022 The specific error would be helpful here. Is the path it's trying to access valid? If so, there may be something on your PC that is blocking Vortex from accessing it. It will pop up on Vortex start after a long time of seeing the 'busy circle' spinning in PLUGINS. This time it popped up randomlyThe disk tests just fine with CHKDSK and other Disk UtilitiesThe path it's trying to access is Valid SATA D:\ internal drive. S.M.A.R.T. says the drive is fine, chkdsk says the drive is fine, other 3rd party tests say it's ok as well.This never popped up until I updated Vortex, to 1.6.7 Link to comment Share on other sites More sharing options...
Tannin42 Posted September 12, 2022 Share Posted September 12, 2022 Could you send in a feedback from after that error occurred with your log file attached? Genuinely, when errors like these happen all we get from the framework (node.js) is a numeric code that is documented as "Input/output error. Usually used for physical read or write errors." - In practice though the framework use that same code for different "similar" problems depending on context.All I can really know is that "The file doesn't exist", "The disk is full", "The file is locked by a different application" or "User has no permissions to open the file" all would have produced a different code. Hence if the log can tell us which file exactly the problem is and what exactly Vortex tried to do with it maybe I get an idea of what else could go wrong in that situation. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 12, 2022 Author Share Posted September 12, 2022 Hopefully the correct log(s) incoming Link to comment Share on other sites More sharing options...
marcusfromsweden Posted December 12, 2022 Share Posted December 12, 2022 Hi, Any news on this problem?I am also experiencing the same problem (popup), while tunning Windows 11 and Vortex version 1.6.14. Happy for Any feedback. Thanks in advace,Marcus Link to comment Share on other sites More sharing options...
DerZocker92 Posted December 13, 2022 Share Posted December 13, 2022 Same Problem here. I tried to move the staging folder for SSE to another location on my hard drive. Now I'm getting this message: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.