Can't install KB5014668

Thanks GeorgeFliger but what "fix" if any have you used in the past and what KB was it used for? I'm interested to see if any listed "fixes" are a permanent solution.

Couldn't find your actual post for some reason so copied your response out of the email I got.

As for fixes in the past... it's been a while since I had any issues with an update, but as I remember I restored my system with a backup I had made (I do a complete system backup every Friday night) about a week or so before the faulty update. It seems something got corrupted in the system after that backup so I was able to do the update after the restore took place. This last time the error must have occurred between updates so restoring the system didn't fix the issue. And, to add insult to injury, I found out that my backup solution wouldn't do a proper restore to the NVMe drive that was my primary in my new PC. That caused a whole can of worms. It seems not all backup software recognizes NVMe's set up using Optane and RAID. I had to change the BIOS/UEFI to see the drive as an ACHI setup which allowed my drive to be seen by my backup. That only partially fixed my problem as I couldn't boot from the drive. Turns out I had to use a Recovery USB, boot to a command prompt, run DISKPART to select the proper drive and primary partition, run BOOTBCD \C:\Windows to get the boot files properly installed then reboot, change the drive configuration back to Optane w/RAID, boot, let DISK REPAIR run and finally got to the login screen to get logged back in. The error was still there and the update still couldn't be installed. What I should have done from the beginning was to simply put in my Windows Install USB, run setup and done an Upgrade, keeping all my apps and files. That fixed the issue and would have saved me a bunch of time had I tried that first. So, after the Windows upgrade and reboot I went back into Windows Update, downloaded the Cumulative Update and let it do it's thing. This time it went in without a hitch. Sometimes doing the simplest things first is the best thing to do.

I got excited when I saw the Cumulative Update Preview for .NET Framework 3.5 and 4.8 hoping that it would solve the problem. But, after successfully installed Cumulative Update Preview for .NET Framework 3.5 and 4.8, I still can't download/install the new KB5015882.

Good morning,

Saw your message about KB5015882 so thought I'd check it out. It was available for download and install when I checked for updates. I didn't disable or change anything before starting the update. It downloaded fairly quickly, only stopping at 5% for several minutes. Next thing I knew it was at 100% where it proceeded to do the install. It slowly proceeded to 25%, waited a bit, then on to 35%. Again, a bit of a wait then slowly proceeded to 69% - another short wait, off to 88% then a slow but steady progression to 100%. Gave me the Restart button which I clicked. Reboot went fine, "Updates are Underway" went fine and then back to my login screen. No burps or errors of any kind. Altogether the download, install, and update took all of about 10 minutes or so to complete.

As I stated at the beginning of this post, I never had to disable, shut down or turn off anything to perform the update. I hope that helps someone.

I know I started this thread but it might not be the best place to ask this:

Was anyone who did the repair reinstall with either KB5014668 or KB5015814 able to install the current KB5015882 without having to go through anything special again? This would be great to know that maybe you only have to do it once.

There was another thread about an unsuccessful install for KB5015882 where the guy submitted his CBS file and he was told him his .NET framework 3.5 was corrupted. It does seem quite a few have disabled .NET framework to get the install to work. So if seems we have either one or a combination of fixes that have worked. Disable Malewarebytes. Turn off .NETframeworks 3.5 or do the repair reinstall. Or no success at all. But I did have a successful download and install today for .NET Frameworks 3.5 and 4.8 (KB5015732). So I'm wondering if that was the fix we've been waiting for assuming the .NET was the problem??????

The fact that Microsoft has not fixed THEIR problem with this issue nor provided their customers who do not have extensive computer experience with a relatively simple solution to this problem, indicates Microsoft's lack of concern for their customers at the highest level. This problem has doubtlessly affected millions and yet, there seems to be little or no interest on the part of this giant to look after their customers. This is disgusting!