Windows 11 November 2026 Patch Tuesday (Nov 10): Prepare, Fix Update Errors and Known Issues

What we know today, and what we do not know yet

The November 2026 Patch Tuesday lands on Tuesday, November 10, 2026, the second Tuesday of the month. As of November 5, nothing about its contents, its KB number or its bugs has been published, so this page does not pretend to know them. Instead, it gives you a method you can use on any Patch Tuesday: prepare before it, read the release notes correctly, fix the common failures, and check Microsoft's known issues list instead of trusting rumours.

Microsoft normally publishes the monthly security update in the morning, Pacific time, on the second Tuesday. The update shows up for most home PCs through Windows Update within hours, although the exact rollout can vary by device, region and whether you chose to get updates as soon as they are available. The KB number and the build numbers will be listed on the Microsoft support page for the release and on Windows release health once the update ships. We will add them to this page after November 10, and not before.

Why write the page early? Because the best moment to protect a PC is the week before the update, not the hour after it fails. Most people who lose a night to a broken update skip the three boring steps in the next section: a backup, a restore point, and a glance at the release health page. If you only read one part of this guide, read the checklist below.

What is already confirmed about the current state of Windows 11

Windows release health for Windows 11 version 25H2 was last updated on November 5, 2026 and shows that Windows 11 version 26H2 is now offered to all eligible devices. The same page lists a small set of known issues from the last few months. Most are marked resolved. One is still open, a USB audio problem that Microsoft describes as mitigated. We list all of them in the known issues section with their official status, and we only report what Microsoft's page states.

If you want the story of last month's update first, our October 2026 Patch Tuesday known issues and fixes guide covers what shipped on October 13 and how people handled it. This page is the forward-looking companion: it is built to be useful before, during and after November 10.

Should you install the update right away?

For most home users the answer is yes, within a reasonable window, because Patch Tuesday updates carry security fixes and delaying them leaves known holes open. The sensible middle path is to prepare first, let the update install when you can afford an hour of downtime, and keep the ability to undo it. For a business PC that runs a critical application, a short delay of a few days while you watch release health is a normal practice, as long as you do not delay for weeks.

What we do not recommend is switching updates off for months. Paused updates only last a limited time, and a PC that skips security updates is the PC that ends up in the ransomware stories. If you manage a small office, our ransomware explainer shows why patch discipline matters.

What to do before Patch Tuesday: the 60-minute preparation

Before November 10, do four things: back up your files to a second place, make sure a restore point can be created, decide when the update will install, and check Windows release health for open issues that match your hardware. This takes about an hour the first time and ten minutes afterwards.

Step 1. Back up your files (and verify the backup)

An update that fails is usually harmless, but an update that fails while the disk is already unhealthy can turn a bad day into a data loss. A real backup means your important files exist in at least two places, and one of them is not the same disk. For most people that means an external drive plus a cloud copy. Open the backup, pick one file at random and confirm it opens. A backup you never tested is a hope, not a backup.

If you already use OneDrive, keep in mind that a synced folder is not a backup: deleting or corrupting a file on your PC propagates to the cloud copy. For a deeper look at what a proper plan looks like for an office, see our cloud backup guide for Canadian businesses. If a PC has already been wiped by a failed update, our guide to data recovery after a Windows update or reinstall explains what can still be saved and what to stop doing immediately.

Step 2. Check that you can create a restore point

System Restore can roll system files, drivers and registry settings back to an earlier moment without touching your documents. It is not turned on by default on every Windows 11 PC, so check it now rather than during a crisis.

1. Press the Windows key, type Create a restore point and open the result.
2. On the System Protection tab, select your Windows drive (usually C:) and choose Configure.
3. If protection is off, switch it on and give it a few percent of the disk. Apply.
4. Choose Create, name it "Before November 2026 updates" and wait for the confirmation.

Windows may also create its own restore point when an update installs, but only when the feature is on and conditions allow it, so do not count on it. A manual restore point takes under a minute and gives you a documented way back.

Step 3. Decide when the update installs

Open Settings, Windows Update. On current Windows 11 builds you can use Pause updates to delay installation for a limited number of weeks, and Active hours or Schedule the restart to avoid a surprise reboot in the middle of a meeting. Menu wording changes slightly between builds, so look for these options rather than a fixed path.

