Closed typpos closed 3 years ago
Normaly explorer just tries to eider set itself up as shell or use an existing explorer instance to open a folder window. I know that a very old sbie version like 3.xx or earlier used to fake some registry keys to make explorer think a custom shell is installed. But the current version don't do that anymore instead it uses some explorer start parameters to get the desired behavior.
to get explorer to run properly you need to start it like this explorer.exe /e,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}
v0.5.4b Win 10 Pro
Reproduce:
SBIE2224 Sandboxed program has crashed: explorer.exe [AAA]
The above happens on my physical PC. Doing the same in Windows 10 Sandbox results in explorer.exe briefly starting up and then silently exiting.
Notes: