This post was migrated from my older blog.

There have been a few times where I found myself starting at an error prompt stating Error: 0x000006C1 or some other unhelpful hex number. Then upon searching for the error code, only finding results for a specific instance of the error for an unrelated application with generic fixes that still don’t hint at the root issue. I found that you can translate some of these error codes using .Net and by extension PowerShell. If you find yourself in this situation, try the following command:

new-object System.ComponentModel.Win32Exception @($ErrorCode);

Where “$ErrorCode” is your error. Example:

new-object System.ComponentModel.Win32Exception @(0x80190193); #Can use integers or hex numbers

I also generated a list of the exceptions here: Win32Exceptions List If the list does not contain your error code, then it is likely just “Unknown error”… not very helpful.

Alternatively, if you utilize SCCM and have the CMTrace tool, you can preform error code lookups directly from the CMTrace application.