Why Won’t My Scanner Be Detected After a Windows Update? Fix Guide 2026

By 2026, thousands of users have searched for the same frustrating answer: why won’t my scanner be detected after a Windows update? You install a routine update, reboot your PC, and suddenly your scanner vanished from Device Manager. The printer works fine, but every scanning app throws “No scanners were detected” or “Cannot communicate with the scanner.” I have helped dozens of people through this exact scenario, and in nearly every case, the fix comes down to one of a handful of causes.

The most common reasons your scanner is not detected after a Windows update are outdated or corrupted scanner drivers, the WIA (Windows Image Acquisition) service stopping during the update, changes to the eSCL protocol in Windows 11 24H2, or a specific KB patch breaking scanner communication. You can fix this by working through the following solutions in order:

1. Restart your PC and reconnect the scanner to a different USB port
2. Check Device Manager for your scanner under Imaging Devices
3. Update or reinstall your scanner driver from the manufacturer website
4. Restart the Windows Image Acquisition (WIA) service
5. Disable and re-enable Windows Fax and Scan
6. Run the Hardware and Devices Troubleshooter
7. Repair corrupted system files using SFC /scannow
8. Install the latest cumulative update (KB5055523 or newer for Windows 11 24H2)

I will walk you through each of these fixes step by step. I will also cover the specific Windows 11 24H2 eSCL protocol bug that has affected Canon, HP, Epson, Fujitsu, and Brother scanners since late 2026, along with the exact KB patches that cause and resolve the problem.

What Causes a Scanner to Stop Being Detected After a Windows Update

When Windows updates, it does not just patch security holes. It can also replace system files, update drivers, change service configurations, and modify communication protocols. Any of those changes can break the connection between your scanner and your PC.

Here are the six root causes I see most often when a scanner disappears after an update:

1. Driver Incompatibility: Windows may replace your manufacturer-specific scanner driver with a generic Microsoft driver during an update. The generic driver often lacks TWAIN or WIA support that your scanning software needs. This is the single most common cause, and it affects every brand from Canon to Fujitsu.

2. eSCL Protocol Changes (Windows 11 24H2): Microsoft modified how Windows 11 24H2 handles the eSCL (Scanner Internet Protocol) protocol. This change broke USB scanner detection for dozens of scanner models across multiple manufacturers. Ricoh, Canon, and Microsoft have all acknowledged this issue.

3. WIA Service Disruption: The Windows Image Acquisition service manages communication between Windows and imaging devices. If an update stops, pauses, or corrupts this service, your scanner will not appear in any scanning app, even though it shows up in Device Manager.

4. Corrupted System Files: Large feature updates can corrupt system DLLs and registry entries that scanners depend on. When these files are damaged, the WIA service cannot initialize properly, and scanning fails silently.

5. USB Port Reassignment: Windows updates sometimes reset USB controller assignments. Your scanner may have been on USB Port 3 before the update and gets reassigned to Port 1 after, confusing the driver. This is why simply plugging into a different port fixes many cases.

6. Problematic KB Patches: Specific Windows updates have been confirmed to break scanner detection. KB5044284, KB5044384, and KB5046617 are the most commonly cited culprits for Windows 11 24H2. Microsoft has released KB5048667 and KB5055523 as fixes, but not every system receives them automatically.

Common Error Messages and What They Mean

Before diving into fixes, it helps to understand the specific error message you are seeing. Different errors point to different root causes, and knowing which one you have can save you time.

“No scanners were detected” (Windows Fax and Scan): This is the most common error. It means Windows cannot find any WIA-compatible scanner. The cause is almost always a driver issue, WIA service problem, or the eSCL protocol bug in 24H2.

“Cannot find scanner. Check the power and the cables”: Windows cannot communicate with the scanner at all. Check physical connections first, then driver status in Device Manager. If the scanner works on another PC, the issue is software-related.

“WIA No Friendly Name” in Device Manager: This is a Windows 11 24H2-specific bug. The scanner appears in Device Manager but with no proper name. It confirms the eSCL protocol issue and requires the KB5055523 update or later.

