Drive not accessible after x seconds timeout device error


  1. Posts : 10
    Windows 10
       #1

    Drive not accessible after x seconds timeout device error


    Drive not accessible after x seconds timeout device error-k-not-accessible.png

    Ever since the drive went into the red (almost full warning), the first time I try to open it in a while, the error shows, but never after I dismiss the error and click the drive again.

    Drive not accessible after x seconds timeout device error-k-drive-almost-full.png

    BEFORE REPLYING: Please read the whole post. It may not be what you think. Thanks.

    I have another drive that is in the red too, but it only sometimes gives the error, but afterword and otherwise behaves fine. The K drive is one of those green drives however, where it goes to sleep or something after a while, then takes longer to spin up than a normal drive. I used to not use it often, now I've been using it multiple times per week doing disc backups. The other drive is just a normal drive (both are connected through USB).

    It appears that Explorer just gives up prematurely and pops up the error while just waiting and scanning whatever crap it thinks it needs to make my "navigation experience" faster... :facepalm: It can still do that with a longer timeout... but it just needs to give it a few more seconds I think.

    I've already scanned the drives for issues, and no problems were found. I don't think there's a problem with the drives, I think Windows 10 is just prematurely error-popping...

    I'd like to increase the time it waits before showing this nonsense generic error, or find out EXACTLY why it's erroring (I'm not sure where to check). Regardless, I'm OK waiting a few more seconds rather than adding multiple clicks each time I try access these two drives for the day.
      My Computer


  2. Posts : 10
    Windows 10
    Thread Starter
       #2

    Can somebody tell me what's going on with this? I'm not seeing how to edit the post or I'd simplify it :/

    TL;DR: The drive pops up that error when I try to open it only from the computer it's attached to when I haven't after hours or days (like the drive is put to sleep or something), but doesn't when I open it through Network.

    Something with Windows 10 when accessing sleeping or near-full drives directly attached causes the access to time out, and I get that error. The two drives it happens on, one is a "green" drive that goes to sleep every hour of not being accessed or something like that, and the other is just a normal drive like any other. Both are connected through USB. Both don't give the error when opening from another computer through the network.

    Is there somewhere to fix Windows' timeout length for this? Just something to say "just give it a few more seconds, c'mon", or do I need to clear some sort of cache or something? Or, what?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:18.
Find Us




Windows 10 Forums