Skip to content

[Bug] - Administrator protection breaks LAPS on 26H2 #264

Closed

Description

@incedIT

Baseline Info (please complete the following information):

  • OS: Windows 11 26H2
  • Version: 4.0

Describe the bug
Since upgrading my laptop to Win 11 Business 26H2, LAPS has broken. It will accept the LAPS password but fail with "the requested operation requires elevation".

To Reproduce
Steps to reproduce the behaviour:

  1. Run cmd / powershell / anything else as admin
  2. Enter the LAPS password

Expected behaviour
The program runs as admin

Screenshots
Image

Additional context
Microsoft document the Administrator Protection feature as being incompatible with LAPS.

I was able to fix by updating Win - OIB - SC - Device Security - D - Administrator Protection - v3.7
User Account Control Type Of Admin Approval Mode - Admin Approval Mode with Administrator protection --> Legacy Admin Approval Mode

I need to look into if I can switch my processes from LAPS to administrator protection, but thought posting this may help others who find LAPS is suddenly broken.

Activity

  1. Gerrits-Justid commented on Oct 23, 2026

    @Gerrits-Justid

    We have had this issue as well and came to the same temporary resolution by changing the Administrator Protection policy. It is also not just with LAPS but also EPM. Issue is reproducable on both 25H2 and 26H2 from our findings after installing KB5127648 (October 2026 patch).

    Either uninstalling KB5127648 or changing the Administrator Protection policy is a temporary solution that fixes it.

    We opened a ticket through MS support and they are further investigation this issue.

  2. bennyocb1291 commented on Oct 23, 2026

    @bennyocb1291

    Either uninstalling KB5127648 or changing the Administrator Protection policy is a temporary solution that fixes it.

    Been experiencing the same issue and the only clue we had was the Oct KB too. I did suspect the Administrator Protection might be the cause, but it'd been in place since release so didn't give it much thought.

    May I ask what you changed the settings to, or did you just exclude affected devices from the policy?

  3. incedIT commented on Oct 23, 2026

    @incedIT
    Author

    2. > Either uninstalling KB5127648 or changing the Administrator Protection policy is a temporary solution that fixes it.

    Been experiencing the same issue and the only clue we had was the Oct KB too. I did suspect the Administrator Protection might be the cause, but it'd been in place since release so didn't give it much thought.
    May I ask what you changed the settings to, or did you just exclude affected devices from the policy?
    

    I provided the fix in the addition context section of my bug report 👍

  4. bennyocb1291 commented on Oct 23, 2026

    @bennyocb1291

    So you did, apologies - too eager after reading that it wasn't just us! Thanks.

  5. incedIT commented on Oct 23, 2026

    @incedIT
    Author

    After reading into this, the administrator protection feature is great for cases where the user has local admin rights already, but in my case my users have standard accounts to prevent them from installing/running things they shouldn't. Might be worth just documenting this as I expect a lot of those deploying OIB want the same behaviour as me. Microsoft document it breaking LAPS so doesn't look like a bug with an update, looks like intentional behaviour but it has only been enforced by the update.

  6. Michael-eit commented on Oct 27, 2026

    @Michael-eit

    oh interestng. I have had this happen with 2-3 devices. LAPs just doesnt function. doing anything as system says it did it but it does not. The UAC prompt is also different though I do not have a picture to show it.

  7. Michael-eit commented on Oct 27, 2026

    @Michael-eit

    hmm, the plot thickens this is my admin protection policy in the tenant in questions

    Image
  8. incedIT commented on Oct 27, 2026

    @incedIT
    Author

    7. hmm, the plot thickens this is my admin protection policy in the tenant in questions
    Image

    In that case it might be a separate issue, if you start a new issue I’ll try to help. Was it working ok? Had you changed anything or did it break with 26H2/October CU?

  9. Fisk3r commented on Oct 27, 2026

    @Fisk3r

    We had the same issue, changing the policy to "Legacy Admin Approval Mode" fixed the issue for us.

    @Michael-eit have you restarted the laptop after changing the policy ?

  10. RToni commented on Oct 27, 2026

    @RToni

    We experienced the same issues since last friday and changed the policy back to "legacy admin approval mode" - curious why a policy set like OIB includes such a settings thats not working well together with LAPS. While OIB is mostly used in such environments where LAPS is used.

  11. Michael-eit commented on Oct 27, 2026

    @Michael-eit

    @Fisk3r this is what I set the policy to over a year ago. I forget the reason why. I have reimaged the device since.

    Hearing about KB5127648 (October 2026 patch). is interesting because I had this issue before then.
    I will have to investigate more.

  12. stephen-martin-atl commented on Oct 28, 2026

    @stephen-martin-atl

    We hit this across a number of devices (Win 11 Business, 24H2 and 25H2/26H2, OIB v3.x policies) after the October updates, but with a different symptom from LAPS/EPM. Posting in case it helps anyone seeing “random” user complaints rather than elevation errors.

    Symptoms (user-facing)

    • Keyboard switched to US, regional formats to US
    • Theme / dark mode reset, text looked blocky (ClearType off), display scaling reset
    • “Show window contents while dragging” turned off
    • Users fix it, sign out, and it’s broken again at the next sign-in

    What we saw on affected devices

    • HKCU\Control Panel\Desktop stripped from ~46 values to ~9; HKCU\Control Panel\International emptied, language list empty
    • HKCU\Control Panel\Desktop\LanguageConfigurationPending reappearing at each sign-in with en-GB → en-US
    • Hidden ADMIN_AzureAD_ accounts created (Administrator protection’s system-managed admin account), even for standard users
    • Unaffected devices on the same build had no ADMIN_ account

    The conflict we found with another OIB policy
    On one device, the Security log showed this right after the post-update restart:

    4720 – ADMIN_AzureAD_ created and added to Administrators (Administrator protection doing its job)
    4733 – four seconds later, removed from Administrators again

    The removal came from Win - OIB - ES - Local Group Membership - D - Local Administrators - v3.7, which uses Add (Replace), so it strips anything not explicitly listed, including the hidden admin account Administrator protection relies on. Config Refresh re-applies it every 30–40 minutes. Each policy is fine on its own; together they keep breaking each other, and the user’s profile seems to get caught in the middle.

    What fixed it

    1. Set Win - OIB - SC - Device Security - D - Administrator Protection - v3.7 → User Account Control Type Of Admin Approval Mode to Legacy Admin Approval Mode (same as @incedIT)
    2. Restart each device. The registry shows TypeOfAdminApprovalMode = 1 as soon as the policy syncs, but the feature only actually switches off at the next restart. Our first test without a restart still failed.
    3. Repair the already-damaged profiles (we used a script to restore International, the language list and keyboard, font smoothing and the missing Desktop defaults, then clear LanguageConfigurationPending). Repairs stuck after a sign-out once Administrator protection was off.

    One difference from @Gerrits-Justid’s findings: for us, uninstalling KB5127648 didn’t fix it. A device rolled back to 26100.9448 was still affected, since the August/September updates already carried the feature. Removing the October update mostly just avoided the restart that activated it. With Administrator protection off, we’ve reinstalled KB5127648 without problems.

    Suggestions for the baseline

    Document that Administrator protection and the Local Group Membership policy in Add (Replace) mode conflict, and consider Add (Update) if both are deployed
    Note that the Administrator protection change needs a restart to take effect

  13. SkipToTheEndpoint commented on Nov 5, 2026

    @SkipToTheEndpoint
    Owner

    Sorry it's taken me a while to chime in on this one.

    I think it's undeniable that there's some weirdness with this policy that's Microsoft's fault, but then also some counter-play with other policies (e.g. Config Refresh) that makes the behaviour more unpredictable.

    Part of the issue is due to Admin Protection being enabled by default as of the October 2026 security update. MS even call this issue out with their own Security Baseline.

    The biggest issue is that it's now documented to specifically NOT enable this feature when devices are managed with LAPS:
    https://learn.microsoft.com/en-us/windows/security/application-security/application-control/administrator-protection/?tabs=intune#troubleshooting

    Image

    So, given the two above facts, I can't remove the policy (because it's enabled by default as of October), and can't leave it as-is due to the impacts it's having on LAPS. As has been mentioned above, the best solution is setting the Approval Mode to "Legacy Admin Approval Mode". I'm just working out the best way to release the change.

    I was already planning on adding a warning to the Config Refresh policy, because while it's great, it can also cause weird behaviour with some other policies (e.g. Wi-Fi profiles being re-applied and dropping the connection briefly).

    On the other UX issues you're seeing @stephen-martin-atl , they're pretty odd, but certainly not something I've seen others reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationwillfixThis will be worked on

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions