WinappDebug - A tool to find error in your winapp2.ini file

CCleaner for Windows
1

Thanks to help from Robbie Ward (User: winapp2.ini); I've made this very simple console app to detect common errors with your winapp2.ini file.

How do I use it?

Simply place ‘winapp2.ini’ in the same folder as ‘WinappDebug.exe’ and run the tool. It will output a list of errors that it detects.

What kind of errors does it detect?

- Starting and trailing whitespace

- LangSecRef, FileKey & RegKey spelling errors

- Spaces in environmental variables

- Missing numbers next to FileKey and Regkey entries

- Missing backslashes next to environmental variables

- Incorrect usage of the ‘Detect’ & ‘DetectFile’ commands.

WinappDebug.png

It’s not working! HELP!!!

WinappDebug requires the Microsoft .NET Framework to be installed on your computer. Make sure winapp2.ini can be accessed by the tool by closing any programs you are using to edit it.

Download (version 0.3)

http://content.thewebatom.net/files/WinappDebug.exe

MetaScan results show 1/40 security products incorrectly detect WinappDebug as malware. If you have any concerns, you're welcome to compile it from the source code below ;)

Source Code

Written in VB.NET. Available from PasteBin.

Please feel free to leave comments and suggestions.

2

Nice, thanks, have to check it out.

3

Can u dump the errors to a txt file?

4

Unfortunately no. It runs so quickly that it essentially IS a text file... just with a black background.

5

Uploaded version 0.2 which can now detect incorrect usage of the 'Detect' & 'DetectFile' commands.

6

It's not detecting the batman entry in my version :o

7

Oops! I updated the link text but not the actual hyperlink. Fixed :)

8

Thanks!

9

Updated to 0.3

- Number of detected issues reported correctly.

- Better support for the new permitted wildcards

- Fixed a compiler warning.

10

- slightly different icon

- new: smartscreen warning on windows 8 ;)

11

Yeah, I used an updated version of the Visual Studio compiler. It's interesting to note that the output was 40% bigger, even before I made changes to the code.

12

I've pinned this topic, the tool will be very useful for the community.

13

Thanks, guys. Very nice.

14

Works like a charm, found two errors in my BleachBit winapp2.ini, and one error in my CCleaner winapp2.ini.

15

Nice work

Could you also add support for the other ini files like Winsys2.ini ?

16

@ TheWebAtom: I know the coding language will have a look and see if I can help you out.

This thing can grow to become really big and helpful.

17

It would be grat to add a check routine for that :

_________________________________________________________________

working of Excludekey: I think these Excludekey should not work, because you use | instead of \, cause Excludekeys work like this.

also true !!!!

but second bug:

ExcludeKey1=FILE|C:\Users\Admin\Desktop\Musik\1.txt;2.txt

; dont work, serperate each file ......

___________________________________________________________________

from winapp2.ini

[Diablo III Logs*]

Section=Games

Detect=HKCU\Software\Blizzard Entertainment\D3

Default=False

FileKey1=%CommonAppData%\Battle.net\Setup\diablo3_engb\Log

FileKey2=%ProgramFiles%\Diablo III\Logs

FileKey3=%ProgramFiles%\Diablo III Beta\Logs|.

FileKey4=%LocalAppData%\VirtualStore\Program Files*\Diablo III\Logs

FileKey5=%LocalAppData%\VirtualStore\Program Files*\Diablo III Beta\Logs|.

FileKey6=%LocalAppData%\VirtualStore\ProgramData\Battle.net\Setup\diablo3_engb\Log

File key 1 ,2 ,6 not cleaning definition! could it work ? like *.log e.g.

______________________________________________________________________

also nice double use of || \\ ;; |\ \| **

also:

Oh shoot, realtek (logs) does a recursive scan from %SystemDrive%, that's just horrid.

Thats not just clean,

Its squeaky clean :)

and doble rules detection....

18

It might be a good addition to detect if the "Default=False (or True)" is missing. :)

19

Old thread is old. Unpinned by request, any information about this debugger ask at the winapp2 thread.

Thanks