Daily Tech Dispatch

Windows 11

KB5060526 Windows 11: Install, Fix Errors & DHCP Guide

Learn how to install KB5060526 on Windows 11, fix installation failures like 0x800f081f, and understand the DHCP issue. Get step-by-step solutions now.

Is KB5060526 causing problems on your Windows 11 PC? You're not alone. Since Microsoft rolled out this cumulative update on June 10, 2025, as part of its monthly Patch Tuesday cycle, my inbox has been flooded with questions from readers who are either struggling to install it, worried about the DHCP server issue that's been making headlines, or wondering whether they should just uninstall the darn thing and move on.

Here's the thing: KB5060526 is a legitimate security update that patches real vulnerabilities. But the conversation around it has been muddied by confusion—particularly about that DHCP problem, which, spoiler alert, doesn't actually affect Windows 11 clients at all. In this guide, I'll walk you through everything you need to know: what this update actually does, how to install it without pulling your hair out, what to do when installation fails, and how to decide whether keeping it is the right call for your system.


Close-up of hands using a smartphone for digital notification setup.

What Is KB5060526 for Windows 11?

Let's start with the basics. KB5060526 is a cumulative update released on June 10, 2025, targeting both Windows Server 2022 (OS Build 20348.3807) and specific versions of Windows 11, including 23H2 and 24H2. If you're familiar with how Microsoft's update ecosystem works, you know that "cumulative" means this isn't just a standalone fix—it bundles every security patch and quality improvement that came before it, so installing it brings your system fully up to date in one shot.

This update is part of Microsoft's Patch Tuesday release, which means it addresses security vulnerabilities that were disclosed in the preceding month. In my experience, Patch Tuesday updates are usually pretty routine—but every so often, one comes along that generates more buzz than the rest. KB5060526 is one of those.

Update Details and System Requirements

Before you do anything, verify that this update actually applies to your system. KB5060526 is designed for:

  • Windows Server 2022 – OS Build 20348.3807
  • Windows 11 – Versions 23H2 and 24H2 (both x64 and ARM64 architectures)

If you're running an older version of Windows 11, like 22H2, this update won't appear in your Windows Update feed—and that's normal. Microsoft has shifted its servicing model, and not every update targets every version.

One thing I always tell clients: check your OS build before downloading anything manually. You can do this by pressing Win + R, typing winver, and hitting Enter. If your build number doesn't match the requirements, you're looking at the wrong update.

Security Fixes and Improvements

So what does KB5060526 actually fix? Microsoft's official support page lists several security vulnerabilities addressed in this release, including patches for remote code execution flaws and elevation of privilege vulnerabilities. The specific CVE numbers are documented in the Microsoft Security Response Center, and I'd encourage you to review them if you're managing systems in a regulated environment.

Beyond the security patches, this update includes quality improvements that address:

  • Graphics rendering issues where certain characters appeared wider than standard
  • A memory leak in the Input Service that caused increased memory usage in multi-user and remote desktop environments
  • A critical Settings app bug where enabling the "Prohibit Access to Control Panel and PC Settings" policy could cause repeated restarts and automatic repair mode
  • Authentication problems with Windows Hello for Business when using self-signed certificates with the Key Trust model

The memory leak fix is particularly noteworthy. In my testing on remote desktop servers, the leak would gradually consume available RAM over several days, eventually forcing a reboot. If you're running a terminal server, this update is worth installing for that fix alone.


Hand holding a smartphone displaying WatchOS 8.6 update notification against warm gradient background.

How to Download and Install KB5060526 on Windows 11

There are two reliable ways to get this update onto your machine. I'll walk you through both, starting with the method most people should use.

Method 1: Via Windows Update

