Jump to content

Winapp2.ini additions


Winapp2.ini

Recommended Posts

Revised Entry

 

[Greenshot*]
LangSecRef=3024
DetectFile=%AppData%\Greenshot
Default=False
FileKey1=%LocalAppData%\Greenshot|*.log

Removed:
%AppData%\Greenshot|*.log
Detect=HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Greenshot_is1

 

I think the DetectFile is enough and there is no .log file in %AppData%\Greenshot\. There is only an .ini file there.

Link to comment
Share on other sites

  • Moderators

Please remove the [Aiseesoft Studio Logs*] entry. "Aiseesoft Studio" program does not exist.

 

Are you sure they aren't tied to any number of AISeesoft software out there? However filekey 3 realllllllllllly does need to be removed so good catch there.

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

  • Moderators

Revised Entry

...

 

there is no .log file in %AppData%\Greenshot\. There is only an .ini file there.

Did you check on xp (or does localappdata translate correctly on XP? It's been a while since I was around an "ancient one" :) )

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

Did you check on xp (or does localappdata translate correctly on XP? It's been a while since I was around an "ancient one" :) )

 

From the first post on this thread....

 

%LocalAppData%

Windows XP: C:\Documents and Settings\{username}\Local Settings\Application Data

Windows Vista/7: C:\Users\{username}\AppData\Local\

Link to comment
Share on other sites

  • Moderators

 

 

 

From the first post on this thread....

 

Lol thanks

 

/me am bad moderator hee hee

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

You miss my point. I'm assuming that is an entry that cleans ALL Aiseesoft Studio software logs and therefore is not necessarily invalid.

This is not true. I use one of their programs. This entry must have been added mistakenly into Winapp2.ini.

Link to comment
Share on other sites

Парни, а добавьте всякие

Readme.txt

Change.txt

History.txt

etc

 

типа 

[README C]
LangSecRef=3021
DetectFile=C:\
Default=False
FileKey1=C:\|readme.txt|RECURSE
 
[README D]
LangSecRef=3021
DetectFile=D:\
Default=False
FileKey1=D:\|readme.txt|RECURSE
 
[README E]
LangSecRef=3021
DetectFile=E:\
Default=False
FileKey1=E:\|readme.txt|RECURSE

 

Хотя возможно уже добавлено?

Link to comment
Share on other sites

  • Moderators

Парни, а добавьте всякие

Readme.txt

Change.txt

History.txt

etc

 

типа 

[README C]

LangSecRef=3021

DetectFile=C:\

Default=False

FileKey1=C:\|readme.txt|RECURSE

 

[README D]

LangSecRef=3021

DetectFile=D:\

Default=False

FileKey1=D:\|readme.txt|RECURSE

 

[README E]

LangSecRef=3021

DetectFile=E:\

Default=False

FileKey1=E:\|readme.txt|RECURSE

 

Хотя возможно уже добавлено?

no, too comprehensive and over reaching...not everybody has each of those drives...not every file with those names should be held equally

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

  • Moderators

no, too comprehensive and over reaching...not everybody has each of those drives...not every file with those names should be held equally

 

That and literally take forever to clean. I wouldn't want it, I need my readme.txt files.

Link to comment
Share on other sites

  • Moderators

This is NOT the place to ask about competition software, please do this elsewhere. Thank you.

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

 

I asked if there's an entry in Winapp2.ini that could have caused it. If there's not I would contact someone at [competition] and obviously not discuss it here.

Then try running CCleaner with winapp2 and see if it does the same, then ask. Otherwise it could be the other programs issue

Link to comment
Share on other sites

  • Moderators

Well, I did run [competition] and CCleaner without Winapp2.ini before and it didn't happen so it has to be Winapp2.ini, right?

Maybe maybe not. Uncheck all winapp2 entries, run cleaning check off one (most likely suspect first) winapp entry and clean again. Repeat one at a time until you confirm which entry it is.

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

Well, I did run [competition] and CCleaner without Winapp2.ini before and it didn't happen so it has to be Winapp2.ini, right?

 

The RegKeys listed below in the [Compatibility Assistant*] entry are causing this issue.

 

HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

HKLM\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

Link to comment
Share on other sites

Revised Entry

 

[Compatibility Assistant*]
LangSecRef=3025
Detect=HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant
Default=False
RegKey1=HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted
RegKey2=HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store
RegKey3=HKU\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted
RegKey4=HKU\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store

Removed:
Warning=The will clear compatibility settings for some applcations.

HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
HKLM\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

There is no need of the Warning anymore.

Link to comment
Share on other sites

Revised Entry

 

[Ashampoo Burning Studio 16*]
LangSecRef=3024
Detect=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16
Default=False
FileKey1=%AppData%\Ashampoo\Ashampoo Burning Studio 16\log|*.xml;*.txt
RegKey1=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Audio Disc Project\SaveDialog_CPlaylistDlgEx|InitialDirectory
RegKey2=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Backup Project\BackupOptions|CustomLocation
RegKey3=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\BDMV Disc Project\SelectBDMVFolder|BdmvPath
RegKey4=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Browse Image Project\BrowseImageFile|ImagePath
RegKey5=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Browse Image Project\SaveDialog_SelectImageBrowse|InitialDirectory
RegKey6=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Burn Image Project\SaveDialog_SelectImageBrowse|InitialDirectory
RegKey7=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Burn Image Project\SelectImage|ImagePath
RegKey8=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Data Disc Project\SaveDialog_AddFilesAndDirs|InitialDirectory
RegKey9=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\DVD-Video Disc Project\MoviesPage|Path
RegKey10=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\DVD-Video Disc Project\SaveDialog_authed.CMoviesPage.Movies|InitialDirectory
RegKey11=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Logs
RegKey12=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\tempFiles
RegKey13=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\Unknown Project
RegKey14=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\VCD Project\SaveDialog_OnAddMovies|InitialDirectory
RegKey15=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\VIDEO_TS Disc Project\DumpImage|ImagePath
RegKey16=HKCU\Software\Ashampoo\Ashampoo Burning Studio 16\VIDEO_TS Disc Project\SelectVideoTSFolder|VideoTSPath

Link to comment
Share on other sites

I use Office 2016 (32-bit) and Windows 10 (64-bit).

 

UBitMenu  is Uninstalled/Removed  by:

[MS Office Unsaved Files*]

why not you run the cleaner first > install UbitMenu back > scan again > instead of cleaning, create exclude rule for detected files

share your edited rule here

 

already tried install and clean > found no file to delete

Win XP

Link to comment
Share on other sites

  • Moderators
is negatively affecting UbitMenu  (and apparently,  other programs...)

is the point.

 

 

That's what the Exclude is for, exclude the file(s) UbitMenu has installed, quick, easy, done. Or don't use the Office cleaner.

Link to comment
Share on other sites

Excluding [MS Office Unsaved Files*] by creating rules

is not the point.

well, i thought that how we create and fix the rule ( find the problem and exclude/modify )

 

as i wrote previously, you need to contribute too

you can't expect the Winapp2.ini's maintainer to install all software available

i've already install the program but nothing to clean

the program install add-in inside folder which already excluded by the exclude rule

this file, maybe? UBitMenu04UK.ppam??

 

from install_script

[Files]
Source: "{userappdata}\Microsoft\Excel\{reg_HKCU\Software\Microsoft\Office\12.0\Common\General_Xlstart_XLSTART}\UBitMenu04UK.xlam"; 
DestDir: "{userappdata}\Microsoft\Excel\{reg:HKCU\Software\Microsoft\Office\12.0\Common\General,Xlstart|XLSTART}"; MinVersion: 0.0,5.0; 

Source: "{userappdata}\Microsoft\Word\{reg_HKCU\Software\Microsoft\Office\12.0\Common\General_Startup_STARTUP}\UBitMenu04UK.dotx"; 
DestDir: "{userappdata}\Microsoft\Word\{reg:HKCU\Software\Microsoft\Office\12.0\Common\General,Startup|STARTUP}"; MinVersion: 0.0,5.0; 

Source: "{userappdata}\Microsoft\{reg_HKCU\Software\Microsoft\Office\12.0\Common\General_AddIns_AddIns}\UBitMenu04UK.ppam"; 
DestDir: "{userappdata}\Microsoft\{reg:HKCU\Software\Microsoft\Office\12.0\Common\General,AddIns|AddIns}"; MinVersion: 0.0,5.0; 

Winapp2.ini

ExcludeKey2=PATH|%AppData%\Microsoft\Word\STARTUP

ExcludeKey3=PATH|%AppData%\Microsoft\Excel\XLSTART

Link to comment
Share on other sites

New Entry:

[NT Registry Optimizer*]
LangSecRef=3024
DetectFile=%ProgramFiles%\NT Registry Optimizer\NTREGOPT.EXE
Default=False
FileKey1=%LocalAppData%\Microsoft\Windows\UsrClass.bak
FileKey2=%WinDir%\ServiceProfiles\LocalService\NTUSER.bak
FileKey3=%WinDir%\ServiceProfiles\NetworkService\NTUSER.bak
FileKey4=%WinDir%\System32\config\COMPONENTS.bak
FileKey5=%WinDir%\System32\config\DEFAULT.bak
FileKey6=%WinDir%\System32\config\SAM.bak
FileKey7=%WinDir%\System32\config\SECURITY.bak
FileKey8=%WinDir%\System32\config\SOFTWARE.bak
FileKey9=%WinDir%\System32\config\SYSTEM.bak

Link to comment
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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.