Windows 10: Bloatware free "fresh start" in 20H2?

Hi, I have a new HP desktop that is on version 20H2. Using "reset this PC" for a clean bloatware free reinstall and the tutorial I am following from the May 2020 update speaks of a toggle under "additional settings" > "change settings" that said: "restore preinstalled apps?" yes or no. This toggle no longer appears in 20H2, what are the proper selections to keep the reinstall from restoring preinstalled apps in 20H2? Thanks!

:)

 

Windows 10 fresh start

The main aim of Fresh start as the name suggests is to start fresh your Windows, by removing all the factory bloatware that came preinstalled with the computer.

https://www.microsoft.com/software-download/win...

 

Have New 20H2 Start (NOW)

The 20H2 Start Menu can be 'released' from within 20H1.

You will, still, do 20H2 via WU in October, BUT can have the new 20H2 Start Menu, now by doing the following:

1. Open up Notepad.
2. Paste the following text:
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\0\2093230218]
   
   "EnabledState"=dword:00000002
   
   "EnabledStateOptions"=dword:00000000
   
   
3. Save the file as 'Start Menu.reg'.
4. Run the file.
5. Reboot
   
   
   
   

now and, still, OS Build 19041.508

Cheers,

Drew

 

Windows 20H2 Domain Join breaks Start Menu

Upon doing a recovery of a system to start with a clean slate, it now installs 20H2. All looks good. Start menu and taskbar look normal.

We then join it to our domain. Upon reboot, the start menu will not show the applications list. No option to expose it. Start menu settings shows "Show app list in start menu" greyed out. Trying to log out shows as the only option "Change Account Settings"
Right clicking on taskbar, the task manager is greyed out. We checked the GPO for the start menu app list removal and it is listed as "not configured". Tried setting the local policy to different settings with no effect.

Read thru the event viewer and nothing jumped out as related.

All very strange. We are a hospital that has been running this AD schema for a number of years. It is based on Windows Server 2012 R2. We have over 250 systems with multiple levels of windows 10 Pro systems in production, with none of them showing these
behaviors. At this point, 20H2 is unusable for us.