• Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Thetechhacker

Simplify your tech life.

  • News
  • Best
  • Guides
    • Android
    • iOS
    • Windows
    • Mac
    • Linux
    • Internet
    • Cryptocurrency
    • VPN
  • Reviews
Home / Guides / How-to

Gayatry Sharma V / Sep 1, 2025

How to fix Microsoft Edge crashing while printing on Windows?

Windows 11

Several Windows 10 and 11 users report Microsoft Edge crashing the moment they hit Print, especially with PDFs. The issue is usually linked to the Windows print subsystem, sloppy extensions, out‑of‑date printer drivers, or an older Edge build. The steps below resolve the problem in most cases.

Fix 1: Refresh the Print Spooler

  • Stop the Print Spooler service, clear stuck jobs, and start it again.

  • Steps: Press Win+R → services.msc → Print Spooler → Stop; then go to C:\Windows\System32\spool\PRINTERS and delete all files; return to Services and Start the Print Spooler. This resets the queue and removes corrupt spool files that can crash apps during print.

Fix 2: Disable or remove Edge extensions

  • Faulty extensions can interfere with print dialogs. In Edge, visit edge://extensions/ and toggle off third‑party add‑ons; remove any recently installed extension and try printing again.

Fix 3: Reinstall or update printer drivers

  • Outdated or corrupted print drivers commonly trigger print‑time crashes. Open Device Manager → Print queues → right‑click your printer → Uninstall device; reboot and install the latest drivers from the manufacturer (or via the official companion app, e.g., Dell or HP Smart).

Fix 4: Update Edge to the latest version

  • Open edge://settings/help and let Edge download and install updates. Click Restart when prompted. New builds often include fixes for print dialog and PDF handling.

Optional checks that also help

  • Run the Windows Printer troubleshooter and restart the PC after changes.

  • If recent OS updates preceded the problem, repair Edge from Settings > Apps > Installed apps > Microsoft Edge > Modify > Repair.

  • If crashes persist across browsers, the root cause is likely the spooler or drivers; repeat Fix 1 and verify driver integrity.

Why this works

  • Clearing PRINTERS removes corrupt .SPL/.SHD files that crash the print pipeline; restarting the service rebuilds a clean queue.

  • The driver reinstalls and replaces damaged binaries and mismatched configs that Edge triggers when invoking the print dialog.

  • Extension conflicts are common with PDF overlays and ad/script blockers, causing dialog crashes.

FAQs

  1. Why does Edge crash only when printing PDFs?
    PDF print paths exercise both Edge’s viewer and the print driver; any corruption in the spool queue or PDF handler can crash the UI. Clearing PRINTERS and updating the driver typically resolves it.

  2. The crash happens in Chrome as well—what does that mean?
    If multiple browsers crash on print, the Windows print subsystem/driver is the culprit, not the browser. Refresh the spooler (Fix 1) and reinstall drivers (Fix 3).

  3. Is it safe to delete files inside C:\Windows\System32\spool\PRINTERS?
    Yes, those are temporary spool files. Deleting them only clears queued jobs; it won’t remove your printer. Stop the spooler first, then start it again.

  4. How do I repair Microsoft Edge without losing data?
    Windows Settings > Apps > Installed apps > Microsoft Edge > Modify > Repair. This reinstalls Edge while keeping your data. Reboot after repair and test print.

  5. What if nothing helps?
    Try printing to “Microsoft Print to PDF” to isolate the driver. If that works, the physical printer driver is at fault. Reinstall the OEM driver or test a class driver. As a last resort, run System File Checker and contact the printer vendor.

Tagged With: Microsoft Edge, Windows

How to fix application was unable to start correctly 0xc0000018 error in Windows

Primary Sidebar

Related Articles

Footer

Thetechhacker-Logo

Website

  • About us
  • Advertise
  • App Review Program
  • Our Services
  • Contact Us

Policies

  • Disclosure
  • Privacy Policy
  • Terms and Conditions

Copyright © 2025 · Thetechhacker

This site uses cookies to serve you better. By continuing to use this website, you agree to our cookie and Privacy Policy.