Installing GTK# inside sandbox gives "Error getting file security"

[stdedos]

Describe the bug
GTK# is installed outside the sandbox.

On a future app update, the GTK# needs to be installed again.
While installing it inside the sandbox, I get the following error:

I tried to change access rights outside the sandbox (to the "default" Administrators), but it doesn't work.
Files outside the sandbox need to be moved away for the installation to proceed.

Also, trying to copy a path from the installer here

crashes the installer very badly.

Expected behavior

• Installation proceeds as normal
• File path can be copied from the installer

System details and installed software

• What is your Windows edition and version? (e.g. Windows 10 Pro 20H2 64-bit) 1909 (18363.836)
• What is your current Sandboxie edition and version? (e.g. Sandboxie Plus 0.9.6 64-bit) 0.9.8d
• What was your previous Sandboxie version before the update, if any? All the way from before Sandboxie was open source
• Please mention in which version this bug got introduced, because it acts as a guide for testers and developers. (maybe) 0.9.0 -> 0.9.8d
• Please mention any security software running in the background, even if the real-time protection is disabled.
  About ... 363 processes. Windows Defender also

If you have a compatibility issue

• Please add a reference link to the program not working properly in Sandboxie.
• Please consider to take a log and make it available for analysis: https://git.io/Jwj2y

Additional context
Add any other context about the problem here.

Sandboxie configuration
If applicable, consider to attach your Sandboxie.ini configuration by copying the content on https://gist.github.com and sharing the resulting link. If you decide to paste the configuration here, make sure to use the backticks around strings, like in this working example:

My initial sandboxie.ini settings

[GlobalSettings]

.....

[UserSettings_175D0429]

.....

[DefaultBox]

.....

[DavidXanatos]

did that work in the past?

[stdedos]

I have installed it once in the Sandbox, and then Natively.

However, I didn't have a reason to try it again 😕

[DavidXanatos]

can you please point me to the instaler download for this issue

[stdedos]

Sadly, I have no idea where to get "the pure one".

• Care to use mine? https://drive.google.com/file/d/14mKTrwV8X9O8lbrqC1gklzou3OyDfRmw/view (link doesn't exist anymore)
• Or otherwise, follow my flow: https://github.com/PintaProject/Pinta/releases/download/1.7.1/Pinta.exe

[DavidXanatos]

hmm... on my system that installed just fine with the upcoming build 1.0.2 can you test with a new standard default box?

[stdedos]

I'm sorry to be like that, but ... is 1.0.2 stable? 😅

[DavidXanatos]

may be, surely more stable then 1.0.0 and 1.0.1 lol

[stdedos]

It seems that ... there is no 1.0.2? 😕

Latest one appears to be 1.0.1.

I'll wait a few around, to make sure it's stable enough (i.e. no BSODs)

[DavidXanatos]

1.0.1 shoudl have no bsod's

[DavidXanatos]

1.0.2 is out: https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.2 please test

[DavidXanatos]

@stdedos so doe it work for you now with the new build?

[stdedos]

Hello David - as I mentioned, I'd prefer to wait for a stable version to come around.

I am additionally in vacation since last week - and therefore far away from the PC-in-question.

[stdedos]

"System is unable to open the device or the file specified"

Trace Log (activated after-the-fact) shows:

|Process|                                   |Type|         |Status|   |Value|                                                        

msiexec.exe (15564, 18060) - 21:38:18.743   Ipc (D)                   \Sessions\1\BaseNamedObjects\SBIE_WindowsInstallerInUse        
msiexec.exe (15564, 32312) - 21:38:49.301   Pipe (U)                  \Device\HarddiskVolume1\Sandbox\stdedos\AOneShotSandbox        
msiexec.exe (15564, 32312) - 21:38:49.301   Pipe (U)                  \Device\HarddiskVolume1\Sandbox\stdedos\AOneShotSandbox\user   
msiexec.exe (15564, 32312) - 21:38:49.301   Pipe (U)                  \Device\HarddiskVolume1\Sandbox\stdedos\AOneShotSandbox        
msiexec.exe (15564, 32312) - 21:38:49.301   Pipe (U)                  \Device\HarddiskVolume1\Sandbox\stdedos\AOneShotSandbox\user   
msiexec.exe (39900, 25288) - 21:38:49.301   WinClass (U)              MsiDialogCloseClass                                            

Which I don't get/makes no sense - explorer.exe can open it.

About Sandboxie-Plus
Version 1.0.7

[isaak654]

In my experience, GTK# installs fine through Pinta 1.7.1 on Sandboxie only when it's not installed outside the sandbox.
I've used Plus 1.0.8 x64 and W10 20H2 x64.

[stdedos]

In my experience, GTK# installs fine through Pinta 1.7.1 on Sandboxie only when it's not installed outside the sandbox.

Exactly my problem. I didn't want to keep Pinta in Sandboxie forever - I only wanted to extract it.
Unfortunately, libraries do need to be installed - so I did install them.

[Simba98]

This is only happening while the same files exist both inside and outside of the sandbox, if we remove the file outside of sandbox, it will work well.

[DavidXanatos]

so how to exactly reproduce this issue when i install gtk outside the inside one does not alow me to instal as it detecits it being installed?

[offhub]

You can install it by clicking Repair, but you will get an error similar to the first message. It can be installed without error by setting MsiInstallerExemptions=y.

[offhub]

If we install the program in the sandbox when the program is not installed on the host computer, the WOW6432Node key is duplicated in the sandbox. I don't know if this is a Sandboxie problem.