“Scan to PC fails after Windows update” — WIA/TWAIN service repair

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, Printers, Networking, Group Policy, Print Servers

Fix Scan to PC after Windows update — WIA service not running, TWAIN DSM/driver issues, USB & network scanner repair

Technician

Hey! We’ll get Scan to PC working again after the Windows update. A few checks so we target the right fix:
• Brand/model (HP/Epson/Canon/Brother/Ricoh/other)? USB or network/Wi-Fi?
• Which app fails — vendor utility, Windows Scan, or Windows Fax and Scan? Any error like “WIA service not running”, “TWAIN error”, or 0x80270491?
• Did Device Manager show the scanner under Imaging devices or Cameras?

Customer

HP OfficeJet over USB. After a Windows 11 update, Windows Scan says “No scanners detected”. HP Smart sees the printer but scanning fails.

Technician

Understood. Feature updates can break the imaging stack: the WIA (Windows Image Acquisition) service may stop, class drivers switch to a generic USB driver, or the TWAIN DSM goes out of sync (32-/64-bit mismatch). We’ll: 1) repair WIA and dependencies, 2) reinstall the scanner driver, 3) fix permissions & firewall for vendor apps, 4) test with Windows Fax and Scan and Windows Scan.

Customer

Where do I turn on WIA? I don’t see anything obvious.

Technician

Step 1 — Make sure WIA runs
1) Press Win+R → type services.msc → Enter.
2) Find Windows Image Acquisition (WIA). Set Startup type to Automatic → click Start.
3) Start its dependencies: Remote Procedure Call (RPC), DCOM Server Process Launcher, Shell Hardware Detection.
4) Reopen the scan app. If the message changes to “No WIA driver”, we’ll reinstall drivers next.

Customer

WIA was disabled. I started it, but Windows Scan still can’t find the device.

Technician

Step 2 — Reinstall the scanner driver (USB)
• Open Device Manager → expand Imaging devices or Printers. Right-click your HP scanner → Uninstall device (check “Delete driver”).
• Unplug USB. Download the latest Full Feature Software for your model (not just the basic driver).
• Reboot → plug the USB directly to the PC (no hub).
• Install, then test in Windows Fax and Scan first; if that works, HP Smart/TWAIN should connect.

Customer

Fax and Scan finds it now, but HP Smart still errors. Could this be TWAIN?

Technician

Likely. TWAIN apps use the TWAIN DSM plus a vendor source.
• Remove leftover TWAIN sources: delete old entries from C:\Windows\twain_32 and C:\Windows\twain_64 (only the HP folder should remain).
• Reinstall the vendor package to refresh twain_32.dll/twain_64.dll mappings.
• If you use 32-bit apps (older Acrobat/Photoshop), install the 32-bit TWAIN source as well. After that, HP Smart should detect the scanner.

Customer

What about network scanners? My colleague’s Brother MFC over Wi-Fi stopped scanning too.

Technician

For Wi-Fi/Ethernet scanners:
• Ensure the device and PC are on the same subnet; assign a static IP to the MFP.
• Install the vendor’s network scanner driver (Brother Scanner / Canon IJ / Epson Scan 2), not only the printer driver.
• In Windows Security → Firewall, allow the vendor ports and the WIA service. Discovery via WSD/mDNS can be blocked after updates; re-add the device by IP if needed.
• For “Scan to Folder”, confirm SMB credentials and that File and Printer Sharing is enabled.

Customer

After these steps, HP Smart scans again. Anything else to prevent future breakage?

Technician

Yes — a few hardening tips:
• Keep the WIA service set to Automatic and its dependencies running.
• Use the manufacturer’s latest full package; avoid mixing Microsoft IPP Class with vendor scan drivers.
• Pin the USB to the same port; for network devices, use a static IP and disable “metered connection”.
• Create a Restore Point before major Windows updates.

Customer

We manage a small office. Any GPO/Intune settings to keep scanners stable?

Technician

For managed PCs:
• Deploy vendor scan drivers via Intune/Endpoint Manager or GPO and block automatic replacement by class drivers.
• Allow vendor executables through the firewall. Keep Function Discovery Provider Host and Function Discovery Resource Publication enabled if you rely on WSD.
• Standardize on one scan app and store profiles (PDF/JPEG, ADF/flatbed) so updates don’t reset defaults.

Customer

Perfect — scanning works. Can you summarize the repair path?

Technician

Summary: After a Windows update, Scan to PC often fails from a stopped WIA service, broken TWAIN sources, or missing network scanner drivers. Start WIA and dependencies → reinstall vendor scanner package → clean TWAIN folders → allow firewall rules → test in Windows Scan/Fax & Scan. Need help with a specific model? Open the chat.

Quick answer: the accepted fix

Accepted fix when Scan to PC fails after a Windows update: start the WIA service and dependencies, reinstall the vendor scanner driver, refresh TWAIN DSM sources, then test in Windows Scan. For network devices, re-add by static IP and allow firewall rules.

FAQ

Step-by-step (Windows 11/10)

1. Open services.msc; set WIA to Automatic and start it. Confirm RPC/DCOM/Shell Hardware Detection run.
2. In Device Manager, remove the scanner and delete driver → reboot → install the latest full vendor package.
3. Clean C:\Windows\twain_32 and twain_64 of old sources; reinstall TWAIN if needed (32-/64-bit).
4. For network MFPs, re-add by static IP, allow firewall rules, and install the vendor network scanner driver.

Note for mixed environments (macOS)

1. macOS uses ICA rather than WIA. If Windows works but macOS fails, reinstall the vendor ICA driver and test from Preview/Image Capture.
2. For SMB “Scan to Folder”, verify shared folder permissions and credentials on the destination OS.

Sources

• Microsoft — Windows Fax and Scan
• Microsoft — Windows Image Acquisition (WIA)
• TWAIN Working Group — DSM and sources

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.