sandboxie-plus / Sandboxie

Sandboxie Plus & Classic
https://Sandboxie-Plus.com
GNU General Public License v3.0
13.45k stars 1.5k forks source link

Sandboxed RDP login dialog prompt an error when logging #3840

Open 0x391F opened 4 months ago

0x391F commented 4 months ago

Describe what you noticed and did

  1. Run mstsc.exe in sandbox
  2. Connect to remote computer
  3. Error 0x800706be

How often did you encounter it so far?

No response

Expected behavior

This bug shouldn't appear.

Affected program

mstsc.exe

Download link

N/A

Where is the program located?

The program is installed only outside the sandbox.

Did the program or any related process close unexpectedly?

Yes, it did, but no .dmp file has been created in the system.

Crash dump

No response

What version of Sandboxie are you running now?

Sandboxie-Plus 1.13.6 x64

Is it a new installation of Sandboxie?

I just updated Sandboxie from a previous version (I don't remember which one).

Is it a regression from previous versions?

No response

In which sandbox type you have this problem?

In a standard isolation sandbox (yellow sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

What is your Windows edition and version?

Windows 10 Exterprise LTSC 2021 x64 (21H2) 10.0.19044.4291

In which Windows account you have this problem?

An account with UAC protection set to Always notify.

Please mention any installed security software

ESET Internet Security 17.1.19.0

Did you previously enable some security policy settings outside Sandboxie?

No response

Trace log

No response

Sandboxie.ini configuration

No response

0x391F commented 4 months ago

1

JanHellwig commented 2 months ago

I have the same issue, but it's only happening on Windows 11 for me. Currently I'm running Sandboxie-Plus 1.13.7 on that machine, but it was the same with earlier versions as well.

One of these shows up in the Windows Event Viewer when trying to RDP into a different computer, not sure why it's seems to switch between System32 and SysWOW64.

Faulting application name: CredentialUIBroker.exe, version: 10.0.22621.3672, time stamp: 0x365a0443 Faulting module name: CoreMessaging.dll, version: 10.0.22621.3672, time stamp: 0x41404c38 Exception code: 0xc0000602 Fault offset: 0x00000000000914c8 Faulting process id: 0x0x3C70 Faulting application start time: 0x0x1DAC3A76A29C855 Faulting application path: C:\Windows\System32\CredentialUIBroker.exe Faulting module path: C:\Windows\System32\CoreMessaging.dll Report Id: a60139ed-7c4c-4c11-a0a0-21a9fc302918 Faulting package full name: Faulting package-relative application ID:

Faulting application name: CredentialUIBroker.exe, version: 10.0.22621.3672, time stamp: 0xfd1beef7 Faulting module name: CoreMessaging.dll, version: 10.0.22621.3672, time stamp: 0x7096cac1 Exception code: 0xc0000602 Fault offset: 0x000162d7 Faulting process id: 0x0x8F8 Faulting application start time: 0x0x1DAC3A6843A72AD Faulting application path: C:\Windows\SysWOW64\CredentialUIBroker.exe Faulting module path: C:\Windows\System32\CoreMessaging.dll Report Id: c12d9aa3-3150-4c26-b2d1-18d7248dfd6b Faulting package full name: Faulting package-relative application ID:

love-code-yeyixiao commented 2 months ago

On my Windows10,there is no problem even if it is connecting to my localhost.