“Cannot communicate with the scanner” (Canon MF Scan Utility): Canon MultiFunction users see this constantly after 24H2 updates. The printer functions work, but the scanner cannot be reached. This is a known eSCL/WIA issue, not a hardware problem.

“Scan to computer no longer activated”: This appears on HP scanner LCD screens. The scan-to-PC feature was disabled during the update. Re-enabling it through HP software or the printer’s embedded web server usually fixes this.

Scanner shows a yellow exclamation mark in Device Manager: The driver is installed but not functioning. Right-click the device, check the error code, and reinstall the driver from the manufacturer website.

Windows 11 24H2 eSCL Protocol Issue Explained

The Windows 11 24H2 scanner crisis deserves its own section because it is the biggest scanner-breaking update in recent Windows history. If you updated to 24H2 and your scanner stopped working, this is almost certainly why.

What is the eSCL protocol? eSCL (also called IPP Scan) is a scanning protocol that allows Windows to communicate with scanners over both USB and network connections. Many modern scanners, especially multifunction printers from Canon, HP, and Brother, use eSCL as their primary scanning protocol alongside or instead of TWAIN and WIA.

What did Microsoft change? In Windows 11 24H2, Microsoft modified the eSCL protocol implementation in the Windows scanning stack. The change affected how Windows discovers and enumerates USB-connected scanners that use eSCL. The result: scanners that worked perfectly on 23H2 vanished after updating to 24H2.

Multiple independent sources have confirmed this is a Windows issue, not a hardware or driver problem. On the Canon community forums, a user wrote: “As soon as I reinstalled a disk image I had just recently made before upgrading 23H2 to 24H2, the scanner worked again, so 100000000% guarantee it is yet another Windows issue in 24H2.”

Which KB patches caused the problem? The scanner detection failure was introduced by these cumulative updates on Windows 11 24H2: KB5044284, KB5044384, and KB5046617. These updates modified the WSD Scan and eSCL components of the Windows scanning stack.

Which KB patches fix the problem? Microsoft released KB5048667 in December 2026 as the first attempted fix. However, many users reported it did not resolve the issue. Ricoh later confirmed that KB5055523 (a subsequent cumulative update) fully resolves the eSCL scanner detection problem. If you are on 24H2 and your scanner still does not work, installing the latest cumulative update is your first priority.

Which brands are affected? Based on forum reports and manufacturer confirmations, these brands have documented scanner detection failures on Windows 11 24H2: Canon (MF4770n, C1127i, MF410, MF733Cdw, MF744Cdw, MF443dw, MF463dw, MF411dw), HP (HP Scanjet Enterprise Flow 5000s5, various OfficeJet models), Fujitsu (fi Series and SP Series with PaperStream IP), Brother, Epson, Kodak (Smart Touch software), and Neat scanners.

One Reddit sysadmin summarized it well: “It’s a known and recognized issue with the eSCL protocol that Microsoft messed with in 24H2.” IT administrators have reported hundreds of new enterprise PCs stalled in deployment because of this single issue.

How to Fix Scanner Not Detected After Windows Update: Step-by-Step Guide

I have organized these solutions from simplest to most advanced. Start at the top and work your way down. Most scanner detection issues are resolved by Step 3 or Step 4.

Step 1: Restart Your PC and Reconnect Your Scanner

This sounds too simple, but it fixes roughly 20 percent of scanner detection issues. Windows updates often leave services and drivers in a half-initialized state. A clean restart forces Windows to reload every service from scratch.

Here is the exact sequence I recommend: Power off your scanner completely (not just sleep mode). Shut down your PC (do not use Restart, use Shut Down, then power on manually). Unplug the scanner USB cable. Plug the scanner into a different USB port than it was using before. Power on the scanner first, wait 10 seconds, then boot your PC.

Why a different USB port? Windows assigns USB device identifiers based on the port. If the update reset the USB controller configuration, the old port may now have a conflicting device ID. A fresh port forces Windows to create a new device entry from scratch.

