Winapp2.ini additions

For easy access here is the entry for Foxit Version 5

[*Foxit Reader 5.0]  
LangSecRef=3021  
Detect=HKCU\Software\Foxit Software\Foxit Reader 5.0 
Default=True  
RegKey1=HKCU\Software\Foxit Software\Foxit Reader 5.0\Recent File List 
RegKey2=HKCU\Software\Foxit Software\Foxit Reader 5.0\RecentFiles 
RegKey3=HKCU\Software\Foxit Software\Foxit Reader 5.0\Preferences\History\LastOpen 
RegKey4=HKCU\Software\Foxit Software\Foxit Reader 5.0\Preferences\Others|csInitialOpenDir

As I stated in the thread about this, it seems the last key does remove the last directory opened from the registry but Foxit still managed to remember the location (still at least the plain text loction is removed)

(Tested XP sp3 but as it is reg entries should work across all OS versions)

I hope they add registry wildcard next

In 1.0.110727 I noticed

[Adobe Updater Logs*]
LangSecRef=3021
Detect=HKCU\Software\Adobe
Default=False
FileKey1=%LocalAppData%\Adobe\AAMUpdater|*.Log|RECURSE
FileKey2=%LocalAppData%\Adobe\Updater6|*.log|RECURSE
FileKey1=%AppData%\Adobe\LogTransport2\Logs|ulog_*.tmp

two FileKey1

[FastStone Image Viewer More*]
LangSecRef=3023
DetectFile=%ProgramFiles%\FastStone Image Viewer\FSViewer.exe
Default=False
FileKey2=%AppData%\FastStone\FSIV|FSViewer.db

no FileKey1

Ah, small errors, I'll fix those up :)

I need help to create an entry for Winapp2.ini. I am listing a reg path here where "CaptureCount" is a DWORD value. I like to reset the value data to 00000000. Is there a way to do that? I don't want to delete the value.

HKEY_CURRENT_USER\Software\TechSmith\SnagIt\10

"CaptureCount"=dword:00000011

MODIFIED ENTRIES

[Corel PaintShop Photo Pro X3*]

LangSecRef=3023

DetectFile=%ProgramFiles%\Corel\Corel PaintShop Photo Pro\X3\PSPClassic\Corel Paint Shop Pro Photo.exe

Default=False

RegKey1=HKCU\Software\Corel\PhotoDownloader\2\PhotoDownloader\DownloadFolder

RegKey2=HKCU\Software\Corel\PhotoDownloader\2\PhotoDownloader\DefaultDownloadFolder

FileKey1=%LocalAppData%\Corel\Thumbs|*.*|RECURSE

FileKey2=%LocalAppData%\Corel|*.PspCache

FileKey3=%AppData%\Corel\PaintShop Photo Pro\13\Cache|*.*|RECURSE

[jv16 PowerTools 2011*]

LangSecRef=3024

DetectFile=%ProgramFiles%\jv16 PowerTools 2011\jv16PT.exe

Default=False

FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups|*.*|RECURSE

FileKey2=%ProgramFiles%\jv16 PowerTools 2011\Settings|UserActionLog.txt

FileKey3=%UserProfile%|NTUSER.DAT.jv16pt_bak2

FileKey4=%UserProfile%|NTUSER.DAT.jv16pt_bak

FileKey5=%UserProfile%|NTUSER.DAT.jv16pt_bak.LOG1

FileKey6=%UserProfile%|NTUSER.DAT.jv16pt_bak.LOG2

FileKey7=%LocalAppData%\Microsoft\Windows|UsrClass.dat.jv16pt_bak2

FileKey8=%LocalAppData%\Microsoft\Windows|UsrClass.dat.jv16pt_bak

FileKey9=%LocalAppData%\Microsoft\Windows|UsrClass.dat.jv16pt_bak.LOG1

FileKey10=%LocalAppData%\Microsoft\Windows|UsrClass.dat.jv16pt_bak.LOG2

FileKey11=%windir%\system32\config|Default.jv16pt_bak

FileKey12=%windir%\system32\config|Default.jv16pt_bak2

FileKey13=%windir%\system32\config|Default.jv16pt_bak.LOG1

FileKey14=%windir%\system32\config|Default.jv16pt_bak.LOG2

FileKey15=%windir%\system32\config|software.jv16pt_bak.LOG1

FileKey16=%windir%\system32\config|software.jv16pt_bak.LOG2

FileKey17=%windir%\system32\config|software.jv16pt_bak2

FileKey18=%windir%\system32\config|software.jv16pt_bak

FileKey19=%windir%\system32\config|system.jv16pt_bak2

FileKey20=%windir%\system32\config|system.jv16pt_bak

FileKey21=%windir%\system32\config|system.jv16pt_bak.LOG1

