Sandboxie-Plus v1.3.4

Thanks "APMichael" and "stapp" for pointig that possible confusion out. You are right, initially the Win11-"fix" was checked by default and the edge-error-messages began popping up ever since Sb-v1.3.4.

After some advice given here by fellow members I unticked the Win11-"fix"-checkbox and - as described - with that the edge-error-popups were gone.

However in the meantime I had an unsolicited update of edge to its latest version v105.0.1343.42 which I then repeated with the sandbox paused to avoid any sandboxing-caused "half-installation"-side-effects.

From then on I got no Sbie-error-pop-ups any longer but rather the "Profile error" pop-up-window depicted above directly from/within MS-Edge.

To make things even more strange re-checking the Win11-"fix"-checkbox in Sbie will make the Edge-"Profile error" pop-up go away again - at the cost however of having the Sbie-"manifest - service not implemented"-error-messages back.

 

if you are using windows 11 i think yes, on windows 10 its irrelevant

 

you have windows 10 right? it seams the profile error happens only on 11

 

No, sad to say. I've never operated a Win11-machine so far. On my system the profile error occurs on Win10ProForWorksations v21H2 without the (presumably irrelevant) Win11-fix. With that fix re-enabled the profile-error is gone but then the Sbie-"manifest - service not implemented"-error-messages are back in business.

 

I'm seeing that too. If you want to have a look remotely...

 

Here's an odd and interesting issue I could use some help with. Yesterday I upgraded ti Winn11 22H2 and SBIE-Plus 1.3.4. Ever since, I've been having a weird issue with Ashampoo Office. I run them in a sandbox. See the config below. It worked fine before the upgrades. But now I cannot successfully open a office file from Explorer.exe; when I try the office app launches but the file does not open. I can however open a file from within the sandboxed apps themselves. Also, it's worth mentioning that pdf files, viewed using Ashampoo PDF Pro, do not have this issue and open just fine from Explorer.exe. And it's using the same sandbox. Only office files seem affected.

Any ideas as to what could be causing this issue? It worked fine before the upgrades. Could this be caused by 22H2? The dir that stores the docs I'm testing this with has read/write permissions; OpenFilePath

Code:

[Office]
Enabled=y
AutoRecover=y
BlockNetworkFiles=y
Template=FileCopy
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=9
DropAdminRights=y
BoxNameTitle=n
CopyLimitKb=81920
AutoDelete=y
ForceProcess=awrite8.exe
ForceProcess=apresent8.exe
ForceProcess=acalculate8.exe
ForceProcess=Ashampoo PDF.exe
LeaderProcess=Ashampoo PDF.exe
LeaderProcess=awrite8.exe
LeaderProcess=apresent8.exe
LeaderProcess=acalculate8.exe
ProcessGroup=<InternetAccess>,awrite8.exe,Ashampoo PDF.exe,apresent8.exe,acalculate8.exe
ProcessGroup=<StartRunAccess>,C:\Program Files\Ashampoo\PDF\Ashampoo PDF.exe,C:\Program Files\Ashampoo\Office\awrite8.exe,C:\Program Files\Ashampoo\Office\apresent8.exe,C:\Program Files\Ashampoo\Office\acalculate8.exe
ClosedFilePath=!<InternetAccess>,InternetAccessDevices
ClosedFilePath=C:\Program Files\IFW
ClosedFilePath=C:\Scripts\
ClosedFilePath=!<InternetAccess>,InternetAccess
ClosedFilePath=C:\Program Files\VoodooShield
ClosedFilePath=C:\Program Files\IVPN
ClosedFilePath=<BlockNetDevices>,InternetAccessDevices
RecoverFolder=N:\Downloads
RecoverFolder=C:\Users\n8chavez\Documents
AutoRecoverIgnore=.tmvx
AutoRecoverIgnore=.ini
OpenFilePath=C:\Users\n8\Documents
BorderColor=#02f6f6,off,6
FakeAdminRights=n

 

Probably too primitive a solution - but have you checked (after the Win11-upgrade) if those office files (via their extensions) are still associated with this particular office-program ("Ashampoo" it was IIRC)? Chances are slim but perhaps 22H2 may have tampered with its default-apps per file-type?

