You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-server/backup-and-storage/windows-server-mpio-troubleshooting.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,9 +150,9 @@ Use this checklist for systematic troubleshooting.
150
150
151
151
The following sections describe the most common issues, and how to fix them.
152
152
153
-
### Windows Server 2022 or 2019: VM IO performance degrades when Hyper-V uses resilient change tracking (RCT) is in use
153
+
### Windows Server 2022 or 2019: VM IO performance degrades when Hyper-V uses resilient change tracking (RCT)
154
154
155
-
If you experience this issue, make sure that your computers are up to date. The [October 23, 2025—KB5070884 (OS Build 20348.4297)](https://support.microsoft.com/en-us/topic/october-23-2025-kb5070884-os-build-20348-4297-out-of-band-9c001fdc-f0d2-4636-87bb-494a59da55d0) update and subsequent updates contain a fix for this issue.
155
+
If you experience this issue, make sure that your computers are up to date. The [October 23, 2025—KB5070884 (OS Build 20348.4297)](https://support.microsoft.com/topic/october-23-2025-kb5070884-os-build-20348-4297-out-of-band-9c001fdc-f0d2-4636-87bb-494a59da55d0) update and subsequent updates contain a fix for this issue.
156
156
157
157
> [!NOTE]
158
158
> After you install this update, VMs that were previously backed up by using a host-level backup application might not be able to start. To fix this issue, delete any .rct and .mrt files that are associated with the affected virtual hard disks. Then, try again to start the VMs. If the issue persists, contact Microsoft Support.
@@ -210,7 +210,7 @@ To fix this issue, follow these steps:
210
210
1. Use Disk Management or diskpart to bring the missing disks online.
211
211
212
212
1. To review the "Favorite Targets" list, use the iSCSI Initiator tool (In the search bar, type *iscsiocpl*, select **iSCI Initiator** in the search results, and then select **Favorite Targets**.
213
-
213
+
214
214
### MPIO is in a degraded state, slow or unresponsive during failover
215
215
216
216
During a failover, you might observe delays that exceed 30 seconds. You also observe IO error messages, and messages such as "MPIO is in a degraded state." You might also observe the following events:
@@ -324,12 +324,12 @@ To fix this issue, follow these steps:
324
324
| Symptom | Cause | Resolution |
325
325
| --- | --- | --- |
326
326
| Disk missing in MPIO properties and Disk Mgmt | Zoning or DSM conflict | Check Device Manager, remove ghost devices, reinstall MPIO, restart |
327
-
| Event IDs 153/129/11 | Path loss, driver/firm| Update firmware or drivers, set MPIO policy, check physical connectivity |
327
+
| Event IDs 153/129/11 | Path loss, driver or firmware issue| Update firmware or drivers, set MPIO policy, check physical connectivity |
0 commit comments