Describe the bug
We are looking into replacing VSC with VSCodium in our Enterprise. I have tested MS VSCode GPOs that are delivered with VSCode and they work fine. I have now installed VSCodium, applied the same policy from gpedit.msc => computer configuration => administrative templates =>VSCodium and checked them in regedit. they appeared here: HKLM\SOFTWARE\Policies\Microsoft\VSCodium. They look exactly the same like the VSC ones so I thought we are all set. But they are completely ignored.

Please confirm that this problem is VSCodium-specific
This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented
I haven't found similar problem.

To Reproduce
Steps to reproduce the behavior locally, outside of the domain to make it as simple as possible:

• copy admx/adml templates (2) to correct folders: admx goes to C:\Windows\PolicyDefinitions\ while adml goes to en-us subfolder.
• open gpedit.msc, find vscodium group, select for example UpdateMode and set it to none.
• you dont need to restart if you test all locally (outside of the domain). Just launch VSCodium and go preferences, find update settings and check if you have Update: Mode set to none with "managed by organization" in the brackets.
• it works exactly like this when I use the same version of VSC.

Expected behavior
It should not ignore the GPOs.

Screenshots
Here are 2 apps opened at the same time , using exactly the same policies, set from gpedit,msc

• 1st is VSCode 1.109.5 x64
• 2nd is VSCodium 1.109.51242 x64

Registry:

Desktop (please complete the following information):

• OS: Windows 11 PRO 25H2
• x64
• Microsoft Windows [Version 10.0.26200.7840]
• App has been installed from ZIP and via installer.
• No virtualization.

Additional context
I have tested this in our domain and on my Private machine. The results are the same.

• Company domain endpoint: I have set all registry manually, 1:1 like VSC. Doesnt work.
• Private machine. I have set desired GPO via gpedit.msc to avoid typos and similar stupid mistakes. Doesn't work either.