Jump to content
CCleaner Community Forums

wraithdu

Experienced Members
  • Content Count

    20
  • Joined

  • Last visited

Everything posted by wraithdu

  1. Win7 x64 Ultimate I have one desktop PC where this function is not working. I've investigated as far as I can - the scheduled task exists, when it runs I can see CCleaner64.exe spawn in Task Manager, but it then closes after a second and the main window never appears. The status of the task changes from 'Ready' to 'Running', but it gets stuck on 'Running' forever until either I log out or restart the PC. I cannot manually end the task either, it remains in the 'Running' state, event though there aren't any ccleaner processes in Task Manager anymore. If I disable SkipUAC by deleting the tas
  2. While I understand the support-for-beta mentality, Firefox is hugely popular with many users of the 4.0 betas. It's not planned to hit stable until January 2011 at the earliest. Considering the development cycle and user base of FFb4, I think it's worth supporting. Besides, beta 7 is a feature/API freeze milestone according to Mozilla: https://wiki.mozilla.org/Firefox/4/Beta
  3. I'm a long time CCleaner user, running 3.00.1310. Since upgrading to FF 4.0b7, the list of cookies is always empty for me. I'm guessing FF changed something in the database format? This is happening on two computers for me, both running Win7 x64. Can anyone else confirm please?
  4. I see my suggestion made it into the new release, nice
  5. I've always missed having some sort of notification from CCleaner when running from the Recycle Bin context menu (CCleaner.exe /AUTO). So I wrote a little AutoIt script that pops up some tray tips that let you know CCleaner in running, and when it's finished. No more checking the Task Manager for me! If anyone is interested, or if I'm even allowed to, I can post a link for it. I used the CCleaner icon from the program. If that's a license problem, I can compile a version without it.
  6. Is 2.0 not able to be made portable, or is it natively portable (that would be cool)?
  7. Can this be accomplished yet with CCleanerPortable? Last discussion I found by searching was 2 years ago. If CCleaner can't do it, are there any other portable cleaners that can? Of most importance would be management of Cookies so I can keep a whitelist.
  8. A bit off topic, but you can make custom entries in winapp2.ini that point to folders and can use wildcards to select specific files. Just make sure to save your entries before updating the file. See the user's guide.
  9. I think I may have found what's causing the problem. There seem to be some special security permissions applied to the PREFETCH folder. Under these permissions: 1. User (even Administrator) may delete *.pf files 2. User MAY NOT securely wipe them. I tried at least 4 different programs and all failed. I did however find a workaround. You can use psexec from the Sysinternals PsTools suite to launch CCleaner in the SYSTEM account. CCleaner now has full access to delete/wipe whatever it wants. Note that to accomplish this, you must have administrative privileges in order to use ps
  10. I think the bug I read about somewhere before still exists. I'm using CCleaner v1.40.520 on WinXP Pro and nothing in the prefetch folder is being deleted when I use any of the "Secure Delete" options. If I switch to regular deletion, everything works fine. This holds true using - 1. Delete old prefetch data checkbox 2. Prefetch folder added to custom folders 3. Prefetch added to winapp2.ini Does anyone know if this bug will be fixed in the next version?
  11. It seems the problem is fixed. However I noticed that there are 4 index.dat files that no longer show up in the list of files to be deleted - Documents and Settings\%username%\Cookies\ Documents and Settings\%username%\UserData\ Documents and Settings\%username%\Application Data\Microsoft\Office\Recent\ Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Feeds Cache\ Should these be deleted, or are they handled differently now in relation to cookie handling?
  12. Well, seems I was wrong. However I noticed that there are 4 index.dat files that no longer show up in the list of files to be deleted - Documents and Settings\%username%\Cookies\ Documents and Settings\%username%\UserData\ Documents and Settings\%username%\Application Data\Microsoft\Office\Recent\ Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Feeds Cache\ Should these be deleted, or are they handled differently now in relation to cookie handling?
  13. I also downloaded without a problem. I can also confirm that the index.dat file and cookie handling issue in IE7 still exists in this version.
  14. :bump Plus a few more: - When you use Run CCleaner from the Recycle bin, have it show a small window with a progress bar. - Ability to enable/disable/edit Startup entries - Ability to change Startup entries from HKLM to HKCU and vice versa - Ability to view/edit Uninstall strings That's all I can think of at the moment.
  15. Yes, the recently-used programs still appear in the Start Menu. But they are not gone after opening the menu several times. After the second run of CCleaner, the list is there the first time I open the Start Menu, then they are gone. If I open the actual program, analyze, clean, then analyze again. It will usally find about 4 desktop.ini files the second time. Clean again, analyze, then it finds nothing.
  16. Running WinXP SP2 here at work. I have to run CCleaner twice to clear the User Assist History. It won't seem to do it on the first run (program is launched from the "Run CCleaner..." option on the Recycle Bin right-click menu). No big deal, but any ideas?
  17. What OS are you running? The $hf_mig$ folder is specific to WinXP SP2 and Windows Server 2003. Previous to SP2 the folder is called %windir%\$xpsp1hfm$\ I believe.
  18. I suppose I should have mentioned it in the first post, but when I hit the Analyze button to see what CCleaner will delete, it lists all the KB###### folders inside my $hf_mig$ folder. As we mentioned, it should not touch these. I noticed this in particular because I have already removed the %windir%\$NTUninstall* folders from my computer (the uninstall folders). As far as removing the uninstallers (%windir%\$NTUninstall* folders) breaking future updates as GreenWhite mentions, this is not the case. These folders as safe to delete, as MS says also. It is the $hf_mig$ folder that
  19. That's my point. The files in the $hf_mig$ folder are not the uninstallers. Windows uses them for more than that - as a file version comparison when installing newly released hotfixes. The uninstall files are in the %windir%\$NTUninstall* folders. Read my whole post, the explanation is in there as well as the Microsoft link. Deleting files out of the $hf_mig$ folder will break future (future being the operative word here) hotfix installations. I'm not trying to give you a hard time, please understand. I really like this program. I'm just trying to save people from problems
  20. CeeCee is right. DO NOT DELETE the folder $hf_mig$ or anything in it. This is a serious mistake in CCleaner (which is otherwise an awesome program that I use, expect for the Hotfix Cleaner). Here's the Microsoft page - http://support.microsoft.com/kb/824994 and the relevant excerpt - ---------- When a security update, critical update, update, update rollup, driver, or feature pack installs GDR version files, the hotfix files are also copied to the %windir%\$hf_mig$ folder. This supports migration to the appropriate files if you later install a hotfix or service pack that includ
×
×
  • Create New...