The disk drive error is a constant warning on my PC at the moment - and I believe that it's software related - either Windows upgrades or AdAware 11.
I have regularly run CHKDSK and it finds no problems - to get rid of the annoying Action Center message - go into Action Center and turn off the drive status message!
To avoid the CHKDSK seeming to stall on 17% I suggest that you run it with the following command chkdsk /spotfix. CHKDSK is always running in the background and the spotfix command will only address any problems found by the background runs. It also has the advantage of showing a progress %age as it runs following a reboot.
I've been running AdAware since my Dell Tablet was new and had no problems, but at some point, I am assuming after an update I ran into the drive error problem. I had run check disk and let action center "fix" the problem several times with no success. I read the above post and gave uninstalling AdAware a try and voila, no hard disk problem. So in my case it must have been some conflict between Lavasoft AdAware and an update from Microsoft. I will now have to try another antivirus and see if I have the same problem.
Great Job Guys!
I have a Surface Pro Original and it's been awesome. Then started the Action Center Message and scanning every time I rebooted. Uninstalled AdAware 11 and checked for errors on the Hardrive and Memory card, and to steal from my buddy, Voila! :-) No action center message and no scanning on boot.
Thanks everyone!
-Droptini
I think it is great that some people are beginning to get the message that uninstalling Adaware may fix the problem. I would dearly love to know of a decent freeware pop-up stopper program to replace Adaware 11 (Internet Explorer in Windows 8.1 Pro just doesn't seem to do enough)..
That being said, it is obvious that in many cases a Microsoft Update is obviously conflicting with Adaware and causing the error we are all seeing, since uninstalling Adaware makes the error go away. Does no one else find it disturbing that two companies as pervasive as Microsoft and Lavasoft are either oblivious to the problem, or unwilling to talk to one another? They should be working together trying to figure out what is causing the error/conflict, not relying on us to fend for ourselves.