Fix Windows Explorer Crashing When Accessing a PDF Form
Question details
The user needs to stop Windows Explorer from crashing when attempting to access or check the properties of a specific government PDF form.

- Product
- Windows File Explorer / PDF Viewer
- Device & OS
- Windows 10
- Scenario
- Opening, viewing, or checking the properties of a downloaded government PDF form in File Explorer.
- Observed behavior
- Windows Explorer crashes unexpectedly when interacting with the PDF file, though the file may work on older Windows versions or open only once immediately after downloading.
Before troubleshooting, make sure to save any open work in other applications, as restarting or crashing Windows Explorer will forcefully close all active folder windows.
Disable Conflicting PDF Shell Extensions
Identify and disable problematic third-party PDF shell extensions that are causing File Explorer to crash when generating previews or reading properties.
Third-party PDF software, such as PDF-XChange Viewer, often install shell extensions to generate thumbnails or file properties within Windows Explorer. Corrupted or incompatible extensions can conflict with specific PDF files, triggering an immediate crash.
Download and run the free ShellExView utility to view all installed shell extensions on your Windows 10 system.
Sort the displayed list by 'Extension Name' or 'Description' to easily find entries related to your third-party PDF software (e.g., PDF-XChange Viewer).
Right-click the suspected PDF extension and select 'Disable Selected Items' from the context menu.
Press Ctrl + Shift + Esc to open Task Manager, locate 'Windows Explorer', right-click it, and select 'Restart'. Try opening the PDF document again.

Run the Program Compatibility Troubleshooter
Use Windows compatibility mode if your primary PDF reader struggles with legacy PDF forms.
Adjust Data Execution Prevention (DEP) Settings
Add an exception for your PDF reader in Windows DEP settings to prevent security protocols from forcefully closing the app.
Open and Edit PDF Forms Safely with WPS PDF
Avoid Windows Explorer crashes caused by unstable third-party shell extensions. WPS Office includes a lightweight, highly stable built-in PDF reader and editor. It securely handles complex government forms and integrates seamlessly with Windows 10, completely eliminating the risk of system conflicts.
- 1. Download WPS Office: Install WPS Office from the official website to equip your PC with a secure, system-friendly PDF reader.
- 2. Set as Default PDF Application: Right-click any PDF file, go to 'Open with' > 'Choose another app', select WPS Office from the list, and check 'Always use this app to open .pdf files'.
- 3. Access PDF Safely: Double-click the problematic government PDF form. It will now open smoothly and securely in WPS PDF without triggering Explorer property crashes.

Frequently Asked Questions
Why does a specific PDF file crash Windows Explorer?
This typically occurs when Windows Explorer attempts to generate a file thumbnail or read metadata properties using a corrupted or incompatible third-party PDF shell extension. Complex government forms often trigger these bugs in legacy extensions.
What is a shell extension in Windows?
A shell extension is a background plugin that integrates into Windows File Explorer. It provides supplementary features like custom right-click menus, document previews, and visual thumbnails for specific file formats such as PDFs.
How do I remove a PDF shell extension without third-party tools?
You can resolve the conflict by completely uninstalling the problematic PDF software. Go to Windows Settings > Apps & Features, locate the third-party PDF application (like PDF-XChange Viewer), and click 'Uninstall'. This automatically removes its associated extensions.
Will updating my Windows 10 fix the Explorer crash?
While updating Windows 10 is good practice for overall stability, it generally will not resolve crashes caused by third-party application extensions. You must isolate and disable the specific software extension causing the conflict.




