dbjes

Look, this is one explanation, that might be true. But if it is so, then CCleaner people must specify it explicitly. Let's see how it does tomorrow. In any case, what will be the limt definition? Of course, you would say depends on what you/I are doing. Sounds swallowable? Not to my mind.

It returns repeatedly to the check disk feature from any config chosen. I take it to the shop tomorrow. In any case, I demand, no less, an explanation from Piriform. We'll go from there. I'll keep posting. I work from home, and i'm lucky for the laptop. 1st time after installing a sftwr in many many years that something like this happens to me. And sftwrs I installed, believe you me.

I clicked F8 on reboot and chose Last known good config. Hold fingers.

AMD, Win 7 Home Premium, C and D disks. But The q is HOW could it happen, when the promise was that ONLY FRRE SPACE will be deleted? I double checked it when making the click.

I know it sounds terrible, but this is exactly what happened. I made a free space erasure and only this, and now the comp reboots and checks disks over and over again without ability to reboot really. I have to say thhat i know my way around comps, so this would not be a problem here. Anyone can help? Thanks, D B