I only use MAS when I need Ohook; otherwise, I manually run TSforge.exe. Also, I noticed that the issue seems to be caused by EnableLUA—at least the problem disappeared after enabling it.
@joshlynn You don't need to run or populate WaaSAssessment, it's pointless nag just clear it if the red notice returned, clear it again there is no "startassessment" command for usoclient
The reg file from abbodi1406 wont stop that nag message reappearing. It'll just keep coming back when usoclient.exe runs a scheduled scan or when you manually check WU. After talking to Gemini, this is what permanently stopped it appearing it for me: In the WaaSAssessment key change the value of the subkey DISABLEASSESSMENT from 0 to 1. Change the value of the RESTRICTION subkey from 0 to 1. Add a 32-bit dword subkey called AssessmentState and give it a value of 1. Add a 32-bit dword subkey called UseSecondarySource and give it a value of 1. Delete the cache subkey in the WaaSAssessment key and reboot. The cache subkey will not be recreated. Check WU. The "Your device is missing important security and quality fixes" message should be gone. It was for me. Gemini assured me that I will still get windows updates after making these changes: "The Defender engine (MpCmdRun.exe) pulls daily definitions directly via its own internal automation task and standard Windows Update protocols without reading your local OS assessment health history. Setting RESTRICTION or AssessmentState to 1 simply feeds a hardcoded "Healthy" note to the graphical interface, stopping it from printing the red text error message. It does not disable the core Windows Update Service (wuauserv) or the Update Orchestrator Service (UsoSvc). When Patch Tuesday arrives next month, your system will still query Microsoft servers normally, pull down the real update payloads, and install them safely." The first statement is correct. I am still getting Windows Defender updates after I got rid of the nag message. It says changing the RESTRICTION key to 1 "tells the interface to actively restrict any old error warnings from displaying". It says "adding those other keys act as your safety fallbacks. If the settings app looks for an assessment state and sees it is disabled, it will read these fallback values, assume your machine is completely healthy, and display the green checkmark". I suppose when the next Patch Tuesday rolls around, you could delete the WaaSAssessment keys then have WU repopulate them to default values to test if Microsoft has fixed this issue by then.
I'm under ESu since 1 year, had activated for 3+ years and got last October update. Today I had a look in update, and got this screen, have you the same ? (clicking on update button change nothing) :
@Seven4ever Server-side issue it only affect "Pause Updates", if you don't use it, then you can ignore for now
I have a Dual Boot Windows 10 Pro Both are Version 22H2 OS Build 19045.7807 Both have MAS 3.12 with just TSForge run and activated fully One says its all up to date while the other says: "You're not up to date your device is missing important security and quality fixes." The working WU boot has Updates from Oct 2026 but before that just July 2026 KB5126657 KB5128925 KB5133964 The problem WU boot has these updates from Oct 2026 (pause updates greyed out) KB5133964 KB5126657 KB5128925 KB5130034 it also has Sept 2026 updates and before that July but not August. I tried merging the WaaS-reset.reg and then ran the powershell code then restarted but WU is still the same on the problem Boot. Any ideas how to get the other boot working again for WU please?
From what i read by @abbodi1406 (a few posts up) and @witherornot (iirc) it should solve itself but we have to wait till novenmer updates to check. This happened in the past too, it was resolved by MSFT/on itself back then, last Jan.
Thanks I will leave it and wait until then. The version of windows 10 that was online most is the one that has this issue. It was only after that i booted up the other one and updated to 3.12 and it did the October updates and was reporting all up to date while the other version may have already updated to the Oct updates with version 3.10.
My update history is now blank, I guess because of he refresh. The control panel search of Installed updates for KB5126256 drawas a blank as does a an admin command prompt search of: DISM /Online /Get-Packages | findstr /i "5126256" I haven't checked the working WU yet for it. So I guess I should try installing it.
Please do check when you have time For the other one you can run this, i guess, it should create a txt file on your desktop showing all installed updates: Code: dism /online /get-Packages /format:table >"%userprofile%\Desktop\Packages.txt"
The KB5126256 wasn't installed on the problem WU boot but i have installed it now and WU still reports not up to date (but not rebooted). Uploaded packages txt Will test the other boot for KB5126256. Odd as both were previously working for ESU.
Likely, I'm on the other boot now and KB5126256 not installed here either this one still working OK. I'm just a bit OCD about it I have another swappable caddy for this laptop and gonna make sure its got the newest MAS 3.12 run 1st. been offline so hopefully will behave itself
I have multiple installations, all with ESU activated via TSforge in MAS and they all show the following after the October patch day: I have a single installation (which is HWID activated via MAS, but without TSforge ESU), where all is good and it says it is up to date and on this installation I am using my Microsoft account, on all other installations I am not. also KB5126256 is NOT installed on this installation. -andy-