Removing "Recommended" from Start Menu on Windows 11 22H2 Pro

I have no idea how it works when you have ExplorerPatcher installed. This setup was created for users who didn't want ExplorerPatcher, and running a clean Windows.

My only suggestion is change the script's delay from 3 to 5 seconds, if Start Menu is taking too long to start up.
Code: 
Start-Sleep -Seconds 5
 
I don't use ExplorerPatcher (its no longer supported).

Seems there is a conflict between the script and the app StartAllBack - that's what I am using to bring back an old taskbar.
 
Last edited:
That's all on StartAllBack. The script just enables the GPO to hide Recommended apps, which normally only applies to EDU or Enterprise editions.
StartAllBack would have the same problem on a real EDU/Enterprise system.

ExplorerPatcher is supported, but it's a single dev project and it takes him a long time to keep up with recent Windows changes.
Good news, he just released today.
 
alias
Using it since the beginning & it is still 90% working all the time, for the other 10% it's a hit or miss
sometimes after reboot, the script won't run/start automatically, I've to manually start the task from task scheduler.

Using: Win11 Pro 22H2 21623.1344 x64

Last I shared some suggestions here on 3rd Oct 2022, not sure after that whether garlin applied any of those my shared feedback or update/modify anything or not because I am using the same old version since Oct 2022
 
The script is straightforward. I can only support SKU's which slmgr is allowed to switch keys, this rules out several SKU's.

Everything else is timing-based. When a logon task starts is slightly random, and it depends if your environment loads other processes in the background. You must kill StartMenuExperienceHost, and wait for it to restart, before reverting to the original SKU.

Just because the new Start Menu starts up, doesn't mean it's run the SKU check yet. There may be many things happening on logon, which slow the entire PC down. The only thing you can do is to extend the Start-Sleep delay by extra seconds. But I'd rather avoid triggering other Windows problems by keeping that delay as short as necessary.

Any risk is up to the user, so I favor the cautious approach even if it's not perfect.
 
You must log in or register to reply here.
Back
Top