If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan and fix myspecific USB flash drives?
I always tell Windows to eject my USB flash drives before physically
pulling them out. When I do a scan, it finds no problems. Thank you in advance. -- "It is said that the lonely eagle flies to the mountain peaks while the lowly ant crawls the ground, but cannot the soul of the ant soar as high as the eagle?" --unknown Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly. /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ / If crediting, then use Ant nickname and AQFL URL/link. ( ) Axe ANT from its address if e-mailing privately. |
Ads |
#2
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan andfix my specific USB flash drives?
On 2017-02-12 13:17, Ant wrote:
I always tell Windows to eject my USB flash drives before physically pulling them out. When I do a scan, it finds no problems. Thank you in advance. I had the same problem on some drive, Windows always wanted to do a scan, and never found anything. I junked it and got another pen drive, problem solved... -- ! _\|/_ Sylvain / ! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society oO-( )-Oo After Tuesday the calendar says: "WTF" |
#3
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan and fix my specific USB flash drives?
"Ant" wrote
|I always tell Windows to eject my USB flash drives before physically | pulling them out. When I do a scan, it finds no problems. | That drives me crazy, too, and I keep meaning to fix it, but haven't got around to dealing with it. I actually get two idiotic messages. One asks me what I want Explorer to do. The other suggests a scan. They always come back, regardless of how I respond. This might help: https://technet.microsoft.com/en-us/.../cc938275.aspx That seems to be the solution on XP. NoDriveTypeAutorun is what TweakUIXP uses to stop autorun on drives, which is a good idea for general security on removable drives and disks.** Shell Hardware Detection service can also be stopped. I haven't actually explored any of this on Win7, but if you do I'd love to hear what works. ** Here's a link to a detailed explanation of the setting. Note that the first section of this article is actually just a lot of gibberish about how to get updates that will add the setting to Group Policy Editor, but if you keep reading you'll find instructions to set it by hand down below. I'm posting the Google cache link for those who don't want to enable script at microsoft.com. MS have taken to blocking their support pages entirely unless script is allowed to run. http://webcache.googleusercontent.co...&gbv=1&ct=clnk |
#4
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan andfix my specific USB flash drives?
On 2/14/2017 6:26 AM, Mayayana wrote:
"Ant" wrote |I always tell Windows to eject my USB flash drives before physically | pulling them out. When I do a scan, it finds no problems. | That drives me crazy, too, and I keep meaning to fix it, but haven't got around to dealing with it. I actually get two idiotic messages. One asks me what I want Explorer to do. The other suggests a scan. They always come back, regardless of how I respond. This might help: https://technet.microsoft.com/en-us/.../cc938275.aspx That seems to be the solution on XP. NoDriveTypeAutorun is what TweakUIXP uses to stop autorun on drives, which is a good idea for general security on removable drives and disks.** Shell Hardware Detection service can also be stopped. I haven't actually explored any of this on Win7, but if you do I'd love to hear what works. ** Here's a link to a detailed explanation of the setting. Note that the first section of this article is actually just a lot of gibberish about how to get updates that will add the setting to Group Policy Editor, but if you keep reading you'll find instructions to set it by hand down below. I'm posting the Google cache link for those who don't want to enable script at microsoft.com. MS have taken to blocking their support pages entirely unless script is allowed to run. http://webcache.googleusercontent.co...&gbv=1&ct=clnk Have you verifed that the capacity of the thumb drive matches the label? Fake flash drives might fail the OS test. |
#5
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan andfix my specific USB flash drives?
Mayayana wrote:
"Ant" wrote |I always tell Windows to eject my USB flash drives before physically | pulling them out. When I do a scan, it finds no problems. | That drives me crazy, too, and I keep meaning to fix it, but haven't got around to dealing with it. I actually get two idiotic messages. One asks me what I want Explorer to do. The other suggests a scan. They always come back, regardless of how I respond. This might help: https://technet.microsoft.com/en-us/.../cc938275.aspx That seems to be the solution on XP. NoDriveTypeAutorun is what TweakUIXP uses to stop autorun on drives, which is a good idea for general security on removable drives and disks.** Shell Hardware Detection service can also be stopped. I haven't actually explored any of this on Win7, but if you do I'd love to hear what works. ** Here's a link to a detailed explanation of the setting. Note that the first section of this article is actually just a lot of gibberish about how to get updates that will add the setting to Group Policy Editor, but if you keep reading you'll find instructions to set it by hand down below. I'm posting the Google cache link for those who don't want to enable script at microsoft.com. MS have taken to blocking their support pages entirely unless script is allowed to run. http://webcache.googleusercontent.co...&gbv=1&ct=clnk My advice would be: 1) Do a scan with the repair box ticked. 2) Review the Winlogon entry in Event Viewer which corresponds to the CHKDSK log output. In it, will be details about what argument a couple of OSes are having. I've had something involving metadata $UpCase being modified by two OSes, to suit their own personality. (Each OS does CHKDSK. Each finds an issue with $UpCase, ad infinitum.) I've also disabled things like Hibernation and System Restore, to stop behaviors like this. Salt to taste. But, at least give CHKDSK a real chance to finish. You could even do it from WinPE (boot the installer, user the Command Prompt window), to give it a good chance to work. The problem with the WinPE, is figuring out the partition labels. For key partitions, I put an empty file at the top level, as a quick way to identify them. For example, this OS would have "IMWinXP.txt" at the top level, as a tag. HTH, Paul |
#6
|
|||
|
|||
Why does Windows (e.g., 64-bit 7) always prompt me to scan and fix my specific USB flash drives?
"Paul" wrote
| 1) Do a scan with the repair box ticked. | Of course I've tried that. It doesn't matter. It always finds no problems and then wants to scan again next time. With this discussion I decided to try an experiment. I disabled Shell Hardware Detection, set NoDriveTypeAutorun to H25 and disabled autoplay in Control Panel. Then I tried two different sticks. Blissful peace. I had always assumed Shell Hardware Detection was involved with seeing plugged in drives, but it's not needed for that. It's only for autoplay, which I don't want enabled anyway. Some sources say Shell Hardware Detection is required for WIA (Windows Image Acquisition). I don't know where that idea come from. It's not listed as a dpendency and I have a script based image editor that uses WIA, which works jusyt fine with Shell Hardware Detection disabled. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|