Still get problems after deep & quick care

[20LEgend]

Got a new computer and dl ASC but I find even after using both deep and quick care to find and repair problems I can scan again immediately and it still shows problems found.

[enoskype]

Hi 20LEgend, welcome to IObit Forum! :-D

 

Please give us more information about which Problems found and what shows when clicking on Show details under the # problems .

 

Cheers.

[20LEgend]

Thanks for the quick response, enoskype.

OK, just done a quick care scan and it shows 3 registry fixes (normal I assume since yesterday). Privacy Sweep 229 problems and junk files 60.23 mb.

Yesterday I could fix these, re-scanned and it still listed mb's of junk files and loads of privacy sweep problems even though I did nothing in-between.

[enoskype]

Please supply us the screenshot of your settings of Junk files clean and Privacy sweep. Also screenshots of found details will help if there is a glitch.

 

Cheers.

[Toppack]

You say you "did nothing", but what programs did you have running in background,

that access the Internet, during that time ?

(Such as software updates, Internet server access, etc.)

[20LEgend]

I have attached 3 screenshots. 1 & 2 are the Privact sweep and junk files settings. 3 is following another scan.

[enoskype]

Thanks 20LEgend, but we need the details window screenshot (full screen, so most of the details could be seen) after clicking Show Details under the # problems and xx MB files after Scan. If you don't want some of the privacy content to be seen, you can blur some parts of it.

 

Also, Toppack's question is valid.

 

Cheeres

[20LEgend]

Sorry guys, tried a couple of different progs to grab screenshots but they all upload too small on here.

[captainron]

Sorry guys, tried a couple of different progs to grab screenshots but they all upload too small on here.

 

 

They need shots of the window showing the actual details of scan results..

 

Click the orange details links after a scan and copy and paste the logs inside code tags in a post here.

 

It's likely a result of file permissions or processes being active and using the files.