The cleanup bug is getting serious. I have just clean installed 24H2 three times today to fix this. I am glad it paid off.
If you insist run in NSudo cmd Code: set "_k_=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" for /f "tokens=8 delims=\" %# in ('reg query "%_k_%" /s /v Baseline ^| findstr /i HKEY_LOCAL_MACHINE') do reg delete "%_k_%\%#" /v Baseline /f
It deletes from every single package the Baseline DWORD making resetbase work again as intented. So you can get rid of that 8,63 GB that you see in Disk Cleanup as Windows Update Cleanup.
24h2 successfully updated KB5044284 from 26100.1882 to 26100.2033, but the system keeps prompting that your computer needs to be restarted to complete the update. After manually restarting the computer, this prompt reappears as if the update was just completed. It keeps repeating. Can anyone tell me which registry entry to modify to turn off this error state, as if the system is handling it after successfully completing the update. Thanks!
no, the kernel itself is built with a version of the DDK (as is nvidia drivers post 556) requiring these instructions, you will only upgrade yourself into an unresolvable boot loop by trying.
tried again fresh install from upp dump iso 26100.2152,now I am liking it I think a few more CU updates it be good to go
Same for me. This build seems really good. sfc scan is working as intended. Same goes for disk cleanup - no pesky residuals.
26100.2152 "bcdedit /set hypervisorlaunchtype off" no longer works even it says successful past builds it did work anyone else try to turn off VBS ?
You are right, no luck here either, not using bcdedit or registry. MS made quite a few changes in the latest build. There is also a new HV Host Service.