FileKey22=%windir%\system32\config|system.jv16pt_bak.LOG2

FileKey23=%windir%\System32\config|SAM.jv16pt_bak

FileKey24=%windir%\System32\config|SAM.jv16pt_bak2

FileKey25=%windir%\System32\config|SAM.jv16pt_bak.LOG1

FileKey26=%windir%\System32\config|SAM.jv16pt_bak.LOG2

FileKey27=%windir%\System32\config|COMPONENTS.jv16pt_bak

FileKey28=%windir%\System32\config|COMPONENTS.jv16pt_bak2

FileKey29=%windir%\System32\config|COMPONENTS.jv16pt_bak.LOG1

FileKey30=%windir%\System32\config|COMPONENTS.jv16pt_bak.LOG2

FileKey31=%windir%\ServiceProfiles\NetworkService|NTUSER.DAT.jv16pt_bak

FileKey32=%windir%\ServiceProfiles\NetworkService|NTUSER.DAT.jv16pt_bak2

FileKey33=%windir%\ServiceProfiles\NetworkService|NTUSER.DAT.jv16pt_bak.LOG1

FileKey34=%windir%\ServiceProfiles\NetworkService|NTUSER.DAT.jv16pt_bak.LOG2

FileKey35=%windir%\ServiceProfiles\LocalService|NTUSER.DAT.jv16pt_bak

FileKey36=%windir%\ServiceProfiles\LocalService|NTUSER.DAT.jv16pt_bak2

FileKey37=%windir%\ServiceProfiles\LocalService|NTUSER.DAT.jv16pt_bak.LOG1

FileKey38=%windir%\ServiceProfiles\LocalService|NTUSER.DAT.jv16pt_bak.LOG2

Added lines

FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups|*.*|RECURSE

FileKey2=%ProgramFiles%\jv16 PowerTools 2011\Settings|UserActionLog.txt

Added lines

FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups|*.*|RECURSE

FileKey2=%ProgramFiles%\jv16 PowerTools 2011\Settings|UserActionLog.txt

I disagree with adding the above code to the current jv16 PowerTools 2011 registry compactor backup files removal code.

FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups|*.*|RECURSE

removes the individual registry cleaning backup entries that jv16 stores when performing a registry cleaning. This is like removing quarantined items automatically along with logs on security programs which can be dangerous in the event of a false positive. I recommend a separate code block that users can leave unchecked.

[jv16 PowerTools 2011 Backup Files*]
LangSecRef=3024
DetectFile=%ProgramFiles%\jv16 PowerTools 2011\jv16PT.exe
Default=False
FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups\|*.*|RECURSE|
FileKey2=%ProgramFiles%\jv16 PowerTools 2011\Settings|UserActionLog.txt 
Excludekey1=FILE|%ProgramFiles%\jv16 PowerTools 2011\Backups\|License.xbin_backup

Folks should leave MSE well enough alone and let it do what it does. Otherwise you're defeating the purpose as well as fudging up processes required for practical future development of the software at the very least.

Folks should leave MSE well enough alone and let it do what it does. Otherwise you're defeating the purpose as well as fudging up processes required for practical future development of the software at the very least.

You could be right, but which post does this refer to ?

N.B. I cannot see "MSE" on page 31, and life is too short to search the 30 previous pages !

I need help to create an entry for Winapp2.ini. I am listing a reg path here where "CaptureCount" is a DWORD value. I like to reset the value data to 00000000. Is there a way to do that? I don't want to delete the value.

HKEY_CURRENT_USER\Software\TechSmith\SnagIt\10

"CaptureCount"=dword:00000011

Thank you.

You can do that with VBScript and run it from Ccleaner like this:

' add a scriptkeyX entry to the SnagIt cleaner code
'[snagIt 10...]
'Detect=HKCU\Software\TechSmith\SnagIt\10
'ScriptKey1=SNAGIT.VBS
'
' save the folowing code as SNAGIT.VBS
' ccleaner has already checked that SnagIt 10 is installed
SET sh=CreateObject("WScript.Shell")
sh.RegWrite "HKCU\Software\TechSmith\SnagIt\10\CaptureCount", 0, "REG_DWORD"
SET sh=Nothing

Very informative, Sailback :)

I think this is better. BTW jv16 PowerTools does not create a backup file for License.xbin into Backup folder.

I disagree with adding the above code to the current jv16 PowerTools 2011 registry compactor backup files removal code.

FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups|*.*|RECURSE

removes the individual registry cleaning backup entries that jv16 stores when performing a registry cleaning. This is like removing quarantined items automatically along with logs on security programs which can be dangerous in the event of a false positive. I recommend a separate code block that users can leave unchecked.

