Consumer Products > Avast Cleanup

Disk Doctor Gets Stuck

(1/3) > >>

Pako7:
After Updating my Cleanup I managed to use Disk Doctor to scan my Internal Drive (C:) AN It did it just well with no errors ...but the problem only raised when i tried to scan my External Harddrive 2TB harddrive it go stuck at 74% for 24 hours ..i then rebooted my computer and tried to do the fresh scan again this time it got stuck at 0% for a few hours so i decided to try again and we got stuck at 74% till now ....is there anyway i could get help

Stellarman:

--- Quote from: Pako7 on April 14, 2019, 11:47:46 AM ---After Updating my Cleanup I managed to use Disk Doctor to scan my Internal Drive (C:) AN It did it just well with no errors ...but the problem only raised when i tried to scan my External Harddrive 2TB harddrive it go stuck at 74% for 24 hours ..i then rebooted my computer and tried to do the fresh scan again this time it got stuck at 0% for a few hours so i decided to try again and we got stuck at 74% till now ....is there anyway i could get help

--- End quote ---

Hi,

I know that I already told you to send us logs regarding another problem but in order to investigate this one we would need them again.

You can simply send them by executing our log collector utility from this path C:\Program Files (x86)\AVAST Software\Avast Cleanup\tulogcollector.exe assuming that you have still Avast Cleanup installed on your computer.
Just please add your email address there so we can join the logs with your report here.

Thank you.

Pako7:
Ok il send again

Pako7:
But if I may ask ... when will the update come for the fix we requested? am just wondering

Stellarman:

--- Quote from: Pako7 on April 16, 2019, 09:25:24 AM ---But if I may ask ... when will the update come for the fix we requested? am just wondering

--- End quote ---

Hi,

good question, however we still don't know where is the problem so it is hard to estimate when the fix will be ready.
Also if I got it right your problem is already gone so you are able to use the product right?

But if we will find the root cause then the fix will be included most likely in the next version (19.2) which will come out sometimes in July.
In case the problem will appear again and prevent you from using the product we would introduce the fix earlier in some kind of Hot Fix.

Regards.

Navigation

[0] Message Index

[#] Next page

Go to full version