Sandboxie-Plus 1.1.1

@catspyjamas

Adding PreferExternalManifest=msedge.exe,y solved it. Thank you.

 

@stapp, awesome, can't wait to try this for myself! One question though, did you try restarting your machine? If I remember from a few pages ago you had a fix with one thing, but it only lasted until restarting.

 

Excellent @stapp BTW David asked me to try 99 & then 98 as per this post. https://www.wilderssecurity.com/threads/sandboxie-plus-1-1-1.445560/page-3#post-3087135

Perhaps give 99 a crack & see how you go? I'm writing this while having dinner at 10pm, which also happens to be lunch! Crazy day today & crazy day in store tomorrow by the looks. If I don't get a chance to try 99 & 98 tomorrow after work, I will do so in the weekend after work & report back.

 

@stapp can you uncheck this option and try 99 again:

 

ok and this: https://xanasoft.com/Downloads/Sandboxie-Plus-x64-v1.1.2.exe with that unchecked?

 

yea there were two issues, one causing a blank edge page and an other causing the welcome page to appear again and agian. and it seams non of them was related to the credentials thing

 

"Non" of them were related to the credentials issue? Is that meant to say "one" or "none". Because my money has been on the banner issue being caused by the credential fix. Haven't had a chance to try the installers that stapp has yet, but will report results as soon as I do. It's 12.14am and I have a 5am start tomorrow.

 

You "disabled and then re-enabled the Win 11 Edge Fix"?
I've had "Win 11 Edge Fix" Disabled since 1.1.1 -> https://www.wilderssecurity.com/threads/sandboxie-plus-1-1-1.445560/page-3#post-3087060
Sorry, I was not clear when I wrote:

I meant that I disabled the enabled "Edge fix for Windows 11".

 

Then why not Windows Filtering Platform (WFP) Support enabled by default?

 

Sbies way is more brute force and blocks also dns queries. WFP does not filter name resolution alone.

 

I have EnableObjectFiltering=y & EnableWin32kHooks=y
I was trying to understand/decide if I should have NetworkEnableWFP=y

 

please try this build: https://xanasoft.com/Downloads/Sandboxie-Plus-x64-v1.1.test.exe

 

as test: from 1.0.22 -> over-install 1.1.test

-
without UseFileDeleteV2=y & UseRegDeleteV2=y
Run Sandboxed -> Test sbox (Default)(Auto delete) - Edge, Chrome, Firefox launch okay.
My Edge, Chrome, Firefox sbox's launch okay.
-
with UseFileDeleteV2=y & UseRegDeleteV2=y ->Test, Edge, Chrome, Firefox sbox's
Run Sandboxed -> Test sbox (Default)(Auto delete) - Edge, Chrome, Firefox launch okay.
My Edge, Chrome, Firefox sbox's launch okay.
-
with UseFileDeleteV2=y & UseRegDeleteV2=y
with Template=Edge_Win11Fix
Run Sandboxed -> Test sbox (Default)(Auto delete) - Edge

-
W10 Home (19044.1706)

 

@DavidXanatos
I have VERY different results to @stapp, but it should be remembered that he is using Windows 10 and I am using Windows 11 21H2 22000.708.
I have a report of 4 installers. All were installed as a clean installation with a new ini, not overwrites. I enabled WFP in all installation wizards but I wasn't sure if I should or not. Otherwise I did not change anything except for enabling auto box delete. Everything else was ou-of-thebox. I did machine restarts between each uninstallation/installation.

1.1.99 - Fail
Loads a white box only, however if I enable the fix for Windows 11 in the compatibility window, it loads Edge, but it loads with the welcome banner.

1.1.98 - Success!
Loads a white box only, but if I enable the fix for Windows 11, it loads Edge as expected! With NO banner, no broken theme, and outlook will load immediately when I got to outlook.com and then hit the "sign in" button. This doesn't happen on any other build for me after 1.0.22 (I haven't tried 1,1.0 having said that). It also survives a machine restart! Yay! This build behaves like 1.0.22 (with the Windows 11 fix added, that is).

1.1.2 - Fail
Loads a white box only. There is no option to enable the fix for Win 11 in this build, however if I manually add PreferExternalManifest=msedge.exe,y in the default sandbox ini, it loads Edge, but it loads with the welcome banner.

1.1.test - thoroughly broken.
Loads a white box with the fix for Windows 11 disabled. If I enable it I get a white box and an error message as per the image below. I tried restarting the machine to see if that helped but I got the same result.



It should also be noted that Edge and Chrome both got updated this morning, so my tests were done on the new stable version of Edge. However I DID test both browsers with 1.0.22 after the browsers updated and they worked just fine. I'm writing this on sandboxed Chrome with 1.1.test, so that works anyway.

 

1.9.98 working unfortunately does not tel much as there everything new is disabled

I would have bet .test will work fine having just the right amount of roll backs.
That said, the errors you see seam strange and unrelated to the previous issues.

do you have UseFileDeleteV2 and UseRegDeleteV2 disabled?

 

Oh. :/

UseFileDeleteV2 and UseRegDeleteV2 were set how they came with the installers out of the box. I didn't specifically check to see if they were in the ini as one or the other, so however you provided the installers is what they were. WFP was the only thing in the wizard I enabled, also auto delete sandboxes, but otherwise the installations (all clean, no overwrites) were fresh out of the box.

BTW I need that PreferExternalManifest=msedge.exe,y for my Edge sandboxes on my Windows 10 machines now too - ever since the last update to Edge (before today's one), which occurred about a week or so after the KB that broke Edge to a white box on Windows 11. With the Windows 10 machines I can avoid the white box if I either disable hardware acceleration, or enable hardware acceleration but apply the PreferExternalManifest=msedge.exe,y
Obviously disabling hardware acceleration in Edge on Windows 11 doesn't stop the white box, but that was broken by a different thing (plus I'm sure you would have established that in your own testing on your Windows 11 machine with that KB). Disabling that was the first thing I tried.

I did test 1.1.2 yesterday already and it failed, and I tried UseFileDeleteV2 and UseRegDeleteV2 both disabled and enabled, with no difference in behaviour between both options. If the installers in the above came disabled out of the box, then yes, they were disabled on the above tests. (Sorry accidentally posted before I'd finished typing).

 

I have a problem starting Chrome and Firefox: I get a "SBIE2303: Could not hook CreateServiceW (SEC)" notification. Edge browser opens sandboxed.

EDIT: Worth adding that I also cannot start LibreOffice applications. There is no notification, but they simply do not open.

EDIT 2: I uninstalled and re-installed Sandboxie-Plus. Now Edge does not run either. I see a white screen with a yellow frame.

EDIT 3: For the record. I tried v.1.1.0 and 1.0.22. They have the same problem as stated above (no web browsing and no LibreOffice apps). I didn't try testing anything else, but I'm hoping for a thorough solution to be found soon.

Windows 11 Pro, Voodooshield and DefenderUI on my laptop.

 

Since things are slightly different between Windows 10 & 11 (based on stapp's & bjm_'s input here), I decided to update my Windows 11 machine from 1.0.22 to 1.1.0 to make sure all is well with that build instead of just assume. No problems with 1.1.0 - it seems no different to 1.0.22. My problems with Edge launching with the banner start with 1.1.1. (Like 1.0.22 I do have to add PreferExternalManifest=msedge.exe,y to get Edge to open beyond a white box).

I'm off to bed. I'll be back on the forum to try any new suggestions in about 19hrs or so (after sleep and work tomorrow).

 

@catspyjamas
please try this one: https://xanasoft.com/Downloads/Sandboxie-Plus-x64-v1.1.2.x1.exe