siliconman01
-
Posts
1,116 -
Joined
-
Last visited
Posts posted by siliconman01
-
-
Plus we are now damaging Chrome Extension when running this new Winapp2.ini
-
OOPPS! One of the most recent changes to MS Edge is removing the Favorites in the Favorites Bar
We had this problem once before when we started including some of the Edge files.
-
You may wish to include removal of the *.chk files and other V01*.log files for Edge as well
-
On 9/22/2018 at 21:03, SMalik said:
Revised Entry
Added: %CommonAppData%\Microsoft\Windows Defender\Definition Updates\Backup|*.*|RECURSE
[Windows Defender *]
LangSecRef=3024
Detect=HKLM\Software\Microsoft\Windows Defender
Default=False
FileKey1=%CommonAppData%\Microsoft\Windows Defender\Definition Updates\Backup|*.*|RECURSE
FileKey2=%CommonAppData%\Microsoft\Windows Defender\Network Inspection System\Support|*.txt
FileKey3=%CommonAppData%\Microsoft\Windows Defender\Scans|*.bin*
FileKey4=%CommonAppData%\Microsoft\Windows Defender\Scans\History\CacheManager|*.*|RECURSE
FileKey5=%CommonAppData%\Microsoft\Windows Defender\Scans\History\ReportLatency\Latency|*.*|RECURSE
FileKey6=%CommonAppData%\Microsoft\Windows Defender\Scans\History\Service|*.log
FileKey7=%CommonAppData%\Microsoft\Windows Defender\Scans\MetaStore|*.*|RECURSE
FileKey8=%CommonAppData%\Microsoft\Windows Defender\Support|*.*|RECURSEI thought it was our "policy" not to remove Backup files from security programs and the like. ??
-
On 9/23/2018 at 01:04, Nergal said:
Pretty sure the first picture are dom cookies and thus are handled by ccleaner already, and the second by sessions under edge.
You may wish to include an entry to remove *.chk files from Webcache as well.
On my Windows 10x64 Pro systems, V01.log, V01tmp.log, WebcacheV01.dat, and WebcacheV01.jfm are locked.
-
9 hours ago, SMalik said:
Revised Entry
Added: %WinDir%\Logs\waasmedic|*.*|RECURSE
https://www.thewindowsclub.com/windows-update-medic-service
[Windows Update *]
LangSecRef=3025
Detect=HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\WindowsUpdate
Default=False
FileKey1=%WinDir%\Logs\waasmedic|*.*|RECURSE
FileKey2=%WinDir%\Logs\WindowsUpdate|*.*|RECURSE
FileKey3=%WinDir%\SoftwareDistribution\DataStore\Logs|*.*|RECURSEI do believe that the %WinDir%\Logs|waasmedic folder is typically a locked folder and CCleaner will not be able to clean it unless the user "Takes Ownership" of the folder. And as you know, that ownership will return to Windows when various Windows Updates are run.
-
CCleaner v5.47.6716 download link is still pointing to CCleaner V5.46.
-
Yes, CCleaner Beta v5.47.6700 does resolve this issue. Thanks very, very much!
-
"C:\Program Files\CCleaner\CCleaner.exe" /AUTOThe command line above does not work on my systems unless I drop back to V5.43 which I have done again. Prior to V5.44, the shown command line has worked for years.
-
This is still not fixed in CCleaner 5.46.6652 for systems with Windows 10x64 Pro and most likely other versions of Windows.
-
Modified entry: [Dell Installation Files *]
Deleted DetectFile and added Detect1 and Detect2[Dell Installation Files *] LangSecRef=3024 Detect1=HKCU\Software\Dell Detect2=HKLM\Software\Dell Default=False Warning=This will delete your Dell installation files. FileKey1=%SystemDrive%\dell|*.*|REMOVESELF -
New entry: [Stocks and Futures *]
[Stocks and Futures *] LangSecRef=3031 Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\24877CutthroatSoftware.StocksandFutures_xgnzh3xnefnqe Default=False FileKey1=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\AC\INet*|*.*|RECURSE FileKey2=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\AC\Microsoft\CryptnetUrlCache\*|*.* FileKey3=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\AC\Temp|*.* FileKey4=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\AppData\Indexed DB|*.log FileKey5=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\LocalState|*.tmp|RECURSE FileKey6=%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\TempState|*.*|RECURSE ExcludeKey1=FILE|%LocalAppData%\Packages\24877CutthroatSoftware.StocksandFutures_*\AC\INetCache\|container.dat -
Modified entry: [Syncios Cell Phone Backup & Manage *]
Added FileKey3
[Syncios Cell Phone Backup & Manage *] LangSecRef=3024 Detect1=HKCU\Software\Syncios Detect2=HKCU\Software\Syncios Data Transfer Default=False FileKey1=%AppData%\Syncios|android.log;log.txt FileKey2=%AppData%\Syncios Data Transfer|*.log FileKey3=%UserProfile%\Documents\Syncios Data Transfer|preference_conf.ini.old.bak -
You should read some of the recent posts under Bug Reports here on the forum
https://forum.piriform.com/forum/8-ccleaner-bug-reporting/
If you are running Windows 10 64-bit you may wish to steer clean of V5.44 and stay on 5.43.
-
1 hour ago, Stephen Piriform said:
Hey guys,
I'm going to hazard a guess at a few things:
- Did you just update CCleaner Professional, Business or Technician Edition?
- Do you have Malwarebytes installed?
- Is the Ransomware Protection feature enabled in Malwarebytes?
- Do you have a 64-bit version of Windows?
If so, the Malwarebytes anti-ransomware feature has broken the CCleaner automatic update and also deleted the CCleaner.exe executable (leaving only CCleaner64.exe). The executable it deleted is used for certain functions of CCleaner. To resolve, please download and install https://download.ccleaner.com/pro/ccsetup544_pro.exe
1. I am running the FREE version of CCleaner
2. I have Malwarebytes 3 installed; however, I have no protection modules enabled and Malwarebytes is not running automatically. I use it only to scan my system on demand.
3. I am running Windows 10x64 Pro Build 17134.137 Version 1803.
I reverted back to CCleaner V5.43 and all is working properly. Something is broken in V5.44.6575.
-
This applies to Windows 10x64 Pro Build 17134.137 Build 1803 with CCleaner V5.44.6575 Free on 3 different PC systems.
Bug 1: The /auto command line results in CCleaner starting and then promptly closing without any cleaning performed.
Bug 2: The "Run CCleaner" context switch on the Recyle/Trash Bin results in CCleaner starting and then promptly closing without any cleaning performed
I tried completely uninstalling CCleaner and then re-installing it and this did not resolve the problem.
-
This fix at the link below worked for me too. And I run KIS 2019 V19.0.0.1088a
-
8 hours ago, Winapp2.ini said:
At this point yes, the features are mostly in their final state under the new menu system. I'll be working on creating documentation for it all soon.
On a related note, I have intention to create likely one more module that executes combinations of the other modules tasks, so simplify the tool further.
Hey, thanks for the feedback. I think I will wait a bit before I send it out. One simplification combination suggestion: One that trims the winapp2.ini file and then edits the ccleaner.ini file.
-
On 6/4/2018 at 22:21, Winapp2.ini said:
Winapp2ool has been (officially) updated to v0.85beta, existing previous versions should inform users of this.
Is the format for 0.85beta for the features included at this point pretty much as you expect to keep them? The reason for my question is that I would like to generate a "How to use" procedure for a few "not so computer savvy" friends and relatives that I help with their computers.
They are currently using the pre-Winapp2ool tools to trim their Winapp2.ini. They only use Trim and the CCinidebug tools because I do the other "stuff" prior to sending them the latest Winapp2.ini each time a new version of CCleaner is released.
TIA for your feedback.
-
5 hours ago, Winapp2.ini said:
A build of winapp2ool.exe with this fixed is available: https://github.com/MoscaDotTo/Winapp2/pull/245
It's not yet on the master as I've made significant changes to the code and want to make sure everything is still functional before pushing. Everything in my tests seemed OK though
Fix is confirmed. From what I have tested thus far, this new version appears to be working okay.
-
On 5/20/2018 at 08:28, APMichael said:
For some reason, the TRIM function of winapp2ool.exe (V0.8.0.0) does not recognize the DetectFile shown below for Chrome and it trims these all out.
DetectFile2=%LocalAppData%\Google\Chrome*
If I change this to DetectFile2=%LocalAppData%\Google\Chrome, then they are not TRIMMED out.
I wonder if CCleaner is recognizing %LocalAppData%\Google\Chrome* where it is used in FileKey and ExcludeKey. ???
-
Did you try what worked for me as posted at
-
Try setting the option as shown in the attached pic. I started having this problem when I installed Kaspersky Internet Security 2019 V19.0.0.1088(a)RC and this stopped the crashing of CCleaner 5.42.6499 when "Run Cleaner" is executed.
-
Modified entry: [Internet Explorer *]
Added: ExcludeKey1=FILE|%LocalAppData%\Microsoft\Windows\INetCache\IE\|container.dat to prevent problems with audio players gadgets such as KRIS Media Player Pro which use the IE built-in wmaplayer2 from losing the song cover picture to display.
[Internet Explorer *] LangSecRef=3022 Detect=HKCU\Software\Microsoft\Internet Explorer Default=False FileKey1=%AppData%\Microsoft\Internet Explorer\UserData|*.*|RECURSE FileKey2=%LocalAppData%\Microsoft\Windows\AppCache|*.*|RECURSE FileKey3=%LocalAppData%\Microsoft\Windows\IECompatCache|*.*|RECURSE FileKey4=%LocalAppData%\Microsoft\Windows\IECompatUaCache|*.*|RECURSE FileKey5=%LocalAppData%\Microsoft\Windows\INetCache|*.*|RECURSE FileKey6=%LocalAppData%\Microsoft\Windows\INetCookies|*.*|RECURSE FileKey7=%LocalAppData%\Packages\windows_ie_ac_*\AC\AppCache|*.*|RECURSE FileKey8=%LocalAppData%\Packages\windows_ie_ac_*\AC\INet*|*.*|RECURSE FileKey9=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\CLR_v4.0\UsageLogs|*.*|RECURSE FileKey10=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\CryptnetUrlCache\*|*.* FileKey11=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\Internet Explorer\DOMStore|*.*|RECURSE FileKey12=%LocalAppData%\Packages\windows_ie_ac_*\AC\PRICache|*.* FileKey13=%LocalAppData%\Packages\windows_ie_ac_*\AC\Temp|*.* FileKey14=%LocalAppData%\Packages\windows_ie_ac_*\LocalState\Cache|*.*|RECURSE FileKey15=%LocalAppData%\Packages\windows_ie_ac_*\LocalState\navigationHistory|*.*|RECURSE FileKey16=%LocalAppData%\Packages\windows_ie_ac_*\TempState|*.*|RECURSE FileKey17=%WinDir%\System32\config\Systemprofile\AppData\Local\Microsoft\Windows\INetCache|*.*|RECURSE RegKey1=HKCR\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\windows_ie_ac_001\Internet Explorer\DOMStorage RegKey2=HKCU\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore RegKey3=HKCU\Software\Microsoft\Internet Explorer\LowRegistry\DOMStorage RegKey4=HKCU\Software\Microsoft\Internet Explorer\Main\FeatureControl RegKey5=HKCU\Software\Microsoft\Internet Explorer\Recovery\PendingDelete RegKey6=HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Stats ExcludeKey1=FILE|%LocalAppData%\Microsoft\Windows\INetCache\IE\|container.dat ExcludeKey2=FILE|%LocalAppData%\Packages\windows_ie_ac_*\AC\INetCache\|container.dat
We had this problem once before when we started including some of the Edge files.
Winapp2.ini additions
in CCleaner
Posted
I have 4 different computers all using Chrome and also Edge on Windows 10x64 Pro Build 17134.286. ALL 4 experience the same failures on Edge and Chrome with this new Winapp2.ini.