A scanner not working in Windows 11 — not appearing in scanning apps, throwing errors when you try to scan, or the hardware light blinking but no scan completing — almost always traces to one of three things: the WIA service is stopped, the driver isn’t correct for Windows 11, or a network scanner lost its IP address. Knowing which takes 30 seconds. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Start here: open the Windows Scan app (search “Scan” in Start → open the app from Microsoft). If your scanner appears in the dropdown and you can scan from there: the issue is with your other scanning software, not Windows or the scanner itself. If it doesn’t appear, or appears but throws errors: keep reading.
The WIA service — restart it first
Windows Image Acquisition (WIA) is the Windows service that handles communication with scanners and cameras. When it stops running (common after updates and after certain software installations): every scanner disappears from Windows, including ones that were working fine. This is the fastest fix to try.
Win+R → services.msc → find “Windows Image Acquisition (WIA)” → right-click → Restart. If the service shows as Stopped: right-click → Properties → Startup type → Automatic → Start. After restarting the service: open the Windows Scan app or your scanning software and check if the scanner now appears.
Driver — use the right one for Windows 11
Many scanner manufacturers provide drivers that work on Windows 10 but aren’t fully compatible with Windows 11. The Windows 11 driver changes broke compatibility for older scanner drivers, particularly for models from 2018 and earlier. If the scanner appeared fine on Windows 10 but stopped after upgrading to Windows 11: this is the likely cause.
Download the driver directly from the manufacturer’s website — not from Windows Update:
- HP: hp.com/support → enter model → drivers
- Canon: canon.com/support → IJ Scan Utility download
- Epson: epson.com/support → Event Manager and Scan Software
- Brother: support.brother.com → select model → Downloads
After downloading: completely uninstall any existing scanner software (Settings → Apps → search for scanner software → uninstall everything from that manufacturer) → restart → install the fresh download. Don’t just run the new installer on top of the old one — the old driver files often prevent the new ones from installing correctly.
Network scanner lost its IP address
Network-connected scanners (on the same Wi-Fi or LAN as the computer) sometimes lose their assigned IP address, making them unreachable. A router restart, a DHCP lease expiration, or a network change can assign the scanner a new IP that the scanning software doesn’t know about.
On the scanner’s own screen: look for a Network or Wi-Fi status menu → find its current IP address. Compare this to what your scanning software has configured. If they differ: update the software to use the new IP, or — better — assign a static IP to the scanner. Router admin → DHCP reservations → add the scanner’s MAC address → assign a permanent fixed IP. From then on, the scanner always has the same address regardless of DHCP cycles.
Compatibility mode for older scanning software
If a scanner works with manufacturer software but not Windows’ built-in Scan app, or vice versa: the software may have a compatibility issue with Windows 11. Right-click the scanning application → Properties → Compatibility tab → check “Run this program in compatibility mode for” → try Windows 8 or Windows 10. Also try “Run as administrator” for software that needs elevated permissions to access the scanner hardware.
Our guide on printer troubleshooting covers the WIA and spooler service interactions that affect both printers and scanners, and our USB device troubleshooting covers USB-connected scanners that aren’t detected at all. For WIA configuration and scanner driver support, Microsoft’s Windows scanning documentation covers the WIA driver model and troubleshooting paths.
WSD (Web Services for Devices) scanning
Modern multifunction printers and scanners support WSD, which allows Windows to automatically discover and use them without manufacturer-specific drivers. If a network scanner is visible via WSD but the scan quality is lower or features are missing: the WSD driver is working but it’s the generic implementation, not the manufacturer’s full-featured version.
WSD scanners appear in the Windows Scan app automatically when connected to the same network. If the WSD scanner appears in Windows Scan but not in the manufacturer’s application: the manufacturer’s app requires the vendor-specific driver rather than WSD. Installing the full driver package from the manufacturer’s site usually adds proper manufacturer software support alongside the WSD connection.
USB scanner not detected
For USB-connected scanners that don’t appear at all: try a different USB port, remove any USB hub between the scanner and PC, and try the rear USB ports on a desktop rather than front panel ports. Scanner hardware can require more consistent USB power than hubs provide.
Device Manager → Universal Serial Bus controllers → look for any unknown devices or entries with yellow warning triangles when the scanner is connected. If the scanner appears as unknown: driver issue. If it doesn’t appear at all: USB connection or power problem. Try the scanner on another computer to confirm whether the hardware itself works.
Firewall blocking network scanner
Windows Defender Firewall can block the communication ports that network scanners use for receiving scan data. If the scanner appears in software and you can trigger a scan, but the data never arrives (the scan “completes” but no image appears): the firewall is blocking the return data path.
Windows Firewall → Allow an app through → look for your scanner software or “WSD Scan Service” → ensure it’s allowed on Private networks. Or temporarily disable the firewall while testing to confirm it’s the cause — then add a permanent exception rather than leaving the firewall off.
Corporate network note: enterprise firewalls sometimes block WSD discovery or scanner return-data ports. If a network scanner works at home but not at an office: the corporate firewall is likely filtering the scanner communication. IT would need to create an exception for scanner traffic on the specific subnet.
Scanner connection via ICA vs TWAIN vs WIA
Scanning software uses one of several APIs to communicate with scanners: WIA (Windows built-in), TWAIN (industry standard, used by most photo editing software), or ICA (Apple/Mac standard). A scanner may work through WIA but not TWAIN, or vice versa.
If a specific application can’t see the scanner: check which scanning API that application uses. Adobe Acrobat, Photoshop, and many professional applications use TWAIN. The Windows Scan app uses WIA. If the scanner works in Windows Scan but not Photoshop: install the TWAIN driver specifically from the manufacturer (often called “TWAIN driver” explicitly in the downloads section).
| Symptom | Most likely cause | Fix |
| Scanner not in any software list | WIA service stopped or driver missing | Restart WIA service; reinstall driver |
| Network scanner not visible | IP address changed | Find current IP on scanner screen; update software config |
| Appears but won’t scan | Driver incompatibility or permissions | Fresh driver install; run as administrator |
| Visible in Windows Scan, not other apps | App uses TWAIN, scanner needs TWAIN driver | Install TWAIN driver specifically |
| Scan triggers but no image received | Firewall blocking return data | Allow scanner app through firewall |
| USB scanner not detected | Hub power or port issue | Direct connection to rear USB port |
The WIA service restart and manufacturer driver reinstall resolve the large majority of Windows 11 scanner problems. Network scanner IP issues are the main scenario that remains after those two are addressed. The TWAIN API distinction is specifically relevant for professional photo and document software where WIA-only drivers aren’t enough.
Windows 11 built-in scan capabilities
Windows 11 includes the Windows Scan app (available in Microsoft Store) that uses WIA to access scanners. It’s simpler than manufacturer software and useful as a diagnostic tool. If it detects your scanner and can complete a scan successfully: the scanner hardware and WIA driver are working. Problems are then limited to the specific software you’re trying to use rather than the underlying scan capability.
The Fax and Scan application (Win+S → “Windows Fax and Scan”) is an older built-in option that also uses WIA and sometimes works differently from the Store app. If one shows the scanner and the other doesn’t: the WIA interface is working selectively. Running both as administrator resolves some permission-related detection differences.
Older scanner hardware and Windows 11 compatibility
Some scanner models from before approximately 2015 have no Windows 11 drivers available and never will — the manufacturer has ended software support. For these scanners: the realistic options are:
- Use a Windows 10 compatibility mode (sometimes works for simple scanning functions)
- Run a Windows 10 virtual machine in Hyper-V or VirtualBox with the old driver installed
- Replace the scanner — flatbed scanners good enough for most home and small office use cost £50-£100
The virtual machine approach is genuinely useful for expensive or specialised scanners (large-format, high-resolution film scanners, sheet-fed office scanners) where replacement isn’t trivial. Running a lightweight Windows 10 VM with USB passthrough gives the old scanner a new lease on Windows 11 systems without hardware replacement.
Mobile scanning as an alternative
If the scanner is unavailable and the fix is taking time: most modern smartphones have excellent document scanning capability built into the camera app or through free apps (Adobe Scan, Microsoft Lens, Apple’s native Notes app scanner). For documents, receipts, and simple photos: mobile scanning often produces results comparable to a flatbed scanner. Worth knowing as a fallback while troubleshooting the hardware setup.
Reinstalling the WIA driver through Device Manager
A scanner driver can be reinstalled specifically through Device Manager without the full manufacturer software package — useful when you need just the core scan function and don’t want the manufacturer’s bloatware:
- Device Manager → Imaging devices → your scanner → right-click → Uninstall device → confirm
- Unplug the scanner (USB) or restart (for network scanners)
- Reconnect or wait for the network scanner to re-appear
- Windows installs a basic WIA driver automatically for recognised hardware
- Test with Windows Scan app
For network scanners that don’t appear after this: Device Manager → Action → Add legacy hardware → manually add the scanner with a known driver. This is more involved but allows adding network scanners that Windows doesn’t auto-discover through WSD.
Getting a scanner working on Windows 11 is almost always a driver or service issue rather than a hardware failure — scanners are durable hardware that outlasts software support. The WIA service restart and manufacturer driver reinstall together resolve the majority of cases. When they don’t: the TWAIN vs WIA distinction, network IP addressing, or firewall configuration are the next diagnostic steps to check.
Paper jam sensors and scanner glass issues
For sheet-fed scanners or ADF (Automatic Document Feeder) models: a physical paper jam sensor that’s stuck in “jam detected” state prevents scanning even when no paper is physically jammed. Open all access panels, look for torn paper scraps or debris that might be triggering the sensor, and close everything firmly before trying again.
Scanner glass with fingerprints or scratches produces visible image quality issues but doesn’t usually prevent scanning. A cracked scanner glass on the other hand can cause the lamp to detect incorrect exposure and abort the scan. Inspect the glass with the lid open and a flashlight at an angle — scratches are usually obvious, cracks less so unless the light catches them right.
Event Viewer for scanner errors
When the scanner appears in software but fails mid-scan: Event Viewer captures the error with more detail than the on-screen message. Win+R → eventvwr.msc → Windows Logs → Application → look for errors around the time of the failed scan attempt. Filter for “Source: WIA” or look for errors from scanner-related processes.
Common WIA event errors and their meanings:
- “Device is busy” or “Device not ready” — the scanner didn’t complete its warm-up or is already processing a request
- “Device not found” — WIA has lost contact; power cycle the scanner
- “Access denied” — permissions issue; run software as administrator
- “Driver load failed” — driver file corruption; reinstall the driver
These specific error messages from Event Viewer are far more actionable than generic “scanner not working” messages and quickly point to the correct fix without trial and error across multiple options.
One environmental reality worth stating plainly: Windows 11 broke compatibility for a significant number of older scanners that worked fine on Windows 10. Microsoft changed the WIA driver model in a way that older unsigned or 32-bit-only scanner drivers don’t load correctly. If you’ve confirmed the WIA service is running, the driver installs without errors, but the scanner still doesn’t appear in scanning software: this is likely the compatibility wall. The manufacturer’s support page will confirm whether a Windows 11 driver exists; if it doesn’t, virtual machine or mobile scanning are the practical alternatives. Related: Mouse Scroll Wheel Not Working.
