-
Posts
6,470 -
Joined
-
Last visited
Posts posted by Winapp2.ini
-
-
Shane is @TheWebAtom
-
2 hours ago, CSGalloway said:
This is from another cleaner so i'd like to get an entry written for CCleaner winapp2.ini please:
Run external command: taskkill.exe /f /IM explorer.exe ?B
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_1280.db
Delete 1MB C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_16.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_1920.db
Delete 1MB C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_256.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_2560.db
Delete 1MB C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_32.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_48.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_768.db
Delete 1MB C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_96.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_custom_stream.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_exif.db
Delete 7.4kB C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_idx.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_sr.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_wide.db
Delete 24B C:\Users\csgal\AppData\Local\Microsoft\Windows\Explorer\thumbcache_wide_alternate.db
Run external command: C:\WINDOWS\explorer.exe C:\WINDOWS\explorer.exe ?Bwinapp2.ini cannot stop programs or services so cannot clean things that require it automatically
-
5 hours ago, PICPro said:
There are a couple of issues in [Firefox Caches*] in winapp2.ini in version 290901.
1. "xulstore.json" has been included for deletion in the %AppData% profiles. Deleting xulstore.json causes the menu bar setting to be lost in Firefox, FirefoxESR, Librewolf, Palemoon, etc. and the status bar view settings in Palemoon. This file doesn't contain personal data or urls or other privacy related issues that I can tell. It is just for maintaining the toolbar presence and window locations. I think that xulstore.json should be removed from those lists (FileKey2, 8, 14, 20, 26, 32, 38)
2. Basilisk is included in the %LocalAppData% FileKeys (FileKey43, 44, 45). Basilisk is not included in the %AppData% FileKeys with the other browsers. Basilisk should be added back in here starting at FileKey7 and can have the same treatment the same as Palemoon. This browser is back in active development now for some time.
Thank you.
noted re: xulstore.json, I have had to delete this file in the past to fix broken view settings and thought that perhaps it generally is automatically generated based on my testing but as always, many are the browser configurations . it's not my intention that the mainline winapp2.ini file include "corrective" deletion routines for stuff like this!
-
On 03/09/2023 at 03:44, siliconman01 said:
Is Winapp2ool.ini version 1.5.8000.34368 considered a beta release or a public release? Reason for my question is that my older brother's Winapp2ool.ini does not offer to update to 1.5.8000.34368 (he is not set to accept beta updates).
1.5.8000.34368 is indeed intended to be public, I neglected to build the application for release. I will fix this soon
-
probably FileKey6=%LocalAppData%\Packages\Microsoft.Windows.CloudExperienceHost_*\AC|*|RECURSE
of the issues, this is the one I can reproduce most consistently. Probably the .tbacctpic* files in \AC\TokenBroker\Accounts
-
I can duplicate this using a roaming account. Still trying to narrow down the exact cause of the issue.
-
Looking into this - I have been traveling for family matters for several weeks without access to my devices, apologies for the radio silence on this. The duplicate entry will also be fixed shortly. Thank you for your patience.
The application FileActivityWatch can be helpful in narrowing down things like this. I also suspect /AC/ directory cleaning may be too aggressive - I only use a local account and did not encounter and issues during testing before pushing those changes.
-
Expect updates again this weekend, I both completed the work required in winapp2ool and got my code signing certificate renewed so I can resume publishing builds :)
-
15 hours ago, GhostMotley said:
Thank you for this, I've been reinstalling Windows 11 over the last few hours and it would constantly brick.
In Winapp2, I changed things to the following
[Windows Temporary Files *] LangSecRef=3025 Detect=HKLM\Software\Microsoft\Windows FileKey1=%SystemDrive%\Documents and Settings\LocalService*\Local Settings\Temp|*|RECURSE FileKey2=%SystemDrive%\Documents and Settings\NetworkService*\Local Settings\Temp|*|RECURSE FileKey3=%WinDir%\ServiceProfiles\*\AppData\Local\Temp|*|RECURSE FileKey4=%WinDir%\System32\config\systemprofile\AppData\Local\Temp|*|RECURSE FileKey5=%WinDir%\System32\config\systemprofile\Local Settings\Temp|*|RECURSE FileKey6=%WinDir%\SystemTemp|*|RECURSE FileKey7=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Temp|*|RECURSE
And have run CCleaner several times and have been able to install applications without Error 2203.
Before Error 2203 would always come up and even after trying sfc /scannow, changing permissions and even doing a full Windows feature upgrade, I could not resolve the error.
has dism been any help?
dism /online /cleanup-image /restorehealth
-
Hi sorry I've been away, some business in real life has come up, as it seems to so often these days :(
Just some small updates which I will elaborate on in longer form at a later date:
I'm in the process of making some changes which require meaningful changes to Diff in winapp2ool to handle processing, which is why activity appears to have stopped. There is a pending set of changes that require that winapp2ool update to handle gracefully, although the current public version will handle them fine (albeit noisily).
There's going to be some annoying overlap with CCleaner for the immediate future while I pivot how the file is maintained and built. The short version is it's going Non-CCleaner by default for the maintenance and then a CCleaner version similar to what has previously been default will be generated using winapp2ool. essentially. it is much easier to automate modifying a non-ccleaner file into a ccleaner version than the reverse which is how it is currently done and has been for a very long time. Part of a wider project which I will elaborate on later. I am taking note of the conflicts that arise with CCleaner, but for now most of the conflicting changes (ie. where ccleaner and winapp2.ini both target the same thing) will remain in place, as I am no intentionally longer avoiding these collisions.
edit: of course, if something is a problem and not merely a conflict with CCleaner, I am trying to be proactive as well...
-
in 1.5, I fixed a few settings which weren't being properly saved/initialized to disk. it's likely that when the tool re-initalized after updating it corrupted the expected state of the settings (resetting the broken settings to default and producing unexpected behavior). I think Diff was most affected by this but it's possible Trim was as well.
-
this output comes directly from Diff :) it has been updated in the latest version to detect when entries have been merged or renamed (rather than simply declaring entries in these categories "removed") under some circumstances. it's not perfect and has occasional false negatives (ie. something was merged but Diff can't tell for some reason, usually related to a broad wildcard), but doesn't seem to report false positives. If you're curious where an entry has gone or how it has changed, it's worth running. Unfortunately the output for diffing against 220615 is too large to fit entirely within the cmd window so you will have to save it has diff.txt or view the winapp2ool log to see the full text
-
yes. most have been merged into other entries and some have simply been moved. i think the store as a standalone category no longer makes much sense to use as part of the latest work. In part because I merged UWP and win32 versions of many entries, but also in part because many things that are in this category are just components of the windows operating system built on UWP instead of win32. Essentially, the governing factor behind whether something is this LangSecRef appears to have been whether or not it has keys pointing to %LocalAppData%\Packages rather than whether or not it actually is an app which came from the Microsoft Store.
Accounts Control * has been merged into Windows Security *
ActiveSync * has been merged into Microsoft Outlook *
Chrome Sandbox * has been removed
Cloud Experience Host * has been merged into Windows Subsystems *
Content Delivery Manager * has been merged into Windows Lock Screen *
Feedback Hub * has been merged into Windows Feedback *
Lock Screen * has been merged into Windows Lock Screen *
Maps * has been renamed to Windows Maps *
MS Visual C++ Library * has been merged into Windows Language Libraries *
Network Speed Test * has been renamed to Microsoft Network Speed Test *
Ookla Speed Test App * has been merged into Ookla Speed Test *
Photos * has been merged into Windows Photos *
Print Dialog * has been merged into Windows Printing *
Settings * has been merged into Windows Settings *
Shell Experience Host * has been merged into Windows Shell *
SmartScreen App Reputation * has been merged into Windows Security *
Start Menu Experience Host * has been merged into Windows Start Menu *
Store * has been merged into Microsoft Store *
Store Purchase * has been merged into Microsoft Store *
Weather * has been merged into MSN Weather *
WebView Host * has been merged into Edge WebView Host *
Windows Client * has been merged into Windows Update *
Windows Library for JavaScript * has been merged into Windows Language Libraries *
Windows Search * and Windows Security * have been moved to LangSecRef=3025
Xbox Console Companion * has been merged into Xbox *
-
oy! lol, copy paste perils. thanks
edit: I pushed a quick fix for this without updating the version string again, if you downloaded 230225 then you should redownload.
-
the non-chromium edge browser entries have been archived and were left in the file by mistake. they are removed in 230225. microsoft no longer supports or distributes the non-chromium version of edge
-
8 hours ago, siliconman01 said:
Modified entry: [jv16 PowerTools Backups *]
Changed kv16 to jv16
jv16 PowerTools Backups *] LangSecRef=3024 DetectFile=%ProgramFiles%\jv16 PowerTools* FileKey1=%ProgramFiles%\jv16 PowerTools*|*.reg FileKey2=%ProgramFiles%\jv16 PowerTools*\Backups|*|RECURSE
HOWEVER, I thought it is the general policy not to include backup file removals in Winapp2.ini !
I think it's fine to have entries for this type of thing as long as they are standalone (ie. only clean the backups). Since most people using winapp2.ini are what I'd call power users, I am placing some faith in their ability to discern for themselves whether or not their backups for software are something they want
edit: also this typo will be fixed today. thanks for the patience :) lots of stuff changed and honestly im surprised at how well it's going
-
2 hours ago, siliconman01 said:
JFI
Bitdefender Internet Security blocks downloading the latest Winapp2ool.exe
Infected web page detectedan hour ago- Feature:
- Online Threat Prevention
We blocked this dangerous page for your protection: https://raw.githubusercontent.com/MoscaDotTo/Winapp2/Branch1/winapp2ool/bin/Release/winapp2ool.exe Dangerous pages attempt to install software that can harm the device, gather personal information or operate without your consent.https://www.virustotal.com/gui/file/1cbf043de09773b501435835d1d396a06a489e931e940e1a1989e912e00e5815
probably need to file a false positive report https://www.bitdefender.com/consumer/support/answer/29358/
winapp2ool has a lot of very suspicious features, I guess.
-
yes, I haven't created a release page for it yet but it should be stable for normal use purposes. it contains the changes necessary to support diffing from 220615 to 23XXXX
-
I also notice you have windows taskbar * enabled, does disabling this fix the issue?
-
could you elaborate on what you mean by the apps are gone and they come back?
-
Thank you for the feedback and diligent testing so far. Fixes will be incoming regularly over the next few days to iron out some of these bugs. I had hoped that the extended availability on the 'beta' branch might have brought some of this to light earlier. Maybe we can develop a system for that in the future.
-
Not to fear, they'll be along shortly. I was getting a little lost in the forest of what I was trying to do with winapp2.ini but I think I achieved the initial goal of a significant size reduction and general consolidation. There's a lot of work to be done modernizing entries, especially the browsers, that I was trying to include in this but I think it's best left to subsequent revisions rather than continuing to delay. I'm hoping that now that the major changes are through I'll be able to make more rapid smaller changes to bring things in line.
-
6 hours ago, siliconman01 said:
The change made to [jv16 PowerTools *] is incorrect. Clearing the Debug folder causes jv16 to fully re-initialize on startup.
[jv16 PowerTools *] LangSecRef=3024 DetectFile=%ProgramFiles%\jv16 PowerTools* FileKey1=%ProgramFiles%\jv16 PowerTools*|*.log;*.reg FileKey2=%ProgramFiles%\jv16 PowerTools*\Backups|*|RECURSE ;FileKey3=%ProgramFiles%\jv16 PowerTools*\Debug|* FileKey3=%ProgramFiles%\jv16 PowerTools*\Settings|*.log FileKey4=%ProgramFiles%\jv16 PowerTools*\Temp|*|RECURSE
Is this a regression from when the key parameters were |*.* instead of |*? 220615 has this as *.* and I've been generally operating under the assumption that almost anywhere we have *.* we might actually wish to use * but this may not be the case here in particular
-
I will post an 'official' change log soon, after the initial cleanup work is completed. There's many hundreds of changes to the point where you may wish to consider resetting your ccleaner settings and reevaluating what each is doing, not all changes will necessarily stick/be non breaking although I've done my very best not to break stuff.
if you want to use the latest winapp2ool.ini to run a diff against 220615 it is attached. The latest tool has been improved significantly over the previous public release to handle the wide variety of changes made in this version of winapp2ool. let me know if you experience issues
Winapp2.ini additions
in CCleaner
Posted
very odd, is this a recent development or just something you recently noticed