Replies: 1 comment
|
I’d treat this as a Start/Search shell failure after the upgrade first, not as proof that the hardware bypass itself caused it. The immediate goal is to stop adding more fix scripts and find out whether the break is per-user or system-wide. Before reverting to Windows 10, I would reduce it to three checks:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
If DISM/SFC do not change anything, create a new local Windows user and test Start/Search there. If it works in a new user, the upgrade left your user profile shell state broken. If it fails for every user, it is more likely a system component or tweak/removal problem. Since this is in the FlyOOBE repo, also check whether any debloat/tweak step removed WebView2, Search, Windows Shell Experience components, or input/IME services. Start search depends on more than just the Start menu process, and running more cleanup scripts can make the state harder to diagnose. The key result to share back is whether a fresh local user has working Start/Search, plus any Event Viewer crash for those shell/search processes and the FlyOOBE options you applied. |
Uh oh!
There was an error while loading. Please reload this page.
I just upgraded from Win 10 to 11, all is working except the start menu.
Here are the glitches that I experienced:
What do I do? I've been looking around to fix it, tried the tutorials out there, tried the scripts. Nothing worked.
Kinda weird I can't upgrade to Win 11 when my PC hardware fits the requirement lol. Anyway, I'll just revert back to Win 10 I guess.
All reactions