Windows 11

not as good as 3.1 , but as Necrosaro said, debloat it, pray to god they don't screw it up with the CU's and see what happens.

My only gripes with the whole M$ corporation is adding crap no-one asks for ( Edge , chatgpt, sidebar ........... the list goes on )
 
Taosd said:
not as good as 3.1 , but as Necrosaro said, debloat it, pray to god they don't screw it up with the CU's and see what happens.

My only gripes with the whole M$ corporation is adding crap no-one asks for ( Edge , chatgpt, sidebar ........... the list goes on )
Click to expand...
Here I am with edge......I will see myself out haha
 
I think that if you want to be completely free from Windows' misfortunes, you have to do the same as the rest of the flock and pledge your brain to a smartphone and live on in complete ignorance :rolleyes:
 
Well - it's plague or cholera with Windows.
Fortunately, NTL is the vaccine, although for some there may be side effects :cool:
 
have you heard about atlasos? another windows edited crap like tinywindows etc and again its promoted by linus tech tips...
 
crypticus said:
have you heard about atlasos? another windows edited crap like tinywindows etc and again its promoted by linus tech tips...
Click to expand...
They have done that before, also had one on Ntlite before as well. He just thought it was God's gift to windows 10 unfortunately others will come here asking questions pertaining to it.
 
What is the Ntlite option (toggle) for this (new) Windows Update settings?
1.png

Checked with W11 Pro 22624.1635, can't find it in the NTLite options (latest v9213)
2.png

Is this option not implemented /added yet in NTlite?
 
SM03 said:
What is the Ntlite option (toggle) for this (new) Windows Update settings?
View attachment 9658

Checked with W11 Pro 22624.1635, can't find it in the NTLite options (latest v9213)
Click to expand...
SM03 said:
Is this option not implemented /added yet in NTlite?
Click to expand...
Not yet.

You can search the running NTLite process with Process Explorer. Run Process Explorer as Admin, select NTLite.exe and look at Properties / Strings / Memory. Find "[reg key name]"

When you can't find it, NTLite doesn't support it. All reg keys that NTLite creates must be hard-coded inside the program.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]
"IsContinuousInnovationOptedIn"=dword:00000001

This feature needs to be enabled by Vivetool/mach2. So it's too early right now for NTLite since it doesn't work by default (yet).
 
garlin said:
This feature needs to be enabled by Vivetool/mach2. So it's too early right now for NTLite since it doesn't work by default (yet).
Click to expand...
Since 22621.1635, it's default now for all users.

and this feature can't be enabled while the target release version is there in registry, in order to work this reg hack, the reg entries of target release version must be deleted.

Tried & tested.

Also, there's a bug in NTLite for the TargetRelease toggle,
even though I kept that toggle untouched (default),
1.png
still after creating an ISO, it automatically set to 23H2
2.png

So, I've to create this reg & add this in order to get that function to work with NTLite-modded ISO

Code: 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"TargetReleaseVersion"=-
"TargetReleaseVersionInfo"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]
"IsContinuousInnovationOptedIn"=dword:00000001



Tagging nuhi to highlight this issue, & hope he'll fix this in the upcoming build.
 
Last edited:
I would agree with Bree's spin on the ElevenForum thread. TargetReleaseVersion needs to override all other WU settings, otherwise it's not effective in blocking unwanted Feature updates.

Does NTLite unexpectedly tamper with TargetReleaseVersion?

I couldn't repeat this behavior on v9213 and 22624.1680 (UUP Dump). Changed the WU settings to match your screenshot, applied changes, and reloaded the saved image. Unless you have a different setup that can recreate this example.