After your PC boots, open Windows Fax and Scan or the Windows Scan app and check if your scanner appears. If it does, you are done. If not, continue to Step 2.

Step 2: Check Device Manager for Your Scanner

Device Manager tells you exactly what Windows sees (or does not see) when it comes to your scanner. This step takes two minutes and gives you critical diagnostic information.

Press Windows Key + X and select Device Manager from the menu. Look for your scanner in two places: under “Imaging devices” and under “Printers.” If your scanner appears under Imaging devices with a yellow triangle, right-click it and select “Update driver.” If it appears with “WIA No Friendly Name” instead of the actual scanner name, you have the Windows 11 24H2 eSCL bug, and you need to jump to Step 8 to install the latest KB patch.

If your scanner does not appear anywhere in Device Manager, click the “View” menu at the top and select “Show hidden devices.” Sometimes Windows hides disconnected or problematic devices. If your scanner appears grayed out under Imaging devices, right-click it and select “Uninstall device,” then unplug and replug the scanner to force Windows to redetect it.

If your scanner still does not appear after showing hidden devices, try clicking the “Action” menu and selecting “Scan for hardware changes.” This forces Windows to query all connected devices. If nothing appears, the issue may be the USB cable itself (swap it for a known-good cable) or the scanner power supply.

Step 3: Update or Reinstall Your Scanner Driver

This is the fix that resolves the majority of scanner detection problems after a Windows update. The update likely replaced your manufacturer driver with a generic Microsoft one, or the existing driver became incompatible with the new Windows build.

To update the driver through Device Manager: Right-click your scanner under Imaging devices and select “Update driver.” Choose “Browse my computer for drivers” and then “Let me pick from a list of available drivers on my computer.” If you see your scanner manufacturer’s driver listed alongside a generic Microsoft WIA driver, select the manufacturer driver and click Next.

To do a clean driver reinstall: Go to your scanner manufacturer’s website (HP, Canon, Epson, Brother, Fujitsu, etc.) and download the latest driver package for your specific scanner model. Make sure you download the version for your exact Windows build (Windows 11 24H2, Windows 11 23H2, or Windows 10 22H2). Before installing the new driver, open Device Manager, right-click your scanner, and select “Uninstall device.” Check the box that says “Delete the driver software for this device” if it appears. Then disconnect the scanner, run the manufacturer’s driver installer, and reconnect the scanner when prompted.

One important tip: always download drivers from the manufacturer’s official website, not from third-party driver sites. I have seen cases where third-party driver updaters installed outdated or modified drivers that made the problem worse. If your manufacturer offers both a TWAIN driver and a WIA driver, install both. Some scanning software requires TWAIN, while Windows Fax and Scan requires WIA.

For Fujitsu scanners using PaperStream IP, the driver reinstall procedure is slightly different. Download the latest PaperStream IP driver from the Ricoh/PFU website, run the uninstaller for the old version first, reboot, then install the new version. This is especially important for fi Series and SP Series scanners affected by the 24H2 eSCL issue.

Step 4: Restart the Windows Image Acquisition (WIA) Service

The WIA service is the backbone of scanner communication in Windows. If this service stops, hangs, or gets set to Manual startup during an update, your scanner will not be detected by any application. This is one of the most overlooked fixes, and it takes less than a minute.

Press Windows Key + R to open the Run dialog. Type services.msc and press Enter. Scroll down the list until you find “Windows Image Acquisition (WIA).” Check the Status column. If it says anything other than “Running,” this is your problem.

Right-click the WIA service and select “Properties.” In the General tab, set the Startup type to “Automatic.” If the Service status says “Stopped,” click the “Start” button. Click Apply and OK. Now try opening your scanning app again.

While you are in the Services window, also check two related services: “Printer Extensions and Notifications” and “Windows Driver Foundation – User-mode Driver Framework.” Both of these support scanner operations, and if either is stopped, set them to Automatic and start them.

If the WIA service starts but immediately stops again, you likely have a corrupted system file. Run the SFC scan described in Step 7 before trying to start the service again. I have seen cases where the WIA service would not stay running until SFC repaired the underlying DLL files.

