In that (possible?) case - Avast overlapped with ChkDsk or something, preventing tha ChkDsk to run. Supposed answer: Avast files itself were maybe damaged due to the bad clusters on that drive. Why Avast on that computer was locking the drive and preventing the ChkDsk to run - newer actually figured out. Install Avast from scratch and let it update. 3 Downloaded KB890830 1 MB Narzdzie Windows do usuwania zoliwego. Mbam was then run on that system and Mbam found NOTHING. Use Get-WUInstall to get list of available updates, next download and install it. However, when ever I attempted to schedule ChkDsk after the system restarted - ChkDsk failed to run with the exit message: this disk is locked due to unknown utility?!? The solution: run a ChkDsk utility on that drive. Hard Disk Sentinel reported vast amount of bat clusters on the hard drive. Consider the following (similar, but not identical to the author's thread) scenario (where avast had to be completely uninstalled in order to provide basic maintenance to the computer?!)Ī computer (Win7 32bit with up-to-date Avast running Ok, no viruses) was slow.
0 Comments
Leave a Reply. |