I have had the same problem, and tried so many solutions but this is the only thing that worked for me.
Open Note pad and copy and paste this in
SC config trustedinstaller start=auto
net stop bits
net stop wuauserv
net stop msiserver
net stop cryptsvc
net stop appidsvc
Ren %Systemroot%\SoftwareDistribution SoftwareDistribution.old
Ren %Systemroot%\System32\catroot2 catroot2.old
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
netsh winsock reset
netsh winsock reset proxy
rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
dism /Online /Cleanup-image /ScanHealth
dism /Online /Cleanup-image /CheckHealth
dism /Online /Cleanup-image /RestoreHealth
dism /Online /Cleanup-image /StartComponentCleanup
Sfc /ScanNow
net start bits
net start wuauserv
net start msiserver
net start cryptsvc
net start appidsvc
Save as Wufix.bat (to desktop)
change to all files before saving
go to desktop
right click on Wufix on your desktop, run as administrator
restart your computer
Fixed!!!
That type of fix you find on many I did trillions of them. Was the last check on compliant drivers that did the trick and removing them with nothing. Don't reckon that's there.
The added complication is that some revised drivers aren't 24h2 compatible whilst old ones are so if you do an upgrade of a driver and get one of them you are stuck.
Time will tell whether Microsoft can make the 24h2 upgrade work now they are taking the brakes of it again. The second issue they revert drivers, the first one where the user has some software installed that doesn't pass the final boot into 24h2 means they would have to junk those old incompatible drivers or replace then in an automated way. Issue being the enforced secure boot that they put into 24h2.... that which I believe some people turned off at installation in 24h2 to get it installed. Unless that's in the command above.
So yes it was the the "memory integrity readiness Microsoft tool" that finally got it to work after removing one problematic driver. The fixes can generally be done by doing an inplace restore which dusts down the system rather than a long list of start, stop etc. So for me those didn't work and I got tired of doing them and reading them. 🫣 As said I believe some people turn the back end of UEFI security checks off rather than dealing with the issue.