Hi, I met a SBIE2205 error when trying to run a game plugin program within Sandboxie.
My machine has Win7 64 bit installed and the latest version of Sandboxie (5.20).
The full error message is:
SBIE2205 Service not implemented : ImpersonateNamedPipe
err=41020897 ... str1= ... str2=poe1 \Device\HarddiskVolume1\Users\Admin
err=41020897 ... str1= ... str2=poe1 \Device\HarddiskVolume1\Users\Admin
err=41020897 ... str1= ... str2=poe1 \Device\HarddiskVolume1\Users\Admin
err=41020897 ... str1= ... str2=poe1 \Device\HarddiskVolume1\Users\Admin
I used to run an old version of Sandboxie (3.72), it was totally fine with that version. What could be the problem here?
SBIE2205 Service not implemented ImpersonateNamedPipe
Moderator: Barb@Invincea
Re: SBIE2205 Service not implemented ImpersonateNamedPipe
It means that the sandboxed program is using a Windows API that Sandboxie does not allow.
After reading the description here: https://msdn.microsoft.com/en-us/librar ... s.85).aspx I must say that one sounds ripe for potential exploits and may have been blocked for a good reason. Perhaps one of the devs will chime in with more thoughts\info?
After reading the description here: https://msdn.microsoft.com/en-us/librar ... s.85).aspx I must say that one sounds ripe for potential exploits and may have been blocked for a good reason. Perhaps one of the devs will chime in with more thoughts\info?
Goo.gl/p8qFCf
Re: SBIE2205 Service not implemented ImpersonateNamedPipe
It seems your post is the final explanation of my issue. ThanksSyrinx wrote: ↑Wed Sep 06, 2017 11:23 amIt means that the sandboxed program is using a Windows API that Sandboxie does not allow.
After reading the description here: https://msdn.microsoft.com/en-us/librar ... s.85).aspx I must say that one sounds ripe for potential exploits and may have been blocked for a good reason. Perhaps one of the devs will chime in with more thoughts\info?
Re: SBIE2205 Service not implemented ImpersonateNamedPipe
I actually looked into this a tad more and it turns out SBIE does handle some things with ImpersonateNamedPipe but with you getting that error it seems (and I am just guessing here) that it was either something that wasn't passed as expected, the hook wasn't designed to handle or was flagged as an issue and blocked. SBIE does allow 'some' stuff used with this API however, unlike what I posted before.
Goo.gl/p8qFCf
Who is online
Users browsing this forum: No registered users and 1 guest