Step 5: Disable and Re-enable Windows Fax and Scan

Windows Fax and Scan is a built-in Windows feature that can become corrupted during updates. Disabling and re-enabling it forces Windows to reinstall the component cleanly, which often restores scanner detection. This fix is particularly effective if you get the “No scanners were detected” error specifically in Windows Fax and Scan.

Press Windows Key + I to open Settings. Go to Apps, then “Optional features.” Click on “More Windows features” (or “View features” depending on your Windows version). Scroll through the list until you find “Windows Fax and Scan.” Uncheck the box next to it and click OK. Windows will remove the feature. Restart your PC.

After the restart, go back to the same Windows Features window. Check the box next to “Windows Fax and Scan” and click OK. Windows will reinstall the component from its update cache. Restart your PC one more time, then open Windows Fax and Scan and check if your scanner is detected.

If you use the newer Windows Scan app instead of Windows Fax and Scan, you can try uninstalling and reinstalling it from the Microsoft Store. Open the Microsoft Store, search for “Windows Scan,” and if it is already installed, click “Uninstall” and then reinstall it. This is a lighter-weight fix that resolves detection issues for users who primarily use the modern Scan app.

Step 6: Run the Hardware and Devices Troubleshooter

Windows includes a built-in troubleshooter that can automatically detect and fix common hardware problems, including scanner detection failures. On older versions of Windows, this was easily accessible in Settings. On Windows 11, Microsoft has hidden it, but you can still access it.

Press Windows Key + R to open the Run dialog. Type the following command exactly: msdt.exe -id DeviceDiagnostic and press Enter. This launches the Hardware and Devices troubleshooter directly. Click “Next” and let it scan your system for hardware issues.

The troubleshooter will check for driver problems, device conflicts, USB issues, and service configuration errors. If it finds a problem with your scanner, it will either fix it automatically or provide specific instructions. Apply any recommended fixes and restart your PC.

This troubleshooter is not a magic bullet, but it catches issues that manual troubleshooting might miss. I have seen it fix USB controller conflicts that were preventing scanner detection when nothing else worked. It is worth running before you move on to more advanced fixes.

Step 7: Repair Corrupted System Files with SFC Scan

Windows updates can corrupt critical system files that scanners depend on. The System File Checker (SFC) tool scans all protected system files and replaces corrupted ones with known-good copies from the Windows component store. If your scanner stopped working after a major feature update, running SFC should be a standard step.

Right-click the Start button and select “Windows Terminal (Admin)” or “Command Prompt (Admin).” Click “Yes” when prompted for permission. At the command prompt, type: sfc /scannow and press Enter.

The scan takes 5 to 15 minutes depending on your system speed. It will report one of three results: “Windows Resource Protection did not find any integrity violations” (no problems found), “Windows Resource Protection found corrupt files and successfully repaired them” (files fixed, restart your PC), or “Windows Resource Protection found corrupt files but was unable to fix some of them” (you need the DISM tool next).

If SFC could not fix everything, run this command in the same admin terminal: DISM /Online /Cleanup-Image /RestoreHealth. This tool downloads clean system files from Windows Update and repairs the component store that SFC depends on. After DISM completes, run SFC /scannow one more time. This two-step approach resolves even deeply corrupted system files.

After the repair completes, restart your PC and check if your scanner is now detected. SFC repairs have resolved scanner detection issues in cases where driver reinstall, WIA service restart, and USB port changes all failed.

Step 8: Install the Latest Windows Updates and KB Patches

If a Windows update broke your scanner, the fix may be a newer update. This sounds counterintuitive, but Microsoft regularly releases patches for issues caused by previous patches. If you are on Windows 11 24H2 and your scanner stopped working, this step is critical.

Go to Settings, then Windows Update, and click “Check for updates.” Install every available update, including optional updates. Look specifically for cumulative updates with these KB numbers:

KB5055523: This cumulative update was confirmed by Ricoh to fix the eSCL scanner detection issue on Windows 11 24H2. If you have not installed this update (or a newer one), your scanner will likely remain undetected regardless of other fixes.

