通过

升级至 Windows 11 25H2 后出现严重问题：磁盘错误、证书问题以及系统故障 尊敬的微软支持团队， 您好！ 在升级到 Windows 11 版本 25H2 后，我遇到了多个系统问题，包括但不限于：

my zhao 0 信誉分
2025-10-04T13:30:17.5933333+00:00

COM 服务器权限错误：应用程序特定的权限设置未授予 COM 服务器应用程序（具有 CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} 和 APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}）的“本地激活”权限给运行于应用程序容器“不可用 SID”（不可用）中的用户“myzhao\my zhao SID”（S-1-5-21-3192212609-1034257735-2234904885-1002）。

网络超时错误：

cp601.prod.do.dsp.mp.microsoft.com 的名称解析超时，因为所配置的 DNS 服务器均未作出响应。客户端进程 ID：14844。

msfwifiv6.3g.qq.com 的名称解析超时，因为所配置的 DNS 服务器均未作出响应。客户端进程 ID：2360。

延迟写入失败（数据丢失）：

Windows 无法保存文件 D： 目录下的“Mft”文件的所有数据。数据已丢失。

Windows 无法保存文件 D:\SteamLibrary\steamapps\downloading\227300 所有数据。数据已丢失。

Windows 无法保存文件 D：盘下的“Mft::$BITMAP”中的所有数据。数据已丢失。

设备与寻呼错误：

在分页过程中，在设备 \Device\Harddisk1\DR1 上检测到一个错误（该错误是循环性的）。

该系统未能将数据写入事务日志。可能会出现数据损坏的情况：卷标识：D：，设备名称：\Device\HarddiskVolume4。

故障状态：指定设备不存在。

设备详情：

型号：東芝 HDWD110

序列号：40LSV9YFS

接口类型：SATA

存储诊断错误（循环型）：

完成了一次失败的非读写型 SCSI 请求的响应处理。

完成了一次失败的上层页面写入请求。

开发人员技术 | 通用 Windows 平台 (UWP)
0 个注释

2 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Danny Nguyen (WICLOUD CORPORATION) 5,405 信誉分 Microsoft 外部员工 仲裁人
    2025-10-06T03:35:09.0766667+00:00

    Hi @my zhao ,

    Thank you for providing such a detailed report. From your logs, the issues you’re seeing after upgrading to Windows 11 version 25H2 appear to involve multiple layers — specifically storage subsystem errors, COM permission conflicts, and network resolution timeouts.

    Let’s address them in order of severity.

    1. Disk and Paging Errors (Critical)

    The repeated messages like:

    “Windows was unable to save all the data for the file D:$Mft…” “An error was detected on device \Device\Harddisk1\DR1 during paging.”

    indicate the storage device (TOSHIBA HDWD110) is either:

    • Experiencing hardware-level instability,
    • Or the upgrade triggered a driver/firmware incompatibility with the SATA controller.

    Recommended steps:

    1. Run a full disk check: 
         chkdsk D: /f /r

      This will scan and repair bad sectors; the process can take time.

    2. Check SMART health: 
         wmic diskdrive get status, model
      → If it reports anything other than OK, back up data immediately.
    3. Update SATA/Chipset/Storage drivers from your motherboard or OEM website — do not rely on Windows Update drivers for this case.

    If issues persist, test the drive on another system to rule out hardware failure.

    2. COM Server Permission Error

    The CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} corresponds to the RuntimeBroker service. This can appear after upgrades when DCOM permissions reset or user accounts lose local activation rights.

    To fix:

    1. Open Component Services → dcomcnfg.
    2. Navigate to: Component Services → Computers → My Computer → DCOM Config → RuntimeBroker
    3. Right-click → Properties → Security tab
    4. Under Launch and Activation Permissions, choose Edit → Add your user (e.g., myzhao) → grant Local Activation.

    Alternatively, you can reset permissions via:

    icacls %windir%\system32 /reset /t /c

    and restart the system.

    3. Network & Certificate Errors

    Timeouts like:

    “Name resolution for cp601.prod.do.dsp.mp.microsoft.com timed out…”

    suggest a DNS or certificate validation delay post-upgrade. This can happen if:

    • The network driver stack wasn’t fully reinitialized, or
    • Corrupt certificate cache interferes with Microsoft endpoints.

    Try:

    ipconfig /flushdns
netsh winsock reset
netsh int ip reset
certutil -urlcache * delete

    Then restart the PC and confirm the network adapter driver is the latest from your OEM.

    4. General Recommendation

    Given the combination of disk errors and post-upgrade instability, I recommend:

    • Backing up your data immediately.
    • Running: 
        sfc /scannow
  DISM /Online /Cleanup-Image /RestoreHealth
    • If corruption persists, consider performing a repair install of Windows 11 25H2 using the Media Creation Tool.

    If you can share the output of:

    chkdsk D:

    and

    slmgr /dlv

    we can narrow down whether this is a failing drive or a software corruption chain.

    Hope this helps. Feel free to reach out if you encounter any problem.

    1 个人认为此答案很有帮助。
  2. my zhao 0 信誉分
    2025-10-06T04:08:03.59+00:00

    Stage 1: Examining basic file system structure... 162048 file records processed. File verification completed. Phase duration (File record verification): 1.90 seconds. 3 large file records processed. Phase duration (Orphan file record recovery): 0.59 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.32 milliseconds.

    Stage 2: Examining file name linkage... 49 reparse records processed. 166372 index entries processed. Index verification completed. Phase duration (Index verification): 7.02 seconds. 0 unindexed files scanned. Phase duration (Orphan file reconnection): 9.72 milliseconds. 0 unindexed files recovered to the recycle bin. Phase duration (Orphan file recovery to recycle bin): 0.26 milliseconds. 49 reparse records processed. Phase duration (Reparse point and Object ID verification): 3.57 milliseconds.

    Stage 3: Examining security descriptors... Security descriptor verification completed. Phase duration (Security descriptor verification): 40.45 milliseconds. 2163 data files processed. Phase duration (Data attribute verification): 0.97 milliseconds. CHKDSK is verifying the Usn Journal... 66784 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 0.88 milliseconds.

    Windows has scanned the file system and found no problems. No further action is required.

    314570751 KB total disk space. 10764720 KB in 13999 files. 28076 KB in 2164 indexes. 0 KB in bad sectors. 238155 KB in use by the system. 65536 KB occupied by the log file. 303539800 KB available on disk.

    4096 bytes in each allocation unit. 78642687 total allocation units on the disk. 75884950 allocation units available on the disk. Total duration: 8.98 seconds (8983 ms).

    0 个注释

你的答案

提问者可以将答案标记为“已接受”，版主可以将答案标记为“已推荐”，这有助于用户了解答案是否解决了提问者的问题。