Jump to content

Return to Piriform.com

Winapp2.ini additions


  • Please log in to reply
3202 replies to this topic

#3201 OFFLINE   Andavari

Andavari

    .

  • Moderators
  • 15,118 posts
  • Gender:Male
  • Location:U.S.A.

Posted Yesterday, 07:30 AM

View Postsiliconman01, on 19 June 2013 - 01:57 AM, said:

I strongly recommend that the entry Windows SCM Logs* be removed from WinApp2.ini because it causes the Event ID 114 failure in the system Task Scheduler as described above.

Good find, and all because of logs.

Hopefully Piriform also looks at your post and makes certain no future version of CCleaner ever touches them "out-of-the-box".
Piriform software help documentation is available at:
http://www.piriform.com/docs

#3202 OFFLINE   Nergal

Nergal

    Volunteer CCleaner Demon/Post Meddler

  • Moderators
  • 5,291 posts
  • Gender:Male
  • Location:Get off my Lawn, y'darn kids!
  • Interests:being grumpier
    Laughing
    Crying
    Sleep comes Later though.

Posted Yesterday, 09:33 AM

thanks for the catch siliconman01
ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION
DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.
Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)
ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.
CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT www.piriform.com/docs
Link to Winapp2.ini explanation

#3203 ONLINE   Winapp2.ini

Winapp2.ini

    Friendly neighborhood addon manager

  • Beta Testers
  • PipPipPipPipPip
  • 4,826 posts
  • Gender:Male
  • Location:Long Island, New York
  • Interests:Sleeping

Posted Yesterday, 01:25 PM

Thanks! These are the things that always get me - entries i run and test but have effects on other things I don't make use of (so I don't run into the problem!)

I'll remove it in the next iteration.