It sounds like the windows registry has been corrupted. It's possible a windows update may repair the damage.
If that doesn't help, let me know, and I will come up with some more idea's.
Rik from RCE
Nearly a Posting Maven
2,335 posts since May 2009
Reputation Points: 127
Solved Threads: 199
xetwnk.... check to see if in the root of each drive there is a file called autorun.inf. If there is please drag one into a notepad, zip it and attach to your next post [use the Go Advanced button]. Then delete each autorun.inf file that you find in the root of any drive. Tell us if they stay deleted ie are not recreated, say, at a fresh startup.
gerbil
Industrious Poster
4,206 posts since May 2005
Reputation Points: 239
Solved Threads: 300
Do you have your windows install cd?
If so, Start, Run, type sfc\ scannow press enter.
You will need a full windows cd in the drive, not a recovery cd for this.
Rik from RCE
Nearly a Posting Maven
2,335 posts since May 2009
Reputation Points: 127
Solved Threads: 199
Oops, it should be sfc/ scannow. Note that there is a space between / and scannow.
The scan should be able to tell the difference between an updated file and an altered or corrupted file.
Rik from RCE
Nearly a Posting Maven
2,335 posts since May 2009
Reputation Points: 127
Solved Threads: 199
you should do what godsp3ed suggested in post #4
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
sfc /scannow performs as per the behaviour you noted. There is no fanfare when it closes, no logfile, it does its job and that is it. Windows File Protection system [which is what this is] takes file version information from protected files, checks for the existence of updates via the Windows\$hf_mig$ folder and then uses that info to replace any corrupted or missing files. So, no, your Windows Updates are not affected. Re the lack of cd activity, you may have a [hidden] i386 folder which is pointed to in registry as the source of valid files, while updated versions are kept iin that $hf_mig$ folder.
And yes, autorun.inf may be hidden; godspeed's del cmd will work if it is.
gerbil
Industrious Poster
4,206 posts since May 2005
Reputation Points: 239
Solved Threads: 300
Um... always reboot after doing sys file work, because the files that are already in memory won't be affected until they are reread.
Just in case malware did this [some do, because it is a lazy way of getting your files to execute], run MBAM, It finds various of the malwares that exhibit this behaviour:
==Please download Malwarebytes' Anti-Malware
from: http://www.majorgeeks.com/Malwarebytes_Anti-Malware_d5756.html
or: http://www.besttechie.net/tools/mbam-setup.exe
=Dclick that file, mbam-setup.exe, to install the application,
-ensure that it is set to update and start, else start it via the icon, and UPDATE it.
Select "Perform QUICK Scan", then click Scan; the application will guide you through the remaining steps.
ENSURE that EVERYTHING found has a CHECKMARK against it, then click Remove Selected.
If malware has been found [and removed] MBAM will automatically produce a log for you when it completes... do not click the Save Logfile button.
Examine the log: if some files are listed as Delete on Reboot then restart your machine before continuing.
Copy and post that log [it is also saved under Logs tab in MBAM].
gerbil
Industrious Poster
4,206 posts since May 2005
Reputation Points: 239
Solved Threads: 300
Swapping HDD circuit boards never works!
Rik from RCE
Nearly a Posting Maven
2,335 posts since May 2009
Reputation Points: 127
Solved Threads: 199