revert change lid close action grey options grey out, from ad gpp settings

Hi, you have that nice Change Lid Close Action in Windows 11 Tutorial Lid-Close tutorial. It states that certain Settings like Shutdown or Sleep will Grey Out and Override the Settings in the UI.

I set Lid Close Action through Windows Group Policy Preferences in an AD Environment.
Computer Configuration > Preferences > Control Panel Settings > Power Options. Here we had our Power Plan "Windows 7 or newer". It Works and Sets Settings as wanted. After configuring Lid Close Action Sleep on Battery, Windows started to Grey the Settings for users. (all Poweroption settings, like changing plan, lid and powerbutton actions in the gui.) I can change them with admin-rights, after clicking the uac icon. I really need the behaviour back that users can edit this.

I changed back the GPP to "do nothing" tried to disable the scheme but the options are still stay greyed out. Does anyone know how the Grey-Out occurs or what changes on the local machine?

Policys in Registry and Machine were deleted, the Setting was deleted in AD. Local Powerschemes were reseted. I tried the key from the tutorial:
Default_user_choice_for_lid_close_action-plugged-in.reg, sadly it doesn't have an effect. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power doesn't even exist before i add this key. No there's no other Power Options through GPP or GPO, i check with gpresult /h.

Anyone knows, how i can revert that to normal? I tried a Compare of the Reg-Settings with a still working machine that didn't bring up any useful and couldn't find clues. Does it whack the ACL or something?

Version 23H2 22631.4037

Best regards
kobi

Welcome to the forum.

Not sure. But you could try resetting group policies?

Have you looked in the settings to see if one of these options in "system" might help?

thank you.

I tried the script, didn't fix. I suspect the gpp uses the xml file it creates from sysvol and feeds it into an api, without saving anything in the policies folders.

Tried a lot of those automatic Problem fix things, only thing it found was a missing reboot, which i did, and still had the problem.