As it is Windows 11 I would suggest using the recovery route.
Go to Settings > System > Recovery > Fix problems using windows update then select Reinstall now.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I get this when trying to update 2026-02 Security Update "(KB5077181)" (26200.7840): Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712).
I ran the DISM tool twice with no issues. I ran sfc /scannow, which supposedly fixed corrupt files. I ran it again and it was fine. There were periods of restart between running these.
I ran Windows Update trouble shooter, yet the Windows Update diagnostic failed to run.
I deleted the files in C:\Windows\SoftwareDistribution\Download.
Still nothing! Any suggestions?
Brian, you are getting a somewhat different error which is strange but it is still a similar enough error to our *983 and *991 errors so you may want to join us in complaining about this fail-to-install February patch at
for what it's worth (I'm having the same problem I had with the previous versions of this patch), my error number is now 0x800f0991
Brian, my first error after the regular attempt to install the patch was 0x800f0983, something you may see with some other users. The second attempt ended with no error and "completed", with no restart demanded, but the reloading of the patch started automatically, and that produced 0x800f0991, which I got several more times as I tried to follow some of the basic instructions to clean the WU cache, sfc, dism etc. I believe that 0x800f0991 is an attractor for these errors and it indicates some failed patch (old files are still physically in charge) that registered somewhere as a successful one..
I have the same issue, also with error 0x800f0991
**Luboš Motl, **Johan De Bruyne, **** & Ian Thow,
Look at the suggestions that John DeV has posted.
Brian, thanks for the update. But I think that I have tried all these things several times. Error persisted. What I did today was dism restore health with the source Windows Update. It ends with success but then I am not offered the February patch. Instead, I am offered the January patch where I already am, and after trying to download a bit, it says I have nothing to install for my level. Then I may choose the optional preview from the late January, it ends with the error 991, too. I have avoided the preview update but if I had not, I would have probably gotten the same errors two weeks earlier.
I ran the DISM tool and sfc /scannow several times. The first time, corrupt files were 'fixed', yet that did not help to install the Feb update. I also had Windows Update state the update was completed, yet when I looked it was not installed! The kicker is that it installed on 2 laptops and the Windows Malicious Software Removal Tool x64 - v5.139 (KB890830), Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.445.12.0) - Current Channel (Broad), & 2026-01 .NET Framework Preview Update (KB5074828) updates all installed! Yet, now I cannot check for updates because it wants me to Retry the 2026-02 Security Update (KB5077181) (26200.7840) update! Argh!I am going to take John DeV's advice and wait a few days before trying again.
Thanks, Brian. I am absolutely convinced that the best chance is through the new Windows tool, Fix problems using Windows Update. Someone who has had the error 991 must try it, especially if he is thinking about reinstalling Windows. This tool is much deeper than any Dism. Dism only fixes particular components but the tool reinstalls the current version of Windows while keeping user data etc, including lists of components. When someone with the 991 error tries it, I want to know the outcome. The tool should have a similar rollback as monthly patches, examples when the tool made things worse seem to be non existent, but sometimes the tool may still fail.
The tool is found under Settings, System, Recovery, on the right side, the second bunch of options is Fix problems using Windows Update, click at reinstall now, choose whether you want an automatic restart. New ssd computers should complete it well below one hour later.
Brian, Ian, I am pretty sure you have the same basic situation with the error 991. I am on a different PC in a different part of the town now. But in Windows Update, History of updates of the problematic PC, I can see that 5077181 was "successfully installed". And that false message is probably the reason why it refuses to install the patch properly. Why didn't anyone try to recommend us to try to REMOVE this flawed patch first? In Control Panels, go to programs, list of all updates, find KB5077181, and if it is there, just remove it. It could remove just the wrong settings or empty folders that were created during a failed attempt to install the patch. Alternatively, the command "wusa /uninstall /kb:5077181" in PowerShell or CMD could do the same thing. Also, in Regedit, there may be the key RebootPending in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing, and you may just rename this RebootPending or delete it. I got to this kind of thinking because of some timestamp errors I found in my WindowsUpdate.log, in combination with another time anomaly right after I installed Windows last week - I had recovery points from the future (by one day when it comes to the date). So the system simply may want to refuse the new files because it believes that it already has some better, newer ones because of some inconsistent timestamps caused by something on our PCs.
I deleted the KB5077181 folder, yet still nothing. Not sure about the change in the registry! The saga continues!
Brian, thanks but... deleted folder? It should not be primarily the folder, it should primarily be registry items and items in some databases. Have you tried that Control Panel, remove the update? Or the command in Command Prompt or PowerShell, wusa /uninstall /kb:5077181 ?
Hello All,
I am having the same issue when trying to install the 2026-02 update. I have been in contact with Microsoft regarding this issue and they collected my installation logs using the Feedback Hub, and they are currently investigating this issue, but they also mentioned that it would be very helpful if others would provide their logs through the Feedback Hub, as they reported that they have not received hardly any feedback related to an issue with this update. So I encourage you to record your download and installation "session" using the Feedback Hub, as this will provide Microsoft with more data points to help resolve the matter.
kb:5077181 was not the Control Panels, list of all updates, yet there was a separate folder, which is why I deleted it. I should have kept track of where it was located. :-( Running wusa /uninstall /kb:5077181 gave me a not installed popup.
I am leaning towards the Fix problems using Windows Update" feature in Settings > System > Recovery yet leery of having to reinstall programs, etc., so I am looking into that some more.
Thanks.
KB5077181 is for Builds 26200.7840 and 26100.7840. My build shows as 26200.7705 so I should not even be getting this update,
You're a freaking genius! ;-) Why didn't anyone else figure this out? My build is also 26200.7705 and I was trying to figure out why it was not installing. I just sent MS a note in the Feedback Hub and hope everyone does the same. EVERYONE check your build! It makes me wonder why folks going with the Settings > System > Recovery > Fix problems using windows update then select Reinstall route are able to get this update installed!
Ian, Brian: Dear Gentlemen, I have joined our Successful Team, Johan, Kevin, several more - we did fix this 991 error from the February patch. We did Settings, System (in the left sidebar), Recovery (in the right column), Fix Problems Using Windows Update (2nd in the right column). I did not check Automatic Restart. It switched to Windows Update except that the new patch was called a "Win 11 25H2 (repair edition)" (in Czech, whatever it is in your language).
The Windows Update screen spent 10 minutes downloading (my home Internet is very fast), 55 minutes installing while I could work (I expected that period faster because my laptop is also powerful), the percentages were much more regular than I saw in a month, and then I got the restart request which Windows Update failed to give me 20 times in the recent week. ;-) The restart only took 5 minutes in the "installation on black screen", plus the subsequent first login was about 2 minutes slower than I expected. Several restarts occurred on the black screens, counting up to 100% maybe twice, slightly smaller fonts than the usual installation of the patches. The new tool seems to be working, I am on 7840 now, too.
Ian, I think you are misunderstanding the build and updates. The update KB5077181 will give you build 26200.7840. (if you have version 25H2)
Luboš Motl that is all Greek to me! ;-) And Neil D I see conflicting AI messages about whether an update changes the build. So, if the update KB5077181 will give you build 26200.7840. (if you have version 25H2), are you saying the only way to get that update is to do a Settings > System > Recovery? too confusing & complicated! :-( Yet, great discussions!
Dear Brian, yes, you want to make Windows Update work properly, and if it does, it will give you the latest released Windows version from Feb 10th, 2026, which is 26100 or 26200 dot 7840. The patch that produces that latest version is stored as KB5077181 in the database. Yes, a button in Settings, System, Recovery is the only successful way to get there. But you may misunderstanding the recovery. It is not a clean install. It is a procedure that preserves all your files, apps, and settings! In practice, it is just a bit slower Windows Update that simply installs everything, even if a faster Windows Update would incorrectly think that you don't need it.
Now about 5 people including me succeeded so if you have an 800f error with KB5077181, don't hesitate, go to Settings, System, Recovery, and choose the SECOND tool on the right sidebar which is Fix Problems with Windows Update. It will only ask you whether you want an automatic restart after the in Windows part of the process is over, and then it switches you to Windows Update. On a fast PC, the whole process will take 10 minutes downloading plus 55 minutes of in Windows installation plus just 5 minutes of installation on black screens outside Windows, plus 2 minutes extra added to the first login. Everything will work, you will see in Settings About System that your Windows 25H2 was installed today! But in practice, you will not distinguish this repair process from the normal monthly Windows Update patch, except for the name of the patch, Windows 25H2 recovery version, or whatever is the right translation from Czech back to English LOL.
This is my Error code: (0x80073712) Do I really need the KB5077181 update because from what I read I have no issues with the Key Fixes. And is there a security reason why I need an update to my build 26200.7705? Thank you for clarifying the difference between recovery and clean install yet I am still hesitant because of all the confusion this update has caused!
Luboš
Many thanks for your help. Following your instructions ("Settings, System (in the left sidebar), Recovery (in the right column), Fix Problems Using Windows Update (2nd in the right column)" I was able to successfully install the Win 11 25H2 (repair edition)" patch, bringing my new laptop up to build 26200.7840.
Thanks for the heads up, Ian, a contribution to the thought that we might be in a successful or productive day. ;-) It surely looks like many if not all laptops that suffered from the error with this patch are rather or very new. My older notebook installed it smoothly right away, the new one did not.
The download is slow even though the game and other downloads are fast
As it is Windows 11 I would suggest using the recovery route.
Go to Settings > System > Recovery > Fix problems using windows update then select Reinstall now.
Nothing helped here with error 800f0922 (the same earlier for the January 2026 update) - neither dism nor offline update with wusa.exe nor clean up of Windows Update. Start > Settings > System > Recovery from recovery fixed the issues (took about 5 hours!)
Yesterday evening I decided to use : SYTSTEM - RECOVERY - FIX PROBLEMS USING WINDOWS UPDATE
After about 2 hours - reboot - and problems are gone ! No lost data (I use also Onedrive - Icloud en Proton Cloud) - All Apps, Office, application still works fine.
Instllation is now (HP Elitebook 255H - 32 GB RAM)
Edition Windows 11 Pro
Version 25H2
Installed on 13/02/2026
OS build 26200.7840
Cool to hear, Johan. Let me admit that I considered you my main role model for 991 so with this good beta tester, I will run the attempted fix that I have been recommending, too.
Andrejko, are you Czech? This diminutive may be common but don't we know each other from Harvard?
Did you use it for this update - ___KB5077181? ___I ask because Ian Thow just posted that this update is for Builds 26200.7840 and 26100.7840, which it does state parenthetically [2026-02 Security Update "(KB5077181)" (26200.7840)] yet I did not know that was the build for which it was meant. My build and Ian's build is 26200.7705 so why are we getting this update notice? And that may be the reason it is not installing!
Brian, No it wasn't because of this particular update. I have just used it in the past. It kept all my apps, programs, files etc. and just reinstalled windows.
The reinstall process was long before the clean install.
This particular update was no problem for me.
You are getting this update because your build is 26200.7705 which is a January update. 26200.7840 is the February update. (the next update in the list)
So, your build is either 26200.7840 or 26100.7840, which is why it was not an issue and why my 2 laptops had no issue with the update. However, I find it fascinating that when folks did the Settings > System > Recovery that they were able to install the KB5077181 update. Moreover, MS states, "[Networking] Fixed: This update (referring to the KB5077181 update) addresses an issue that prevented some devices from connecting to certain WPA3‑Personal Wi‑Fi networks. The issue might occur after you install KB5074105." Yet, the KB5074105 update was only for OS Builds 26200.7705 and 26100.7705. I am really confused! :-(
Finally, since the KB5077181 update is not for my OS build, do you know how I remove it from the Windows Update because it keeps wanting to 'retry'?
Brian and Neil, both of you seem to be confused about the numbering yet the resolution is so easy. And I think that someone at Microsoft was actually confused, too because my PC showed inconsistencies on whether I was eligible for the newer patches at various moments.
The January 13th patch was labeled KB5074109 and it is what upgrades the PC to 26100 or 26200 dot 7623. You cannot say which previous level of Windows the patch updates because the patches are cumulative so any Win 11 25H2, or whatever has the same half-year as your final version and is an older version at the same moment, can be upgraded to 7623. Similarly on January 29th, you had KB5074105 which upgrades a previous version to 7705. However, this patch is an optional preview version so it is normal to omit it. Similarly, the latest February 10th patch KB5077181 upgrades any previous version to 7840. That is the patch many of us had a problem with. Once successfully installed, we have the latest released Windows 11, 7840.
I did install the KB5074105 preview patch & i do have 26200.7705. Is that why the KB5077181 update will not install? If so, if I uninstall the KB5074105 preview patch, will the KB5077181 update install? Thank you.
Brian, 7705 is the version from the end of January. It is a preview version but I have a different PC, ASUS TUF, where I also did install 7705, and then updated to the latest 7840 from 7705 without any problems. The latest patch is from February 10th, that is the release date, the patch is called KB5077181, and it upgrades a previous version of Windows 11 to 26100 or 26200 dot 7840. This patch KB5077181 works with any previous version of Windows before a big upgrade, so it will work both on 7623 from early January as well as your 7705 from late January. If you fix the error using the Fix Problems with Windows Update tool in System, Recovery, you will get 7840. It has been verified to work against the errors starting with 800f. Your error might be a bit different but the tool really looks impressive. Again, the Fix Problems with WU tool is new for Windows 11, it preserves files and settings just like patches, runs just like Windows Update patches, and only takes about twice as long.
Brian, The preview install that took the system to .7705 does not effect KB5077181. KB5077181 will only install whatever is extra to the preview update, so should in theory be quicker than if you hadn't installed the preview.
The recovery install option is probably your best bet to make sure there are no other problems affecting the installation of Feb. build update.
Brian, In addition. (look at the link I provided) The Feb. update KB5077181 is for all builds irrespective of what you have installed. The cumulative updates will bring a system fully up to date even if the Jan. and Preview update have been missed.
If you wait until the March update that will take the system build to the new Mar. update even if you are unsuccessful in applying KB5077181. That assumes there is not something about your system that is stopping the updates from completing.
That is why the recovery option would be the best idea at this point.
I tried to uninstall the Preview KB5074105 update and got a message that it was required by my computer and cannot be uninstalled. So, I ran Settings > System > Recovery and it brought me to Build 26200.7840. Then I checked for the 2026-02 Security Update (KB5077181) update yet it was not in the history. So, I ran the update Standalone Installer again and the message came back that it was already installed. I guess the update to Build 26200.7840 automatically installed the 2026-02 Security Update.
MS confuses me because what I read the February 10, 2026—KB5077181 is for OS Builds 26200.7840 and 26100.7840.
Oh well, I think I am good, yet no more installing Preview updates! ;-)
I don't believe MS ever wrote that KB5077181 is "for" 7840. The KB5077181 is what brings Windows to 7840, it was always like that. Also, your argument against the 7705 preview, or any preview, release is utterly irrational. If something cannot be removed, it has a good reason, and whether or not the patch is a preview patch has nothing to do with the essential character of the patch.
Well, then we can agree to disagree. With all the issues with the preview update, I am just not willing to go there again & will wait for the 'real' update. Besides, I was not arguing, I was stating a fact! ;-)
As for "I don't believe MS ever wrote that "KB5077181 is "for" 7840", a link is worth a 1,000 words - https://support.microsoft.com/en-us/topic/february-10-2026-kb5077181-os-builds-26200-7840-and-26100-7840-f0fa9e54-a22a-4a06-96b6-bf5b2aded506
which states, "February 10, 2026—KB5077181 (OS Builds 26200.7840 and 26100.7840)" and I do not know any other way to take it. I am not willing to get into semantics over 'for'.
Luboš Motl sorry I misunderstood. At least Brian has the latest update installed now, which was the point of the comments in general.
@Brian When you carry out the recovery the updates are applied as part of the recovery and not individually as they would be once per month. Much the same as a clean install does not list all updates.
I don't have the option Get the latest updates as soon as they're available set On. But that's a personal choice.
I replied to your comment, yet MS deleted it why? I do not know because it was not inflammatory at all. I provided the MS link that stated "February 10, 2026—KB5077181 (OS Builds 26200.7840 and 26100.7840)", which I took to mean for those builds in parentheses.
As for any more preview updates, that is my choice and I am sticking to it! ;-)
Brian, AI sometimes removes things. I just read an article about a picture of a puppy and kitty that were removed as child porn on Facebook, the entrepreneur with these pets had her business destroyed, could not contact FB in any way etc. Good choice of yours, it is yours... but I believe it is based on misunderstandings. Do you understand that most people who had this error with 5077181 were avoiding 7705? My laptop that had the preview 7705 did install the 181 correctly, while this laptop where I avoided 7705 did not complete the 181! The error has nothing to do with the patch's preview status, either. If you avoid some updates, you may also avoid regular monthly patches, e.g. every other one.
Guys, I undeleted the comment from Brian. It can be a bit over zealous.
That is funny about FB! I am sure it is an AI thing.
It very well may be my misunderstanding, and I certainly am not afraid to admit that. Yet from **John DeV - *"***Microsoft has begun implementing and releasing Optional preview updates that are typically released on the 3rd or 4th week of every month. These updates allow admins to test the patch before its mandatory launch on Patch Tuesday (2nd week of the month). If you are not experiencing any issues with your system, there is no need to install the preview update." And since I am not an admin & if I do not have any issues, I will just wait & leave the Previews to the experts, which I am not!
With all that said, I really appreciated all the assistance & guidance that you, Neil D, & John DeV have provided. Years ago, when I was learning how to program in MS Access, I used this community to get through the rough spots, and I am glad to see that assistance & guidance are still available. Take care all.
Glad to hear that the issue has been resolved. You're most welcome, Brian, and have a great day.
High,
I installed Win11 pro last saturday 08/2/2026 - new laptop HP Elitebook 8 AD3T0ET#UUG
Yesterday update 2026-02 installed without problems (installation completed) ... (sorry messages are in, Dutch)
Today same update is still coming in and trying to apply (twice) ... now error 0x00f0991
How can this happens ... and now ?
2026-02 Beveiligingsupdate (KB5077181) (26200.7840) (2)
De installatie is mislukt op 11/02/2026 - 0x800f0991
2026-02 Beveiligingsupdate (KB5077181) (26200.7840)
De installatie is voltooid op 10/02/2026
same problem here: today second attempt to install failed with error 0x800f8011
This one just does not install, plain & simple!
Another of MS fantastic ********
Sebastian,
It installed without a hitch on 2 laptops! It is the desktop that is the issue! Who knows?
Same experience ... on my other laptop HP Elitebook 660 G11 ... installation also today no problems .... update is NOT reappearing
Yup. I've had this problem for two months now. They still have no idea and keep telling people the same old lame BS to solve it. FIX THE UPDATE.
It's not anything we can do differently.
All,
I have been having the same issue trying to download and install the 2026-02 Update, and I reached out to Microsoft for help. They collected my installation logs using the Feedback Hub, and they are investigating the issue right now, but they also mentioned that there are basically no other reports of this issue, so they are encouraging everyone/anyone to record your downloading and installation session using the Feedback Hub, as the more data points they have the faster they can resolve the matter.
Hi, good day!
Please let me know if you have tried the methods below.
If the issue persists, open Settings > System > Recovery.
Few things to check on the PC
Under Fix problems using Windows Update, click Reinstall Now
Once completed, your system will restart.
I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Do keep me informed by clicking "Add comment" below.
Standard Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
I literally made a Microsoft Learn account just to thank you! I've been having the exact same issue since this update rolled out. I couldn't find any solutions, even after reinstalling Windows. Your suggestion to manually reset the Windows Update components worked!
John DeV,
I did everything you suggested except for the Settings > System > Recovery for which I am very leery!
At one point Windows Update stated it completed et it is not in the history. The same thing happened yesterday. I do not believe it is a history thing because it installed fine on 2 laptops and it shows. Even the download did not work, i.e., the message came back that it was not installed.! :-(
With the Reset Windows Update components manually, I noticed there were a few lines that stated something was not found in the registry. Is there a way to look at that after the fact?
I ran the DISM tool and sfc /scannow again with no issues!
This is bizarre!
I have to thank you for your response that is infinitely better that the AI response, which I can get online anytime and have used it in Chrome & CoPilot in Edge. I go here for real people who know the issue and provide the assistance. So, thanks!
I recommend that you wait a few days and try installing the update again since it was recently released. You may consider continuing with the last method as it usually fixes this type of issue.
By the way, I really appreciate you taking the time to share that. My goal is always to provide clear, practical help that actually addresses the issue, so I’m glad I could assist in a way that felt more personal and useful.
Thanks again. I genuinely appreciate it!
I will wait a few days and hope it works. Just weird it worked on the laptops! Also, the Settings > System > Recovery method is the nuclear option, and I do not want to risk losing data especially because OneDrive has been wonky. Another issue! ;-)
Thanks again!
PS I just wish MS would listen about the AIi responses.
I understand. Feel free to reach out to this forum again if you have any concerns in the future.
Stay safe and have a great day.
Brian, it is funny you mention a wonky OneDrive, it was the primary reason I had to reinstall Windows 11 in the last week. I just lost access to all subfolders of the C Users Myself Onedrive personal folder, the problem with access lasted even when OneDrive was turned off as an app. Copilot (AI) recommended me absolutely safe brutal commands with ICACLS which made it impossible for me to successfully login or create a new user very quickly. Then I started with new Windows via Cloud Recovery, everything great for 9 days, and suddenly I could not install a patch.
I want to avoid the nuclear option as much as possible. Good luck!
Hi,
I've done everything you suggested, but I still can't install this darn update. What should I do? Just wait?
Won't that mess up my computer?
Best regards
Using the Recovery option to reinstall should fix any problems.
If it still doesn't install, please try reporting it through the Feedback Hub app to notify Microsoft. You may want to consider doing the last method as a last resort as it usually fixes this type of issue. Rest assured that your files and important data will not be lost.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
To resolve the issue with the 2026-02 Security Update (KB5077181) not installing and the error code (0x80073712), you can try the following steps:
DISM.exe /Online /Cleanup-image /Restorehealth
This command helps to repair the Windows image.C:\windows\logs\CBS\CBS.log for any specific errors related to the update. This may provide more insight into what files are causing issues. DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
Make sure to replace C:\temp\Source\ with the correct path of your repair source.These steps should help you troubleshoot and potentially resolve the installation issue with the update.