Thats really the only poblem I found using SBIE in W10 after updating to the FCU. I waited about 25 seconds, and it didn't open.
I dont open sandboxed Windows explorer by right clicking it but by clicking on a sandboxed shortcut. Regarding the 2 known issues you reported in the opening post, I cant test Chrome as I dont install it in my real system but I can confirm the problem sandboxing Windows explorer. Also, forcing my Download folder and forcing USB drives worked as good as ever. I tested Firefox 32 bits, Internet explorer 11, Libre Office portable, Foxit portable, 7Zip, KMPlayer, Irfan view and Windows media player. I am glad to report that despite Sandboxie not officially supporting the Fall Creators Update as of yet, all programs and functions I run sandboxed work excellent in my laptop. Hi Barb, I upgraded my W10 64 bits laptop to FCU.
This thread is for windows Creator's Fall Update issues + Sandboxie latest beta ONLY. If the issue persists, provide this information:įor questions regarding betas (as well as download links), please see: Please feel free to reply with any new issues you encounter while using the latest Windows Insider v17017 (Fast Ring), or once you receive the Fall Update and the latest Sandboxie beta.īefore posting a problem, be sure to test it in a new Sandbox with default settings + Sandboxie latest beta. "SBIE2101 OpenProcess(C0000022) access=001FFFFF initialized=1" when using "OpenWith" via a Sandboxed Explorer -> Related to Windows Defender.
Right-clicking on sandboxed Windows Explorer files/folders crashes explorer for 5 minutes (after 5 minutes or so, the right-click action starts working). For example, Chrome extensions may leak outside the Sandbox and corrupt the host ones when trying to update them inside Sandboxie. ReplaceFileW windows API function is causing a leak into the host. Here's a list issues that have been addressed:
Please try the latest beta 5.21.7 for full support for Windows 10 - Fall Update.
0 kommentar(er)
