GeUk
Member
- Local time
- 11:55 AM
- Posts
- 1
- OS
- Windows 11
I want to share a solution to a Windows upgrade failure that took me some time to diagnose and isn’t documented anywhere. If your upgrade to Windows 11 (including 24H2 or 25H2) fails with error 0xD000000D during “Start Monitoring Driver” this may be the cause.
A key clue was found in setuperr.log:
WinSetupMon::GetStablePath: Failed NtDeviceIoControlFile [\??\C:\Drive_D] (0xC000000D)
WsmInstall: Failed to create driver config; hr = 0xd000000d
SETUPMON: Failed to install/start monitoring driver. Error: 0xD000000D
These errors indicate that Windows Setup could not attach its monitoring filter driver to one of the mounted volumes, which is a fatal condition for the upgrade.
The root cause turned out to be a persistent SUBST drive mapping created in the registry under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices.
Mine looked like this:
"D:"="\\??\\C:\Drive_D".
This creates a fake D: drive. During an upgrade, Windows Setup must attach its monitoring driver to every mounted volume. SUBST drives aren’t real volumes and return invalid responses, which causes the monitoring driver to fail and the entire upgrade to abort.
The fix was simple once identified. Before running the upgrade, I removed the mapping for the current session using:
subst D: /d.
After that, the upgrade to Windows 11 25H2 completed successfully on the first try.
A key clue was found in setuperr.log:
WinSetupMon::GetStablePath: Failed NtDeviceIoControlFile [\??\C:\Drive_D] (0xC000000D)
WsmInstall: Failed to create driver config; hr = 0xd000000d
SETUPMON: Failed to install/start monitoring driver. Error: 0xD000000D
These errors indicate that Windows Setup could not attach its monitoring filter driver to one of the mounted volumes, which is a fatal condition for the upgrade.
The root cause turned out to be a persistent SUBST drive mapping created in the registry under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices.
Mine looked like this:
"D:"="\\??\\C:\Drive_D".
This creates a fake D: drive. During an upgrade, Windows Setup must attach its monitoring driver to every mounted volume. SUBST drives aren’t real volumes and return invalid responses, which causes the monitoring driver to fail and the entire upgrade to abort.
The fix was simple once identified. Before running the upgrade, I removed the mapping for the current session using:
subst D: /d.
After that, the upgrade to Windows 11 25H2 completed successfully on the first try.
- Windows Build/Version
- Windows 11
My Computer
System One
-
- OS
- Windows 11
