Error message from QuestionExplorer appears briefly before the system stops unexpectedly.
Error message from QuestionExplorer appears briefly before the system stops unexpectedly.
The program encounters random issues where explorer.exe reports an application error, referencing memory address 0x00000000 and stating it cannot be read. In the event viewer, a volume shadow service is identified as the main cause, with details about the CLSID and system shutdown status. After shutting down, the explorer.exe error appears only after some delay or when OK is clicked. There are no fixes found so far—trying automatic start options and a clean boot didn’t help. A RAM diagnostic test also showed no errors. The process seems harmless but bothersome.
volume shadow copy corresponds to system restore. Have you checked the number of records already? You might need to reduce them.
This guide explains how to manage system restore points on Dell systems.
Disabling it can be helpful when no new drivers are installed, as it creates a restore point beforehand.
Learn how to enable or disable System Restore in Windows 11 through this tutorial.
System Restore keeps track of changes and saves a snapshot of your system. If a problem arises after a change, you can revert to the previous state.
Consider disabling it temporarily to test if it resolves an issue.
Another approach: right-click Start, select Terminal (as Administrator), and if it doesn’t open in PowerShell, click the arrow in the title header and choose from the list.
You can paste this command into the window:
Repair-WindowsImage -Online -RestoreHealth
Press Enter.
Then run SFC /scannow and press Enter.
If needed, restart your PC as some fixes require a restart to apply.
The first command cleans the files SFC uses and updates system files via DISM.
SFC stands for System File Checker. The initial command runs DISM.
You can find more details here: https://docs.microsoft.com/en-us/windows...windows-11
I verified that system restore is active on my C drive, then turned it off using the local policy group editor. I also ran the Terminal and SFC commands as recommended. No issues were found. I lowered the restore level to 0%. I'm just wondering why system restore is connected to the explorer.exe error message before shutdown.
Event 8193 is probably responsible for the explorer pop-up.
https://learn.microsoft.com/en-us/t...st...orm-backup
Running disk cleanup might be useful; it seems to clear temporary folders.
Looking for cleanup options appears to show the second choice in the app.
If an app isn't fully done at shutdown, you'll see the explorer indicating it's not finished, particularly when files are involved.
I would consider using system restore as if it weren't very effective, since it creates a restore point before any updates can occur.
I completed everything, including crafting the script precisely as intended. Even after that, the issue continues to occur.
did you mention this on another site? just checking as I came across it today -
links provided point to several discussions.
I saw the event on my PC. It doesn't halt shutdown, but it also doesn't display a process ID, so those results won't apply here. The last time the event happened was on 25th May. Hope this gives you some insight.
Crpytservice - Cryptography Service
not new attempts to resolve this issue. You might want to review these threads and look for possible fixes.
https://www.tenforums.com/general-suppor...-13-a.html
(41 page discussion)
are there any external drives connected to the PC? They could be causing the problems.
Do you use Macrium Reflect? I’m not using it, but it’s mentioned often in that thread.
No clear solutions so far; it seems the events began around 1909 with Windows 10.
I haven't used external tools or Macrium before.
It's confusing because most discussions claim it's safe but still slows down the shutdown process, which is unclear whether that's acceptable.
It's strange that Microsoft hasn't addressed this yet. I checked to see if anything could help.
The previous execution occurred on the 18th of May. There are no indications of failure on that date in reliability records, so it isn't linked to any updates or store patches. No errors were logged in the Windows error reports for that day—perhaps I was mistaken... I’ve run out of options.
https://learn.microsoft.com/en-us/window...py-service
I wonder how my last version was created.
It’s not clear what steps to follow to find it.
Would you consider searching for "create restore point"?
Open the Control Panel and select the result.
Click on the System restore... option.
A wizard will appear, then you’ll see date options. You can click a button at the bottom to reveal more details.
You should avoid making any choices—this will revert the system.
We’re just going to click Cancel.
My creation dates don’t match the last time it ran, which seems to happen roughly every week.
I’m curious about the processes involved in tracing it if we knew what to look for.
Have you tried a clean boot to check if the issue persists during shutdown?
Try a clean boot and observe any changes—follow the instructions carefully and make sure not to disable any Microsoft services, or Windows won’t load properly.
https://support.microsoft.com/en-au/help...in-windows
It doesn’t remove anything; it simply stops non-Microsoft programs from starting with the start menu. Easy to undo.
If a clean boot resolves the problem, it likely points to a startup program. You should restart those programs one by one over several attempts to pinpoint the culprit.