You click Print, the dialog freezes, and moments later every printer vanishes from Settings — the print spooler has crashed again. On a Windows 11 ARM laptop, this loop is maddeningly common: the spooler (spoolsv.exe) dies, Windows restarts it, and the same poisoned driver or stuck job kills it again within seconds.

ARM laptops add a special twist. The print subsystem is one of the few places where driver architecture matters absolutely — an x64-only print driver loaded on ARM64 does not limp along, it takes the whole spooler down. That makes driver verification step zero on Snapdragon machines.

This guide gives you six fixes in technician order: clear the poison, verify the driver architecture, then repair the subsystem. Work through them in sequence and test a print after each step.

Why this happens

  • Wrong-architecture print driver: An x64-only driver package installed on ARM64 crashes the spooler the moment it loads. This is the number-one ARM-specific cause.
  • Corrupted spool files: A malformed print job stuck in the spool queue crashes the spooler every time the service starts and tries to process it.
  • Damaged driver store entries: Partially installed or half-removed printer drivers leave orphaned files that the spooler chokes on during enumeration.
  • Conflicting third-party print monitors: Old port monitors or print processors from previous printers hook into the spooler and fail under ARM64.
  • Corrupted system print components: Damage to spoolsv.exe’s supporting DLLs from bad updates breaks the spooler for every printer at once.
  • Unsigned or blocked driver files: Overzealous driver signature enforcement or a corrupted driver catalog can crash the spooler while validating drivers — a cousin of the unsigned driver error seen on other device classes.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Clear the stuck spool queue manually

A single corrupted print job can crash the spooler on every startup. Clearing the queue by hand removes the poison without touching your printer configurations — and it resolves the classic “spooler crashes seconds after starting” loop.

  1. Open Services (press Win+R, type services.msc), find Print Spooler, right-click it, and choose Stop. If it is already crashed, it will show as stopped.
  2. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS, then delete every file inside — these are only queued jobs, not printer settings.
  3. Return to Services, right-click Print Spooler, and choose Start.
  4. Try printing a test page. If the spooler stays alive, a stuck job was the whole problem.

Fix 2: Verify every printer uses an ARM64 driver

On ARM64 Windows, the driver architecture is non-negotiable. Open each printer’s properties and confirm the driver is genuinely ARM64 — an x64 driver here is a guaranteed spooler crash, no matter how well it worked on your old Intel machine.

  1. Go to Settings > Bluetooth & devices > Printers & scanners, click your printer, then Printer properties.
  2. On the Advanced tab, note the driver name, then check the vendor’s site for an ARM64 version of that exact driver package.
  3. If the vendor offers one, download it and use New Driver on that same Advanced tab to swap it in; restart the spooler afterward.
  4. If no ARM64 driver exists, try the built-in Microsoft IPP Class Driver or Microsoft Print to PDF path as a stopgap — and see the ARM64 printer driver guide for vendor-specific options.

Fix 3: Remove and reinstall the printer completely

When the driver store holds a damaged or half-removed printer package, the spooler can crash just from listing printers. A full removal — device, driver package, and all — followed by a clean reinstall clears the damage.

  1. In Settings > Bluetooth & devices > Printers & scanners, remove the printer, then open Print Management (Win+R, printmanagement.msc).
  2. Under Custom Filters > All Drivers, right-click the printer’s driver package and choose Remove driver package — this deletes it from the driver store, not just the device list.
  3. Restart the laptop, then re-add the printer with the verified ARM64 driver from Fix 2.
  4. Print a test page before reinstalling any vendor utility software, so you can isolate whether the crash comes from the driver or the utility.

Fix 4: Strip out third-party print monitors and processors

Old port monitors (from label printers, PDF tools, or long-removed printers) load into the spooler process and crash it under ARM64. This is the fix when the spooler dies even with no printers installed.

  1. Open Print Management, expand Print Servers > your computer > Printers, right-click any printer, choose Properties > Advanced, and note the Print Processor — reset anything exotic to WinPrint / RAW.
  2. In the registry-free safe way: check Settings > Apps > Installed apps for old printer utilities, PDF printers, or fax software and uninstall them.
  3. Restart the spooler from Services and watch whether it stays alive with no printers configured.
  4. Re-add printers one at a time, testing after each — the one that kills the spooler is carrying the bad monitor.

Fix 5: Repair the print subsystem with SFC and DISM

If the spooler crashes with no printers installed and no third-party software involved, Windows’ own print components are damaged. The standard system repair tools fix spoolsv.exe and its DLLs without affecting your files.

  1. Open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth — allow 10–20 minutes.
  2. Follow with sfc /scannow, then restart the laptop.
  3. After reboot, start the Print Spooler service manually and confirm it stays running for several minutes.
  4. Re-add your printer and test. Global spooler crashes that survive this repair are rare — and if printing works but apps themselves keep crashing , the problem is app-level, not the spooler.

Fix 6: Reset the printing stack to a clean state

As a last resort before considering a Windows repair install, you can reset the entire printing stack: stop the spooler, clear drivers, and let Windows rebuild. This is the heavy hammer for damage that targeted fixes cannot reach.

  1. Stop the Print Spooler service, then delete all files in C:\Windows\System32\spool\PRINTERS and C:\Windows\System32\spool\drivers subfolders you can (leave the folder structure).
  2. In Print Management, remove every driver package, then restart.
  3. Reinstall only the one printer you need, using the ARM64 driver verified in Fix 2, and confirm stable printing.
  4. If even a clean stack crashes, run an in-place Windows repair from the Windows 11 download page — or check whether a system-level driver conflict is the root cause, similar to documented driver conflict patterns on ARM machines.

Closing

A crashing print spooler on an ARM laptop almost always comes down to architecture: the wrong driver, a corrupted queue, or a leftover component that does not belong on ARM64. Clear the queue, verify ARM64 drivers, strip the junk, and repair the subsystem in that order — and printing becomes boring again, which is exactly what you want. Keep only the printers you use, keep their drivers current, and your spooler will stay out of the crash loop for good.

Frequently asked questions

Why does the print spooler keep crashing on ARM laptops?
The most common cause is a mismatched or damaged print driver — often an x64 driver that Windows tried to use on ARM64. Corrupted spool files from a stuck print job are the second most common trigger, and both are fully fixable.
Will clearing the spooler delete my printers?
No. Clearing the spool folder only deletes pending print jobs, not your installed printers or their settings. Your printers reappear exactly as configured once the spooler restarts.
Can I use my old printer with a Snapdragon laptop?
Usually yes, if the manufacturer offers an ARM64 driver or a universal/class driver supports it. If only an x64 driver exists and the vendor never released ARM64 support, the spooler will crash whenever it loads — check the vendor site before troubleshooting further.
Is it safe to disable the print spooler?
Only as a temporary diagnostic step. Disabling the spooler stops all printing and some fax software. Re-enable it after testing; the fixes below aim to keep it running, not to keep it off.