[jv16 PowerTools 2011 Backup Files*]
LangSecRef=3024
DetectFile=%ProgramFiles%\jv16 PowerTools 2011\jv16PT.exe
Default=False
FileKey1=%ProgramFiles%\jv16 PowerTools 2011\Backups\|*.*|RECURSE|
FileKey2=%ProgramFiles%\jv16 PowerTools 2011\Settings|UserActionLog.txt 
Excludekey1=FILE|%ProgramFiles%\jv16 PowerTools 2011\Backups\|License.xbin_backup

Thank you. I think there should be an easy option to reset value data.

For example: |RESET

VB Script is not an easy option. :)

You can do that with VBScript and run it from Ccleaner like this:

' add a scriptkeyX entry to the SnagIt cleaner code
'[snagIt 10...]
'Detect=HKCU\Software\TechSmith\SnagIt\10
'ScriptKey1=SNAGIT.VBS
'
' save the folowing code as SNAGIT.VBS
' ccleaner has already checked that SnagIt 10 is installed
SET sh=CreateObject("WScript.Shell")
sh.RegWrite "HKCU\Software\TechSmith\SnagIt\10\CaptureCount", 0, "REG_DWORD"
SET sh=Nothing

MODIFIED ENTRIES

[snagit 9 More*]

LangSecRef=3024

Detect=HKCU\Software\TechSmith\SnagIt\9

Default=False

FileKey1=%LocalAppData%\TechSmith\Snagit\DataStore|*.*

FileKey2=%LocalAppData%\TechSmith\Snagit\DataStore\AppIcons|*.*

FileKey3=%LocalAppData%\TechSmith\Snagit\DataStore\WebSiteIcons|*.*

[snagit 10 More*]

LangSecRef=3024

Detect=HKCU\Software\TechSmith\SnagIt\10

Default=False

FileKey1=%LocalAppData%\TechSmith\Snagit\DataStore|*.*

FileKey2=%LocalAppData%\TechSmith\Snagit\DataStore\AppIcons|*.*

FileKey3=%LocalAppData%\TechSmith\Snagit\DataStore\WebSiteIcons|*.*

Update: for TeeWorlds you can delt the old entries and use this:

[Teeworlds Others*]
LangSecRef=3021
DetectFile=%AppData%\Teeworlds
Default=False
FileKey2=%AppData%\Teeworlds\ghosts|.|REMOVESELF
FileKey3=%AppData%\Teeworlds\tmp|.|REMOVESELF
FileKey4=%AppData%\Teeworlds\dumps|.|REMOVESELF
FileKey5=%AppData%\Teeworlds\ghosts|.|REMOVESELF

[Teeworlds Maps*]
LangSecRef=3021
DetectFile=%AppData%\Teeworlds
Default=False
FileKey1=%AppData%\Teeworlds\downloadedmaps|.|REMOVESELF
FileKey2=%AppData%\Teeworlds\maps|.|REMOVESELF
FileKey3=%AppData%\Teeworlds\downloadedfiles|.|REMOVESELF

[Teeworlds Screenshots,Demos*]
LangSecRef=3021
DetectFile=%AppData%\Teeworlds
Default=False
FileKey1=%AppData%\Teewords\Screenshots|.|REMOVESELF
FileKey2=%AppData%\Teeworlds\demos|.|REMOVESELF

Thank you. I think there should be an easy option to reset value data.

For example: |RESET

VB Script is not an easy option. :)

Even better how about |ASSERT"nnnn" where nnnn is any chosen value that could be zero

Perhaps it should also stipulate what sort of value, e.g.

DWORD;

QWORD;

Binary value;

String Value;

etc.

I suggest it should be kept as a difficult option.

It does not seem right that WinApp2.ini should be used as a click-n-go fixit for the registry by those who cannot safely use RegEdit.

The hard part you have already done, you have identified what registry value you wish to change in which registry key.

I have not learnt how to program in VB script,

but have no difficulty in creating and executing a BAT script that incorporates a VB script and launches cscript.

I suggest that an EASY OPTION would be MERGE{THIS.reg}

Where THIS.reg is the path and name of an exported registry key,

which has then been manually edited so that desired defaults will be imposed when it is merged.

It does not seem right that WinApp2.ini should be used as a click-n-go fixit for the registry by those who cannot safely use RegEdit..

+1

if the program doesn't recreate the entry at 0 then the isn't much ccleaner can (should) do. Ccleaner does not write/create/modify registry entries. Ccleaner is not the correct route to achieve this.

One treads upon dangerous ground, modifying the registry beyond RegKeys

BTW jv16 PowerTools does not create a backup file for License.xbin into Backup folder.

It does on my system. A copy of the License.xbin is in the backup folder.

So the Backup folder is not safe to complete empty?