Closed hg421 closed 1 year ago
I can confirm this issue on Plus 1.0.11 as well.
I can reproduce the initial issue but un checking "Prevent change to network and firewall parameters" solves it for me.
SBIE1314 error related to ping.exe appears only in a sandbox with App Compartment, not in the standard sandbox. Is it expected?
no thats a bug and will be fixed, but after you uncheck "Prevent change to network and firewall parameters" ping should work as normal
after you uncheck "Prevent change to network and firewall parameters" ping should work as normal
Not here, if you need remote support just ask.
the difference is the template: RpcPortBindingsExt when its added then ping works in the next build this tempalte will be auto enabled when switchign a box to compartment mode or creating a new one, existing boxes will need this to have added manually
So, to sum up, we have two bugs in the same issue:
Still repeat in SBIE v1.3.2
Still repeat in SBIE v1.3.2
Can confirm on 1 3 3 with a new created no isolation box BlockNetParam=n is not set but from the look of it it was not intended to be added to begin with , only the template was said to be added and that is there ,so diasble BlockNetParam and you're good to go.
please provide feadback if the build 1.8.2a solves the issue for you or not
I can confirm the fix after updating to 1.8.2a:
What happened?
ping
does not work in an App Compartment box. Instead it fails and produces the messagePING.EXE (30532): SBIE1314 Blocked request to alter network/firewall settings by process 'PING.EXE'
.If the option "Prevent change to network and firewall parameters" is turned off, the message no longer appears, but it still gets stuck.
If the box type is changed to Standard Isolation, the problem disappears and ping works normally.
To Reproduce
ping 127.0.0.1
Expected behavior
ping works normally in AppComp box (like it does in a normal box)
What is your Windows edition and version?
Windows 10 20H2 64-bit
In which Windows account you have this problem?
A local or Microsoft account without special changes.
Please mention any installed security software
Windows Defender
What version of Sandboxie are you running?
Sandboxie Plus 1.10
Is it a regression?
No response
List of affected browsers
No response
In which sandbox type you have this problem?
In an Application Compartment sandbox with no isolation (green sandbox icon).
Is the sandboxed program also installed outside the sandbox?
Not relevant to my request.
Can you reproduce this problem on an empty sandbox?
I can confirm it also on an empty sandbox.
Did you previously enable some security policy settings outside Sandboxie?
No response
Crash dump
No response
Trace log
No response
Sandboxie.ini configuration
No response
Sandboxie-Plus.ini configuration (for Plus interface issues)
No response