SBIE 2205 Clipboard Error (CloseClipboard, C0000058) in Standard/Hardened Sandboxes on Windows 11 — Works in Application Compartment

F

FengXinZi

New member
1. Description
Copy-and-paste between the sandbox and the host fails in both Standard and Hardened sandboxes, triggering the error SBIE 2205 Service not implemented: CloseClipboard C0000058. The same operation works normally in an Application Compartment sandbox (a lower isolation level), which indicates that the core clipboard mechanism is intact and that the issue is specific to the code path used by higher-isolation configurations.
2. Environment
Host OS: Windows 11, clean installation from the official Microsoft ISO. (The reinstall was performed because the machine itself had suffered a failure that Windows’ built-in recovery and repair features could no longer fix; therefore the system is completely vanilla, with no third-party system modifications or bundled software.)
Sandboxie version: first observed on v1.18.0; still reproducible on v1.18.3. Behavior on intermediate versions has not been tested.
Sandbox types tested: Standard, Hardened (and other enhanced-security templates), Application Compartment.
3. Exact error message
PID 14448: SBIE 2205 Service not implemented: CloseClipboard C0000058
4. Steps to reproduce
Perform a clean installation of Windows 11 using the official Microsoft ISO.
Install Sandboxie.
Create a Standard sandbox (or use a Hardened template).
Run File Explorer inside the sandbox and attempt to copy and paste text between the sandbox and the host.
Expected behavior: Clipboard content can be exchanged between the sandbox and the host without any errors.
Actual behavior: The operation fails and the SBIE 2205 error shown above is displayed. This behavior occurs consistently in both Standard and Hardened sandboxes.
5. Troubleshooting observations
Copy-and-paste works perfectly inside an Application Compartment sandbox.
This suggests the fault lies in the clipboard brokering path used exclusively by Standard/Hardened isolation levels, rather than in the Windows clipboard service itself.
6. Questions for the developers
Have the security policies of Standard/Hardened sandboxes been changed in recent releases in a way that could block CloseClipboard (status code C0000058, i.e., STATUS_INVALID_LOCK_SEQUENCE)?
Could a completely clean Windows 11 installation be missing a component that Sandboxie previously relied on to implement clipboard brokering in higher-isolation sandboxes?
 
Sandboxie uses an internal compatibility workaround to adjust clipboard integrity information. During service startup, it temporarily places marker formats on the clipboard to detect the Windows clipboard structure.

That detection can fail if another application was using the clipboard at that moment, if delayed rendering changed the clipboard contents, or if the current Windows build uses a different internal structure than Sandboxie expects. Later, Standard/Hardened sandboxes call the workaround and receive `C0000058` (`STATUS_UNKNOWN_REVISION`), which is then shown as the generic SBIE2205 error.

Application Compartment works because it bypasses this workaround. Restarting the Sandboxie service or rebooting may allow initialization to succeed; if the error persists, it likely indicates a Windows-build compatibility issue rather than a missing clipboard component.

Did this issue start specifically after upgrading to Sandboxie v1.18.0? Have you tested earlier versions, such as v1.15.12, v1.16.9, or v1.17.9, and if so, did the same error occur?

Could you also provide the exact Windows 11 version and OS build number (`winver`), and confirm whether the same issue occurs on Windows 10, if you have tested it there? This will help determine whether the failure is specific to a particular Windows build.
 
offhub said:
Sandboxie uses an internal compatibility workaround to adjust clipboard integrity information. During service startup, it temporarily places marker formats on the clipboard to detect the Windows clipboard structure.

That detection can fail if another application was using the clipboard at that moment, if delayed rendering changed the clipboard contents, or if the current Windows build uses a different internal structure than Sandboxie expects. Later, Standard/Hardened sandboxes call the workaround and receive `C0000058` (`STATUS_UNKNOWN_REVISION`), which is then shown as the generic SBIE2205 error.

Application Compartment works because it bypasses this workaround. Restarting the Sandboxie service or rebooting may allow initialization to succeed; if the error persists, it likely indicates a Windows-build compatibility issue rather than a missing clipboard component.

Did this issue start specifically after upgrading to Sandboxie v1.18.0? Have you tested earlier versions, such as v1.15.12, v1.16.9, or v1.17.9, and if so, did the same error occur?

Could you also provide the exact Windows 11 version and OS build number (`winver`), and confirm whether the same issue occurs on Windows 10, if you have tested it there? This will help determine whether the failure is specific to a particular Windows build.
Click to expand...
Thanks for the reply. I actually managed to solve the problem myself, so I’d like to share my findings as a heads-up for anyone else affected.

It turns out Windows 11 26H1 seems to be incompatible with Sandboxie. Based on what I found on Microsoft’s official documentation, 26H1 is a rather “special” release: unlike previous Windows 11 feature updates, it’s not offered through Windows Update, but only comes preinstalled on select new devices that launched in early 2026, and it’s scoped specifically to those platforms. What’s worth noting is that 26H1 is built on a different Windows core than 24H2, 25H2, and the upcoming 26H2 feature updates. So my guess is that 26H1 differs from 24H2/25H2 — the versions most of us run daily — in some low-level interfaces, which breaks the communication between Sandboxie and the host, resulting in the SBIE2205 error.

Of course, this conclusion is something I worked out together with AI. I’m not a programmer, so I could well be wrong about the details. I’ll attach the official Microsoft page for reference: https://learn.microsoft.com/en-us/windows/whats-new/windows-11-version-26h1 — I’m a Chinese user so my original post is in Chinese; please translate it yourself if needed.

As for how this happened: I ran into the error after mistakenly installing 26H1 during a system reinstall, without realizing it was a special release not meant for regular users. I’ve since clean-installed the latest Windows 11 25H2 (the August version), and the problem has never appeared again.

That’s my summary of the whole incident. If my experience helps you, I’d be really glad. Thanks!
 
Thanks, that is very useful information. A change in the 26H1 kernel could invalidate the clipboard layout detection and cause the `SBIE2205` error. Could you please provide the exact build number from `winver`?
 
offhub said:
Thanks, that is very useful information. A change in the 26H1 kernel could invalidate the clipboard layout detection and cause the `SBIE2205` error. Could you please provide the exact build number from `winver`?
Click to expand...
Sorry, but I’m afraid I can’t help you with that this time. I just reinstalled my system recently, so all my data has been wiped and updated. I also forgot to write down the exact Windows version number when the problem occurred. Based on my recollection, I believe the system I had installed at the time was Windows 11 26H1 Build 28000.2804. The official image I used was named:

zh-cn_windows_11_consumer_editions_version_26h1_updated_aug_2026_x64_dvd_c2bc5d06.iso

MD5 checksum: 5642c3e434720fa40130823c74405193

That said, my guess is that the problem likely affects the entire Windows 11 26H1 Build 28000 branch as a whole — individual minor updates probably wouldn’t change the overall system framework.

Hope this information helps!
 
You must log in or register to reply here.
Back
Top