Can't install some applications utilizing the Nullsoft installer: The file does not have an app associated with it for performing this action.

[birdie-github]

I'm running Windows 10 LTSC (which is based on Windows 1809) with all updates installed: Microsoft Windows Version 1809 (OS Build 17763.973). I'm running SandBoxie 5.33.1 - the application says it's the latest available version - no updates found.

I cannot install some applications which use the Nullsoft installer.

Sandboxie is installed by default, nothing has been changed in its config.

Here's a sample application: https://www.hdtune.com/files/hdtune_255.exe

The errors are: The file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the Default Apps Settings page. Unable to execute file in the temporary directory. Setup aborted. Error 1223: The operation was canceled by the user.

The application can be installed directly without using SandBoxie. I'm a local administrator. UAC is off. I've verified that the installer unpacks a payload in the temporary location and it's a valid exe file though it doesn't have the usual extension (exe).

Here's the global settings section:

[GlobalSettings]

Template=WindowsRasMan
Template=WindowsLive
Template=OfficeLicensing

(Strangely I don't remember ever installing MS Office or Windows Live).

Edit: the issue affects Windows 10 built-in Administrator account only.

[DavidXanatos]

Strange for me it worked just fine

Here's the global settings section:

[GlobalSettings]

Template=7zipShellEx
Template=AdobeLicensing
Template=WindowsRasMan
Template=WindowsLive
Template=OfficeLicensing
Template=OfficeClickToRun
FileRootPath=G:\Sandbox\%SANDBOX%

May be try clearing the sandbox content...

The most recent version here is 5.40.1, you can always find the most recent release at https://github.com/DavidXanatos/Sandboxie/releases
The version check in older Sophos builds wont longer work.

[birdie-github]

I'm using Windows 10 LTSC and it's reproducible right away. You can download it and trial it for 90 days: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise - choose "ISO - LTSC".

[birdie-github]

@DavidXanatos

Cannot test the latest 32bit released version due to:

[birdie-github]

@DavidXanatos

After disabling drivers signatures verification I managed to make SandBoxie work, alas the error persists:

I'd be glad if you fixed the issue which is affecting Windows 10 LTSC - millions of people and organizations are using it.

[DavidXanatos]

So the first errors were on a x64 version?

About "disabling drivers signatures verification", bloody windows, i will re-upload a fixed 32 bit installer asap.

[birdie-github]

So the first errors were on a x64 version?

Yes, they were from my host OS, now I'm testing in a VM as I'm too lazy to reboot.

About "disabling drivers signatures verification", bloody windows, i will re-upload a fixed 32 bit installer asap.

Thank you! :-)

[DavidXanatos]

ok the 32 bit installer should now work.

i tested the 64 bit version of LTSC and it worked for me:

[birdie-github]

OK, then I will reinstall W10 LTSC again and recheck. It's OK if you close this bug report.

[birdie-github]

@DavidXanatos

I've realized what the issue is, hooray! SandBoxie shows this error when you're using it under the built-in Administrator account (it's disabled by default). If you're using a newly created account (e.g. created during an installation) there's no error. Hope you can now reproduce it and fix it.

I presume it's down to some UAC workarounds in the source code which break down when the user is UAC free (the built-in Administrator account is exempt from the UAC restrictions). I might be totally wrong though.

[DavidXanatos]

@birdie-github

Indeed from the built in administrator i can reproduce this error as well.

I will look into it.

[DavidXanatos]

I have been investigating this issue and it seams that the elevation mechanism of sandboxie fails when run under the admin account as there is no such thing like elevation.

The proper fix would be to detect that its running as admin and skip this mechanism in such case,

[birdie-github]

@DavidXanatos

The proper fix would be to detect that its running as admin and skip this mechanism in such case,

This sounds like a simple fix, no?

[birdie-github]

@DavidXanatos

Are you going to fix this issue? No rush, I'm just curious.

[DavidXanatos]

@birdie-github
I intent to fix that somehow at some point but as the issue affects only the built in Administrator account and no other user accounts its not very high priority unfortunately.

[DavidXanatos]

I found a fix and its quite easy first we don't apply any out of palce atempts to elevate using uac, also we use teh enw fake admin rights option for the build in administrator account by default