81

Is there a function in win API which can be used to extract the string representation of HRESULT value?

The problem is that not all return values are documented in MSDN, for example ExecuteInDefaultAppDomain() function is not documented to return "0x80070002 - The system cannot find the file specified.", however, it does! Therefore, I was wondering whether there is a function to be used in common case.

1
  • 2
    Title is different, but essentially the answer will be the same as for this one. Commented Aug 10, 2011 at 8:49

4 Answers 4

115

You can use _com_error:

_com_error err(hr);
LPCTSTR errMsg = err.ErrorMessage();

If you don't want to use _com_error for whatever reason, you can still take a look at its source, and see how it's done.

Don't forget to include the header comdef.h

8
  • 8
    A more complete sample for convenience: inline CString GetMessageForHresult(HRESULT hr) { _com_error error(hr); CString cs; cs.Format(_T("Error 0x%08x: %s"), hr, error.ErrorMessage()); return cs; }
    – nietras
    Commented Feb 9, 2012 at 15:55
  • 5
    header file required: #include<comdef.h> Commented Dec 22, 2016 at 11:36
  • 2
    @nietras what is CString? Commented Nov 11, 2019 at 15:04
  • @PhaniRithvij, CString is MFC's string type (actual C++ class, that is; not a pointer to a C string like LPCTSTR and such).
    – Eran
    Commented Nov 13, 2019 at 11:07
  • 2
    how we should free the errMsg? Commented Jan 9, 2021 at 3:56
37

Since c++11, this functionality is built into the standard library:

#include <system_error>

std::string message = std::system_category().message(hr)
2
  • 3
    This works for system errors, not generic HRESULT error codes. @che You are confusing HRESILT with NT_STATUS. Though they have similar encodings, the former is used throughout the Windows API (COM) as well as the Windows Runtime. You won't be using either one in a kernel mode module. Commented Oct 7, 2020 at 11:01
  • _com_error from <comdef.h> nicely encapsulates all for you without using the "dreaded" <system_error> ... sadly that pushes you into a windows unresolved legacy land. We might actually reimplement that, minus the IErrorInfo functionality. Without using the std lib. Commented Oct 8, 2020 at 6:28
19

The Windows API for this is FormatMessage. Here is a link that explains how to do it: Retrieving Error Messages.

For Win32 messages (messages with an HRESULT that begins with 0x8007, which is FACILITY_WIN32), you need to remove the hi order word. For example in the 0x80070002, you need to call FormatMessage with 0x0002.

However, it does not always work for any type of message. And for some specific messages (specific to a technology, a vendor, etc.), you need to load the corresponding resource DLL, which is not always an easy task, because you need to find this DLL.

2
4

Here's a sample using FormatMessage()

LPTSTR SRUTIL_WinErrorMsg(int nErrorCode, LPTSTR pStr, WORD wLength )
{
    try
    {
        LPTSTR  szBuffer = pStr;
        int nBufferSize = wLength;

        //
        // prime buffer with error code
        //
        wsprintf( szBuffer, _T("Error code %u"), nErrorCode);

        //
        // if we have a message, replace default with msg.
        //
        FormatMessage(FORMAT_MESSAGE_FROM_SYSTEM,
                NULL, nErrorCode,
                MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
                (LPTSTR) szBuffer,   
                nBufferSize,    
                NULL );
    }
    catch(...)
    {
    }
    return pStr;
} // End of SRUTIL_WinErrorMsg()
1
  • 4
    Win32 is C. That above is a mixture of C and C++ exceptions. I am unaware that FormatMessage or any other Win32 function trows c++ exceptions? FormatMessage is returning a value and it is well documented. And. That function can not be used on raw HERROR values. HRESULT_CODE(hr) will (likely) give you the error code you need to call that function with it. Commented Sep 24, 2020 at 6:18

Not the answer you're looking for? Browse other questions tagged or ask your own question.