up vote 5 down vote favorite
1
share [g+] share [fb]

When I reboot my Windows 7 machine, I get the error:

Autochk cannot run due to an error caused by a recently
installed software package

The only way I can get rid of it is to boot from the Windows install DVD, get into command prompt and run chkdsk. Then when I reboot from the hard disk, there is no error, however, it eventually comes back.

Any ideas?

link|improve this question
65% accept rate
In all my years, I've never seen this error before. – surfasb Jan 3 at 10:57
The relevant error message will actually be on the line above that one. – JdeBP Jan 3 at 10:59
feedback

3 Answers

up vote 0 down vote

Hello i had this problem too... it is related to a corrupted usb***.sys file.

Check your recently installed software first and hardware... memory, hdd...

FIX: Boot from the Windows install DVD, get into command prompt and run "chkdsk X: /F" where X is the driver you have your system on.

link|improve this answer
That does solve the problem temporarily but then it comes back again eventually. – JoelFan Jun 6 '10 at 12:59
If the usb**.sys is a file from Microsoft, then you can fix it with sfc /scannow when you have booted the system and go into the console. If it is not, then you should update the related drivers to the latest versions. @JoelFan: Please note that your problem could be unrelated with the mentioned file. – Tom Wijsman Jul 17 '10 at 23:32
feedback
up vote 0 down vote

Use AutoRuns, look for the AutoChk line and disable it by removing the checkmark,
have caution when you decide to remove other things to optimize your boot as you could brick your OS.

It's safe to disable AutoChk, but you should scan sometimes so you don't run into unexpected problems.

link|improve this answer
feedback
up vote 0 down vote

You might be able to prevent autochk from running with Chkntfs ant the /x

http://technet.microsoft.com/en-us/library/cc771787(WS.10).aspx

but the bigger issue is why is your drive being flagged as dirty? Is the drive starting to die maybe. try running some HDD diagnostics on it. like WD lifeguard or the Seagate equivalent.

link|improve this answer
feedback

protected by Diago Nov 25 '10 at 8:52

This question is protected to prevent "thanks!", "me too!", or spam answers by new users. To answer it, you must have earned at least 10 reputation on this site.

Not the answer you're looking for? Browse other questions tagged or ask your own question.