|
Problem description: Ever since I upgraded from Windows 8.1 to 10 last summer, I occasionally get a notification (i.e. one of the the native ones) that says "Removable disk (G:) Select to choose what happens with removable drives." This happens whenever I wake up the computer, and occasionally while I'm using it (or even if it's been sitting idle for a little while). The notification used to be accompanied by an Explorer popup. Attempted fixes: I asked in the Windows 10 thread and astral suggested I change the "Hide Empty Drives" setting in Explorer. This stopped the pop-ups, but hasn't affected the notifications. nielsm suggested using Process Monitor to log what's trying to access that drive. The results are in this pastebin. Recent changes: No. -- Operating system: Windows 10 Pro System specs: Processor: core i5 2500K Motherboard: MSI P67A-G45 (MS-7673) Graphics card: GeForce GTX 460 Memory: 8 GB DDR3 Location: USA I have Googled and read the FAQ: Yes
|
#
?
Aug 17, 2016 20:42
|
|
|
|
| # ? Apr 25, 2024 02:05 |
|
|
I'd try changing the drive letter to something else if possible. That might fix it.
|
|
#
?
Aug 17, 2016 22:51
|
|
|
Ah, I might have misunderstood the advice given previously; I tried to change the letter of a flash drive to G, rather than scrolling down to G and changing its letter. I'll try that and see what happens.
|
|
#
?
Aug 17, 2016 23:19
|
|
|
I changed the drive to M and got the same notification on wake, except for drive M rather than G.
|
|
#
?
Aug 18, 2016 02:22
|
|
|
I reset Windows yesterday, and today it started in with a new message about the M drive on login: "The object invoked has disconnected from its clients". The only things I've found on Google are people having problems not actually being able to log in due to this message, but everything works just fine. Any ideas?
|
|
#
?
Aug 22, 2016 01:37
|
|
|
I ran into a similar issue, today, and there was a seating issue with the card reader that made Windows continually think that it was being added/removed. It was connected to the internal USB headers via a faulty cable. Replacing the cable made it work and there haven't been any additional craziness in about four hours time. Perhaps you have a bad cable? It could be either power or data causing the muck up, if that's the case.
|
|
#
?
Aug 28, 2016 22:53
|
|
|
Haha, I wish you'd posted this before I dusted out my computer. I'll have to try at least unplugging the card reader soon. Thanks for the idea.
|
|
#
?
Aug 29, 2016 01:58
|
|
|
hooah posted:Haha, I wish you'd posted this before I dusted out my computer. I'll have to try at least unplugging the card reader soon. Thanks for the idea. At least now you can see the cables when you pull it back apart. 
|
|
#
?
Aug 29, 2016 04:07
|
|
|
|
| # ? Apr 25, 2024 02:05 |
|
|
I unplugged the card reader and then had a brief panic when I was sent to the grub shell upon booting, even after plugging it back in. After some BIOS/UEFI mucking about, it boots fine again, but the problem persists. I guess I'll try leaving the card reader unplugged tomorrow.
|
|
#
?
Aug 30, 2016 02:54
|
|