FACILITY_WINDOWS: the Windows subsystem.
The source of the error code is the Windows subsystem.[1][2]
0x00081600: NOTE: This dummy error message is necessary to force MC to output the above defines inside the FACILITY_WINDOWS guard instead of leaving it empty.[3]0x80080001: Attempt to create a class object failed[2]0x80080002: OLE service could not bind object[2]0x80080003: RPC communication failed with OLE service[2]0x80080004: Bad path to object[2]0x80080005: Server execution failed[2]0x80080006: OLE service could not communicate with the object server[2]0x80080007: Moniker path could not be normalized[2]0x80080008: Object server is stopping when OLE service contacts it[2]0x80080009: An invalid root block pointer was specified[2]0x80080010: An allocation chain contained an invalid link pointer[2]0x80080011: The requested allocation size was too large[2]0x00080012: Not all the requested interfaces were available[2]0x00080013: The specified machine name was not found in the cache.[2]0x80080015: The activation requires a display name to be present under the CLSID key.[2]0x80080016: The activation requires that the RunAs value for the application is Activate As Activator.[2]0x80080017: The class is not configured to support Elevated activation.[2]0x80080200: Appx packaging API has encountered an internal error.[2]0x80080201: The file is not a valid Appx package because its contents are interleaved.[2]0x80080202: The file is not a valid Appx package because it contains OPC relationships.[2]0x80080203: The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present.[2]0x80080204: The Appx package's manifest is invalid.[2]0x80080205: The Appx package's block map is invalid.[2]0x80080206: The Appx package's content cannot be read because it is corrupt.[2]0x80080207: The computed hash value of the block does not match the one stored in the block map.[2]0x80080208: The requested byte range is over 4GB when translated to byte range of blocks.[2]0x80080209: The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data.[2]0x8008020A: The APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data.[2]0x80080300: The background task activation is spurious.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0
- CiError.h from Windows SDK 10.0.14393.0