APP_TAGGING_INITIALIZATION_FAILED
Code: 0x10a (266)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x010a (266)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x010a (266)
Description
The APP_TAGGING_INITIALIZATION_FAILED bug check has a value of 0x0000010A.
This bug check appears very infrequently.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x10a | 78.11011 | %1 |
| KernelBase.dll | 0x10a | 78.1 | The copy functions cannot be used. |
| kernel32.dll | 0x10a | 78.11011 | The copy functions cannot be used. |
| mispace.dll | 0x10a | 1011 | The specified file system is not supported on the drive. |
| ntdll.dll | 0x10a | 78.11011 | This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed. |
| storagewmi.dll | 0x10a | 8.11011 | The specified file system is not supported on the drive. |
| webservices.dll | 0x10a | 78.11011 | A pipe could not be created. |
| 7 entries | |||