Windows 10: DisableStoreApps Enabled is inherited from Local Policy when it is explicitly set to Disabled

Greeting! I turn to the community because my IT department cannot find any solution and their only proposal is re-imaging my laptop. Which is frustrating on several levels. This might be a good challenge for the community, I have combed the internet and I cannot find any solution. I have combed the registry for hidden settings. My Setup:OS: Windows 10 21H2 Enterprise domain controlled ADComputer : HP Elitebook x360 1040 G8My Problem: "HKLM\Software\Policies\Microsoft\WindowsStore\DisableStoreApps" is constantly several times a day being enabled blocking every type of store app in Store lik

:)

 

How to force compliance with Local group Policy settings ?

IN VAIN have I done the suggested registry change and also set Local Group Policy to ENABLED for "Turn off display of recent search entries in the File Explorer search box" - but search history still shows.

 

Local Security Policy on Windows 10?

Local Security Policysหายคับ

 

SCCM Local Policy - BITS

Managing BITS policy for clients can be done several ways - just a few listed here:

1. Group Policy template
2. Local Policy template
3. registry
4. and more...

SCCM client settings for BITS uses local policy to enforce the BITS agent settings.

Consider the following scenario:

SCCM client settings contains BITS settings for max throttle, start and stop times, etc...

SCCM Client settings also have the "Limit the maximum network bandwidth for BITS backgrounds transfers" set to "NO" so, effectively no settings that are configured are actually being enforced.

This is working fine. Here's the issue:

If I fun the following command:

GPResult /scope computer /h file.htm

... the output file will show that this local setting is "enabled" and appears it is enforced.

The setting is not enforced but the reporting mechanism thinks it is. I'm considering this a bug. This burned a customer and cost them several hours of troubleshooting where this setting was coming from because they swore that SCCM was not setting it.