Severe Issues After Upgrading to Windows 11 25H2: Disk Errors, Certificate Problems, and System Failures Dear Microsoft Support Team, Hello! After upgrading to Windows 11 version 25H2, I have encountered multiple system issues, including but not limite

Dear Microsoft Support Team,

I hope this message finds you well. I am writing to report multiple persistent issues on my Windows 11 system (Version 24H2, Build 26100.6725) after installing the preview cumulative update (KB5065789) dated September 2025 for x64-based systems.

I have performed extensive diagnostics to rule out common hardware or software conflicts, including:

Full Disk Check (CHKDSK): No errors were detected. The scan completed successfully in read-only mode, confirming the file system integrity.

Hard Drive Health Checks:

HD Tune Pro: No bad sectors detected.

  CrystalDiskInfo: All drives reported as "Good."
  

Despite these checks, I continue to experience the following critical issues:

1. Wi-Fi Adapter Failures

The Intel(R) Wi-Fi 6 AX200 160MHz adapter repeatedly encounters internal errors and fails to function properly.

Specific errors include:

"System determined the network adapter is not functioning correctly."

  "Refreshed time zone information, exit reason: 0. Current time zone bias: -480."
  
  This has disrupted applications like Steam and other internet-dependent services.
  

2. System Time and RTC Issues

The system time frequently resets during startup, with logs indicating:

"System time synchronized with the hardware clock."

  RTC time discrepancies and incorrect time zone offsets.
  
  Example log entry:
  
  text
  
  ```
  System time changed from 2025-10-06T03:10:36.841992300Z to 2025-10-06T03:29:40.500000000Z.  

Change reason: System time synchronized with the hardware clock.
```

3. COM Server Permission Errors

Application-specific permission issues related to CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}.

Error message:

text

Local activation permission not granted to user SID (S-1-5-21-...) for COM server application.  

4. Pluton-Windows Firmware Failure

The system fails to load Pluton-Windows firmware with status:

text

StatusCode: STATUS_SUCCESS, Reason: Failed to apply firmware.  

5. "Delayed Write Failed" Errors

Frequent pop-ups:

text

Windows - Delayed Write Failed: Exception Processing Message 0xc0000222 - Unexpected parameters.  

Given the complexity and interdependency of these issues, I believe they may stem from the recent update or underlying system conflicts. As someone with a technical background, I am eager to collaborate with your team to resolve these problems.

Request for Real-Time Assistance

Could we schedule a live chat or remote session to troubleshoot these issues in real time? I am available to provide additional logs, system details, or perform diagnostic steps as needed.

Thank you for your attention to this matter. I look forward to your response.Dear Microsoft Support Team,

I hope this message finds you well. I am writing to report multiple persistent issues on my Windows 11 system (Version 24H2, Build 26100.6725) after installing the preview cumulative update (KB5065789) dated September 2025 for x64-based systems.

I have performed extensive diagnostics to rule out common hardware or software conflicts, including:

Full Disk Check (CHKDSK): No errors were detected. The scan completed successfully in read-only mode, confirming the file system integrity.

Hard Drive Health Checks:

HD Tune Pro: No bad sectors detected.

  CrystalDiskInfo: All drives reported as "Good."
  

Despite these checks, I continue to experience the following critical issues:

1. Wi-Fi Adapter Failures

The Intel(R) Wi-Fi 6 AX200 160MHz adapter repeatedly encounters internal errors and fails to function properly.

Specific errors include:

"System determined the network adapter is not functioning correctly."

  "Refreshed time zone information, exit reason: 0. Current time zone bias: -480."
  
  This has disrupted applications like Steam and other internet-dependent services.
  

2. System Time and RTC Issues

The system time frequently resets during startup, with logs indicating:

"System time synchronized with the hardware clock."

  RTC time discrepancies and incorrect time zone offsets.
  
  Example log entry:
  
  text
  
  ```
  System time changed from 2025-10-06T03:10:36.841992300Z to 2025-10-06T03:29:40.500000000Z.  

Change reason: System time synchronized with the hardware clock.
```

3. COM Server Permission Errors

Application-specific permission issues related to CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}.

Error message:

text

Local activation permission not granted to user SID (S-1-5-21-...) for COM server application.  

4. Pluton-Windows Firmware Failure

The system fails to load Pluton-Windows firmware with status:

text

StatusCode: STATUS_SUCCESS, Reason: Failed to apply firmware.  

5. "Delayed Write Failed" Errors

Frequent pop-ups:

text

Windows - Delayed Write Failed: Exception Processing Message 0xc0000222 - Unexpected parameters.  

Given the complexity and interdependency of these issues, I believe they may stem from the recent update or underlying system conflicts. As someone with a technical background, I am eager to collaborate with your team to resolve these problems.

Request for Real-Time Assistance

