Windows / Code / 0x0000003f
0x0000003f
Decimal: 63 · Signed: 63
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x003f (63)
As NTSTATUS:- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x003f (63)
Associated Modules
| Module | Found in | Description |
|---|
| EventCreate.exe | 78.11011 | %1 |
| KernelBase.dll | 78.1 | Your file waiting to be printed was deleted. |
| WinMgmtR.dll | 1011 | A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. |
| cipher.exe | 78.11011 | Key Information:
Algorithm: %1
Key Length: %2!d!
Key Entropy: %3!d! |
| dsreg.dll | 1011 | Unable to send WinHTTP request. Error: %1 |
| dssec.dll | 78.11011 | Migrate SID history |
| ehepgres.dll | 7 | %1 |
| hvloader.dll | 11 | Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware. |
| hvservice.sys | 10 | Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware. |
| kernel32.dll | 78.11011 | Your file waiting to be printed was deleted. |
| nslookup.exe | 78.11011 | Success |
| ntdll.dll | 78.11011 | STATUS_WAIT_63 |
| reagentc.exe | 11 | A recovery test mode run was last completed on: %1!s! %2!s! |
| webservices.dll | 78.11011 | The same parameter appeared more than once in the content type. |
| wevtutil.exe | 78.11011 | Uninstall event publishers and logs from manifest.
Usage:
wevtutil { um | uninstall-manifest }
File path to an event manifest. All publishers and logs defined in the manifest
will be uninstalled. To learn more about event manifests and using this option,
consult the Windows Eventing SDK on Microsoft Developers Network (MSDN) at
http://msdn.microsoft.com.
Example:
The following example uninstalls publishers and logs from the myManifest.man
manifest file.
wevtutil um myManifest.man |
| 15 entries |
Associated Headers