Windows Error Codes Explained

Martin Brinkmann
Nov 21, 2006
Updated • May 19, 2013

What do you do if windows pops up saying the operation was aborted because of Error Code 32? Not really helpful is it? Looking it up would be one solution but this is not the best one, as you may spend some time finding a description of the error code, and a solution to fix the issue that caused it.

A library of all error codes would be helpful and Gregory Brauns Error Messages for Windows is just that. Once installed you can either use it to find out more about an error that you have just experienced, or browse the list of all error codes and messages that it has to offer information about.

Error Codes for Windows is pretty handy if  you encounter errors in Windows from time to time, or only once, as you can look them up by loading the program on your system and doing so locally. You do not need an Internet connection for that and do not need to spend time browsing through results on search engines to find the solution to your issue.

Error Code 32 by the way meant that "The process cannot access the file because it is being used by another process." As you can see it is useful although you may have troubles fixing some of the messages by yourself. Finding the other process in the example is not that easy as it sounds for example.

Still, it is better than nothing. The tool is only about a hundred Kilobyte in size.

Update: The program has last been updated in 2005, and while it may still work fine in the newest versions of Windows, some of its error code information may be outdated, or not included in the program database at all. It will work fine on Windows XP and older versions of Windows, and while you can run it on newer versions as well, its use on those systems may be limited.

Update: Gregory Braun really came through and has updated his program. The most important addition in the update is support for newer Microsoft Windows operating systems such as Vista, Windows 7 and Windows 8.


Tutorials & Tips

Previous Post: «
Next Post: «


  1. philip usher said on December 25, 2007 at 8:24 pm

    The instruction at “0x2077660c” referenced memory at “0x033a8d44”. The memory

    could not be “written”. Click on ok to terminate the program

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.