Strange (obscure) error in GPEdit on Windows 11 IoT ENT LTSC (24H2)

Sonicmojo

Member
Messages
97
Reaction score
9
Built a test ISO last week for a possible file server deployment and everything seems 100% solid - except this:

View attachment 13525

For reasons unknown - this error pops up in GPEDIT at startup.

Now - I know exactly what is causing the error - This specific file is nowhere to be found:

View attachment 13526

But the question is why? Why this specific file - when all other *.adml files are present?

All I can think of is I have possibly removed something (virtualization related?) in my NT Lite settings - that I probably shouldn't have. But what?

I do have this specific file installed on other machines - so grabbing a copy should work. But what I am missing in this specific build?

Perhaps something to do with this?:


Appreciate any input - or if anyone else has come across this.

S
 
You must have 2 files with the same name and extension .adml and .admx
Check if you have both (one is in the language folder)
 
You must have 2 files with the same name and extension .adml and .admx
Check if you have both (one is in the language folder)
Understood. Have the admx. But for reasons I cannot explain - there is no adml.

This is brand new install - and that specific file does not exist.

It DOES exist on other builds here (win 10 22H2, Windows Server 2022) but not in this specific ISO - Win 11 IoT ENT LTSC 24H2.

I am going to test an untouched ISO right now and see if this is an actual payload issue on the ISO for Microsoft.

S
 
Ok - so NT Lite is playing some sort of role here:

This file IS present in an untouched ISO install:

View attachment 13527

So it would be nice to know exactly what settings in NT Lite are stripping this thing upon install.

My customizations for my current NT Lite build are very very subtle. More cleaning up privacy settings and the like and not removing almost anything.

But something in this build is causing this file to be stripped. Would be nice to know if this file is specifically targeted in the NT Lite source code and what components, features or settings are causing it to be removed. If NT Lite is removing it.

If NT Lite is not touching this file in any way during a typical build cycle - my issue here is even more obscure than first thought.

S
 
Do a test on a full ISO and your preset, you will see if NTLite (with your preset) deletes this file and not the others (if you keep the component in question)
If this is the case, you can protect this file (if the associated registry keys are not deleted too) while waiting for this "problem" to be resolved
 
On startup, Group Policy Editor expects to find certain GPO template files in the system.

The normal GPO files for a specific feature are self-contained in that component. Removing UEV implies the UEV templates are removed, since you don't need that feature.

GPE on the other hand, has no clue that file has gone missing. Should it really care? No, because if you don't have a template then GPE would be "blind" to editing that policy feature. But MS has encoded a required policy list into the app. Removing Defender in some Windows releases triggers the exact same warning.

Use Compatibility mode's file patterns to keep a specific file (like UserExperienceVirtualization.adml) while removing its parent component. Protected files are specified using a relative path (by using the most unique end to a pathname).

View attachment 13528
 
Yeah, always checked first, if the associated component is not deleted or "child" of another deleted component
On the other hand, if the component is deleted, it is because there are still traces, otherwise you would not have the error when opening GPEDIT
 
Back
Top