A detailed report will become available to you after the scan is complete as to see what possible error's were found and what Windows did to fix the problem. During this scan Windows will try to locate any errors and bad sections of your hard drive and will attempt to fix all the error's that it finds. This scan depending on the size and style of your hard drive could take a short period of time for a small hard drive, and or take hours if your hard drive size is large. Windows will now tell you that this scan can not be done with Windows active, it will tell you it needs to restart yourĬomputer and then it will then start the scan, select ((okay)) A final set of commands for this check will appear, click on both the "automatically fix file systems errors" and "scan for andĪttempt to recover all bad sectors", please click to accept both options.Ĩ. When that pop menu opens you should see at the top something called "error checking" ((click on that))Ħ.
Another pop menu will appear, giving you a lot of hard drive information, above, select the ((tools)) tab button.ĥ. A pop out menu will appear, select ((properties)) should be an option located at the bottom of the list.Ĥ. When open, you will see your "C" drive, that's the hard drive, ((right click)) on the hard drive icon.ģ. click on your "my computer" icon or click on your "my computer" through your Windows start menu.Ģ. If you don't feel like replacing your hard drive, I would then recommend you conduct a disk check, the point & click way of doing this would be.ġ. It was then proven that those clients had damaged and dieing hard drives, I replaced those, and at a later time the client would do virus scans without any problems. There scan would stop all of a sudden and would continue to do so almost always at a particular file. I've had a couple of my clients have similar problems in the past with other antivirus company's.
I'm having a funny feeling that where the C:WINDOWS/system32/com/mtsadmin.tlb is being stored on your hard drive, that section of hard drive may be damaged some how. I don't know if this will help, but to me it almost sounds like with the scan stopping at C:WINDOWS/system32/com/mtsadmin.tlb is more a coincidence than anything else.
0 kommentar(er)
