Hello,
Rolling back an annual feature update in Windows 11 is not something you can do with a simple DISM command or a lightweight MDM policy. The rollback mechanism is handled by the OS uninstall stack itself, and it requires that the Windows.old folder created during the upgrade is still present. Once that folder has been cleaned up (either manually or automatically after 10 days by default), rollback is no longer possible.
The supported command‑line method is to use setup.exe with the /uninstall switch, or invoke the rollback through the recovery environment. Specifically, you can run:
%windir%\system32\setup.exe /uninstall /system /quiet /noreboot
This command initiates the uninstall of the latest feature update and reverts the system to the previous OS build, provided the rollback files are intact. It must be executed with administrative rights, and it will only succeed if the Windows.old directory has not been purged.
From an MDM perspective, Intune does not expose a direct policy to force OS rollback. The only supported remote option is to trigger the rollback via Update/Feature Update Uninstall CSP (Update/Uninstall/FeatureUpdate). This CSP is available in Windows 11 and allows an MDM solution to call the rollback API. You would configure a custom OMA‑URI policy pointing to:
./Vendor/MSFT/Update/Uninstall/FeatureUpdate
with the value set to the target feature update version you want to uninstall. This is the documented way to remotely roll back a feature update across managed devices.
In short, if you need to fix the network adapter regression immediately, you should either run setup.exe /uninstall locally or push the uninstall through Intune using the Update CSP. There is no supported DISM command to roll back a feature update; DISM only manages component cleanup, not OS version rollback.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.