Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content Count

    755
  • Joined

  • Last visited

Posts posted by APMichael


  1. Thanks for the new and revised entries.

    On 21/06/2020 at 03:17, SMalik said:

    ... Added: FileKey2 and FileKey6

    [MS OneDrive *]
    LangSecRef=3021
    Detect=HKCU\Software\Microsoft\OneDrive
    FileKey1=%LocalAppData%\Microsoft\OneDrive\logs|*.*|RECURSE
    FileKey2=%LocalAppData%\Microsoft\OneDrive\logs\Common|*.*|RECURSE ...

    The new FileKey2 is already covered by FileKey1 (same path with *.*|RECURSE).

    On 21/06/2020 at 03:17, SMalik said:

    ... Added: FileKey18 thru FileKey24

    [Xbox *] ...
    FileKey18=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\Microsoft\CryptnetUrlCache\*|*.*|RECURSE
    FileKey19=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\Temp|*.*|RECURSE
    FileKey20=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\TokenBroker\Cache|*.*|RECURSE
    FileKey21=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalCache|*.*|RECURSE
    FileKey22=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalState\Cache|*.*|RECURSE
    FileKey23=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalState\DiagOutputDir|*.txt
    FileKey24=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\TempState|*.*|RECURSE ...

    "Microsoft.XboxGamingOverlay" is the separate app "Game Bar". So I updated the entry [Game Bar *] for you:

    [Game Bar *]
    DetectOS=10.0|
    LangSecRef=3031
    Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe
    FileKey1=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\INet*|*.*|RECURSE
    FileKey2=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\Microsoft\CryptnetUrlCache\*|*.*|RECURSE
    FileKey3=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\Temp|*.*|RECURSE
    FileKey4=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\AC\TokenBroker\Cache|*.*|RECURSE
    FileKey5=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalCache|*.*|RECURSE
    FileKey6=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalState\Cache|*.*|RECURSE
    FileKey7=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\LocalState\DiagOutputDir|*.txt
    FileKey8=%LocalAppData%\Packages\Microsoft.XboxGamingOverlay_*\TempState|*.*|RECURSE


  2. On 12/06/2020 at 23:07, Winapp2.ini said:

    Beta versions (and all future release versions) of winapp2ool are now digitally signed. This should help prevent things like anti virus' deleting it from your machines or browsers blocking the download

    Great news! 😃 Let's hope this helps in the long run.


  3. On 22/05/2020 at 16:17, CSGalloway said:

    ... and I wanted the entry to be padded out to the length of the wais_entries ...

     

    Sorry, but this is just a "cosmetic thing". Whether there is a 0 more or less shouldn't bother you. I just took 5 digits now, because that should be enough "forever". An adjustment to the actual number of entries would only work with more lines of code, but I don't have time for that at the moment.

     

    On 22/05/2020 at 16:17, CSGalloway said:

    ... I would just like to output the line number from the INI file before the wais_line.  Something like:

    
    ECHO nLine | !wais_line! >>"%wais_folder%\preamble.txt"

    where nLine is the line numbere from the INI file being read.

     

    Ok, I understand, but as already written, the batch script unfortunately skips blank lines and therefore the line numbers do not match those of the INI and are therefore actually useless. In addition, I still don't understand what the indication of the line numbers is supposed to help. (I can find an entry also by its name in the INI, the line numbers are not needed for this).

    Maybe you can find someone who can rewrite the batch script according to your wishes or better rewrite it in another programming language.

    (By the way, since this is rather off-topic, we should discuss possible further things via PM.)


  4. @Nergal CSGalloway's question was not directly related to Winapp2.ini, but to a batch script on GitHub.

    19 hours ago, CSGalloway said:

    i'd like some assistance in, for instance if the INI file has 1035 entries, have the first one be numbered 0001 and not 1, and so on and so on......

    Also how can I output the line number that the current line from the INI file is going to preface and not the new split INI file? ...

     

    Unfortunately, I have very little time for other things at the moment, but with a little trick I was able to insert the leading zeros quickly. You can download the updated batch script on GitHub.

    Excuse me, but I don't quite understand the line number question. Which line number should be output where exactly? And what use is the information about the line number then? Since the batch script skips all blank lines, the line numbers would not match those in Winapp2.ini anyway.

    Please keep in mind that this is only a simple batch script. Compared to a "real" programming language it has very limited functionality and performance.


  5. I am not an employee of Piriform, so this is just my humble opinion:

    Unfortunately, I have not been able to reproduce the problem on any system, neither with Office 2016 nor 2019. I also tried to reproduce the problem in a virtual machine for several days, but this was not successful either. As far as I know Piriform cannot reproduce the problem either. So how do you want to fix a bug that cannot be reproduced on your system?

    At least someone who always has this problem could help by finding out which cleaning rule is responsible for it. To find the cleaning rule, one could proceed as follows:

    - Go to "Custom Clean", right-click on the name of the first section "Microsoft Edge" and select "Clean Microsoft Edge".
    - Run Office to check if it is broken.
    - If not, repeat with the next section ("Edge Chromium", "Internet Explorer", ...) until you find the responsible section.
    - Repair the Office installation.
    - Now right-click on the first cleaning rule of the responsible section and select "Clean <rule name>".
    - Run Office to check if it is broken.
    - If not, repeat with the next cleaning rule until you find the responsible cleaning rule.

    This would not only help Piriform, but also all other affected users.


  6. 13 hours ago, erincc said:

    ... I found the reg dir, but not sure which folder(s) to delete. ...
    btw in this entry "C:\Users\<your user name>\AppData\Local\Microsoft\Edge". should I delete this folder, there's a ton of stuff in there ...

    e2.png

     

    If still of interest:

    The highlighted registry key "Edge" on your screenshot is the correct one. Click on "Edge" and delete it. You can also delete the key "EdgeUpdate".

    Yes, you can delete the entire folder "Edge" under "C:\Users\<your user name>\AppData\Local\Microsoft\". This folder only contains the Edge Chromium user profile ("User Data"), which you no longer need.

    The old Edge has its own keys and folders.


  7. Check if the following folders or registry keys still exist:

    C:\Program Files (x86)\Microsoft\Edge
    C:\Users\<your user name>\AppData\Local\Microsoft\Edge
    HKEY_CURRENT_USER\Software\Microsoft\Edge

    After deleting them, Edge Chromium should hopefully no longer be detected by CCleaner.


  8. I had a little more time to check the bug and have to correct parts of my previous post. (I use Windows 10 for my following examples.)

    The following DetectOS strings no longer work:

    DetectOS=|10.0 (= for Windows 10 and older)
    DetectOS=10.0|10.0 (= only for Windows 10)

    The problem seems to be that the version number after the pipe symbol now also needs the build number, because the following strings work:

    DetectOS=|10.0.18363.778
    DetectOS=10.0|10.0.18363.778

    Please make sure that CCleaner, if no build number is included in the string, behaves like the previous versions and accepts a simple "|10.0" again. Thanks!

    @hazelnut: Thanks for the flagging.

×
×
  • Create New...