Could we schedule a live chat or remote session to troubleshoot these issues in real time? I am available to provide additional logs, system details, or perform diagnostic steps as needed.

Thank you for your attention to this matter. I look forward to your response.

I created a local account to change the username in the user folder (during the initial system setup, I had used my Microsoft account, which caused the username to become the first five characters of my email address). Then, I deleted the Microsoft account data and signed back into the Microsoft account using the local account. As a result, an issue occurred with the username (it is not "my zhao"), even though my user folder displays "my zhao".

Thank you for the detailed follow-up — I appreciate how thoroughly you’ve already verified the hardware and storage integrity.

Based on your findings, the remaining issues point toward driver and firmware regressions introduced with KB5065789 (September 2025 preview) rather than hardware faults. Please try the following targeted steps:

Wi-Fi Adapter

• Roll back or reinstall the Intel® Wi-Fi 6 AX200 driver using the official package from Intel.
• After reinstalling, reset the network stack:

    netsh winsock reset
    netsh int ip reset
  

System Time / RTC

• Run:

    w32tm /query /status
    w32tm /resync
  

• Confirm your BIOS firmware is current and that Pluton/Secure Time is enabled. Some 24H2 devices required firmware updates to stabilize RTC synchronization.

Pluton Firmware Failure

• Check Event Viewer → System → Source: Firmware for detailed Pluton entries.
• If failures persist, temporarily disable Pluton in BIOS to confirm whether it’s causing driver initialization issues. Re-enable afterward for security.

Regression Check

Since the behavior started after installing KB5065789, please uninstall it to validate:

wusa /uninstall /kb:5065789

and restart. If system stability returns, that confirms a regression introduced in the preview build.

---

For advanced diagnostics or to open a remote troubleshooting session with Microsoft Support, please submit a case via: https://support.serviceshub.microsoft.com/supportforbusiness/create

---

Hope this helps with your problem.

https://support.serviceshub.microsoft.com/supportforbusiness/createI am unable to open this link (perhaps it's for enterprise support? Also, as I am in China, I do not have a U.S. ID or phone number). I can only access community support.

I think you're very helpful. Is there any way we can have a real-time conversation?

The uninstallation of update KB5065789 failed. After I installed the latest Intel drivers, the network issues were resolved. However, even after performing your suggested steps (To fix: Open Component Services → dcomcnfg......), the following application-specific permission issue persists:

"Application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

(Actually, the option to modify this is grayed out and cannot be selected.)

Additionally, new issues have appeared:

• Event 556: The system session has changed from 6 to 8. / The system session has changed from 1 to 2.

Reason: Unknown / Reason: SxTransition

BootId: 29

Could not find the description for Event ID 26 from source Application Popup. The component that raised this event is not installed on the local computer, or the installation is damaged. You can install or repair the component on the local computer. If the event originated from another computer, the display information must be saved with the event. The following information was included with the event: \SystemRoot\system32\drivers\XLGuard.sys failed to load. The message resource is present, but the message was not found in the message table.

The GameDVR and Broadcast User Service_64d46 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

DCOM encountered error "1053" while attempting to start the service BcastDVRUserService_64d46 with parameters "Unavailable" to run the server: Windows.Media.Capture.Internal.AppCaptureShell. The connection to the GameDVR and Broadcast User Service_64d46 service timed out (30000 milliseconds).

User MYZHAO\my zhao attempted to restart/shutdown computer MYZHAO but failed. (What's going on here?)

The following boot-start or system-start drivers did not load: dam, EhStorClass, uiomap, WinSetupMon, XLGuard.

The default transaction resource manager on volume D: encountered a non-retryable error and could not start. The data contains an error code.

Corruption was found in the file system structure on volume D:. The exact nature of the corruption is unknown. The file system structures need to be scanned and repaired offline.

This is very contradictory...

The following might be potential time error sources (Time-Service):

The NtpClient was unable to set a manual peer to use as a time source because of a DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the retry interval thereafter. The error was: No such host is known. (0x80072AF9).

The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment are unsupported and has stopped. This is expected behavior for VMICTimeProvider in non-HyperV guest environments. It might also be normal for the current provider in the current operating environment.

The NtpClient was unable to set a manual peer to use as a time source because of a DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the retry interval thereafter. The error was: No such host is known. (0x80072AF9).

There are no Firmware-related entries in Event Viewer.

That's all the information. Please acknowledge this issue!I am unable to open this link (perhaps it's for enterprise support? Also, as I am in China, I do not have a U.S. ID or phone number). I can only access community support.

I think you're very helpful. Is there any way we can have a real-time conversation?

The uninstallation of update KB5065789 failed. After I installed the latest Intel drivers, the network issues were resolved. However, even after performing your suggested steps (To fix: Open Component Services → dcomcnfg......), the following application-specific permission issue persists:

"Application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

(Actually, the option to modify this is grayed out and cannot be selected.)

