Jump to content
Piriform Community Forums
Winapp2.ini

Winapp2.ini additions

Recommended Posts

It might be appropriate to start a different pinned thread on the forum for Winapp3.ini so that users now and in the future do not get confused between what's what and mistakenly grab Winapp3.ini and run it.  If you do start a new thread, perhaps you could/would move all previous posts concerning Winapp3.ini from the Winapp2.ini thread to the Winapp3.ini thread.  And all the necessary warnings about Winapp3.ini should be part of the first post in the new thread.  JMO :)

 

Share this post


Link to post
Share on other sites

Re new thread and moving posts:

That seems to entail an extreme amount of work for moderators.

Share this post


Link to post
Share on other sites

I don't think winapp3 is substantive enough yet to warrant its own thread or really even much discussion on this one besides update notifications. Any discussion about it is likely best kept to GitHub for the sake of keeping this thread on topic for now.

Share this post


Link to post
Share on other sites
On 4/24/2018 at 02:42, siliconman01 said:

It might be appropriate to start a different pinned thread on the forum for Winapp3.ini so that users now and in the future do not get confused between what's what and mistakenly grab Winapp3.ini and run it.  If you do start a new thread, perhaps you could/would move all previous posts concerning Winapp3.ini from the Winapp2.ini thread to the Winapp3.ini thread.  And all the necessary warnings about Winapp3.ini should be part of the first post in the new thread.  JMO :)

 

Actually, I would much rather starting moving things over to GitHub. Once Winap2ool comes out of beta, I will be working on making a better readme and documentation over at GitHub. Eventually, we will probably end up closing the Winapp2 website as it doesn't have much purpose anymore, but this hasn't been discussed, yet.

I don't mind keeping this thread open. Perhaps a bit of cleaning of this thread would coming in handy (we are almost at 300 posts). Maybe people will be nice enough to specify if there contributions belong to Winapp2 or Winapp3 for the future.

Share this post


Link to post
Share on other sites
19 hours ago, ROCKNROLL said:

Actually, I would much rather starting moving things over to GitHub. Once Winap2ool comes out of beta, I will be working on making a better readme and documentation over at GitHub. Eventually, we will probably end up closing the Winapp2 website as it doesn't have much purpose anymore, but this hasn't been discussed, yet.

I don't mind keeping this thread open. Perhaps a bit of cleaning of this thread would coming in handy (we are almost at 300 posts). Maybe people will be nice enough to specify if there contributions belong to Winapp2 or Winapp3 for the future.

300 posts? There's over 7000! :lol: (but I suppose you probably meant pages)

I don't think the thread needs cleaning. That's a lot of work for moderators and now that winapp2 itself is on GitHub it's a lot easier to track which changes actually make it into the file (when I was maintaining it alone and by hand, any changes I missed would be lost to the ages unless someone specifically audited for those changes and pointed out that I'd missed them).

Overall I think that it'd be fitting for winapp3 contributions to be kept exclusively on GitHub. This is the winapp2 thread, and I think it'd be less confusing for everyone if it stayed that way.

 

Share this post


Link to post
Share on other sites
8 hours ago, Winapp2.ini said:

300 posts? There's over 7000! :lol: (but I suppose you probably meant pages)

I don't think the thread needs cleaning. That's a lot of work for moderators and now that winapp2 itself is on GitHub it's a lot easier to track which changes actually make it into the file (when I was maintaining it alone and by hand, any changes I missed would be lost to the ages unless someone specifically audited for those changes and pointed out that I'd missed them).

Overall I think that it'd be fitting for winapp3 contributions to be kept exclusively on GitHub. This is the winapp2 thread, and I think it'd be less confusing for everyone if it stayed that way.

 

Agreed (and yes I meant pages, haha).

 

On a different note, I am pleased to announce the first official stable release of Winapp3 (though it can still nuke your system due to the number of aggressive entries). The changes include some new entries and some minor cleanup and improvements. See the full list of changes here: https://github.com/MoscaDotTo/Winapp2/commit/9e966b3afa74eee160a421d4557cbf182e337306

Also, I am looking for someone who would be willing to spend a little time looking over the "Windows 10 Useless Files" entry and the " Useless File Extension". The "Windows 10 Useless Files" entry should probably be renamed to something else, but I do not know what those files are (look like some video files) or what they are for as they don't seem to exist on my system. As for the "Useless File Extension" entry, I have given it the best I can, but it is quite a big task. I do not have enough time on my hand to do extensive testing and improvements for it, so if anyone has some time to spare, I would appreciate it if they could go over this entry. If not, it will likely stay as it is for the time being.

Over the next week (actually Wednesdays are really my only free time now), I will be working on improving our documentation. It should be much more thorough compared to what is posted on the first page. I also need to update the headers on both Winapp2 files. Looks like I got a full week ahead of me, huh.

Share this post


Link to post
Share on other sites

In Winapp3.ini, why is [QuickLaunch *] considered dangerous?  This feature was removed in starting with Windows 7.  There is a procedure that permits users to add the Quick Launch bar back in, but I suggest that 99.9% of Windows users do not add it back in. 

