I suspect the problem also affects the other "Folder - ...." settings.
EDIT:
...just went through the changelogs and found this:
June 7, 2022 changelog for v.2.3.6.8775
FIX: Settings: Removed non-Policy options for the Start folders settings as they are not working if unforced
No, no I do not touch this setting after Windows installation.
All my test were done in an offline VM.
In the latest NTLite you have 3 options Enabled (Policy), Disabled (Policy) and Default (User)
In the old NTLite i might remember there was just Enabled, Disabled & Default. (can't verify that...
There is a preset conversion bug from version 2.3.2.8526 to 2.3.7.8826
I used the setting:
<TweakGroup name="StartTweaks">
<Tweak name="Start\AllowPinnedFolderSettings">3</Tweak>
</TweakGroup>
That tweak forced the settings icon to show up on the Start Menu (Windows 11)
After...
If you don't speak about special RAID-Controllers you should be good with the Windows built in standard drivers.
The only drivers i usually integrate are the new Intel VMD (boot.wim) as some newer Laptops need them or Windows Setup can't find any SSD...
Basically i know of 3 ways (2 offline & 1 online) to configure this setting in NTLite:
"DisableWindowsConsumerFeatures"=dword:00000001
1. Configure - Settings -> BAD (sync broken)
2. Integrate - Registry -> WORKS (sync not broken)
3. Automate - Post-Setup -> WORKS (sync not broken)
I've tested...
Nuhi,
the bug is still present in current NTLite (2.3.0.8396)
Testing now with Windows 11 but makes no difference. Attached a screenshot of the broken sync.
In the WOW6432Node there exist only one DWORD32 key.
Hi Nuhi,
well, i'll describe how to reproduce the issue:
I always use a untouched MSDN Windows 10 Business Edition ISO image for customization's.
Loading the Enterprise Edition in NTLite then i call my preset which include:
<Tweak name="CloudContent\DisableWindowsConsumerFeatures">1</Tweak>
I...
When you disable "DisableWindowsConsumerFeatures" setting under Privacy Setting - this will break the shared Policy key sync in the registry! (verified)
Details:
Key "HKEY_LOCAL_MACHINE\SOFTWARE\Policies"
is a shared location with
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies"...
Sorry....i can't figure out how this should work if you have different hardware devices...like Dell Latitude 7400, 5401, 5310,...
Your dynamic driver guide is based on OS architecture???
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.