A pause is a tool, not a plan. Our advice for November is simple: if your PC is a family laptop, let the update come and install it on a quiet evening. If the PC runs accounting software, a scanner, a point of sale or specialised drivers, pause for a few days after November 10, read the release health page, then install on a day when you are not on deadline. Do not leave the pause on for the full maximum.

Step 4. Check Windows release health and your own device

Bookmark the Windows 11 release health page and read the known issues table for your version. In the 25H2 table you will see the issue summary, the originating update, the status (for example Resolved or Mitigated) and the last updated time. Then ask three questions: does the issue match my hardware or setup, is it marked resolved, and is there a safeguard hold? A safeguard hold means Microsoft is deliberately not offering the update to devices with a known incompatibility, which is a good thing.

Also check the simple things on your own machine: at least 20 GB of free space on the system drive for a comfortable update, a charger connected on a laptop, no pending firmware warnings, and no external devices you do not need plugged in (printers, USB hubs, old docks). Unplugging them removes a whole class of driver surprises.

Why the BitLocker key matters on update day

Some updates, especially firmware or boot-related ones, can cause a PC with device encryption to ask for the recovery key at the next start. Without the key the drive stays locked. Signed-in Microsoft accounts usually store the key online, and work PCs may store it with the organisation. Look it up now, not at 7 a.m. on a screen asking for 48 digits.

How to read the release notes and the KB article

Every Patch Tuesday update has a Microsoft support article titled with the release date, the KB number and the OS build. Read four parts: the highlights or improvements, the known issues section, the servicing stack and prerequisites notes, and the file or update replacement information. Ten minutes with the article is worth more than an hour of forum scrolling.

Decode the title

The article title carries three facts. The date is the release date. The KB number identifies the update, and it is the string you search for in Windows Update history. The OS build tells you what number you will see in winver after installing. Windows 11 versions 24H2, 25H2 and 26H2 share a common servicing branch, so one update commonly lists several build numbers, one per version, with the same last digits.

Which type of update is it?

There are several kinds of monthly releases, and mixing them up causes confusion:

• Security update (Patch Tuesday, "B" release): the second Tuesday. Security fixes plus quality fixes.
• Non-security preview update ("C" or "D" release): optional, usually in the last week of the month. It previews next month's fixes and is only installed automatically if you opt in to get the latest updates as soon as available.
• Out-of-band (OOB) update: an unscheduled release, often to fix a problem introduced by a previous update. The release health page mentions one such case from September 14, 2026.

This is why release health references more than one KB number for the same problem: the problem is introduced in one update, and the fix arrives in a later one. For October the pattern was visible on the release health page: issues with an originating update in August or September were marked resolved by the October 13 update or by the October 28 update, which Microsoft lists under KB5127936.

Read the "Known issues" and "How to get this update" parts

The known issues section of a KB article is often short and links back to release health, which is the authoritative, updated list. The "How to get this update" section tells you the channels: Windows Update, Microsoft Update Catalog, WSUS. If you manage several PCs, the standalone package from the Update Catalog is useful for a retry, but it does not replace reading the prerequisites.

Finally, note the servicing stack update (SSU) line. Modern Windows 11 packages bundle the SSU with the cumulative update, which affects how you uninstall them later. We come back to that below.

Where rumours come from, and how to filter them

Within hours of every Patch Tuesday, social posts and videos announce that "the update breaks X". Some are right, many are a single user's driver problem. Use a three-source rule: a problem is credible when (1) it appears on Microsoft's release health page, (2) several independent users with different hardware report the same symptom, and (3) the fix or workaround is documented by Microsoft or a reputable vendor. If only one of those is true, treat the story as unconfirmed and keep your backup handy.

The common classes of Windows Update failure

Nearly every failed Windows update falls into one of six classes: not enough space, corrupted update cache, damaged system files, a driver or security product in the way, a hardware or disk fault, or a boot-level problem after installation. Identifying the class tells you which fix to try first.

Step 1: read the error code, but do not panic about it

Error codes look scary but each one narrows the cause. We keep dedicated pages for the most frequent ones. Here is a quick map, with links to the full fix for each:

• 0x800f0922: usually a space or partition problem, or a failure while the update configures components. Often involves a small system partition or a VPN. See our 0x800f0922 fix for Windows 11.
• 0x80070002: files the update expects are missing or the update cache is damaged. See error 0x80070002.
• 0x80073712: a component the update needs is missing or corrupted in the component store. See error 0x80073712.
• 0x800f081f: Windows cannot find the source files it needs to repair or enable a feature. See error 0x800f081f.
• 0x80070005: access denied, often permissions or a security product. See error 0x80070005.