I recommend the name should be [Quick Launch *] because Windows does not refer to it as Quicklaunch, but Quick Launch.  I suggest that the code below be added to Winapp2.ini.  I am assuming that DetectOS=6.1| means "Show if Windows version is Windows 7 or later".  

[Quick Launch *]
DetectOS=6.1|
Section=3024
Detect=HKCU\Software\Microsoft\Internet Explorer
Default=False
Warning=Do not activate if you have manually re-implemented the Quick Launch bar in Windows 7/8/or 10
FileKey1=%AppData%\Microsoft\Internet Explorer\Quick Launch|*.lnk

 

Share this post


Link to post
Share on other sites

If this entry is not considered dangerous in Winapp3.ini, why not add it to Winapp2.ini ?

[Windows Tracing *]
LangSecRef=3025
Detect=HKLM\Software\Microsoft
Default=False
FileKey1=%WinDir%\tracing|*.log;*.old|RECURSE

 

Share this post


Link to post
Share on other sites
On 27.4.2018 at 09:13, siliconman01 said:

In Winapp3.ini, why is [QuickLaunch *] considered dangerous?  This feature was removed in starting with Windows 7.  There is a procedure that permits users to add the Quick Launch bar back in, but I suggest that 99.9% of Windows users do not add it back in...

The entry was removed by request: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=234&tab=comments#comment-277438.
I was not happy about that also: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=234&tab=comments#comment-277444.

On 27.4.2018 at 09:27, siliconman01 said:

If this entry is not considered dangerous in Winapp3.ini, why not add it to Winapp2.ini ? [Windows Tracing *]...

That's just a mistake; all entries should have Section=Dangerous. I can't find any information why this entry was removed from Winapp2.ini.
(It seems that the folder isn't used by Windows anymore. On my systems the folder is empty always.)

Share this post


Link to post
Share on other sites
On 27.4.2018 at 07:06, ROCKNROLL said:

...Also, I am looking for someone who would be willing to spend a little time looking over the "Windows 10 Useless Files" entry and the "Useless File Extension"...

Winapp3.ini:

IMHO the entry [Useless File Extension *] should be used with "Analyze" only. It would be hard work to make this entry safe.

The entry [Windows 10 Useless Files *] seems to be wrong: The path "%ProgramFiles%\WindowsApps\Microsoft.CloudExperienceHost_*\" doesn't exist; it should be "%WinDir%\SystemApps\Microsoft.Windows.CloudExperienceHost_*\". But the sub-folder "media" doesn't contain *.mp4 files. We can correct the path and rename the entry to "Windows Apps Media Files". (Or because the files don't exist on your system also; maybe we can remove the entry then?)

Share this post


Link to post
Share on other sites

I think it'd be a better user experience to use a tool like Everything to do broad recursive searches for filetypes 

Share this post


Link to post
Share on other sites

Modified entry:  [Acrok Video Converter Ultimate *]

Added FileKey3

[Acrok Video Converter Ultimate *]
LangSecRef=3023
Detect=HKCU\Software\Acrok Software\Acrok Video Converter Ultimate
Default=False
FileKey1=%AppData%\Acrok\Acrok Video Converter Ultimate|*.dmp
FileKey2=%AppData%\Acrok\Acrok Video Converter Ultimate\log|*.*
FileKey3=%AppData%\Auxre\Blu-ray Plugin|*.log
FileKey4=%UserProfile%\.BDAccess|*.*|RECURSE

 

Share this post


Link to post
Share on other sites

Safari for Windows is supported natively in ccleaner however there isn't a Winapp2.ini entry for additional files to be removed so I'm suggesting adding:

[Safari *]
LangSecRef=3028
Default=False
DetectFile=%ProgramFiles%\Safari\Safari.exe
FileKey1=%AppData%\Apple Computer\Logs|*.*
FileKey2=%LocalAppData%\Apple Computer\com.apple.Safari.PrivateBrowsing|Cache.db
FileKey3=%LocalAppData%\Apple Computer\Safari|WebpageIcons.db

FileKey2 only appears after using the private browsing function so removing it seems prudent.  FileKey3 is regenerated after restarting Safari but other popular cleaners do remove this file although ccleaner doesn't.

Share this post


Link to post
Share on other sites

Been quiet on this thread this past week.

Anyways, I am pleased to announce our new readme is now published on GitHub. The new readme contains more information on how to create your own entries, all the variables we use, all the code we use, etc.

Please check out the new readme here: https://github.com/MoscaDotTo/Winapp2/blob/master/README.md

Also, all the headers of each file has been updated to better reflect the new licensing system and our new readme file.

Share this post


Link to post
Share on other sites

For Winapp2.ini and Winapp3.ini:

line 5:

"If you plan on modifying, distrubuting,"... 

"distrubuting" should really be "distributing".

Share this post


Link to post
Share on other sites
2 hours ago, PICPro said:

For Winapp2.ini and Winapp3.ini:

line 5:

"If you plan on modifying, distrubuting,"... 

"distrubuting" should really be "distributing".

Thank you. They are fixed now.

Share this post


Link to post
Share on other sites

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

 

KrisPlayerGadget.png

Edited by siliconman01
added pic

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×