Hi Blaise Pascal Hirwa,
This behavior is consistent with a known issue introduced by recent Windows 11 Enterprise cumulative updates where the shell and application launch subsystem fails, leaving only Explorer functional. Since you’ve confirmed rollback works inconsistently, the most reliable preventive measure right now is to block deployment of the April 2026 cumulative update across the environment using WSUS or Intune update rings until Microsoft publishes a fixed build. For devices already impacted, if uninstalling the update does not restore functionality, the only supported recovery path short of a full reinstall is an in‑place upgrade repair using the latest ISO that predates the faulty update. Startup Repair and System Restore are not reliable in this scenario because the corruption is introduced at the servicing stack level.
As a preventive step, I recommend exporting a full system image (DISM /Capture-Image or enterprise backup) before applying future updates, and staging updates in a pilot ring to catch regressions early. Also verify that your EDR or endpoint security agents are not injecting DLLs into explorer.exe or winlogon.exe, as conflicts have been reported with certain AV/EDR drivers after cumulative updates. At this point, the best course is to hold updates, monitor Microsoft’s release notes for the next cumulative patch, and plan to re‑deploy once a hotfix is confirmed. If you need to stabilize affected systems immediately, the in‑place upgrade repair from ISO is the only supported alternative to a clean install.
If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Harry.