KB5132061 fails with 0x800F0922 on 26H2 Home China, event manifest registration returns 1630

There is no Microsoft-listed 26H2 or Home China known issue matching 0x800F0922, Events-installer manifest registration, and Win32 error 1630; the next useful step is to extract the complete eventsXml payload and query the affected provider’s registered metadata rather than repeat general Windows Update repairs.^1^

1. Known-issue status

Microsoft’s current and recently resolved 26H2 issues include USB audio, Remote Desktop, desktop loading, AC-3, and domain-trust problems, but not this event-manifest failure.^1^^2^

There are reports of 0x800F0922 on 26H2, but that code is only the update-level failure. Other cases have had unrelated underlying causes, so they do not establish a Home China regression.^3^

A separate Q&A case confirms that an Events-installer provider/channel conflict can trigger 0x800F0922, but its provider and error were different: Microsoft-Windows-Store/Operational and error 15010, not System-Events/Kernel-WDI and 1630.^4^

2. Getting more detail than 1630

No documented CBS switch is available that expands ERROR_UNSUPPORTED_TYPE into the rejected XML attribute or registry value. The most specific public evidence is normally:

1. The complete eventsXml: block immediately before the error.
2. Any preceding wevtconfig warning.
3. The provider GUID, provider name, channel name, and resource/message file paths.
4. Whether Windows can currently open that provider’s metadata.

Run these read-only commands in an elevated Command Prompt, replacing the sample provider names with the exact names shown in eventsXml:

mkdir "%USERPROFILE%\Desktop\EventDiag" 2>nul
wevtutil ep > "%USERPROFILE%\Desktop\EventDiag\publishers.txt"
wevtutil el > "%USERPROFILE%\Desktop\EventDiag\channels.txt"
wevtutil gp "Microsoft-Windows-Kernel-WDI" /ge:true /gm:true /f:xml ^
  > "%USERPROFILE%\Desktop\EventDiag\Kernel-WDI.xml" 2>&1
wevtutil gp "Microsoft-Windows-Eventlog" /ge:true /gm:true /f:xml ^
  > "%USERPROFILE%\Desktop\EventDiag\Eventlog.xml" 2>&1
findstr /i /c:"eventsXml" /c:"wevtconfig" /c:"1630" /c:"0x8007065e" ^
  "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\EventDiag\CBS-events.txt"

wevtutil ep enumerates publishers, while gp returns publisher configuration and optionally event metadata and resolved messages. These operations require elevation.^5^^6^

Interpret the result as follows:

• gp succeeds: compare its XML with the CBS eventsXml block, especially provider GUID, channel name/type, and resourceFileName/messageFileName.
• gp fails for the exact provider: capture the full error text. That indicates the existing registration cannot expose valid metadata, although it does not by itself identify which manifest field caused 1630.
• The same channel appears under another provider GUID: record both GUIDs. The analogous Store case failed because an existing provider already declared the channel.^4^
• The resource/message path is missing or points to an unavailable binary: record that path. Installed manifests require valid absolute resource and message-file locations so event metadata can be decoded.^7^

The useful CBS excerpt starts at Begin executing advanced installer ... Installer name: 'Events' and ends after Failed execution of queue item. Include all intervening eventsXml text; a single 1630 line is insufficient.

3. Do not remove or reinstall the provider yet

Do not delete WINEVT\Publishers keys or run wevtutil um/im against System-Events or Kernel-WDI based only on the error number. wevtutil um removes all publishers and logs defined by the supplied manifest, so changing an inbox provider without first identifying the exact conflicting registration can damage event logging.^5^

The registry deletion proposed for the Store-provider case is specific to that provider GUID and is not transferable to Kernel-WDI.

4. Escalation

If the full XML shows no duplicate provider/channel and wevtutil gp returns valid metadata, this requires Microsoft servicing analysis. Open Get Help, provide the CBS excerpt and the EventDiag outputs, and emphasize that:

• three consecutive LCUs fail at the identical Events-installer operation;
• repair install, DISM/SFC, cache reset, offline MSU installation, event-log rebuilding, and registry-type auditing have already been completed;
• the failure is reproducible on build 26300.9457, Home China x64;
• the requested analysis is of the Events advanced installer’s rejected manifest element, not generic 0x800F0922 troubleshooting.

References

1. Windows 11, version 26H2 known issues and notifications
2. Resolved issues in Windows 11, version 26H2
3. install error 0x800f0922 for Windows 11, version 26H2
4. Error 0x800f0922 installing windows update KB5066793 - rollback in ...
5. wevtutil
6. Windows Event Log Tools
7. Event Metadata Overview