Start Menu Critical Error question

[digitalis99]

Howdy all, first time poster, long time Windows tweaker. I've built a fairly minimalist installer using the most recent NTLite and Win10 Home 21H1. I did integrate the available Windows updates into my image prior to further modification with NTLite. I've also imported some of the reg hacks and post-setup stuff from MR's work, even though his stuff was originally geared for LTSC builds.

After installing my custom image, clicking the Start Menu causes a "Critical Error" window to show up that says, "Your Start menu isn't working. We'll try to fix it the next time you sign in." It only displays a "Sign out now" button.

Questions:
1) I've backed out any/all of the MR tweaks that I thought might have an impact, but should I remove all the rest just to see what happens?
2) Has anyone else encountered this with an updated 21H1 build?
3) Where would you start to look to resolve this kind of problem?

I have the Windows Store stuff disabled, as I don't need it. I'm wondering if that broke some aspect of the tiles that normally display, and that's causing the error. Any other suggestions welcome.

 

[nipponico]

Do you want to make the Start menu work again or prevent the error message?
If first, verify to not uncheck the Start Menu component.
If second, you can use a utility to disable the Windows key and the mouse click on Windows flag.
I follow the second way...

 

[francis11]

Not seen the preset - but be sure keep ShellExperienceHost and as proposed Start Menu or/ and at least use the Compatibility options in the Components removal section of NTL (upper left corner). When be sure everything works without tweaks it's time to start "play" from there.

 

[digitalis99]

I'd like to make the Start menu work again. The Start menu component is checked, locked by compatibility, as is the ShellExperienceHost. I have made use of the compatibility options in NTL, so that should help.

 

[francis11]

Your preset would be helping to look into the issue.

 

[digitalis99]

Absolutely! I just ran a build without any of the reg tweaks or post-install scripts, and the Start Menu is still broken. That preset is attached.

 

[francis11]

Hi - after testing your preset START (needed for startmenu to work) was not showing up in taskmanager. When try to start (StartMenuExperienceHost.exe) from Windows\Systemapps an error came up show the process stopped coz of stack buffer underrun.
Tried change preset and set Compatibility with OOBE and then it seems to work. Startmenu is opening and START process in taskmanager as well. Attached image show StartMenu open after set Compatibility with OOBE too.

 

[digitalis99]

Cool! Thanks for tracking that down. Seems like NTL is broken somewhere, then. Either it's not enabling enough for the Start Menu component to work, or it should add a Start Menu compatibility option as well. Glad you were able to track it down, though!

 

[francis11]

Thanks.
NTL warns you with red text before you start your preset on the Apply page. This should be a hint that your configuration might not work as intended.
Autopilot alone was not the cause, which is one of the components OOBE Compatibility protects + many others.
Keep in mind that Compatibility are components that are protected due to the experience of many users over the years.

 

[getdown71]

Hi - after testing your preset START (needed for startmenu to work) was not showing up in taskmanager. When try to start (StartMenuExperienceHost.exe) from Windows\Systemapps an error came up show the process stopped coz of stack buffer underrun.
Tried change preset and set Compatibility with OOBE and then it seems to work. Startmenu is opening and START process in taskmanager as well. Attached image show StartMenu open after set Compatibility with OOBE too.

Thanks for the hint here francis11 - How do I "Change preset and set Compatibility with OOBE" as I have yet work it out in my licenced version of NTLite. Cheers!

 

[garlin]

NTLite enforces Compatibility rules to protect key components from removal, if they're required for an important function.

If you're on the Components screen, click on the Compatibility icon in the top left corner. Each row of the Components listing will have the rules protecting that feature listed in the (right hand) Extra Info column. You cannot remove a component while it's protected.

To override it, uncheck the Compatibility rule(s) which are blocking removals. Some components may be protected by multiple rules, and you will need to uncheck all of them. Be aware, once you disable a rule -- all checking for that rule is disabled, even if it covers other components under the same rule. Use this feature carefully.

 

[getdown71]

NTLite enforces Compatibility rules to protect key components from removal, if they're required for an important function.

If you're on the Components screen, click on the Compatibility icon in the top left corner. Each row of the Components listing will have the rules protecting that feature listed in the (right hand) Extra Info column. You cannot remove a component while it's protected.

To override it, uncheck the Compatibility rule(s) which are blocking removals. Some components may be protected by multiple rules, and you will need to uncheck all of them. Be aware, once you disable a rule -- all checking for that rule is disabled, even if it covers other components under the same rule. Use this feature carefully.

Got it Garlin! Many thanks.