[FIXED] Windows Update is not shown in Settings

A

Alt68er

Member
Hi,
I just found out that in the settings of my NTlited Win11 the Windows Update is hidden caused by NTlite.
But what I could not find out is the item in the xml-file causing it.
Can someone please check my enclosed xml-file and tell me what I've done wrong and which line in the xml-file should be deleted or amended to not hide the Windows Update?
1000 thanks in advance.
Peter
 

Attachments

  • Win11 01dc017e_ohne_user.xml
    31.3 KB
WU is not broken but simply not shown in the settings so that I don't have manual access to it. The update(s) are working well.

I did some more tests and what I found is:

1. I never did a Group Policy setting about (non-)visibility of WU, but
2. there is a registry entry causing the non-appearance of the WU in the settings screen.

3. now I restored an old image of the system drive to force windows for installation of the latest kumulative update.
4. after Windows found and downloaded the latest update the registry entry still is there
5. after deleting this entry (see enclosed reg-file) the WU is visible in the settings....

6. now I did a restart of Windows for finalizing the update
7. the registry entry still disappears
8. I started NTlite to remove the re-installations and
9. during this procedure I monitored the registry and immediately before NTlite asked for a reboot of Windows this entry was created again...

For me this means that this registry entry is created by NTlite.

What is strange for me is that WU is not shown in the settings although the registry entry is not containing a setting for the WU....

Insofar my initial question is not quite correct; but: why is Windows hiding the WU although it is NOT stated in this registry entry? Is there something wrong with this registry entry?

A longer time ago I read a notice in a forum (don't remember in which one, sorry) about this entry and as per my memory there it was stated that the sequence of the entries in the registry entry is not correct and/or it contains an item which does not exist anymore...

Can it be that there is a very small bug in NTlite creating this entry?

I'm very excited to hear more comments.

Thank you in advance!

Peter
 

Attachments

  • settings_page_visibility.reg
    828 bytes
I'm pretty sure its about your reg entries and not about ntlite

<File>F:\SAMMLUNG\REGs INIs etc\Windows 10\ADMIN\HKLM + HKCR - div. Tweaks ADMIN.reg</File>
<File>F:\SAMMLUNG\REGs INIs etc\Windows 10\BENUTZER\HKCU + HKCR - div. Tweaks PRO USER.reg</File>
 
Last edited:
I knew that this or a similar answer will come and therefore wanted to attach these reg-files to my previous post, but forgot it.
But here they are.
If the reason is located here, please give me a hint. Thank you!
 

Attachments

  • HKLM + HKCR - div. Tweaks ADMIN.reg
    24.2 KB
  • HKCU + HKCR - div. Tweaks PRO USER.reg
    10.5 KB
NTLite didn't make this change, there is no Settings for it. And the UI doesn't allow for multiple options to be selected, or a text box in order to create SettingsPageVisibility's show/hide list.

I don't have a better explanation, but it's not NTLite.
 
I know it's annoying being asked this, but did you specifically try making a new iso using exactly the same settings, but do NOT add your reg files, and see if it works as you expected?

Since you said you deleted the key and it reappears again afterward, it tells me it's a policy key that is causing it.

Edit: updated reply after investigating more
 
Last edited:
Also, are you using any tweaks that change permissions of reg keys, that causes huge problems for some things and makes them error out in different ways.
 
garlin
After having checked it again and again I'm almost 100% sure that this entry is made by NTlite. The entries correspond to what I've disabled via NTlite.

@Hellbolvine
No, up to now I didn't create a new ISO without the reg-files. I'll do that now and post the result tomorrow.-

And: no, I don't use more tweaks than the ones shown in my reg-files, I don't use any tweaking tools, and I did not change any permissions to specific keys in the registry.
 
You're right. NTLite is creating this reg key, because you removed components. System Settings is monolithic (one app for all settings), and removing a component doesn't hide its matching screen.

delivery-optimization
easeofaccess-speechrecognition
gaming-broadcasting
gaming-gamebar
gaming-gamedvr
gaming-gamemode
gaming-trueplay
gaming-xboxnetworking
holographic-audio
maps
network-airplanemode
privacy-automaticfiledownloads
privacy-feedback
speech
Click to expand...

Reviewing the current MS docs, these three are undefined:
gaming-broadcasting
gaming-trueplay (deprecated in 1809)
gaming-xboxnetworking (deprecated?)
Click to expand...

The key value looks correctly formatted. More testing is required.
 
Is this the culprit?
<Feature enabled="no">WindowsUpdate</Feature>

I don't have Win 11 to test. I thought by Garlin's screenshot earlier though that he installed this preset and the update was working fine, so I thought we ruled out NTLite because of that?
 
No, that's the compatibility mode list.

When you read the preset, it's misleading unless you see the parent block.
Code: 
        <Compatibility protectHidden="true">
                <ComponentFeatures>
                        <Feature enabled="no">WindowsUpdate</Feature>
                </ComponentFeatures>
        </Compatibility>
 
FIXED: Removing "delivery-optimization" from the reg key restores WU. You have a temporary workaround.
nuhi is this a bug regression?
 
Thanks a lot for all your testing and further answers.
garlin
Thank you for having found out that removing the delivery-optimization will temporarily fix it.

I'm now believing that it's a Windows bug cause this setting should not hide the complete Update-section in the settings but only the sub-item "delivery-optimization".

Thank you so much for all your efforts!
 
garlin said:
FIXED: Removing "delivery-optimization" from the reg key restores WU. You have a temporary workaround.
nuhi is this a bug regression?
Click to expand...
Thanks for finding this.
That reg entry was there for a while, ever since that component was split.
There is no mistake, setting is simply not doing what it is supposed to, on Win11.
Tested it on Win10, works fine, needed a reboot to apply.

Will skip it on Win11 - and this is not the first time these kinds of bugs slipped into Win11.
Another one that I found that hides the WU page is the windowsinsider entry as well, that was silently fixed/skipped, again Win11.

Gonna report it to Microsoft somehow, even though it probably seems too minor of an issue for them to fix any time soon.
 
Win 11 really isn't going to be worth using for a few more years. Unfortunately in today's age developers and publishers push to get things released before they are ready, to save money. The status level that games, even triple A titles are released in today is easily comparable to an Alpha or Beta product 15-20 years ago. Anyone using Win 11 right now is really just a beta tester.
 
Last edited:
You must log in or register to reply here.
Back
Top