Additionally, new issues have appeared:

Event 556: The system session has changed from 6 to 8. / The system session has changed from 1 to 2.

Reason: Unknown / Reason: SxTransition

BootId: 29

Could not find the description for Event ID 26 from source Application Popup. The component that raised this event is not installed on the local computer, or the installation is damaged. You can install or repair the component on the local computer. If the event originated from another computer, the display information must be saved with the event. The following information was included with the event: \SystemRoot\system32\drivers\XLGuard.sys failed to load. The message resource is present, but the message was not found in the message table.

The GameDVR and Broadcast User Service_64d46 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

DCOM encountered error "1053" while attempting to start the service BcastDVRUserService_64d46 with parameters "Unavailable" to run the server: Windows.Media.Capture.Internal.AppCaptureShell. The connection to the GameDVR and Broadcast User Service_64d46 service timed out (30000 milliseconds).

User MYZHAO\my zhao attempted to restart/shutdown computer MYZHAO but failed. (What's going on here?)

The following boot-start or system-start drivers did not load: dam, EhStorClass, uiomap, WinSetupMon, XLGuard.

The default transaction resource manager on volume D: encountered a non-retryable error and could not start. The data contains an error code.

Corruption was found in the file system structure on volume D:. The exact nature of the corruption is unknown. The file system structures need to be scanned and repaired offline.

This is very contradictory...

The following might be potential time error sources (Time-Service):

The NtpClient was unable to set a manual peer to use as a time source because of a DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the retry interval thereafter. The error was: No such host is known. (0x80072AF9).

The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment are unsupported and has stopped. This is expected behavior for VMICTimeProvider in non-HyperV guest environments. It might also be normal for the current provider in the current operating environment.

The NtpClient was unable to set a manual peer to use as a time source because of a DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the retry interval thereafter. The error was: No such host is known. (0x80072AF9).

There are no Firmware-related entries in Event Viewer.

That's all the information. Please acknowledge this issue!

Thank you for the clarification. Unfortunately, since this is a public community forum, I’m not able to conduct real-time or remote sessions here.

However, if you still prefer to solve this problem through live chat, the following alternative link to contact Microsoft Support directly should work: https://support.microsoft.com/en-us/home/contact?SourceApp=smc2&ContactUsExperienceEntryPointAssetId=S.HP.SmcContactUsLanding

Here’s how to proceed:

1. Sign in with your personal Microsoft account.
2. In the “Describe your issue” box, enter something general like “Windows Update error after installing KB5065789.”
3. Scroll down and click “Contact Support.”
4. Select Windows under Products and services, then click Confirm. (You should see a screen like this one with “Tell us a little more about your problem.”)
5. This should route you to the real-time chat option with Microsoft Support.

This path should work globally.

As for the detailed follow-up, thank you. you’ve done a very thorough job isolating each layer of the problem.

It looks like some of the earlier issues (like network instability) are resolved, so I'll try to address persistent and new ones:

1. COM Permission (grayed-out options) The CLSID {6B3B8D23...} and APPID {4839DDB7...} correspond to system-level DCOM components that are protected by Windows permissions inheritance. When the “Edit” option is greyed out, it typically means the configuration is locked by TrustedInstaller.
   • You can technically take ownership via Registry Editor and adjust it under:

          HKEY_CLASSES_ROOT\CLSID\{6B3B8D23...}
     

   but this is best done under guided supervision since incorrect permission changes can cause cascading DCOM errors.
2. Driver and Service Load Failures The missing or failed drivers (XLGuard.sys, dam, uiomap, etc.) suggest there are remnants of either security software or services that didn’t transition properly after the update. The “XLGuard.sys” file, for example, is often tied to endpoint or antivirus components.
   • You may want to check Device Manager → View → Show Hidden Devices → Non-Plug and Play Drivers to confirm if any leftover or disabled components are listed.
   • If yes, remove them or reinstall their associated software cleanly.
3. Disk and Transaction Resource Errors (Volume D:) Since the system is now showing non-retryable NTFS transaction errors, these could be secondary symptoms from earlier disk paging failures.
   • Although you have tried this already and no errors came up then, if possible, please run a full offline chkdsk D: /f /r again during boot, and back up your data before continuing.
4. Time-Service and NTP Resolution The time.windows.com resolution errors and unsupported VMICTimeProvider warnings are generally benign, but repeated occurrences may indicate your Windows Time Service configuration was corrupted by the update.
   • Resetting it (w32tm /unregister → w32tm /register) is still a safe step to take, though your system clock will still depend on BIOS RTC stability.

Since these issues span several system areas — permissions, drivers, and file integrity — I’d recommend getting a manual review, either via the chat support link I shared earlier (if it works on your end) or through a trusted local technician from a trusted vendor.

Hope everything goes smoothly with your setup from here on.