For the general picture of why updates stall or fail and how to work through them, our broader Windows Update stuck or failing guide goes deeper than this page can. Here we keep to the sequence we use on update day.

Step 2: run the built-in troubleshooter

In Windows 11, open Settings, System, Troubleshoot, Other troubleshooters and run the Windows Update troubleshooter. It resets a few services and clears some obvious blockages. It fixes fewer cases than people hope, but it costs one minute and rules out the simple ones.

Step 3: free space and unplug the extras

Windows needs room to download, unpack and keep a copy of the previous state. On a PC with under 10 GB free, updates fail in confusing ways. Open Settings, System, Storage, run Temporary files cleanup, and empty the Recycle Bin. Then shut down, unplug external drives, docks, printers and USB gadgets, and try again with only mouse, keyboard and power.

Step 4: repair system files with DISM and SFC

These two built-in tools repair the component store and system files. Open Terminal (Admin) or Command Prompt (Admin) and run the commands one at a time, letting each finish:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

RestoreHealth can sit at 20 percent or 62 percent for a long time, and that is often normal. It needs internet access to fetch good copies of files from Windows Update. When it completes, restart and try the update again. If DISM itself fails with a source error such as 0x800f081f, that is a sign you need a repair install, which keeps your files and apps.

Step 5: reset the Windows Update components

If the cache is damaged, the cleanest fix is to stop the update services, rename the two folders where Windows keeps its working files, and start the services again. In an administrator Command Prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Windows rebuilds both folders. You lose the local update history view, not the installed updates. Restart and check for updates again. Keep the .old folders for a week in case a support technician wants to look, then delete them to recover space.

Step 6: "stuck at percent" and what to do about it

People ask the same question every month: the screen says "Working on updates, 30 percent, do not turn off your computer" and it has not moved for an hour. What now?

• Be patient longer than feels natural. The percentage on the restart screen is not linear. The final configuration phase on a slow hard drive can take well over an hour. A slow laptop on battery can take longer.
• Look for disk activity. If the drive light blinks or the fans move, it is probably working. A completely silent, frozen machine for several hours is different.
• Do not hold the power button as the first step. A forced shutdown during servicing can corrupt files. It is sometimes the only option, but treat it as the last resort after a long wait, for example two to three hours with no sign of activity.
• If you have to force it off, let Windows try to roll back by itself at the next start. Do not interrupt a rollback either.

If the PC then lands on a recovery screen or repeats the loop, jump to the WinRE section below.

Step 7: the rollback loop

A message such as "We couldn't complete the updates, undoing changes" means Windows detected a failure and is reverting. It is working as designed. The cause is usually a driver, a third-party security tool, low disk space or corruption. After the rollback finishes, do not retry blindly. Free space, update the PC maker's drivers and BIOS if they are old, temporarily uninstall third-party antivirus (keeping Windows Security active), run DISM and SFC, and then retry once. If it fails the same way twice, stop and look for the error in Update history.

How to uninstall a Windows update that causes a problem

If a freshly installed update causes a real problem and your PC still starts, open Settings, Windows Update, Update history, Uninstall updates, choose the update by its KB number and remove it, then pause updates for a short time until Microsoft publishes a fix. Only uninstall when the problem started right after the update; removing security fixes without a reason is a trade-off, not a free action.

The graphical way

1. Open Settings, Windows Update, Update history.
2. Scroll to Related settings, Uninstall updates.
3. Find the KB number (it is listed with an installation date) and select Uninstall.
4. Restart when asked.

If Uninstall is not offered for an item, Windows is telling you that the update is not removable that way. Some cumulative packages are bundled with the servicing stack, and for those the Settings page may not give you the option.

The command line way

For ordinary updates, an administrator prompt can run wusa /uninstall /kb:NUMBER (replace NUMBER with the digits of the KB). For a combined package that wusa refuses to remove, administrators use DISM: list the packages with DISM /Online /Get-Packages, find the package whose identity matches the update, and remove it with DISM /Online /Remove-Package /PackageName:NAME. Be careful with the exact package name, and do not remove anything you cannot identify. If this paragraph looks risky, that is the right instinct: ask for help rather than experiment on a work PC.

What about the 10-day rollback after a feature update?