KB5048667: Released in December 2026 as Microsoft’s first attempt to fix the 24H2 scanner issue. Some users reported it resolved their problem, while others (particularly Canon MF series owners) said the scanner still did not work. If KB5055523 is available, prefer that over KB5048667.

KB5095093: A later cumulative update that includes all previous scanner fixes. If your system offers this update or anything newer, install it.

After installing updates, restart your PC (not just a quick restart, do a full shutdown and power on). Then check Device Manager and your scanning app. If your scanner was showing “WIA No Friendly Name” before the update, it should now display the correct scanner name.

If Windows Update does not offer the patch you need, you can download it manually from the Microsoft Update Catalog (catalog.update.microsoft.com). Search for the KB number, download the version matching your system architecture, and install it manually.

Step 9: Use Network Scanning as a Bypass

If your scanner supports Wi-Fi or Ethernet, connecting it to your network instead of USB can bypass the eSCL protocol issue entirely. This workaround has been confirmed by multiple IT administrators on Reddit as one of the most reliable fixes for the 24H2 scanner crisis.

As one sysadmin on r/sysadmin put it: “The easiest way to fix scanner issues is to scan to network drive. This bypasses most issues caused by Windows 11.”

Here is how to set it up: Connect your scanner to your Wi-Fi network or plug it into your router via Ethernet. On your PC, go to Settings, then “Bluetooth and devices,” then “Printers and scanners.” Click “Add device.” Windows should detect your scanner on the network. If it does not appear, click “Add manually” and select “Add a Bluetooth, wireless, or network discoverable printer.”

Once the network scanner is added, open Windows Scan or your manufacturer’s scanning software. Select the network scanner from the device list. Network scanning uses a different communication path than USB, so it often works even when USB scanner detection is broken.

For scanners that support scan-to-folder or scan-to-FTP, you can configure the scanner to send scanned documents directly to a shared folder on your PC. This completely bypasses the Windows scanning stack and is the most reliable method for enterprise environments where scanner reliability is critical.

Step 10: Try Third-Party Scanning Software

When Windows Fax and Scan and the Windows Scan app both fail to detect your scanner, third-party software can sometimes communicate with the scanner using different protocols. This is not a permanent fix, but it can keep you productive while you troubleshoot.

NAPS2 (Not Another PDF Scanner 2) is a free, lightweight scanning application that supports both WIA and TWAIN drivers. It is frequently recommended by IT professionals as a diagnostic tool. If NAPS2 can detect your scanner when Windows Scan cannot, the problem is with the Windows scanning app, not your scanner hardware or driver.

Download NAPS2 from naps2.com, install it, and click the “Scan” button. If prompted, select your scanner from the list. NAPS2 can use either the WIA or TWAIN driver, so try both if one fails. If NAPS2 successfully scans, you know your hardware is fine and the issue is isolated to the Windows scanning stack.

Your scanner manufacturer’s own software is also worth trying. Canon’s MF Scan Utility, HP’s Scan software, Epson Scan, and Fujitsu’s PaperStream Capture all use proprietary communication methods that may work even when Windows Fax and Scan does not. Download the latest version from the manufacturer website.

Step 11: Run a Malware and Virus Scan

Malware can interfere with scanner detection by modifying system services, blocking device communication, or corrupting driver files. While this is a less common cause than driver or update issues, it is worth checking if nothing else works.

Open Windows Security, go to “Virus and threat protection,” and click “Quick scan.” For a more thorough check, click “Scan options” and select “Full scan” or “Microsoft Defender Offline scan.” The offline scan reboots your PC and scans before Windows fully loads, which catches rootkits and deep infections.

After the scan completes and removes any threats, restart your PC and check for your scanner. If malware was interfering with system services, scanner detection should return after cleanup.

Step 12: Use Compatibility Mode for Older Scanners

If you are using an older scanner that has not received driver updates in years, the manufacturer’s software may not be compatible with the latest Windows build. Compatibility mode can trick the software into running as if it were on an older version of Windows.

