Jump to content
Piriform Community Forums

dvdbane

Members
  • Content count

    405
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dvdbane

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

743 profile views
  1. Winapp2.ini additions

    it doesn't matter if you're not using Google Chrome, as long as you're using chrome variant and use extension, that cleaning rule will make some extension lose settings or corrupted that will make a lot of user really mad esp Stylish/Stylus user which is why [Logs *] was modified i don't make the decision but if you need more explanation, then @APMichael can help with that
  2. Winapp2.ini additions

    didn't notice the modified entry until @siliconman01 mentioned it *.log and excludekey was removed from the entry [Logs *] due to issues #320
  3. Winapp2.ini additions

    2.2. Write-Ahead Log (WAL) Files A write-ahead log or WAL file is used in place of a rollback journal when SQLite is operating in WAL mode. As with the rollback journal, the purpose of the WAL file is to implement atomic commit and rollback. The WAL file is always located in the same directory as the database file and has the same name as the database file except with the 4 characters "-wal" appended. The WAL file is created when the first connection to the database is opened and is normally removed when the last connection to the database closes. However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened. 2.3. Shared-Memory Files When operating in WAL mode, all SQLite database connections associated with the same database file need to share some memory that is used as an index for the WAL file. In most implementations, this shared memory is implemented by calling mmap() on a file created for this sole purpose: the shared-memory file. The shared-memory file, if it exists, is located in the same directory as the database file and has the same name as the database file except with the 4 characters "-shm" appended. Shared memory files only exist while running in WAL mode. The shared-memory file contains no persistent content. The only purpose of the shared-memory file is to provide a block of shared memory for use by multiple processes all accessing the same database in WAL mode. If the VFS is able to provide an alternative method for accessing shared memory, then that alternative method might be used rather than the shared-memory file. For example, if PRAGMA locking_mode is set to EXCLUSIVE (meaning that only one process is able to access the database file) then the shared memory will be allocated from heap rather than out of the shared-memory file, and the shared-memory file will never be created. The shared-memory file has the same lifetime as its associated WAL file. The shared-memory file is created when the WAL file is created and is deleted when the WAL file is deleted. During WAL file recovery, the shared memory file is recreated from scratch based on the contents of the WAL file being recovered.
  4. Winapp2.ini additions

    if removing wpndatabase.db break Microsoft Store Apps Live Tile feature. then i think *.db-shm;*.db-wal need to be remove too as it is created by wpndatabase.db and will be deleted automatically https://www.sqlite.org/tempfiles.html
  5. ccleaner deleted many shortcuts on my desktop

    please provide Applications tab screenshot too
  6. Winapp2.ini additions

    @Winapp2.ini got this error and winapp2ool crash when running offline while trying to setup winapp2.ini on my friend laptop no error when running online test function merge and trim, no problem, didn't test other features does this cause by not using dotnet 4.6 like issue #251 on github? win 7 sp1, dotnet 4.5.2
  7. Winapp2.ini additions

    [Thunderbird DOM Storage *] LangSecRef=3030 Detect1=HKLM\Software\Mozilla\FossaMail Detect2=HKLM\Software\Mozilla\Mozilla Thunderbird Default=False FileKey1=%AppData%\FossaMail\Profiles\*|webappsstore.sqlite FileKey2=%AppData%\Thunderbird\Profiles\*|webappsstore.sqlite - follow firefox naming for cleaning webappsstore.sqlite
  8. Winapp2.ini additions

    Agreed ej-technologies seem not connected to OxygenXML except for their java app being used by OxygenXML same like Jdownloader [Oxygen 14 *] LangSecRef=3021 DetectFile=%ProgramFiles%\Oxygen XML Editor 14 Default=False FileKey1=%LocalAppData%\VirtualStore\Program Files*\Oxygen XML Editor 14|*.properties;*.log FileKey2=%LocalAppData%\VirtualStore\Program Files*\Oxygen XML Editor 14\.install4j|*.log FileKey3=%LocalAppData%\VirtualStore\Program Files*\Oxygen XML Editor 14\dicts|*.txt;*.html FileKey4=%LocalAppData%\VirtualStore\Program Files*\Oxygen XML Editor 14\lib|*.txt|RECURSE FileKey5=%ProgramFiles%\Oxygen XML Editor 14|*.properties;*.log FileKey6=%ProgramFiles%\Oxygen XML Editor 14\.install4j|*.log FileKey7=%ProgramFiles%\Oxygen XML Editor 14\dicts|*.txt;*.html FileKey8=%ProgramFiles%\Oxygen XML Editor 14\lib|*.txt|RECURSE ExcludeKey1=FILE|%ProgramFiles%\Oxygen XML Editor 14\.install4j\|files.log - change Detect to DetectFile found the entry, 2013
  9. ccleaner registration

    Remove ccleaner folder inside "Program Files" folder after uninstall then reinstall ccleaner back
  10. Ccleaner version dead?

    try this
  11. @iSandman in my test for Waterfox, Intelligent Cookie Scan work as expected after adding both CustomLocation
  12. Winapp2.ini additions

    %AppData%\Microsoft\CryptnetUrlCache = C:\Users\{username}\AppData\Roaming\Microsoft\CryptnetUrlCache not C:\Users\{username}\AppData\LocalLow\Microsoft\CryptnetUrlCache i hope you can confirm whether you have that folder in Roaming directory, not LocalLow
  13. Not a good idea

    you should untick the option to install avast when notified by the installer and avast disable mbam to avoid conflict during installation and real time protection
  14. try check whether windows defender controlled folder access is enable or not if it is enable, try disable it then clean the registry again Do not clean all detected registry problem unless you know what you're doing https://support.microsoft.com/en-us/help/4046851/windows-10-controlled-folder-access-windows-defender-security-center
×