Microsoft-Windows-Runtime-WebAPI
Event ID 1: Async operation asyncOperation at asyncObject started.
#Event ID 2: Async operation asyncOperation at asyncObject failed to start.
#Event ID 3: Async operation asyncOperation at asyncObject completed successfully.
#Event ID 4: Async operation asyncOperation at asyncObject failed with error code errorCode: hresult.
#Event ID 5: Async operation asyncOperation at asyncObject was cancelled.
#Event ID 6: Async operation asyncOperation at asyncObject was closed.
#Event ID 7: Async operation asyncOperation at asyncObject called completion callback at callback.
#Event ID 8: Async operation asyncOperation at asyncObject called progress callback at callback.
#Event ID 9: Async operation asyncOperation at asyncObject failed to remove handler from GIT.
#Event ID 10: Async operation asyncOperation at asyncObject failed to register handler at GIT.
#Event ID 11: Async operation asyncOperation at asyncObject failed to retrieve handler from GIT.
#Event ID 13: Failed to create URI with base URI 'str1' and relative URI 'str2'.
#Event ID 14: Add HTTP header 'str1: str2'.
#Event ID 15: Start to connect to 'str1' with credential of 'str2'.
#Event ID 16: Start to connect to 'uri' with default credential.
#Event ID 17: Failed to connect to 'uri' at port port.
#Event ID 18: Opening request to 'str1' to 'str2' with flags flags.
#Event ID 19: Failed to open request to 'uri'.
#Event ID 20: Request context obj1 has request handle obj2 to 'uri'.
#Event ID 21: Set HTTP send and receive timeout to lengthms on request handle obj.
#Event ID 22: Start to send to request handle obj with content length length.
#Event ID 23: Request handle obj completed synchronously.
#Event ID 24: Request context obj completed send asynchronously.
#Event ID 25: Writing length bytes to request handle obj.
#Event ID 26: Failed to send entity body to request handle obj.
#Event ID 27: Sent HTTP request at request handle obj: statusDescription.
#Event ID 28: Start to receive response from request handle obj.
#Event ID 29: Received HTTP response from request handle obj with status code statusCode and status description 'statusDescription'.
#Event ID 30: Receive HTTP response from request handle obj: statusDescription.
#Event ID 31: Failed to receive HTTP response from request handle obj.
#Event ID 32: Request context obj received HTTP response of length bytes, which is over the limit limit.
#Event ID 33: Request context obj resubmiting the request.
#Event ID 34: Reusing the request handle obj for server 'statusDescription'.
#Event ID 36: Progress to 'statusDescription': int1 bytes sent; int2 total bytes to send; int3 bytes received; int4 total bytes to receive.
#Event ID 37: HTTP request to 'uri' completed.
#Event ID 38: Async operation asyncOperation at asyncObject failed to process HTTP response 'response'.
#Event ID 39: runtimeClass::api is called.
#Message #
Fields #
| Name | Description |
|---|---|
runtimeClass UInt32 | |
api UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Runtime-WebAPI",
"guid": "{6BD96334-DC49-441A-B9C4-41425BA628D8}",
"event_source_name": "",
"event_id": 39,
"version": 0,
"level": 5,
"task": 1,
"opcode": 10,
"keywords": "0x0000000000000001",
"time_created": "2026-06-02T06:02:22.672+00:00",
"event_record_id": 0,
"correlation": {},
"execution": {
"process_id": 15540,
"thread_id": 13464
},
"channel": "ETW Trace",
"computer": "DESKTOP-FF3N5XK",
"security": {
"user_id": ""
}
},
"event_data": {
"api": 140,
"runtimeClass": 25
},
"message": "tasks.API"
}
Event ID 40: runtimeClass::api returned successfully.
#Message #
Fields #
| Name | Description |
|---|---|
runtimeClass UInt32 | |
api UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Runtime-WebAPI",
"guid": "{6BD96334-DC49-441A-B9C4-41425BA628D8}",
"event_source_name": "",
"event_id": 40,
"version": 0,
"level": 5,
"task": 1,
"opcode": 11,
"keywords": "0x0000000000000001",
"time_created": "2026-06-02T06:02:22.672+00:00",
"event_record_id": 0,
"correlation": {},
"execution": {
"process_id": 15540,
"thread_id": 13464
},
"channel": "ETW Trace",
"computer": "DESKTOP-FF3N5XK",
"security": {
"user_id": ""
}
},
"event_data": {
"api": 140,
"runtimeClass": 25
},
"message": "tasks.API"
}
Event ID 41: runtimeClass::api failed with HRESULT hresult: errorMessage.
#Message #
Fields #
| Name | Description |
|---|---|
runtimeClass UInt32 | |
api UInt32 | |
hresult UInt32 | |
errorMessage Int32 |
Example Event #
{
"system": {
"channel": "Microsoft-Windows-Runtime-WebAPI/Tracing",
"computer": "10.2.10.21",
"correlation": {},
"event_id": 41,
"event_record_id": 0,
"event_source_name": "",
"execution": {
"process_id": 11460,
"thread_id": 7900
},
"guid": "",
"keywords": 0,
"level": 4,
"opcode": 11,
"provider": "Microsoft-Windows-Runtime-WebAPI",
"security": {
"user_id": ""
},
"task": 0,
"time_created": "2026-07-21 23:45:21.840Z",
"version": 0
},
"event_data": {
"api": 141,
"errorMessage": -2089484279,
"hresult": 2205483017,
"runtimeClass": 25
},
"message": ""
}
Event ID 42: Start downloading category document at 'uri'.
#Event ID 43: Category document downloaded successfully at 'uri'.
#Event ID 44: Failed to download category document at 'uri'.
#Event ID 45: Failed to download category document at 'uri'.
#Event ID 46: Failed to parse category document downloaded from 'uri'.
#Event ID 48: Required attribute 'str1' is missing on element 'str2'.
#Event ID 51: Required attribute 'str1' is missing on element 'str2'.
#Event ID 52: The parsed 'feed' element does not have an 'author' element.
#Event ID 53: Multiple 'uri' elements are found.
#Event ID 54: Ignore the 'entry' element found in 'source' element.
#Event ID 55: The 'entry' element does not have a 'content' element or a 'link' element with rel='alternate'.
#Event ID 56: The 'item' element is missing both 'title' and 'description' elements.
#Event ID 57: The 'link' element with rel='enclosure' is missing 'length' attribute.
#Event ID 58: Unexpected child element is found in element with XML: uri.
#Event ID 59: Unexpected 'type' attribute 'str1' when 'src' attribute is present.
#Event ID 60: Unexpected 'type' attribute 'str1' in Atom text content.
#Event ID 61: Element 'str1' should not contain child element or text.
#Event ID 62: Atom text content with type='xhtml' must have a single child element 'div' in namespace 'http://www.
#Description
Atom text content with type='xhtml' must have a single child element 'div' in namespace 'http://www.w3.org/1999/xhtml'.
Message #
Fields #
| Name | Description |
|---|---|
uri UnicodeString |
Event ID 66: Failed to create attribute node.
#Event ID 67: Failed to create element node.
#Event ID 68: Failed to add attribute 'str1' in namespace 'str2' in to the element.
#Event ID 69: Failed to parse JSON string 'uri'.
#Description
Failed to parse JSON string 'uri'. The error happened near statusCode.
Message #
Fields #
| Name | Description |
|---|---|
uri UnicodeString | |
statusCode UInt32 |
Example Event #
{
"system": {
"channel": "Microsoft-Windows-Runtime-WebAPI/Tracing",
"computer": "10.2.10.21",
"correlation": {},
"event_id": 69,
"event_record_id": 0,
"event_source_name": "",
"execution": {
"process_id": 8992,
"thread_id": 9672
},
"guid": "",
"keywords": 0,
"level": 4,
"opcode": 30,
"provider": "Microsoft-Windows-Runtime-WebAPI",
"security": {
"user_id": ""
},
"task": 0,
"time_created": "2026-07-21 23:45:44.788Z",
"version": 0
},
"event_data": {
"statusCode": 0,
"uri": "null\n"
},
"message": ""
}
Event ID 70: The JSON string exceeded the maximum allowed depth obj.
#Provenance
ETW provider GUID {6BD96334-DC49-441A-B9C4-41425BA628D8}
Defined in windows.web.dll, which carries the event manifest.
- Win11-26200.6584, sample captured from a live trace, binary version 10.0.26100.3037, captured 2026-06-02 — Manifest XML pack, 2.0 MB
- WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02 — Manifest XML pack, 1.9 MB
- Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.3037, captured 2026-06-02 — Manifest XML pack, 2.0 MB