New: Windows Error Lookup Tool Portable 2.0.3 (get details on Windows error codes) Released 5a4837

computerfreaker's picture
Submitted by computerfreaker on March 12, 2011 - 10:35pm

logoRead on for more details...

Windows Error Lookup Tool is packaged for portable use with permission from Gunner Inc.

Features 5m3f1z

ScreenshotWhen an error occurs, Windows will often display either decimal, hex, HRESULT, NTSTATUS or STOP error codes. Type in an error code and WELT will display in English the error. You also have the option to create a note for an error (so you can keep track of what you have done to create the error)

Learn more about Windows Error Lookup Tool...

portableapps.sitesunblocked.org Installer / portableapps.sitesunblocked.org Format 1y1x1j

Windows Error Lookup Tool Portable is packaged in a portableapps.sitesunblocked.org Installer so it will automatically detect an existing portableapps.sitesunblocked.org installation when your drive is plugged in. It s upgrades by installing right over an existing copy, preserving all settings. And it's in portableapps.sitesunblocked.org Format, so it automatically works with the portableapps.sitesunblocked.org Suite including the Menu and Backup Utility.

3j2c6h

Windows Error Lookup Tool Portable is available for immediate from the Windows Error Lookup Tool Portable homepage. Get it today!

Story Topic: 6q3g2y

Comments 19c1v

date on homepage 42i56

The homepage say march 11 should this be march 12 

32 bit Only fails with 64 bit f4l73

This app should be marked as 32 bit only.

It doesn't know things like SibdbySide error 35 for 64 bit Win 7

John T. Haller's picture

Nope 5bl64

It works fine on 64-bit Windows. The only issue is that it doesn't know *every* error (for example, the one you mentioned). There are some errors missing (not specifically 64-bit errors) and you can ask the author to add them.

Sometimes, the impossible can become possible, if you're awesome!

beta then? q3x

I wasn't saying it wouldn't run on 64 bit.
I didn't see anythong that said that there was a lack of data for
both 32 bit and 64 bit.
I shouldn't have mentioned 64 bit - that was an assumption because
32 bit errors are well known.

I've seen a lot of these windows error decoders come and go.
I see that MS has folded all the errors into a single source.

http://msdn.microsoft.com/en-us/library/ms681381%28v=vs.85%29.aspx

Actually, I get the error 1d2666

Actually, I get the error code descriptions directly from the OS.. the error number to the OS and I get the description... Maybe I have to do something dif with x64... but I have Win7 x32 to work with...