View Single Post
  #5  
Old February 14th 17, 07:04 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default 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
Ads