search

sandboxie-plus / Sandboxie

Sandboxie Plus & Classic
https://Sandboxie-Plus.com
GNU General Public License v3.0
13.69k stars 1.52k forks source link

"Setup is unable to open data file" from spawned process #1433

Open memorynoise opened 2 years ago

memorynoise commented 2 years ago

FollowUp to https://github.com/sandboxie-plus/Sandboxie/issues/1408: after spawning the acmsetup.exe process the installer now shows a different error: Screenshot (3).

Tested on both v1.0.3 / 5.55.3 and v1.0.2 / 5.55.2.

No idea about what's going on, It looks like some kind of environment start folder error?

Here's the trace log: https://gist.github.com/memorynoise/eda35bb72d0c1afc828f4f8a6352dc85

As I said earlier, it works fine when I run outside of sandboxie.

Originally posted by @memorynoise in https://github.com/sandboxie-plus/Sandboxie/issues/1408#issuecomment-992832646

memorynoise commented 2 years ago

Tried a few more tests, unfortunately I'm still experiencing the same bug. Tried uninstalling and reinstalling the latest version of Sandboxie Plus, tried running it from the original CD and an ISO image,and yet it still crashes with the "Setup is unable..." error. The system is a fresh and fully updated install of Windows 10 64 Bit, with basically nothing more than GOG Galaxy, Steam, Daemon Tools Ultra (tried with both DT enabled and disabled) and the Xbox controller utility.

I'm really stumped. Can't think of anything that could affect the installer behaviour while running inside of the sandbox.

For what it's worth I'm adding a copy of a full trace log and a copy of my sandboxie.ini file.

sandboxie.ini: https://gist.github.com/memorynoise/e5a922ce00debd14403a8ab0040dc0dd full trace log: https://gist.github.com/memorynoise/4c1333229192057601b418e50d8e6b19

memorynoise commented 2 years ago

Alright, I think the issue could be related to the following:

It looks like that Windows 10 can actually replace several 16-bit executables from an hardcoded list from the registry with specifically recompiled 32-bit equivalents. According to this blog post, this MSDN article and this old post by Raimond Chen, the ACME Installer (a.k.a. the aforementioned acmsetup.exe) is one of those.

This is only valid for 64-bit of windows 10, 32-bit releases still use the legacy NTVDM subsystem.

Is there any read/write permission required for the specified registry path or the SysWOW64 folder that could be causing the issue with Sandboxie?

DavidXanatos commented 2 years ago

No access issues but sbie doesn't always play ncie with the program compatybility asistent so possibly thats the issue right tehre