0xC0190018: STATUS_CURRENT_TRANSACTION_NOT_VALID
Windows Error Code Lookup: Decode Windows error codes: Win32, HRESULT (0x80070005), NTSTATUS, Windows Update, msiexec and blue-screen stop codes, with what to check next.
Paste the number from an error dialog, event log, script or setup log: 0x80070005, 80070005,
-2147024891, 1603, 0xC0000005, a stop code like 0x7E, a name like
E_ACCESSDENIED, or a few words. You get every way Windows could mean that number (an HRESULT often wraps a
Win32 error, so 0x80070005 is "Access is denied" too), its parts decoded, and what to check for the common ones. Names
and messages come from the Windows SDK headers and Windows' own message tables; see Microsoft's
System Error Codes and
[MS-ERREF] for the full references.
Try: 0x80070005, 1603, 0xC0000005, 0x800F081F, 0x8024402C, 0x7E, access denied
0xC0190018 = 3,222,863,896 = -1072103400
NTSTATUS 0xC0190018
The current transaction context associated with the thread is not a valid handle to a transaction object.
Becomes the Win32 error: 6714ERROR_CURRENT_TRANSACTION_NOT_VALID: The current transaction context associated with the thread is not a valid handle to a transaction object.
| Severity (bits 30-31) | 3: Error |
|---|---|
| Customer (bit 29) | 0: Microsoft |
| Facility | 25 (0x019) TRANSACTION |
| Code | 24 (0x0018) |