Jump to content
Piriform Community Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About APMichael

  • Rank
    Power Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1,705 profile views
  1. Winapp2.ini additions

    @CSGalloway @siliconman01 @Nergal Thanks for the tip. Sometimes it can be easier than you think.
  2. Winapp2.ini additions

    Unfortunately, I don't know how to do this trick either. (The winapp1.ini file would definitely need a cleanup and more maintenance...)
  3. Winapp2.ini additions

    Sure, I will add it. Ok, sorry, I didn't know that, because I have a non-English Windows and always remove all pre-installed apps.
  4. Winapp2.ini additions

    I would suggest that we rename the existing entry [News *] to [Bing News *] and add DetectOS=6.2|6.3 (as with the other Bing entries). And rename your new entry [Microsoft News *] to [News *]. We should then add DetectOS=6.2|6.3 to the existing entry [Microsoft Reader *].
  5. Ok, thanks for your reply. Then Piriform has to look at it.
  6. Do you use a file for extended cleaning, like the file "winapp2.ini"? What is the version number of your CCleaner and Chrome?
  7. Winapp2.ini additions

    Many thanks for all revised and new entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/fb71a172c8873be292f166e6be9f921f100096e5
  8. Winapp2.ini additions

    Thank you very much for all your replies and entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/26cd94044d952b62d0782a06c86eaf6f6d22eeb2
  9. Winapp2.ini additions

    No, why should we? You obviously did not read what siliconman01 and I wrote: If the current entry is used without "Windows Safe Mode", it BREAKS the "Windows Search". And that is the big difference to the entries you mentioned! Because the other entries do not break anything! The reason why we will remove the FileKeys is not that CCleaner cannot delete these files or that "Windows Safe Mode" is needed for a complete cleaning, they are removed because they BREAK a function. When an entry or key breaks a function, it is removed, that was always the policy. So please calm down and do not take such things personally. By the way, there were many entries that were removed only on your request, while other people still liked the entries... Right, the rest of us are not working hard at it at all. Thank you so much for your appreciation. As long as CCleaner is not able to remove locked files, a few entries will not work as in other cleaner programs that have this ability. Therefore, CCleaner cannot be fully compared with these programs. Yes, it may be a privacy concern in this case, but with the limited functions of a Winapp2.ini respectively CCleaner it is not possible to make a safe/harmless entry. But people who are more familiar with Winapp2.ini can still easily add their own entries. (Thanks to Winapp2ool this is now very easy.) And these people will also know how to use "Windows Safe Mode" for some of the entries.
  10. Winapp2.ini additions

    @siliconman01 Just to be safe: Is the name of the entry correct? Because there is a "Dell Mobile Connect" app and a "Dell Customer Connect" app. https://www.microsoft.com/en-us/p/dell-mobile-connect/9nx51w9gbs5t https://www.microsoft.com/en-us/p/dell-customer-connect/9nf0ggq5s6qx
  11. Winapp2.ini additions

    I enabled "Windows Sarch" again and did some tests. Now I can confirm that the current entry causes multiple "Search" errors and a rebuild of the index after a reboot. The reason for this behavior is that the .000 files are locked and CCleaner cannot delete them. The only way to avoid this problem is to use "Windows Safe Mode". But using "Windows Safe Mode" for CCleaner is not the default and we cannot force users to use it either. Since the current entry breaks "Windows Search" (if CCleaner is used as usual) and therefore always causes a rebuilding of the search index, the corresponding keys should be moved to Winapp3.ini.
  12. Winapp2.ini additions

    I just wanted to say that if [MS Search *] is supposed to be an entry that needs a reboot for a successful cleanup, why do the errors only occur after a reboot? Then the theory with the necessary reboot cannot be completely correct.
  13. Winapp2.ini additions

    Yes, this cannot be intentional, as it would also collide with the "Smart Cleaning" or "Schedule" function of CCleaner. By the way, you have the "Search" errors even though you rebooted Windows after using CCleaner, right? So a reboot didn't help...
  14. Winapp2.ini additions

    Ok, thanks for your reply. But this is a special feature of the other programs, they delete these locked files in a special phase of the boot process. I don't think you can do the same by simply rebooting Windows manually after using CCleaner. Whether Windows is rebooted manually after using CCleaner or not should not matter then, because CCleaner can't delete these files anyway, right?
  15. Winapp2.ini additions

    Can you please explain a little more? You mean that the system should be rebooted immediately after using CCleaner, right? Is the reason that Windows caches the content in the memory (RAM)? Or what else does the reboot do? Files that CCleaner can not delete are also not deleted after a reboot, right? (I ask this because I usually don't reboot after cleaning and I haven't noticed any side effects yet.) I think that's the only thing we should be judging. Are there errors due to the current entry or not? Unfortunately I have disabled Windows Search on all my systems, so I can't help here. Can someone else please tell here if the entry causes errors on their system? Thanks!