Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About kxkvi

  • Rank

Profile Information

  • Gender
  • Location
    Wisconsin, USA
  • Interests
    Amateur radio, shortwave listening, space science, telecommunications, music.
  1. I seem to recall that "slim" builds were posted to the web site serveral days, or in some cases as much as a couple of weeks after a new version release. It's been nearly a month since 1.44 was rolled out, and still no slim available. Is there a new policy regarding this? Enjoy the day.
  2. Technically, you may be correct, and losing my restore points may well be the price of a good drive wipe. However, in the real world, it doesn't really make much difference who is technically responsible. The sequence of events was: 1. I had system restore points. 2. I ran CCleaner 3. I had no system restore points. In this scenario, who do you think will receive the blame nearly 100% of the time? If you're out there trying to market software, it's never a good idea to "surprise" a user with an event like this. It's just considered bad form. Back in the days when I was using Jetico's product under XP, that utility at least gave me a "heads-up" about this issue. In that way, I knew what the cost was going in. Best regards.
  3. Hi guys. It's been a while since I've posted. After last night, I decided it's time again. Lately, Piriform products, namely CCleaner and Recuva, have not been working out too well for me. My OS is Windows 7 HP SP1 x64. User account control turned off. 320 GB hard disk. C: partition. NTFS. Avast AV disabled for this issue. CCleaner version 3.22. Recuva version 1.43. Last night, I decided to test CCleaner's drive wipe function. I configured it to "Wipe Free Space", including the "Wipe MFT Free Space" option. As such, I fired it up, then gave it the two hours that it required to do its job. The program reports success. Fair enough. Afterwards, just out of curiosity, I fired up Recuva to see what it could find. I let it run for 50 minutes in "deep scan" mode, and it reports that it has found some 121,000 files. This doesn't surprise me much. But then, I start paging through the results and, sure enough, right there out in the open is much of the stuff I wanted CCleaner to overwrite. This is not good news. Not only that, but apparently CCleaner has deleted all of my system restore points in the process as well. I certainly never gave CCleaner permission to do that, nor did it ever warn me that it needed to do so. I found many recoverable file types, including simple text files, and also some images. The images though, are not represented with the .jpg, .gif, or .bmp file extensions. Generally, they seem to appear with .ini or .lnk extensions. Still.. it's all just free space, right? Interestingly, when I tried to use Recuva's built-in overwrite function, it also fails to do so, simply reporting that the file was "not overwritten", with no explanation or clue as to why it's having a problem. I'm puzzled about why I'm seeing this kind of behavior. Is anyone else experiencing these kinds of issues? .
  4. Hi. I just noticed that version 1.43 has been released. I'm surprised that I'm seeing no announcement here in the forum. When was it releaseed, and where might I find the release notes? I seem to be unable to find them on the Piriform web site. Thanks much. Thomas
  5. Hi, Are you referring to the built-in update feature? I'm accustomed to doing clean installs. I remove the old version of CCleaner with Revo Uninstaller, then reinstall the updated slim version. I find that, due to some leftover Piriform registry entries, I can install using the full version as well, and do not get prompted to install the toolbar. Still, I always download the slim and portable versions, and add them to my file archive. Regards, Thomas
  6. I too enjoy the slim (and portable) versions of Piriform products. For whatever reason, the availability of the slim version always seems to be delayed for a few days. Is there a reason for this? Regards.
  7. Hi kroozer. Thanks for replying! I think you're correct. I'm convinced that it is indeed a bug, and a very serious one that needs to be addressed. Those restore points are critically important. Since I've now been hit twice by this issue, I won't be using CCleaner to delete any more points until I see that it has been addressed in future release notes. I'm glad you got a handle on it, and thanks again for taking the time to respond. Best to you! Thomas
  8. I just wanted to report two recent experiences with CCleaner, version 3.14, regarding the unwanted deletion or corruption of restore points. The first experience was on a PC running Windows 7 (no service pack) 64-bit. The hard drive was a 1 Terabyte capacity drive, with over 900 GB of free space. Simply for the purpose of testing CCleaner on Win 7, I attempted to clean up some old restore points. Initially, there were about 20 or so, and I believe I selectively deleted about half of them with CCleaner version 3.14. Prior to using CCleaner, system restore seemed to work just fine. However, after deleting those points, I found I could no longer restore the system to any previous point. On my first restore attempt, the machine blue-screened, and I had to restart the PC. On a second attempt, Win 7 simply reported that it was unable to restore to the previous points. I created a fresh restore point, and subsequently was able to use it without any difficulty. No other issues have occured on that machine since that date, which was about 2 weeks ago. The second experience was on a machine running Windows XP Pro SP3, 32-bit. The main hard drive is an 80 GB capacity drive with about 30 GB free on a 40 GB primary system partition. On that date, I noticed that my drive images were running a little heavy, size wise, so I did some housecleaning to lighten things up. Included in that housekeeping was the selective deletion of about 6 unneeded restore points, with about 4 remaining, again with CCleaner 3.14. On my second attempt to image the system, I noticed that it now was running a little on the light side. I fired up Treeview Pro to investigate, and looked at the various folder sizes on the C: drive. System Volume Information was reporting 0 Bytes of disk usage. I went into System Restore and confirmed this to be true; all of the restore points had been wiped from the drive. I also accessed System Volume Information to verify this, and all of the usual restore point folders were gone. If anyone else has experienced these sorts of issues, I would appreciate hearing about it. Both of these experiences have taught me, the hard way, that the restore points are best left alone and undisturbed, at least for now. Regards, Thomas
  • Create New...