This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I've been running Windows 11 since Nov 2021. This is the first update failure I've encountered. I was trying to install KB5014668. It stopped at 25% install and showed error 0x80000ffff. I ran troubleshooter (multiple times) to no avail. Upon a restart, it showed installing an update, in the middle it rebooted and then on the subsequent restart it showed install to 48% then said something went wrong, not to worry as it was restoring. It rebooted again, showing the same message, on the next restart it booted into windows. I've run sfc /scannow and dism restorehealth. Neither showed an error or helped. I use Macrium and also tried mounting an image taken before I tried the update and copied the Software Distribution folder and pasted it over the current folder. No help there either. I am able to download Windows Defender definition updates okay at this point.
I could just restore the whole drive to a point before I tried the install but would like to use that as a last resort. Right now I can perform multiple restarts with it booting straight into Windows. So I'm not sure if I should just wait until the July cumulative is available to see what happens or is there something I can or should try at this point, like try to download and install it straight from the update catalog?
Thanks for any help with this.
Update... I did try to use the Windows Catalog to do a manual install. It seemed to download ok but when I hit install it failed immediately with an error code of 0x80070002 (I got this from the reliability monitor)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
14668's changes should also be represented in KB50115882. That's why they're called Cumulative Updates. That would explain why you don't see 14668 as part of your final update process. The older updates might have supplied some missing key items required so the .NET updates could be installed properly. Hard to say for sure.
Glad to hear it! I think the main culprit is the .NET 6 framework, which I don't think I had to begin with.
Possible, but not in my case. Never had to mess with anything that had to do with the .NET 6 Framework. Different solutions for different folks, I guess. I suppose it all has to do with individual configurations, hardware and software.
I have just carried out a re-install of Windows 11, from ISO and bootable USB with the option to keep files and Apps. This has resolved the issues with the updates, all looks to be working fine all updates installed without a problem. Thanks for all the advise
Glad it worked and was relatively painless. :-)
Thanks, George - all done now. 👍
And there was actually no need for me to burn the ISO and boot to disc/usb - simply running the SETUP from within the ISO worked a treat. Plenty reboots and more updates later, took about 90 mins in total I think.
I now have no more pending/optional windows updates, and my historical updates installed today look like this (below), from top to bottom. It's weird there are 2 older updates - I wonder if that was to fix the original issue with 14668 (which is no longer showing) ?
> 2022-07 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5015732)
> 2022-07 Cumulative Update for Windows 11 for x64-based Systems (KB5015882)
> 2022-06 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013889)
> 2022-04 Update for Windows 11 for x64-based Systems (KB4023057)
Glad to hear it! I think the main culprit is the .NET 6 framework, which I don't think I had to begin with.