Some users report Windows 11’s February update, KB5077181, is failing to install and causing a range of system issues

Screenshot of Windows 11 settings with a skull and crossbones overlay
(Image credit: Future)

Microsoft's February 2026 cumulative update for Windows 11, known as KB5077181, is generating a growing number of reports from users experiencing installation failures and system instability after applying the patch.

Although the company has not acknowledged any critical issues, multiple reports across Microsoft's Q&A forums reported a variety of error codes, including 0x800F0991, 0x800F0983, 0x800F0922, 0x80073712, and 0x80096004. In addition, DHCP errors have prevented internet access on some devices, leaving Wi-Fi connected but nonfunctional.

Installation failures

Problems with this update begin with the installation process itself. Many users reported that KB5077181 fails to complete, resulting in errors such as 0x800F0991, 0x800F0983, 0x800F0922, 0x80073712, and 0x80096004.

Of all these errors reported in the forums, only the error code 0x800F0922 had an accepted answer. While the original users didn't mention the method that resolved the issue, solutions included disabling Windows Sandbox and Hyper-V, temporarily disabling third-party antivirus software, and using the DISM command to restore system health.

👉How to protect your PC from buggy Windows 11 updates with restore points, Quick Machine Recovery, and full backups

On the report for error 0x800F0991, a commenter noted that the original error originated as 0x800F0983, and later, "the error switched to the number with 991." In this case, the person also noted that they have tried the DISM command, resetting the Windows Update components, and other methods, but everything failed.

Another user also reported a similar issue, but with the error code 0x80073712, with the "Some update files are missing or having problems. We'll try to download the update again later. "

The only reliable solution for installation errors has been to perform a repair reinstall of Windows 11 using the "Windows Update" recovery option through the Settings app.

Network connectivity problems

Some users have been reporting that KB5077181 disrupts network connectivity after reboot, particularly affecting Wi-Fi connections with DHCP errors.

Mills Robert described his experience: "after the restart my wifi failed with a dhcp error. Connected but no internet." He continued saying, "I tried resetting adapters, rebooting, etc then using the troubleshooting tool and internet advice, but nothing worked."

The most effective temporary fix has been uninstalling the update and pausing Windows Update until Microsoft releases a corrected patch.

Bluetooth failures

The update KB5077181 also interferes with Bluetooth devices. Sergei reported, "latest update KB5077181 broke my Bluetooth on Windows 11, I cannot use my mouse or airpods because system says I don't have bluetooth anymore."

This person noted that no yellow warnings appeared in Device Manager, and reinstalled the drivers, but it didn't work. However, later on, he found success with a full power reset: shutting down the PC, unplugging it for 10 minutes, or holding the power button for 30 seconds before rebooting restored Bluetooth and sometimes Wi-Fi connectivity.

Audio glitches and system hangs

Several users with gaming laptops reported audio malfunctions and system freezes after installing the February 2026 Security Update.

Edric Atreides explained that the update caused his audio to pop every second, ultimately freezing the system at sign-in.

In this case, the user pointed out that the solution required either a full SSD wipe and OEM system restore or a repair reinstall of Windows 11.

Beyond installation and connectivity failures, KB5077181 is also linked to graphics-related issues, particularly on systems with Nvidia GPUs or external displays. A few users report that the update disrupts sleep behavior, graphics stability under load, and HDMI output detection. In some cases, rendering systems are unusable until the patch is uninstalled.

According to george carlin, the update appears to reintroduce longstanding "S3 sleep" issues, causing system freezes accompanied by a black screen after resuming from sleep. He also reported NVIDIA-related instability, with the system freezing under GPU load after installing the update.

In the same forums, EHG noted a similar problem, explaining that his "Samsung TV connected through an NVIDIA 3050 wouldn't load after the update. I tried reinstalling KB5077181 twice, but it didn't help."

Finally, Luciene Nascimento reported an HDMI signal loss on an external monitor after installing build 26200.7840, adding that uninstalling the update resolved the issue immediately.

Bottom line

While the number of reports remains relatively small compared to the overall Windows 11 install base, the range and severity of the issues linked to KB5077181 show that some users are still being negatively affected by cumulative updates.

Although most devices will likely install the February 2026 update without incident, the persistence of installation failures and post-update instability highlights an ongoing challenge for Microsoft in delivering consistent update quality across an increasingly diverse set of hardware configurations.

Did you stumbled upon any issues after installing the February 2026 Security Update on Windows 11? Let me know in the comments.

More resources

For more helpful articles, coverage, and answers to common questions about Windows 10 and Windows 11, visit the following resources:


Click to join us on r/WindowsCentral

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.


Mauro Huculak
Windows How-To Expert

Mauro Huculak has been a Windows How-To Expert contributor for WindowsCentral.com for nearly a decade and has over 22 years of combined experience in IT and technical writing. He holds various professional certifications from Microsoft, Cisco, VMware, and CompTIA and has been recognized as a Microsoft MVP for many years.

You must confirm your public display name before commenting

Please logout and then login again, you will then be prompted to enter your display name.