Open e-t-l opened 8 months ago
DontCopy=*.dll
and DontCopy=*.exe
to your config
- Add
DontCopy=*.dll
andDontCopy=*.exe
to your config- Delete Content
- See if it helps
I'll try that. It might be a few weeks before Office updates and I'm able to see if the issue recurs.
Well, that actually happened quite quickly! The same issue occurred. @offhub's config instructions didn't make a difference.
Going back to my initial theory that the conflict is occurring in the Registry, I deleted all the files in the sandbox but left the RegHives intact. Tried restarting an Office app and sure enough, the issue was still present.
Browsing the sandbox's reg hives, it looks like Office writes tons and tons of stuff, including important HKLM values like Certificate Authorities, so I don't want to give my Office sandbox a blanket whitelist to OpenPipe all the reg keys it wants to write to. But I also don't want to make it Read Only (for the registry), because I have a feeling it does need to write to some keys in order to handle Office software updates properly, and maybe store some Office app settings as well. I'd really like to identify which keys are safe and/or necessary to OpenPipe and just do that. Frequently deleting sandbox content is not a sustainable solution.
Honestly I'm surprised more folks haven't encountered this issue when using MS Office in Sandboxie. It can't just be me, right?
HKEY_USERS\SANDBOX_user_BoxName\
one by one, adding an underscore at the end. (machine or user)
Describe what you noticed and did
I have Microsoft Office sandboxed with the standard Office template, and it works fine at first, but after a while Office will try to update, and after that it will become unusable. On the splash screen for any Office app, instead of "Starting Microsoft [program]..." it will say, "Updating Microsoft 365 and Office..." and after 30-60 seconds it will crash with error code
0xc000142
.It seems likely that Sandboxie is not permitting Office to fully update correctly outside of the sandbox, so there is some sort of mismatch with the contents of the sandbox and the current C2R Office installation. Emptying the sandbox temporarily fixes the issue, but the issue returns within a few weeks (whenever the next Office update rolls out).
At first I suspected there were some leftover Office update/installation files that were causing conflicts, so I tried setting "C:\Windows*" to "Open," and when that didn't work, to "Read only," but the issue persisted. Since I couldn't find any other likely suspects in the sandboxed filesystem, I believe the conflict is likely happening in the Registry.
How often did you encounter it so far?
Every time until I empty the box
Expected behavior
Microsoft Office updates should be applied outside the sandbox, so that Office apps (e.g. Word) run normally and up-to-date inside the sandbox.
Affected program
Microsoft Office 365 ProPlus C2R
Download link
https://c2rsetup.officeapps.live.com/c2r/download.aspx?ProductreleaseID=O365ProPlusRetail&platform=x64&language=en-us&version=O16GA
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 v1.12.9 64-bit
Is it a new installation of Sandboxie?
I recently did a new clean installation.
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?
My sandbox contains existing programs or data.
What is your Windows edition and version?
Windows 11 Enterprise 23H2 64-bit
In which Windows account you have this problem?
A local account (Administrator).
Please mention any installed security software
Avast One
Did you previously enable some security policy settings outside Sandboxie?
No response
Trace log
No response
Sandboxie.ini configuration