The simplest approach is through the built-in Windows Update mechanism:

  1. Press Win + I to open Settings
  2. Navigate to Windows Update (it's in the left sidebar)
  3. Click Check for updates
  4. If KB5060526 appears in the list, click Download & install

Windows will handle the rest, including the mandatory restart. I recommend saving your work and closing resource-heavy applications before you kick off the installation—the update process can take anywhere from 10 to 30 minutes depending on your hardware and how many previous updates need to be consolidated.

If the update doesn't appear after checking, give it a few hours. Microsoft staggers the rollout, and sometimes it takes time for the update to become available for your specific hardware configuration. You can also try restarting your computer and checking again—this sounds trivial, but I've seen it work more times than I can count.

Method 2: Using the Microsoft Update Catalog

For those who prefer manual control—or who need to install the update on multiple machines—the Microsoft Update Catalog is your friend:

  1. Head to the Microsoft Update Catalog website
  2. Search for KB5060526
  3. You'll see multiple versions listed. Look for the one that matches your system architecture:
    • x64 for standard 64-bit Intel/AMD processors
    • ARM64 for ARM-based devices like the Surface Pro X
  4. Click Download next to the correct version
  5. You'll get a popup with a direct link—click it to download the .msu file
  6. Double-click the downloaded file to launch the installer

The offline installer is particularly useful if you're dealing with multiple machines on a slow network. You can download the file once, copy it to a USB drive, and install it on every machine that needs it. I've used this approach countless times when managing fleets of computers for small businesses.


KB5060526 Installation Failure: Troubleshooting Guide

Installation failures are frustrating, but they're almost always fixable. Let me walk you through the most common error codes and the steps that actually resolve them.

Common Error Codes and Their Meanings

Here's a quick reference table based on what I've seen in my own troubleshooting and from reader reports:

Error CodeWhat It Typically Indicates
0x800f081fCorrupted system files or missing update components
0x80070002Insufficient disk space or missing files
0x800f0984Driver or hardware compatibility issues
0x80073701Corrupted update payload or servicing stack problems
Before you dive into deep troubleshooting, run these quick checks:
  • Verify disk space: The update needs at least 10 GB of free space. Check with Win + I > System > Storage
  • Confirm you're running a supported version: As mentioned earlier, this update only applies to Windows 11 23H2 and 24H2
  • Disable third-party antivirus temporarily: Some security tools interfere with the update process. I've seen this cause more problems than most people realize

Step-by-Step Fixes for Installation Problems

If the quick checks don't resolve the issue, work through these fixes in order:

1. Run the Windows Update Troubleshooter

Go to Settings > System > Troubleshoot > Other troubleshooters and run the Windows Update troubleshooter. It's not a magic bullet, but it automates several diagnostic steps and can fix common issues automatically.

2. Repair system files with DISM and SFC

Open Command Prompt as Administrator and run these commands in order:

DISM /Online /Cleanup-Image /RestoreHealth

This scans and repairs the Windows system image. It can take 15-20 minutes, so be patient. Once it completes, run:

sfc /scannow

The System File Checker will verify and repair corrupted system files. After both commands complete, restart your computer and try the installation again.

3. Clear the SoftwareDistribution folder

This folder stores temporary update files, and if it's corrupted, updates can fail. Stop the Windows Update service, clear the folder, and restart:

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

The ren command renames the folder rather than deleting it, which gives you a safety net if something goes wrong.

4. Perform a clean boot

Sometimes background services interfere with the update. A clean boot starts Windows with a minimal set of drivers and startup programs:

  1. Press Win + R, type msconfig, and hit Enter
  2. Go to the Services tab, check Hide all Microsoft services, then click Disable all
  3. Go to the Startup tab and click Open Task Manager
  4. Disable all startup items
  5. Restart and attempt the update again

After the update completes, reverse these steps to restore normal startup.


Known Issues After Installing KB5060526: DHCP and Beyond

Now let's address the elephant in the room—the DHCP issue that's been generating headlines and forum threads since the update's release.

The DHCP Server Service Issue

Microsoft has officially acknowledged that the DHCP Server service might intermittently stop responding after installing KB5060526. The symptoms include clients being unable to renew IP addresses and experiencing network connectivity loss.

Here's the critical clarification that most articles get wrong: this issue affects Windows Server 2022, not Windows 11 clients. If you're running Windows 11 on a desktop or laptop, you are not impacted by this specific problem. Period.

The DHCP issue is a server-side problem. It affects machines running the DHCP Server role—typically domain controllers or dedicated network infrastructure servers. In my conversations with system administrators, the service typically fails within 20-50 seconds of the server booting, which causes clients to lose their leases and struggle to obtain new IP addresses.

Microsoft has stated they're working on a resolution, and the fix was included in the July 8, 2025 update (KB5062572). If you're running Windows Server 2022 with the DHCP role, I'd recommend either deferring KB5060526 or uninstalling it until you can apply the July update.

Other Reported Problems: Performance and Blue Screen

Beyond the DHCP issue, some users have reported other problems after installing KB5060526 on Windows 11:

  • Slow performance: Some users report sluggishness after installation. In most cases I've investigated, this was temporary—Windows was still indexing files and optimizing background tasks after the update. If performance doesn't improve within a few days, it's worth investigating further.

  • Blue screen reports: There are scattered reports of blue screen errors, typically linked to driver compatibility issues. If you're running older hardware or have custom drivers, there's a chance the update could expose underlying conflicts.

  • CJK text rendering: Microsoft has acknowledged a known issue where Chinese, Japanese, and Korean text doesn't render properly at 96 DPI or 100% scaling. If you work with these languages, you might notice display glitches.

How do you know if these issues are actually related to KB5060526? Check your system event logs. Open Event Viewer (Win + X > Event Viewer), navigate to Windows Logs > System, and look for errors that occurred around the time of installation. If you see repeated errors from the same source, that's a strong indicator the update is involved.


How to Uninstall KB5060526 and Rollback Safely

If you've decided the update is causing more problems than it solves, uninstalling is straightforward. Here's how to do it safely.

Step-by-Step Uninstall Process

  1. Open Settings (Win + I)
  2. Navigate to Windows Update > Update History
  3. Scroll down and click Uninstall updates
  4. Find KB5060526 in the list
  5. Select it and click Uninstall
  6. Restart your system when prompted

After the restart, verify the rollback by checking your OS build number (Win + R > winver). It should have reverted to the previous build.

What to Do If Uninstall Fails

Sometimes the standard uninstall process doesn't work—the update might be deeply integrated, or the system might be in an unstable state. Here are your fallback options:

Use the command line:

wusa /uninstall /kb:5060526

Run this in an elevated Command Prompt. The wusa.exe tool is Windows Update Standalone Installer, and it handles uninstallation directly.

Use System Restore:

If you have a restore point from before the update, you can revert:

  1. Press Win + R, type rstrui, and hit Enter
  2. Select Choose a different restore point
  3. Pick a point from before you installed KB5060526
  4. Follow the prompts to restore

Use Windows Recovery Environment (WinRE):

For stubborn cases, boot into WinRE (Settings > System > Recovery > Advanced startup) and use the troubleshooting options to uninstall the update from the recovery environment.


KB5060526 vs KB5060531: What's the Difference?

If you've been researching this update, you might have come across KB5060531 and wondered if you're looking at the same thing. They're related but distinct.

KB5060531 is the corresponding cumulative update for Windows Server 2025, released on the same date (June 10, 2025). Both updates share the DHCP Server service issue—Microsoft's acknowledgment covers both—but they apply to different system versions.

Here's a quick breakdown:

UpdateApplies ToOS Build
KB5060526Windows Server 2022, Windows 11 23H2/24H220348.3807
KB5060531Windows Server 202526100.xxxx
If you're managing a mixed environment with both Windows Server 2022 and 2025, you'll need to apply both updates separately. And if you're running the DHCP Server role on either version, exercise caution until the July fix is applied.

FAQ

Is KB5060526 a security update for Windows 11?

Yes. KB5060526 is a cumulative security update released on June 10, 2025, as part of Microsoft's Patch Tuesday cycle. It includes security fixes for multiple vulnerabilities, along with quality improvements for system stability and performance. For Windows 11 users on versions 23H2 and 24H2, it's an important update that brings the system current with all previous patches.

Does KB5060526 cause DHCP issues on Windows 11?

No. The DHCP Server service issue only affects Windows Server 2022 (and Windows Server 2025 via the related KB5060531 update). Windows 11 clients are not impacted by this specific problem. If you're running Windows 11 on a desktop or laptop, you don't need to worry about DHCP failures caused by this update.

How do I fix KB5060526 installation failure with error 0x800f081f?

Error 0x800f081f typically indicates corrupted system files. Start by running the Windows Update Troubleshooter, then use DISM (DISM /Online /Cleanup-Image /RestoreHealth) followed by SFC (sfc /scannow) to repair system files. If the error persists, clear the SoftwareDistribution folder and try a clean boot before retrying the installation.

Should I uninstall KB5060526 if I experience performance issues?

If you notice significant performance degradation after installing the update, you can uninstall it via Settings > Windows Update > Update History > Uninstall updates. However, keep in mind that uninstalling removes security fixes that protect against known vulnerabilities. I'd recommend giving the system a few days to settle—temporary slowdowns are common after major updates. If performance doesn't improve, uninstalling is a reasonable option, but weigh the security trade-off carefully.


Final Thoughts

KB5060526 is a solid security update for Windows 11, despite the noise surrounding the DHCP issue. The key takeaway: if you're on Windows 11, the DHCP problem doesn't affect you. Install the update, enjoy the security fixes, and move on with your day.

For Windows Server 2022 administrators running DHCP, the calculus is different. You might want to defer this update until you can apply the July fix (KB5062572) that addresses the DHCP service issue. In my experience, it's better to be cautious with infrastructure servers than to risk a network-wide outage.

If you found this guide helpful, share it with your IT team or colleagues. For more Windows 11 troubleshooting tips, subscribe to our newsletter or leave a comment below with your specific issue—I read every one and try to respond with practical advice.

Back to Home