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

[Plus 0.8.1] Regression with some installers #906

Closed Shadowized closed 3 years ago

Shadowized commented 3 years ago

Describe the bug It would seem that after upgrading to SBIE+ v0.8.1, bug #595 is happening again.

To Reproduce

  1. Run setup.exe inside a sandbox
  2. a dialog with "Runtime error 229" appears, a few more of the same dialog spawn with no interaction after some time.
  3. Clicking OK closes the installer.
  4. See screenshot.

Expected behavior The installer should run fine like in the prior versions.

Screenshots image

System details and installed software (please provide the following information):

Additional context Tried testing and toggling the new flags but to no avail, using both my own and clean Sandboxie.ini

DavidXanatos commented 3 years ago

what installers are causing this issue?

Also please try the optionApplyElevateCreateProcessFix=y

Shadowized commented 3 years ago

Also please try the optionApplyElevateCreateProcessFix=y

I did, along with the other documented additions and it still errors.

DavidXanatos commented 3 years ago

on my system the installer opens just fine, should I click on something? (i would guess than it would error out mussing the other files)

Shadowized commented 3 years ago

interesting, perhaps its related to my systems not having UAC enabled? I didn't see much in the changelog from v0.8.0 to v0.8.1 that could cause this. I'll try and narrow it down further by spinning up a cleaner VM image.

DavidXanatos commented 3 years ago

ok and 0.7.5 was working fine?

Shadowized commented 3 years ago

yes, 0.7.4, 0.7.5, and 0.8.0 work fine.

Shadowized commented 3 years ago

So I installed a fresh Win10 201H VM, All I did was create a new user, install SBIE+ v0.8.1 x64, ran the setup.exe in defaultBox and received the same Runtime error. Uninstalled v0.8.1 and installed v0.8.0, it works fine. I tested a bit further and downloaded a fresh Win10 20H2 development environment VM, which are neat ready-to-go VM's and did the same thing, the results did not change,

so at the very least, I can confirm to the best of my knowledge that the issue is in fact not on my end as I can replicate it on multiple fresh VM's and bare metal.

DavidXanatos commented 3 years ago

ok that is strange... and you tried with this stripped down installer you posted here? or with the full one?

Shadowized commented 3 years ago

the stripped down one, as its easier to chuck it on a network share and copy the files to desktop in a few seconds.

DavidXanatos commented 3 years ago

ok will take a second look also with a clean vm may be some artefact in my dev vm prevents the issue from manifesting

DavidXanatos commented 3 years ago

darn it... i have found the bug, its the fix for the driver verifier fix, working on fixing it probably we wil soon have a 0.8.2 LOL