Ok i can waitHold on! I'm trying some things myself... Don't do a repair install yet. I'll let you know what I find. I have the time today and I'm determined to squash this issue. TODAY.
Also... I don't see anywhere that you tried running DISM. Just to be sure... Run the following from a command line to make sure you don't have any other problems: DISM /Online /Cleanup-Image /CheckHealth. It won't change anything; it will just report if your installation is healthy or not.
)Hope you figure this out because it's driven me nuts with no good clue. You may want to look at this to see where it may be gettng stuck Boot and UEFI - Windows driversHold on! I'm trying some things myself... Don't do a repair install yet. I'll let you know what I find. I have the time today and I'm determined to squash this issue. TODAY.
While MB has been an issue on some machines this problem goes beyond that and is pretty elusive. In my case, I essentially did a complete Reset which wipes out all the apps from the machine thinking it was related to some incompatible app that was the cause of the problem. I then attempted to install KB5018418 and I still encountered the endless spinning wheel after 30% restart. My suspicion is that it's related to some system driver even though they all check out as being current. If new builds of Windows can't even install on hardware which was previously fine with older build then it has to be some new security feature that they've added that's screwing things up. The standard SFC, DISM, WU Reset, removing MB etc. made no difference for me. MS is supposedly aware of this ongoing problem and so far hasn't been able to provide a fix in these monthly updates. Pretty frustrating.
To give you a little background my problem started with KB5016629 which came out in early August. That's when I decided to go back to KB5015882 July 21 update, and that went in fine with no issues whatsoever and even with MB running and doing nothing special. All subsequent Cumulative Updates since KB5016629 have an installation issue with my hardware. I have a Gigabyte Z390 UD Rev 1.1 with F10 Bios and haven't done anything to the system since when it was working. I have made multiple Macrium backups and tried different scenarios with the same result. I am convinced that there's some code that was added in August around the time KB5012170 Security Boot patch was issued and that is in all these new Cum Updates including new ISOs that you download from MS. This code is not working with some hardware configurations and that's the best conclusion I can come up with after months of troubleshooting. Sounds like we just have to wait for MS to come up with a universal fix because what works for some may not work for others.
It appears that your update brought your machine to 22H2 build which is the new version. Sounds like your upgrade was an entire OS upgrade. Did you do a complete in-place upgrade install or just chose to do the KB5018418 upgrade? I wonder if they've fixed the issue.
Hi all i did was the computer said it needed to restart to complete critical updates so i just clicked on restart.
Thanks for the info, sounds like MS is forcing the complete install to overcome whatever issue they are having. How long did the whole process take for you? I'll make a back up just in case before doing this so I can revert back if something happens.
Interesting that your update was from 21H2 to 22H2 via automatic updates. I am only getting KB5018418 as the updates available and I've had to hide it and prevent it from installing because it fails. I may try an in-place upgrade with manual 22H2 download from MS to see if something changed.
