Windows 10 v1809 / LTSC 2019 2026-11 KB5131085 LCU is also affected by the sppwmi.dll bug it uses different feature id 64073911, hence the required registry value for the workaround is different Code: reg.exe add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 1863277711 /t REG_DWORD /d 0 /f system restart is probably not required (but i didn't test)
Hello everyone, I am using Windows 10 LTSC 2021. During my previous installation, I activated it using HWID, and it successfully converted to KMS/Digital License as expected. Today, I reformatted my PC, but HWID gave an error this time. Should it normally activate automatically, or did I miss something? Also, I encountered an error with Office ohook. Any advice?
I’ve just finished reading the posts and watching the videos/GIFs—thank you all for the advice you’ve provided. If I’ve understood correctly, would using `WaaS-reset_v2.reg`—followed by a restart and an automatic Windows check—cause that red warning message to reappear in Windows Update? I’m wondering: if I just leave everything as it is and do nothing, will Microsoft resolve it on their own? Or could I run into other issues—beyond the fact that, as I mentioned, I had to use `gpedit` to defer updates? Alternatively, if I were to simply delete the key `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WaaSAssessment`—or just the subkey `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WaaSAssessment\Cache`—would that fix it? Would Windows then recreate the deleted key correctly upon restart, thereby resolving the issue? Thanks
For MSFT windows 10 is dead And the fixes are published, the safe one and the one with caution, no need to re-invent the wheel again.
I actually considered that, too—given that Windows 10 is nearing the end of its support, you might be right that Microsoft won't fix this issue. However, I wondered about it because I recall that back in October 2025, when I first enabled ESU (Extended Security Updates) for Windows 10, I saw that same red warning message; Microsoft eventually fixed it, so I thought perhaps they might do the same this time around. In any case, just to be safe, I’ve exported the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\waasassessment HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU If I understand correctly, to resolve this, I just need to run `WaaS-reset_v2.reg` to modify the registry and then restart Windows. Naturally, I would also be able to revert the changes I made via `gpedit` to stop automatic updates. Alternatively, could I just leave everything as it is? If I’ve understood correctly, aside from the red warning message and the need to use `gpedit`, I shouldn't run into any other issues either way—is that right? I’m a bit undecided; what would you recommend?
Hi abbodi1406, thanks for your reply, and for all the help and effort you put into the forum. As I mentioned, to address the issue of pausing updates, I’ve used `gpedit.msc`—navigating to Computer Configuration > Administrative Templates > Windows Components > Windows Update—to enable "Configure Automatic Updates." In the drop-down menu under Options, I selected "2 - Notify for download and auto install." I hope this works, and that—as I suggested—Microsoft eventually fixes the problem. Thanks again, and have a great Sunday, everyone.
"Pause Updates" in WU advanced options page if you don't use it or need it, then just ignore the message
Hi, yes, I understood that—in fact, I do use the "Pause Updates" option on the Windows Update advanced settings page—but since that isn't working at the moment, I’m using `gpedit` as a workaround.