Hi Alon,
I'm on this build and have no issues
at all. There are no Known Issues with
this build.
Have you run sfc /scannow?
Have you run the DISM /Online /Cleanup-Image /RestoreHealth?
Please report the issue in the Feedback
Hub using WIN+F.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I attempted to update my Windows 11 Insider Preview installation from build 26340.9616 to build 26340.9750.
After the update and signing in, Windows displays a completely grey screen with only the mouse cursor visible. The desktop does not load, and the taskbar and Start menu are missing.
Task Manager remains accessible, but restarting the computer has not resolved the issue. This appears to have started after the update to build 26340.9750.
Windows boots and allows me to sign in.
The desktop remains grey, with only the mouse cursor visible.
The taskbar and Start menu do not appear.
Task Manager works.
Launching explorer.exe through Task Manager does not restore the desktop.
Restarting the computer does not fix the problem.
I have attempted the following troubleshooting steps:
Restarted the computer multiple times.
Attempted to relaunch Windows Explorer through Task Manager.
Attempted to open Recovery settings using ms-settings:recovery.
Received File system error (-2147219200) when attempting to access Recovery settings.
Attempted DISM-based Windows image repair troubleshooting, but the issue remains unresolved.
I want to use Settings → System → Recovery → Fix problems using Windows Update → Reinstall now to reinstall the current Windows installation while preserving my personal files, applications, and settings.
However, the Recovery settings page fails to open because of the file system error. I need an officially supported way to access this repair option without relying on the broken Settings interface.
Is the grey-screen issue a known regression in build 26340.9750 when upgrading from build 26340.9616?
Why does Windows fail to initialize the desktop even though Task Manager remains accessible?
Is there a way to invoke the Reinstall now repair operation without opening Settings?
What is the recommended recovery procedure that avoids losing personal files, installed applications, and settings?
Is it possible to recover the existing installation or roll back the update without performing a clean installation?
Please investigate whether this is an issue with build 26340.9750 and provide a recovery method that does not require resetting the PC or reinstalling Windows from scratch.
Hi Alon,
I'm on this build and have no issues
at all. There are no Known Issues with
this build.
Have you run sfc /scannow?
Have you run the DISM /Online /Cleanup-Image /RestoreHealth?
Please report the issue in the Feedback
Hub using WIN+F.
I managed to identify the cause of the grey screen after further troubleshooting.
I captured and analyzed an explorer.exe crash dump using WinDbg. The crash occurs in SettingsHandlers_DesktopTaskbar.dll during taskbar initialization.
Crash details:
Faulting application: explorer.exe
Faulting module: SettingsHandlers_DesktopTaskbar.dll
Exception code: 0xc0000409
Fault offset: 0x000000000003a274
Related function: DesktopTaskbarSettingsSingleton::EnsureAssistantManager
The investigation led me to ViVeTool feature ID 58381341, identified as SystemComposer. It had a User-priority override forcing the feature to be enabled.
Resetting this override from an elevated Command Prompt using the following command restored the desktop, taskbar, and Start menu:
ViVeTool.exe /reset /id:58381341 /priority:8
However, I discovered another problem. Resetting this feature also removes the new WinUI 3 Windows Search experience from my system. When I re-enabled feature 58381341, Explorer immediately started crashing again and the grey screen returned.
This strongly suggests a conflict between the forced SystemComposer feature and Explorer's taskbar initialization on my current configuration of build 26340.9750.
For now, resetting the feature is the only workaround I have verified that restores a usable desktop. I have not found a way to keep the new Search experience enabled without reproducing the crash.
This also provides a more specific explanation for the original issue than general Windows image corruption. sfc /scannow found no integrity violations, although DISM previously failed with error 0x800F0915.
Could the Windows Insider team investigate this interaction and clarify whether it is a known issue with build 26340.9750? Ideally, the new Search experience should not cause Explorer to crash, and users should not have to disable an experimental feature to keep the desktop working.
Hi Alon,
This might be a prime example as to
why Insiders have always been advised
not to play with vivetool on Insider builds.
No one from Microsoft is going to investigate
your issue except on the Feedback Hub.