F5F Stay Refreshed Software Operating Systems Windows 10 explorer experienced a crash when attempting to open HTML files.

Windows 10 explorer experienced a crash when attempting to open HTML files.

Windows 10 explorer experienced a crash when attempting to open HTML files.

X
xAquamarine
Member
70
11-22-2016, 11:15 AM
#1
Unable to determine why explorer fails when opening .html files. Created a blank HTML file for testing. Double-clicking it triggers crashes (associated with Edge browser). Doesn't open in File Explorer. Opened via "Open With" works, but Explorer does. Editing with Notepad++ allows normal operation without crashes. File appears in browser windows but not in Explorer. Right-click lets me edit directly. No issues when accessing from FrontPage 2003 or Notepad. The test file contains minimal content.
X
xAquamarine
11-22-2016, 11:15 AM #1

Unable to determine why explorer fails when opening .html files. Created a blank HTML file for testing. Double-clicking it triggers crashes (associated with Edge browser). Doesn't open in File Explorer. Opened via "Open With" works, but Explorer does. Editing with Notepad++ allows normal operation without crashes. File appears in browser windows but not in Explorer. Right-click lets me edit directly. No issues when accessing from FrontPage 2003 or Notepad. The test file contains minimal content.

R
R0CKET_RAC00N
Junior Member
32
11-22-2016, 12:46 PM
#2
Review the EventViewer logs
R
R0CKET_RAC00N
11-22-2016, 12:46 PM #2

Review the EventViewer logs

A
AlexPFM7
Member
52
11-22-2016, 05:28 PM
#3
I verified the crash reports related to Explorer. The faulty component appears to be linked to "windows.storage.dll". After researching this file, several fixes have been proposed. Possible reasons for the failure seem connected to security adjustments. It looks like I might have caused the issue by modifying settings, even though I'm not entirely confident about that. I haven't fully prepared to reset all associated configurations or install a new version of this file yet. Since there are no other major problems, I'll accept this limitation and opt for the workaround—using "open file" instead of double-clicking. This approach is much simpler than trying a potential fix that could break the modifications I made.
A
AlexPFM7
11-22-2016, 05:28 PM #3

I verified the crash reports related to Explorer. The faulty component appears to be linked to "windows.storage.dll". After researching this file, several fixes have been proposed. Possible reasons for the failure seem connected to security adjustments. It looks like I might have caused the issue by modifying settings, even though I'm not entirely confident about that. I haven't fully prepared to reset all associated configurations or install a new version of this file yet. Since there are no other major problems, I'll accept this limitation and opt for the workaround—using "open file" instead of double-clicking. This approach is much simpler than trying a potential fix that could break the modifications I made.