Feature updates such as moving to a new Windows 11 version offer a "Go back" option for a limited period, in Settings under System, Recovery. That is separate from uninstalling a monthly update, and the option disappears after the window passes or if you clean up the old files with Disk Cleanup. Monthly security updates do not use that mechanism.

After uninstalling: pause, do not forget

Windows will try to install the same update again at the next check. Use Pause updates for one or two weeks, watch release health for a fix, and reinstall when the status changes. Write down the KB number and the date so you can explain what you did if a support person asks later.

Windows Recovery Environment (WinRE): when the PC will not start after an update

If Windows will not start after an update, the Windows Recovery Environment lets you uninstall the latest quality update, run Startup Repair, use a restore point or open Safe Mode without a working desktop. Windows normally opens WinRE by itself after two or three failed start attempts. You can also force it.

How to get into WinRE

• Automatic: after repeated failed boots, Windows shows "Preparing Automatic Repair" and then a blue recovery menu. Choose See advanced repair options.
• From a working or half-working desktop: hold Shift and select Restart from the Start menu or sign-in screen.
• Forced: if nothing else works, power the PC on and interrupt the start with the power button when the logo appears, three times in a row. Use this only if the PC is otherwise stuck, because repeated hard power-offs are not good for any disk.
• From a USB recovery drive: if WinRE is damaged, boot from a recovery drive you prepared on another PC (this is what the photo near the top of this guide illustrates).

What each WinRE option does

The order we use on a PC that will not start

1. In WinRE choose Troubleshoot, Advanced options, Uninstall Updates, Uninstall latest quality update. If the problem began right after Patch Tuesday, this is the highest-yield fix.
2. If that does nothing, try Startup Repair.
3. Then System Restore, picking the restore point you created before updating.
4. Try Safe Mode with Networking and remove the most recently installed driver or security tool.
5. Only if all of this fails, think about Reset this PC, and before that, copy your files off the drive with the Command Prompt option or ask a technician to do it.

Is WinRE even enabled on your PC?

You can check before an emergency. In an administrator Command Prompt, run reagentc /info. It reports whether Windows RE is enabled and where its image sits. If it says Disabled, reagentc /enable usually turns it back on. If the recovery partition is missing or too small, do not experiment: that is a case for a technician. A PC with a broken WinRE has no safety net when an update goes wrong, which is why we check it during preventive maintenance.

BitLocker prompts inside WinRE

If the drive is encrypted, WinRE may ask for the BitLocker recovery key before it lets you use the drive. This is by design. It is the reason the checklist asked you to store that key somewhere safe.

Three realistic scenarios (illustrative)

Realistic scenario (illustrative, not a real client case). These examples show how the steps combine. Numbers are plausible, not statistics.

Scenario 1: home laptop, update stuck at 35 percent for 90 minutes

A 5-year-old laptop with a hard drive and 8 GB of memory reaches "Working on updates 35%" after the restart. The owner waits another hour while the drive light still blinks, and the update completes at the two-and-a-half-hour mark. No action was needed beyond patience. Lesson: on an older hard drive, the configuration phase is slow, and the busy drive light is the sign that things are alive.

Scenario 2: small accounting office, one PC rolls back twice

One of six office PCs shows "Undoing changes" two nights in a row. The other five updated fine. The affected PC has 6 GB free on a 256 GB drive and an old USB docking station. The owner clears 40 GB of old files, unplugs the dock, runs DISM RestoreHealth and SFC, and the update installs on the third try. The office keeps the other PCs on the same patch cycle and sets a calendar reminder for the next month. Lesson: low space and peripherals cause most single-PC failures.

Scenario 3: a PC will not reach the desktop after a restart

A desktop restarts into a black screen with a spinning circle, twice. On the third restart Windows shows the recovery menu. The user goes to Troubleshoot, Advanced options, Uninstall Updates, removes the latest quality update, and the PC starts normally. They then pause updates for a week, check Windows release health, and retry. Lesson: knowing the WinRE path turns a panic into a ten-minute job.

Known issues (we update this page after Nov 10)

This section lists only issues that Microsoft's Windows release health page for Windows 11 version 25H2 shows as open, and the recent ones it shows as resolved, as of November 5, 2026 (the page's own "last updated" date that day). Nothing about the November 10 update is listed here because it has not been released. We will edit this section after November 10.

Still open on November 5, 2026

