Explorer.exe constantly crashing

[Smokey]

explorer.exe is constantly crashing on 2 pcs, both have wallpaper engine on, I think it might be related to Wallpaper Engine. Anyone else experiencing this? I'm on the beta, windows 11

[Salt Incarnate]

Im not on beta, but Ive been experiencing crashes for months. Not sure if its related to Wallpaper Engine, but is suspected

[butcho]

The solution is easy: never use a beta of an OS that is unstable, even in it's released form and far worse in it's insider preview state. ^^

[butcho]

Originally posted by Salt Incarnate:

Im not on beta, but Ive been experiencing crashes for months. Not sure if its related to Wallpaper Engine, but is suspected

Most of the time the explorer.exe is the cause of many hassles on a standard windows system. Doesn't matter if it's 10 or 11. They are both cramped with Bloatware and other stuff no user ever asked for. You'll see how good a Windows system can run, if you remove all this crap with a modification like Revision OS for example. Then you got a clean, fast OS. It looks like Windows 10 or 11 and runs as fast like Windows 7 but sadly, Microsoft is not interested in giving people some value for their money.

[Capt.Luke]

yeah the cause might be your BETA version of windows , revert to stable version or try to disable your HDR
read this post
https://steamcommunity.com/app/431960/discussions/1/1746720717352689476/
the beta version of wallpaper engine might contain a fix to your problem

[Smokey]

Honestly doesn't even seem to be related to wallpaper engine. Explorer.exe is having trouble even with it off, just windows being windows but thanks for the replies

[El Psy - エル・プサイ]

After a few months of the problem of the Windows 11 explorer crashing and not being able to identify its cause, on a new computer with clean Windows, after installing the walpaper the same error started to occur, so this error is related to it.
I tried disabling some options but it still happens.

It initially occurs once after starting Windows, and does not occur again until it is turned off. When hibernating Windows and returning the error does not occur.
I didn't have the problem with Windows 10, only when installing on a machine with Windows 11. It possibly started to occur during the Windows 22h2 update, as I noticed that after the update the problem started to occur, and my new computer already came with this version .
It occurs on both Windows 11 Pro and Windows 11 Home.

The only solution I found to get around the error, since it is annoying and if you copy something, it corrupts the file and you have to start the copy again, is to hibernate the computer. Fast shutdown still causes the error.
However, be careful, because if you use an external hard drive, if you hibernate, you need to disconnect it first, as you cannot corrupt the disk without ejecting it, unlike turning it off, which can be removed.

The windows event reports an error in sihost.exe, where I was constantly checking which application called and caused the error, but I discovered it by chance when installing on a new computer.

I don't know which page to open an error discussion, so if anyone can, please inform the developer.

Here's the windows error report:
Faulting application name: sihost.exe, version: 10.0.22621.3672, timestamp: 0xc546fdbd
Faulting module name: ntdll.dll, version: 10.0.22621.3672, timestamp: 0x0cdcba7b
Exception code: 0xc0000409
Fault offset: 0x00000000000c92d7
Faulting process ID: 0x0x1938
Failed application start time: 0x0x1DAB41C44471922
Faulting application path: C:\WINDOWS\system32\sihost.exe
Failing module path: C:\WINDOWS\SYSTEM32\ntdll.dll

[Salt Incarnate]

For me it turned out to be the quick start for Windows. Disabled showing recent files and folders seemed to fix it