Search results

So there's a few options here: If you think about it, it's silly to add currentuser entries before the first login. Therefore it follows that NTLite delete all those entries if added to the registry portion or before login portion in post-setup. This will prevent lots of problems for users. All...

Confirmed, the confirmed suspect(s) are: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Search] "CortanaConsent"=dword:00000000 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Start] "ShowRecentList"=dword:00000000 End of...

Wrong again apparently, these entries vindicated: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\SettingSync] "SyncPolicy"=dword:00000005 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\SettingSync\Groups\Personalization] "Enabled"=dword:00000000...

The offender has been confirmed to be here: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CDP] "RomeSdkChannelUserAuthzPolicy"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Search]...

LMAO this is one elusive MOFO, my stab at it failed as well. Namely, the following maintains start menu and search function: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001...

Good try, but that wasn't it. I'm developing my own theory, let's see.

When applying add.reg on the post-setup page, the issue goes away, start menu and search work. Good I will try just keeping those entries you have mentioned.

I have re-affirmed that the offender is in here: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive] "PreventNetworkTrafficPreUserSignIn"=dword:00000001...

Scratch that last, offending bits superseed last reply Consequently, the two tests I just did are useless and I have learned nothing.

I will test that momentarily, the offending bits appear to be in here: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\activity] "Value"="Deny"...

The offender is somewhere in here: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive] "PreventNetworkTrafficPreUserSignIn"=dword:00000001...

When the following reg file is applied, Start Menu works; this is good news for Nuhi, Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "ValidateAdminCodeSignatures"=dword:00000000 Applying halving algorithm

Suspect vindicated; issue persists with add.reg even with that entry removed.

I have a potential suspect, [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DusmSvc\Settings] "DisableSystemBucket"=dword:00000001

Confirmed. As previously stated, when add.reg is applied post setup, the start menu and search function remain intact. Examining add.reg closely now.

add.reg is the only offending file - debugging continuing

so, add.reg is an offending file, let's see if it is the only offending file.

ok so with the 3 postsetup: unlimited accounts, hibernation off and compression....all is fine...debugging commencing.

Ill tell you what, let's just apply the commands without the additional files see if that works and if it does then that would warrant further debugging on my behalf.

No I have not because it doesn't seem to make sense. The files themselves are ok, proven by post setup manual application and restart. So something about the software interacting with LTSC 2021 IoT, I believe is causing the problem.