Code: 
            <TweakGroup name="WindowsUpdate">
                <Tweak name="Preferences\ModelDownloadAllowed">1</Tweak>
                <Tweak name="DeliveryOptimization\DODownloadMode">3</Tweak>
                <Tweak name="Settings\AllowAutoWindowsUpdateDownloadOverMeteredNetwork">1</Tweak>
                <Tweak name="7971f918-a847-4430-9279-4a52d1efe18d\RegisterWithAU">0</Tweak>
                <Tweak name="MRT\DontOfferThroughWUAU">0</Tweak>
                <Tweak name="Settings\IsExpedited">1</Tweak>
                <Tweak name="Settings\RestartNotificationsAllowed2">1</Tweak>
                <Tweak name="AU\AUOptions">4</Tweak>
            </TweakGroup>
 

Attachments

  • Windows 10 x64-2023-04-30-15-43-55.png
    Windows 10 x64-2023-04-30-15-43-55.png
    128 KB
  • Windows 10 x64-2023-04-30-15-54-20.png
    Windows 10 x64-2023-04-30-15-54-20.png
    125.7 KB
garlin said:
I would agree with Bree's spin on the ElevenForum thread. TargetReleaseVersion needs to override all other WU settings, otherwise it's not effective in blocking unwanted Feature updates.

Does NTLite unexpectedly tamper with TargetReleaseVersion?

I couldn't repeat this behavior on v9213 and 22624.1680 (UUP Dump). Changed the WU settings to match your screenshot, applied changes, and reloaded the saved image. Unless you have a different setup that can recreate this example.

Code: 
            <TweakGroup name="WindowsUpdate">
                <Tweak name="Preferences\ModelDownloadAllowed">1</Tweak>
                <Tweak name="DeliveryOptimization\DODownloadMode">3</Tweak>
                <Tweak name="Settings\AllowAutoWindowsUpdateDownloadOverMeteredNetwork">1</Tweak>
                <Tweak name="7971f918-a847-4430-9279-4a52d1efe18d\RegisterWithAU">0</Tweak>
                <Tweak name="MRT\DontOfferThroughWUAU">0</Tweak>
                <Tweak name="Settings\IsExpedited">1</Tweak>
                <Tweak name="Settings\RestartNotificationsAllowed2">1</Tweak>
                <Tweak name="AU\AUOptions">4</Tweak>
            </TweakGroup>
Click to expand...
my UUPD ISO was 22624.1635 (as it's clearly visible in the SS I shared here earlier), not 22624.1680 like yours
Not sure whether that makes any difference or not

& In my (2x) testing, the result is the same as I described earlier.
 
UUP dump doesn't have 22624.1635, which is why I chose .1680. Not that it would matter.
The next question is can you recreate the bug using 22621.1635 or another build?
 
Another way to force "in the middle" test updates.
Unfortunately MS dont update GPO/ reg settings in the tempo they integrate how they can exploit users.
 
garlin said:
UUP dump doesn't have 22624.1635, which is why I chose .1680. Not that it would matter.
The next question is can you recreate the bug using 22621.1635 or another build?
Click to expand...
tried & tested today with the new 9215 beta version of NTlite where nuhi added support for the Get the latest updates as soon as they’re available

1. Fresh UUP 22621.1635 ISO loaded in NTL before applying preset or modding anything (with default settings)
a.png

2. Loaded my PRESET where that TargetRelease option is untouched
[Ignore the wrong Preset name showing here, that'd be 'GM 22621.1635' instead of 'GM 22624.1635', forgot to rename it]
b.png

3. Complied the ISO & then reload the modded ISO in NTLite, TargetRelease set to 23H2 (like I reported here earlier)
c.png

Tested in Virtual Machine as well, here're the screenshots
- 'Get the latest updates as soon as they’re available' is disabled despite selecting this as Enable in NTLite settings (see above screenshot #3)
1.png

here're the screenshot from the registry editor
- Targetrelease reg entities are preset despite leave that option default (untouched) in NTLite settings

2.png

So the reg key to enabling the 'Get the latest updates as soon as they’re available' is preset in the registry,
but not working as Targetrelease reg entities are preset
3.png
 

Attachments

  • 2.png
    2.png
    657 KB
You must log in or register to reply here.
Back
Top