Can you still open your office-files in Ashampoo if the latter one is run outside a sandbox (e.g. with sandboxing paused for this test)?

 

Yes. Each app is selected as the default for those types.

Yes. In that case, they all open just fine.

 

1.3.4 re-enabled Default Box again

 

Update to the Edge-issue reported earlier:

I can now report that after a new installation of latest, externally downloaded version of Edge, willfully executed with Sandboxie-forcing-programs paused, the profile-error documented above seems to be gone. So I can now uncheck that ominous "Win11-fix" which triggered all those Sbie-"manifest - service not implemented"-error-messages, until now occurring under Win10 amazingly enough.

So - at least without that "Win11-fix" - things with Edge are back to normal here.

 

I'm not using the latest version, but I noticed that I couldn't run mp4 files sandboxed in Media Player Classic HC. I just tried to run them via the right-click ''Run Sandboxed'' menu, via an unsandboxed Win Explorer. I don't believe I tweaked any settings in SBIE. MPC will open and close within a second. Can anyone verify, this is with SBIE Plus v1.2.6, but perhaps it also doesn't work with the newest version?

 

@Rasheed187
Plus v1.3.4 - W10 Home 21H2 (19044.1826) - Shadow Mode
as test:
new install MPC-HC.1.7.13.x64.exe
new MPC HC TEST sbox (Default)
mpc-hc64.exe - Forced
Open with MPC-HC against mp4

Spoiler: related pics

as test:
Pause Forcing
Run Sandboxed against MPC-HCx64 shortcut [DefaultBox] File -> Open

Spoiler: related pics

 

Profile Error

I would get this from time to time. If I restarted or signed out, this would clear it and would no longer appear until next Sandboxie update.

W11
Sandboxie Latest Version Classic

 

Why not test it in the Default Box with Sandboxie's right click menu? So you should simply open a .mp4 file via the Run Sandboxed context menu, I wonder what will happen. With me it really doesn't work, perhaps others can also test? And MPC should not be a forced process.

 

Sorry my as test: does not satisfy.
Run Sandboxed against MPC-HCx64 shortcut [DefaultBox] File -> Open #40.

 

My bad, so you actually did already test this. Perhaps I should upgrade to the newest Sandboxie Plus version and try again.

 

Sandboxie-Plus downloads on the project homepage...
https://sandboxie-plus.com/downloads/...v1.3.2...at this time.
~ by my experience Plus builds are forward/backwards over-install-able ~

 

Thanks, I upgraded to the newest version and it still doesn't always work. I wonder what's up with this. Also, I don't like the ugly Patreon button, so I think I will downgrade again.

 

my Plus has supporter certificate.

 

A small observation--prob. too esoteric but you never know. For a number of builds now, every time the machine boots to desktop, if I open Firefox boxed before Rainmeter has loaded, the mouse pointer is knocked back to the default white one. I noticed Sandman doesn't run now until Firefox is launched, but it doesn't matter when the pointer and Rainmeter are concerned.

I updated my other drive to Windows 11 v. 22623.730 earlier today and restarted, opening Firefox before Rainmeter loaded. Hmmm, mouse pointer stayed at the one of my choice. Tried over and over, I can open Firefox whenever and the mouse pointer stays the same. Well that's great!

Still happens on Windows 10 v. 19044.2075, and tried swapping various skins--no luck. So it seems unique to 10. Not enough to motivate a 100% move to 11, though, I still just don't like it.

 

This button is also in older versions of SBIE Plus, but in the newest it has become ugly, there is no need for this.

 

I`ve started getting a lot of error massages and Firefox crashes in the latest few builds. It would seem that the major culprit is when trying to view a video, be that on Youtube or elsewhere. It doesn`t always happen so is hard to reproduce, anyone else seeing the same error?

SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 14 - WerFault.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 14 - WerFault.exe [FF000000]

Firefox 106 beta 5 (could be the fact it`s a beta but I`ve never had this before)
Windows 10 21H2 19044.2006 (latest)
SBIE 5.58.5 classic

Cheers,
Matt