Printer Scan to PDF crashes – real fixes that work

1. Old or wrong printer driver – the most common crash cause

What's actually happening here is that the printer driver you installed doesn't match your Windows version or is outdated. When you hit "Scan to PDF", Windows calls the driver's WIA (Windows Image Acquisition) component. If that component is buggy or not fully compatible with your OS, the scan software crashes – often without any error message.

I've seen this on HP Envy 6000 series with drivers from 2020 on Windows 11 22H2, and on Canon Pixma MG3620 with the default Windows driver instead of Canon's own.

Real fix – not the generic "update driver" advice:

1. Go to Settings > Bluetooth & devices > Printers & scanners. Find your printer, click it, then click Printer properties.
2. In the driver tab, check the driver version and date. If it says "Microsoft" as provider, that's the problem – you need the manufacturer's driver.
3. Uninstall the printer completely. Then download the latest full driver package from the printer maker's site – not the basic one. For HP, get the "Full Feature Software" package, not just the driver bundle. For Canon, get the "MP Drivers" or "ScanGear" package.
4. Install it, restart your PC, then try scanning again.

Why step 3 matters: The basic driver only handles printing. The full package includes the WIA scanner driver and the scan utility. Without it, Windows uses its own generic WIA driver which crashes with many modern printers.

2. Windows Image Acquisition (WIA) service stuck or broken

WIA is the service that handles communication between your scan software and the scanner hardware. If it's stopped, disabled, or hung, the scan process just freezes. I've seen this most often on laptops that wake from sleep – WIA starts but doesn't initialize properly.

You'll know this is the issue if the scanner is detected but nothing happens when you start scanning, or the scan preview shows black for 30 seconds before crashing.

How to fix it:

1. Press Win + R, type services.msc, press Enter.
2. Find Windows Image Acquisition (WIA) in the list. Double-click it.
3. If the service status says Stopped, click Start. If it's Running, click Stop, wait 10 seconds, then click Start again – this resets its state.
4. Set Startup type to Automatic (not Automatic (Delayed Start)). Then click Apply and OK.
5. Restart your PC and try scanning again.

The reason step 3 works: When WIA gets into a stuck state after sleep, restarting the service clears whatever half-opened connection it was holding. Setting startup to Automatic instead of Delayed means WIA starts before any scan software tries to talk to it.

3. Corrupted scan profile or user data folder

Less common but I've seen it on HP and Epson scanners after a software update. The scan software stores your last used settings (resolution, file type, color mode) in a local user data folder. If that file gets corrupted – for example, from an incomplete update or antivirus blocking file writes – the software crashes when trying to load it.

You'll see the crash happen right after you select "Scan to PDF" but before the actual scanning starts. Or the software opens but instantly freezes.

Fix it by clearing the profile:

1. Close the scan software completely.
2. Press Win + R, type %appdata%, press Enter. This opens your AppData Roaming folder.
3. Look for a folder named after your printer brand – like HP, Canon, Brother, or EPSON. Inside there's usually a Scan or Scanner subfolder.
4. Rename that folder to something like Scan_old (don't delete it, you might need it).
5. Restart the scan software. It will create a new profile with default settings. Try scanning now.

I've had this work on an HP DeskJet 3755 where the scan software crashed every time on Windows 11 after a driver update. Renaming the folder forced it to rebuild the settings file cleanly.

If that doesn't help, also check %localappdata% and look for similar folders there – some apps store data in Local instead of Roaming.

Quick-reference summary table

Try these in order. The driver fix solves about 70% of cases. The WIA restart fixes another 20%. The profile trick handles the rest.