The important detail here is the scope of the failure: Explorer stops responding when opening an SD card with mixed RAW photographs and videos. First determine which part still works before changing any settings.
What is actually failing?
Observed behavior: Explorer stops responding when opening an SD card with mixed RAW photographs and videos. Record the exact app or device build, affected account or file, and the first time this happened. A screenshot of the error state or a short log excerpt is useful when it contains no sensitive information.
Control comparison: Switch the folder temporarily to Details view and compare performance with thumbnails disabled; check the same files copied to a safe local folder. Keep the account, file, network and hardware unchanged wherever the comparison permits. If the control works, the difference between the two paths is your most useful clue.
- Does this reproduce every attempt, or only after a reboot, resume, update or account switch?
- Can the affected action complete through another supported route without changing the original data?
- Is the problem limited to one file, one profile, one device or every user of the service?
Separate possible causes
Rendering and device detection can fail independently. Check which file or driver path fails before rebuilding the operating system or resetting all media settings.
Focused investigation: Use Reliability Monitor and Event Viewer application logs to correlate Explorer or codec crashes; inspect the card read-only before trying repairs. Treat this as a way to test a cause, not proof that the cause has already been established.
| What you observe | What to check next |
|---|---|
| The controlled comparison succeeds | Compare the settings, permissions or content specific to the failing path. |
| Both original and control fail | Check the shared device, account, network or service dependencies before changing the application. |
| It works only after a fresh start | Inspect background processes, cache state, session expiry or a reconnect sequence. |
Protect the current setup
Record the current Windows build and application version. Preserve user documents, account access and working drivers before touching device settings.
Save the current configuration, note its values, and use a harmless test item where possible. Avoid combining this repair with unrelated updates. In particular, Do not run a file-system repair on the only copy of irreplaceable photos without backup.
Choose Beginner for reversible checks or Advanced for targeted diagnostics. Explorer stops responding when opening an SD card with mixed RAW photographs and videos. Confirm the affected product, user account, file or device, then record the time and a screenshot without private account information. This is the baseline; do not change settings yet. Switch the folder temporarily to Details view and compare performance with thumbnails disabled; check the same files copied to a safe local folder. Perform the comparison with one harmless test item. Write down both the successful and failing paths so that the next action targets the actual difference. Safely eject and reconnect the card, update supported image codecs and avoid previewing damaged media files; identify whether one thumbnail causes the hang. Change one setting or workflow at a time. Preserve an easy route back to the previous configuration and allow any synchronization, indexing or activation step to complete before retesting. The folder opens in thumbnail view without Explorer restarting, and camera files remain readable. Test the original failing situation rather than an unrelated feature. If it passes, repeat after one normal restart or reconnect; if it fails, restore temporary diagnostic settings and use the Advanced track. Use Reliability Monitor and Event Viewer application logs to correlate Explorer or codec crashes; inspect the card read-only before trying repairs. Note which component provides the first observable failure. Avoid logging secrets, account recovery keys, authentication cookies or the contents of private documents. Use the least invasive diagnostic appropriate to Windows 11 Explorer Freezes While Generating Thumbnails from a Camera Card. Compare the result with the supported control path: Switch the folder temporarily to Details view and compare performance with thumbnails disabled; check the same files copied to a safe local folder. If there are policy restrictions, involve the administrator rather than bypassing them. Safely eject and reconnect the card, update supported image codecs and avoid previewing damaged media files; identify whether one thumbnail causes the hang. Tie any configuration change to a specific observation. If the result is ambiguous, collect additional evidence instead of layering new resets onto an unexplained problem. The folder opens in thumbnail view without Explorer restarting, and camera files remain readable. If this does not pass, reverse temporary changes. Safety limit: Do not run a file-system repair on the only copy of irreplaceable photos without backup. Provide support with the error text, environment version and reproducible comparison; do not submit private tokens or user data.Step-by-Step Troubleshooting
Capture the exact symptom
Use a supported comparison
Apply the narrow repair
Test the original workflow
Establish the failing boundary
Collect focused diagnostics
Get-WinEvent -LogName Application -MaxEvents 25 | Select-Object TimeCreated, ProviderName, Id, MessageValidate the likely cause
Restore and escalate safely
Solution Checklist
Avoid these shortcuts
- Do not run a file-system repair on the only copy of irreplaceable photos without backup.
- Do not treat a successful unrelated feature as evidence that the failing action is fixed; run the original comparison again.
- Do not erase logs, synced files or working credentials before you know which layer was responsible.
Confirm the outcome
Pass condition: The folder opens in thumbnail view without Explorer restarting, and camera files remain readable. Repeat the same test using the original account, document, peripheral or network path; a passing test on a substitute is useful evidence but is not the final result.
For intermittent problems, repeat the operation after a normal application restart and again after the state change that originally triggered it, such as reconnecting a dock, signing in, or resuming from sleep. Check for new errors in the same location as the original symptom.
When troubleshooting does not help
If the controlled test still fails, return temporary settings to their earlier state and collect the minimum relevant evidence. Next diagnostic: Use Reliability Monitor and Event Viewer application logs to correlate Explorer or codec crashes; inspect the card read-only before trying repairs. Note exactly which comparison failed and what changed after the attempted repair.
For managed devices, privacy-sensitive files, damaged storage or account security concerns, escalate to the responsible administrator or vendor with timestamps and non-sensitive logs rather than attempting a broad reset.
Keep this configuration reliable
Maintain supported Windows/Office updates and document any local, device-specific policy or driver settings that were required.
When the system is stable, record the specific working change: Safely eject and reconnect the card, update supported image codecs and avoid previewing damaged media files; identify whether one thumbnail causes the hang. Keep this as a reversible troubleshooting record so a later upgrade does not require repeating unrelated repair attempts.