Jump to content
CCleaner Community Forums

siliconman01

Experienced Members
  • Content Count

    929
  • Joined

  • Last visited

Community Reputation

0 Neutral

About siliconman01

  • Rank
    Power Member
  • Birthday 10/12/1942

Profile Information

  • Gender
    Male
  • Location
    West Virginia, USA

Recent Profile Visitors

2,110 profile views
  1. Modified entry: [Syncios Cell Phone Backup & Manage *] Added Detect3 [Syncios Cell Phone Backup & Manage *] LangSecRef=3024 Detect1=HKCU\Software\Syncios Detect2=HKCU\Software\Syncios Data Transfer Detect3=HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\Syncios Data Transfer.exe FileKey1=%AppData%\app_sycnios_transfer_loader|*.*|REMOVESELF FileKey2=%AppData%\Syncios|android.log;log.txt FileKey3=%AppData%\Syncios Data Transfer|*.log|RECURSE FileKey4=%AppData%\Syncios Data Transfer\GPUCache|*.* FileKey5=%Documents%\Syncios Data Transfer|preference_conf.ini.old.bak FileKey6=%SystemDrive%\temp|*.*|REMOVESELF
  2. Visual Studio 2015/2017/2019 C++ Redistributable has been updated to 14.26.28720.3 https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
  3. JFI for those users of Winapp2ool.exe (beta version 1.4.7441.15296), VirusTotal is showing 6 engines detecting the tool as infected. In my case, I use Bitdefender Internet Security 2020 and it is tagging the tool as Gen.Variant.Razy.675528. I submitted the file to Bitdefender on 29-May and thus far there has been no FP correction.
  4. Modified Entry: [Bitdefender *] Added FileKey2 [Bitdefender *] LangSecRef=3024 Detect1=HKLM\Software\Bitdefender\Bitdefender Internet Security Detect2=HKLM\Software\Bitdefender\Bitdefender Total Security Detect3=HKLM\Software\Bitdefender\Bitdefender Total Security 2015 Detect4=HKLM\Software\Softwin\Bitdefender Antivirus FileKey1=%AppData%\Bitdefender\Desktop\profiles\Logs\*|*.xml FileKey2=%CommonAppData%\Bitdefender\DTrace|*.log FileKey3=%ProgramFiles%\Softwin\Bitdefender*\Logs|*.* FileKey4=%SystemDrive%|bdlog.txt
  5. Okay, I have 1.4.7427.18862 on all my systems and it does not get flagged via VirusTotal. HitManPro is no longer flagging it either. Be interesting to see what KIS 2020 does the next time you issue a new Beta and Winapp2ool.exe beta attempts to upgrade automatically
  6. No, the one I get from the Beta download URL is 1.4.7427.18038.
  7. VirusTotal is showing Kaspersky and ZoneAlarm flagging Winapp2ool.exe as a trojan.
  8. Also, please keep in mind that Kaspersky and HitmanPro continue to flag these new betas as VHO:Trojan.Win32.Sdum.gen. (false positive needs fixed before a new public release of Winapp2ool.exe). Kaspersky even blocks a VirusTotal submission as a malicious website.
  9. I'm not seeing that behavior either on Beta version 1.4.7427.18038. It seems to be working okay [Trim] TrimFile1_Name=winapp2.ini TrimFile1_Dir=C:\Program Files\CCleaner TrimFile2_Name=whitelist.ini TrimFile2_Dir=C:\Program Files\CCleaner TrimFile3_Name=winapp2.ini TrimFile3_Dir=C:\Program Files\CCleaner TrimFile4_Name=blacklist.ini TrimFile4_Dir=C:\Program Files\CCleaner DownloadFileToTrim=False UseWhiteList=True useBlackList=True ModuleSettingsChanged=True
  10. Winapp2ool.exe v1.4.7426.15696 does not save the useblacklist=TRUE status in winapp2ool.ini when using both a Whitelist and Blacklist in the CCleaner folder. [Trim] MergeFile1_Name=winapp2.ini MergeFile1_Dir=C:\Program Files\CCleaner MergeFile3_Name=winapp2.ini MergeFile3_Dir=C:\Program Files\CCleaner DownloadFileToTrim=False ModuleSettingsChanged=True TrimFile1_Name=whitelist.ini TrimFile1_Dir=C:\Program Files\CCleaner TrimFile2_Name=whitelist.ini TrimFile2_Dir=C:\Program Files\CCleaner TrimFile3_Name=winapp2.ini TrimFile3_Dir=C:\Program Files\CCleaner TrimFile4_Name=blacklist.ini TrimFile4_Dir=C:\Program Files\CCleaner UseWhiteList=True useBlackList=False UPDATE: If UseWhiteList=True and useBlacklist=True at the same time, a TRIM removes all of the Winapp2.ini entries and leaves only the Whitelist entries....weird.
  11. I have a Whitelist.ini and Blacklist.ini in my CCleaner folder. Using Winapp2ool.exe v1.4.7426.15696, the Whitelist.ini and Blacklist.ini appear to be honored.
  12. Is the beta version 1.4.7426.13493 ??
  13. Apparently, Kaspersky uses the Build and Version number of Windows 10 to issue corrections on False Positives. Kaspersky has not caught up with the latest Insider Build 19619.1000 Version 2004 and is continuing to flag Winapp2ool.exe on my Insider test computer.
  14. HitManPro also detects the Trojan as long as Kaspersky is falsely detecting it. UPDATE as of 01-May-2020 04:30 am EDT. It appears that Kaspersky has corrected the false positive. Both KIS 2020 and HitmanPro now scan clear.
  15. KIS 2020 suddenly started quarantining V1.4.7419.18289 of Winapp2ool.exe Had to add to KIS 2020 exclusions. KIS 2020 blocks it as VHO:Trojan.Win32.Sdum.gen
×
×
  • Create New...