Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

Windows Vista/Server 2008 January 2026 Update UAC Bug (Patreon)

Published:
2026-05-20 19:52:54
Imported:
2026-05

Content

A warning to all users who plan to install the final updates on Windows Vista and Windows Server 2008; I have discovered that the User Account Control (UAC) checkbox is broken in the User Accounts Control Panel applet. Any clicks of the checkbox are not retained, which means that the setting can no longer be changed with this method.Users must now Win+R to secpol.msc to access the Local Security Policy editor and navigate to Local Policies -> Security Options -> User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode, or User Account Control: Behavior of the elevation prompt for standard users, depending on the user's account type.

This is now the third "parting gift" I am aware of from Microsoft, following the non-registration of MSI DLLs in Windows Embedded POSReady 2009's final update from April 2019 and the replacement of wallpapers with a black colour fill in Windows 7's January 2020 cumulative updates.

Files

Comments

Miraak Thuri

Wasn't there also a breaking of some Dwrite function in one of W7 ESU update ?

TSNH

I believe adding user accounts from the control panel applet has also been broken for quite some time now

TSNH

I've figured out which component is causing this error: it's lsasrv.dll. As I wrote earlier, the bug is not only about the UAC switch but it also breaks creating user accounts via control panel and editing their properties via control panel The bug was first introduced with KB5014743 - 14th June 2022 security update and the first affected version of lsasrv.dll is 6.0.6003.21507 The last updates that didn't have this bug were KB5014010 - 10th may 2022 monthly rollup and KB5014990 - hotfix for that update The last working version of lsasrv.dll is therefore 6.0.6003.21480 from KB5014990, however it won't work by itself on system with later updates installed without the kerberos files also being from KB5014990 So to fix the bug you will need to replace 3 files in system32 with the following versions: lsasrv.dll version 6.0.6003.21480 kdcsvc.dll version 6.0.6003.21483 kerberos.dll version 6.0.6003.21483 and if you're an ESU user you can obtain them from MSUpdateCatalog https://www.catalog.update.microsoft.com/Search.aspx?q=KB5014990 and by installing KB5014990 on a VM or extracting them from the update Note that any security fixes that were made to lsasrv.dll, kdcsvc.dll, kerberos.dll in later version won't be applied anymore after replacing and always BACKUP original files in case something goes wrong. And remember that amd64 (x64) files go to system32

9doorsempire

are you or anyone else aware of ESU bricking installs? on my end, after installing any rollup from 2024-03 onwards makes Vista unable to boot either normally or in safe mode. enabling verbose boot prior shows it hang on the Microsoft(R) Windows(R) screen right before its supposed to show the cpu/memory count. this is happening regardless of any modifications and will also happen in a vm on the same hardware (Ice Lake machine). i know this platform has known issues on Vista but im unsure if this is related to the drift bug at all

win32

No, but as a result of the other known bugs, my AVX patch will exist for both early and late 6003 patch levels.

9doorsempire

i have now tested on 10th, 9th, and 2nd gen intel and a friend tested it on 13th gen intel and only 2nd gen will boot, but i did also find that from KB5035920 onwards replacing ntoskrnl.exe with the version from KB5034795 allows the system to boot again KB5034795 ntoskrnl ver is 6.0.6003.22510 KB5035920 ntoskrnl ver is 6.0.6003.22567 and grew about ~4KB