It's not my day with Sandboxie! When I try to sandbox explorer.exe it crashes every time. I have also tried using a newly created sandbox, but the result is the same: 27.02.2024 12:40:43.672 explorer.exe: SBIE2224 Sandboxed program has crashed: explorer.exe [New_Box] Searching for SBIE2224 doesn't give me any solution. SBIE+ 1.12.9, Windows 11 Beta 23H2 (22635.3212)
Tried that way & crashes every time, as does going to explorer.exe directly and running sandboxed. I suspect I will have to uninstall & reinstall SB+, create new, clean, ini files, and see what happens. To recreate my exclusions and settings will take quite a bit of effort, and I'll have to leave that for another day.
I wish I new. I'll try it on my laptop which hasn't had the latest beta update; it uses the same ini files.
Same on my laptop ie explorer crashes when sandboxed, and not updated to latest beta. I had forgotten that 1.13.0 was installed on my laptop.
I've seen Explorer crash when closed in Windows 11, but if the crash occurs during normal use (maybe right-click?) or when launching, this could be caused by another issue.
It's fine when not sandboxed, right-click or otherwise. That nobody else seems to have a problem means it must likley be down to my SB settings, or a SB conflict with something else I have installed; I do have lots of utils installed, but no issues when not sandboxed.
Uninstalled SB+ deleting all settings and sandboxes, reinstalled with defaults, and while Explorer actually showed its window it then closed after c30secs with no error messages. Never loaded the full tree.
You are not alone, the exact same situation happened to me. Maybe it’s related to the Windows 11 update? Because this problem only occurred about this month. I have several sandboxes, some of which have not cleared their contents for more than a month. Using these sandboxes, I can start Windows Explorer without crashing. And if I try to start Windows Explorer with an empty sandbox, it will crash. Other programs can be sandboxed normally. But there is a very strange way to solve the problem. I can launch Windows Explorer through other programs in the empty sandbox (although explorer.exe is not launched). For example, run Adobe Reader with an empty sandbox, use Adobe Reader's file opening option to open Windows Explorer, and then close Adobe Reader, then you can start Windows Explorer in the sandbox in the normal way, However, if you clear this sandbox, just have to do it all over again. The above situation occurs in both Host and Hyper V Guest. In addition, I have also encountered the situation where the sandboxed explorer sometimes crashes when closed. But the strange thing is that only the explorer in the Guest of Hyper V crashes when I close it, and the explorer of the Host never crashes when I close it. The crash will not happen when you just sandbox the explorer and then close it directly. It will happen if you perform some actions in the explorer, such as creating or deleting a folder, so the sandboxed explorer will crash when you close it. Then there is a another bug related to explorer. In the sandboxed explorer, try to browse the system32 folder under Windows. After sliding down for a while, the explorer will definitely freeze. After a while, the explorer will recover, but the system32 folder It will become blank, and you cannot go to other paths. In the end, you can only close the explorer. I also encountered another bug. In the sandbox with "Block read access to the clipboard" checked, it is indeed impossible to copy or paste text and other objects under normal circumstances. But when using sandboxed cmd, if you have copied any text before, as long as you right-click, the text will be automatically pasted into cmd. These are the 4 bugs I encountered recently.
