SB v5.31.4 "The Windows Installer Service Could Not Be Accessed" when trying to install programs.

I can confirm the issue too. One machine with windows 10 build 18362 and SBoxie 5.31.4 throws the installer error. 

Another machine with Windows 10 build 14393 and SBoxie 5.31.4 lets the installer run just fine.

So yes it looks to be a windows update issue.

I also tried all sorts of windows installer repair and other hacks but keep hitting the same wall.

If anyone finds a workaround, please post. Sandboxie is dead in the water until this is resolved.

I can confirm the issue too. One machine with windows 10 build 18362 and SBoxie 5.31.4 throws the installer error. 

Another machine with Windows 10 build 14393 and SBoxie 5.31.4 lets the installer run just fine.

So yes it looks to be a windows update issue.

I also tried all sorts of windows installer repair and other hacks but keep hitting the same wall.

If anyone finds a workaround, please post. Sandboxie is dead in the water until this is resolved.

I thought that I found a workaround but no: I was not awake enough, it was not working... 

Hello Sir Toto,

I tried your trick but it didn't work for me, I still get that message. Maybe I didn't do it right. My steps:

1. Made a folder on the desktop.

2. I right-clicked on the folder and opened it up in the default sandbox.

3. I right-clicked in the sandboxed folder and created a new notepad file.

4. I opened it, wrote something in it and saved it.

5. I then copied the msi installer from outside the sandbox into the sandboxed folder.

6. I run the installer - and got the error message.

What have I done wrong?

Thanx.

Hello Bellzemos, 

My bad ! I't not working: I didn't realize that the installer was not running sandboxed the way I did.

I'm sorry, I should have noticed that.

My apologies for this false hope...

No need to be sorry, I wish it would work! This is a big problem, I'm unable to install programs under Sandboxie anymore. Will this get fixed (soon)?

Bellzemos said:

Will this get fixed (soon)?

Barb is gone. Seth doesn't want to reply to questions about community and support. Sophos is neither publishing the source code nor telling when it will be published.

In this situation, do you really think any problem will get fixed soon?

The communication of this company is really very bad. Not just during the time between the beginning of the sandboxie problem and the announcement that it will be made open source, but also after these announcement. When they would answer to the most urgent questions, and tell us a time schedule of making it open source, the discussions in the forum (and also outside in other forums) would be less negative. Missing communication is the real problem here.