Right-click the scanner software shortcut or executable file. Select “Properties,” then go to the “Compatibility” tab. Check “Run this program in compatibility mode for” and select the Windows version your scanner software was designed for (usually Windows 8 or Windows 7). Check “Run this program as an administrator” as well. Click Apply and OK, then launch the software.

This fix is particularly useful for older Canon, HP, and Neat scanners whose manufacturers stopped releasing driver updates years ago. It does not always work, but it has extended the life of many scanners that would otherwise become e-waste after a Windows update.

USB vs Network Scanner Troubleshooting

The troubleshooting steps differ depending on whether your scanner connects via USB or over a network. Understanding the differences can help you zero in on the right fix faster.

USB scanners are more vulnerable to Windows update issues because they depend on the WIA service, eSCL protocol, and USB controller drivers. The 24H2 eSCL bug specifically affects USB-connected scanners. If your USB scanner stopped working after an update, focus on Steps 3, 4, 7, and 8.

USB scanners also suffer from physical connection issues that can mimic software problems. Try a different USB cable (USB cables fail more often than people expect). Use a port directly on the motherboard (back of a desktop PC) rather than a front panel or hub. Avoid USB 3.0 ports for older scanners that were designed for USB 2.0.

Network scanners (Wi-Fi or Ethernet) are generally more resilient to Windows updates because they use network protocols (IPP, Bonjour, SMB) that are less likely to be modified by Windows updates. If your network scanner stopped working, the issue is usually DNS resolution, firewall rules, or the scanner’s IP address changing after a DHCP renewal.

For network scanners, try pinging the scanner’s IP address from a command prompt. If the ping fails, the scanner is offline or has a network configuration problem. If the ping succeeds but Windows cannot scan, remove and re-add the scanner in Settings. For enterprise environments, assign a static IP to the scanner to prevent IP conflicts.

How to Prevent Scanner Issues After Future Windows Updates

Once you get your scanner working again, you want to prevent the next Windows update from breaking it. While you cannot control what Microsoft changes in updates, you can take steps to minimize the risk.

Create a system restore point before installing updates. Press Windows Key, type “Create a restore point,” and open it. Click “Create” and name it “Working scanner.” If a future update breaks your scanner, you can roll back to this restore point in minutes instead of hours.

Delay major feature updates. Windows 11 feature updates (like the 24H2 release) are the most likely to break scanner detection. In Windows Update settings, you can pause updates for up to 5 weeks. Wait 4 to 6 weeks after a major update release before installing it. This gives Microsoft time to release patches for known issues.

Keep manufacturer drivers downloaded and backed up. Download the latest driver package for your scanner and save the installer file somewhere permanent (not just your Downloads folder). If an update breaks scanner detection, you can reinstall the known-good driver immediately without hunting for it online.

Consider switching to network scanning permanently. If your scanner supports network connectivity, using it over Wi-Fi or Ethernet bypasses most Windows USB scanning issues. Network scanning survived the 24H2 eSCL bug largely unscathed, making it the most update-resistant scanning method.

For IT administrators managing multiple scanners: Use Windows Update for Business policies to control update deployment. Test scanner functionality on a pilot group before rolling updates to all machines. Maintain a standard driver package and deployment script so you can quickly reinstall scanner drivers across multiple PCs if an update causes widespread failures.

FAQs

Conclusion

When your scanner is not detected after a Windows update, the problem almost always comes down to a driver issue, a stopped WIA service, or the eSCL protocol change in Windows 11 24H2. Work through the 12 solutions in this guide starting with a simple restart and USB port change, then move to driver reinstall, WIA service restart, and SFC repair. If you are on Windows 11 24H2, installing the latest cumulative update (KB5055523 or newer) is essential.

The scanner detection problem after a Windows update is widespread but solvable. Canon, HP, Epson, Fujitsu, and Brother scanner owners have all confirmed that the fixes in this guide work. If USB scanning remains broken despite every fix, switching to network scanning provides a reliable bypass that keeps you productive. And going forward, creating a system restore point before each update and keeping your manufacturer drivers backed up will save you from repeating this troubleshooting process every time Windows updates.