If your USB headset, DAC or microphone stopped working after the September update, check Device Manager for a Code 10 on the device and compare it to this entry. Our own tip, which is not a Microsoft instruction: try a different USB port and reboot with the device unplugged, then reconnect it. Microsoft's page mentions that some customers restored sound by switching to 2-channel mode for the multichannel symptom, and notes that this specific behaviour is resolved in the September 14 out-of-band update. If your problem is the Code 10 itself, expect to wait for Microsoft's fix, or to use a device that is not USB Audio Class 1.0, such as a Bluetooth or a different class of headset.

Recently resolved, for context

For the full October story, including how these items developed during the month, see our October 2026 Patch Tuesday guide.

What this section will contain after November 10

After the update ships, we will read the November KB article and the release health page, then add the KB number, the build numbers, the issues Microsoft lists, their status and the official workaround for each. We will not add an issue because it is trending on social media. Until then, if you see someone claiming that the November update breaks something, ask for the Microsoft page that says so.

After the update: the 24-hour watch and when to install the next one

After installing, spend two minutes confirming the update is listed in Update history, then use the PC normally for a day while watching for new symptoms: sound, printing, network, sign-in and your key applications. Most regressions appear within the first day or two.

• Open Settings, Windows Update, Update history and confirm the KB shows "Successfully installed".
• Run winver and note the OS build so you can quote it to a support person.
• Test the five things you depend on: Wi-Fi or Ethernet, Bluetooth and USB audio, printing, your VPN or remote access, and your business application.
• If something breaks, search the symptom on Windows release health before you change anything.
• If you must uninstall, use the steps above and write down the KB number and date.

What about moving to a newer Windows 11 version?

Release health says that Windows 11 version 26H2 is available for all eligible devices and that Microsoft recommends updating to it. Whether to jump the same week as a Patch Tuesday is a separate decision. Our advice is to change one thing at a time: install the monthly update, wait a few days, and then do a feature update when you have a fresh backup. For version choices and what the recent versions changed, see our Windows 11 25H2 update guide. If you are still on Windows 10, the Windows 10 end of life migration guide explains the options.

What this costs: do it yourself versus calling a technician

The backup drive price is an indicative range, not a quote, and prices change. The point of the table is the trade-off: an hour of preparation is cheap compared to a day of lost work.

Official resources to bookmark

• Windows 11 version 25H2 known issues and notifications on Microsoft Learn (Windows release health), the page we used for the known issues section.
• Microsoft's Windows message center, for announcements about upcoming changes.
• The Windows 11 update history page on support.microsoft.com, which lists each release, its KB number and OS build.
• Microsoft's guidance "Troubleshoot problems updating Windows" on support.microsoft.com.
• Microsoft's guidance on safeguard holds (KB5006965), explaining why some PCs do not get an update yet.
• The Get Help app in Windows, and the Feedback Hub for reporting problems to Microsoft.

When to call a pro

Stop and call for help when the PC loops in recovery, when you see a BitLocker recovery prompt and do not have the key, when disk errors or clicking noises appear, when DISM fails with a source error you cannot resolve, or when the PC is the one thing your business cannot do without. Doing more repairs on a dying disk can reduce the chance of saving your data. IT Cares has supported Windows PCs in Quebec and across Canada since 2014. We can connect remotely, run the repair with you watching, and explain what happened. Call 1 (888) 711-9428 or use the booking button below.

Summary: the method in six lines

1. Back up and test the backup before Patch Tuesday.
2. Make sure a restore point can be created, and save your BitLocker key.
3. Read the release notes and the known issues table for your Windows version.
4. Install when you can afford an hour of downtime, with the PC plugged in.
5. If it fails, work from space and peripherals, to DISM and SFC, to the update component reset.
6. If it breaks the PC, uninstall the update (Settings or WinRE), pause for a short time, and wait for a documented fix.

Note on freshness: this page was last verified on November 5, 2026, before the November 10 update was released. Its known issues section will be revised after the release.

Frequently asked questions

Related guides

• October 2026 Patch Tuesday: known issues and fixes
• Windows Update stuck or failing: complete fix guide
• Windows 11 update failed 0x800f0922: fix
• Windows 11 25H2 update guide
• Data recovery after a Windows update or reinstall
• Cloud backup guide for Canadian businesses

Sources and official references

Last verified: November 5, 2026

• Windows 11, version 25H2 known issues and notifications (Microsoft Learn, Windows release health), page dated November 5, 2026