Page 1 of 2
With Beta 5.23.3 no Office 2013 C2R program will work?[SOLVED in Beta 5.23.5]
Posted: Tue Jan 09, 2018 7:01 am
by SiDi
Hi all,
i also had to install the beta version 5.23.3 because of the windows 7 update(s). Unfortunately no Office 2013 program will work in sandboxie anymore. Is the problem already known or does anyone else have the problem? Here it can be reproduced on three computers.
Regards Simon
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Tue Jan 09, 2018 1:47 pm
by Barb@Invincea
Hello SiDi,
I am not seeing any problems with Sbie 5.23.3 + Office 2013 + Win 7 x64 with latest patches.
Does the issue occur in a new Sandbox with default settings?
Is Office 2013 working on your host?
Please provide this info:
viewtopic.php?f=11&t=19746
Regards,
Barb.-
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Fri Jan 12, 2018 2:59 am
by SiDi
Hi Barb,
thx for the reply. Strange thing , just now everything is working with the beta and office also with my old sandoxes. Maybe the Microsoft Patchday changed something?!?
I will test the problem without the patches from tuesday and than give feedback.
Simon
Re: With Beta 5.23.3 no Office 2013 program will work? [SOLVED]
Posted: Mon Jan 15, 2018 7:22 am
by SiDi
Windows Version: Windows 7 SP1 Pro. x64 with the latest Updates
Sandboxie Version: 5.23.3
Microsoft Word 2013 (15.0.4997.1000) 32-Bit (Home and Business 2013 not Office 365!)
Antivirus: F-Secure Client Security 13.00 ( deactivated for testing no change )
The Problem occurs on three different computers (out of four).
I can reproduce the problem in my virtual machine. Clean install of sandboxie 5.23.3 and Office 2013 with default sandbox settings. No error message from sandboxie and no error message from office. Without sandboxie office works normal. The Problem occurs since meltdown windows patch and the necessary sandboxie beta 5.23.3.
Is there any debug switch or logfile i can provide to find the problem?
I am not the only one with that problem:
viewtopic.php?f=11&t=25290&sid=a6d97530 ... 56#p131802
I don't know why it works on my PC an not on the three other computers.
Simon
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Mon Jan 15, 2018 3:50 pm
by Barb@Invincea
Hello SiDi,
What is the exact error / problem that you are experiencing? Is it crashing? Is it freezing?
What are the steps to reproduce the problem?
Is Word the only affected program? How about Excel / Outlook?
Are there any Office plugins installed?
What's the AV software installed on the computer that does work? Is it the same?
Are there any other differences that you can think of between the machines?
Regards,
Barb.-
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Tue Jan 16, 2018 2:32 am
by SiDi
Hi,
the exact problem is that if i try to open any office program in sandboxie no office windows is opening. (nothing happens) When i click on winword.exe and choose open in sandbox, for a short time some processes in sandboxie control start and then all processes will close and the sandboxie control windows is empty:
First :
https://ibb.co/c5agBm
Then after a couple of seconds:
https://ibb.co/kB0L46
I deactivated our AV Software (F-Secure Client Security) to reproduce the problem in my VM. Its installed on all computer.
On my virtual Machine no Office Plugins are installed. The only differences between the computer where it works and the other computers are:
1. The Office Version Number: 15.0.4971.1002 works -> 15.0.4997.1000 doesn't work. On both computers, Office believes to be up-to-date and does not find any new updates
2. The install directory of office is different. On the computer where it works is office installed to C:\Program Files (x86)\Microsoft Office 15\... and on the computers where it doesn't work its installed to c:\program files\Microsoft Office\... . All Computers running win 7 sp1 x64 and office 2013 32 bit! No Office x64!
I try to reproduce it in my virtual machine again and write the steps to reproduce it down.
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Tue Jan 16, 2018 3:54 pm
by Barb@Invincea
Hello SiDi,
Progams installed under "Program Files" are typically x64 bit. Anything other than that (32 bit) will be under the Program Files (x86) folder. I went ahead and re-tested Office x64 v15.0.4997.1000 --> Launched with no problems .
Since it requires about 80 Windows updates to test this, I am going to have to finish testing x86 tomorrow. I will post an update then.
Can you please provide the results of running Resource Access Monitor? Copy/paste the output here, highlight it and then click on the "</>" button to format it.
https://www.sandboxie.com/ResourceAccessMonitor
Regards,
Barb.-
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Wed Jan 17, 2018 2:47 am
by SiDi
I can reproduce the problem in my virtual machine with updates from december 2017 ( and without meltdown patches ) . I installed office 2013 home and business
32bit and then sandboxie. when i use sandboxie 5.22 everything works and when i install 5.23.3 office wont´t open anymore. switching back to 5.22 everything works again.
the office online installer is now installing a 32bit copy on a 64 bit machine to c:\program files\. Its not a bug its a feature from Microsoft
:
https://answers.microsoft.com/en-us/mso ... d75?auth=1
In the taskmanager all office processes are *32bit processes.
Code: Select all
(Drive) \Device\CdRom0
(Drive) \Device\Floppy0
(Drive) \Device\HarddiskVolume1
Clsid -------------------------------
File/Key -------------------------------
Image -------------------------------
Image *:\program files\microsoft office 15\root\office15\winword.exe
Image *:\program files\sandboxie\sandboxiedcomlaunch.exe
Image *:\program files\sandboxie\sandboxierpcss.exe
Image *:\program files\sandboxie\start.exe
Image c:\program files\microsoft office 15\root\office15\appvisvstream32.dll
Image c:\program files\microsoft office 15\root\office15\appvisvsubsystems32.dll
Image c:\program files\microsoft office 15\root\office15\c2r32.dll
Image c:\program files\microsoft office 15\root\office15\msvcr100.dll
Image c:\program files\sandboxie\32\sbiedll.dll
Image c:\program files\sandboxie\sbiedll.dll
Image c:\windows\system32\advapi32.dll
Image c:\windows\system32\api-ms-win-core-synch-l1-2-0.dll
Image c:\windows\system32\cfgmgr32.dll
Image c:\windows\system32\clbcatq.dll
Image c:\windows\system32\comdlg32.dll
Image c:\windows\system32\credssp.dll
Image c:\windows\system32\cryptbase.dll
Image c:\windows\system32\cryptsp.dll
Image c:\windows\system32\devobj.dll
Image c:\windows\system32\dwmapi.dll
Image c:\windows\system32\gdi32.dll
Image c:\windows\system32\imm32.dll
Image c:\windows\system32\kernel32.dll
Image c:\windows\system32\kernelbase.dll
Image c:\windows\system32\lpk.dll
Image c:\windows\system32\msctf.dll
Image c:\windows\system32\msvcrt.dll
Image c:\windows\system32\nsi.dll
Image c:\windows\system32\ntdll.dll
Image c:\windows\system32\ntmarta.dll
Image c:\windows\system32\ole32.dll
Image c:\windows\system32\oleaut32.dll
Image c:\windows\system32\profapi.dll
Image c:\windows\system32\propsys.dll
Image c:\windows\system32\psapi.dll
Image c:\windows\system32\rpcepmap.dll
Image c:\windows\system32\rpcrt4.dll
Image c:\windows\system32\rpcrtremote.dll
Image c:\windows\system32\rpcss.dll
Image c:\windows\system32\rsaenh.dll
Image c:\windows\system32\sechost.dll
Image c:\windows\system32\secur32.dll
Image c:\windows\system32\setupapi.dll
Image c:\windows\system32\shell32.dll
Image c:\windows\system32\shlwapi.dll
Image c:\windows\system32\sspicli.dll
Image c:\windows\system32\sxs.dll
Image c:\windows\system32\user32.dll
Image c:\windows\system32\usp10.dll
Image c:\windows\system32\uxtheme.dll
Image c:\windows\system32\wldap32.dll
Image c:\windows\system32\ws2_32.dll
Image c:\windows\syswow64\advapi32.dll
Image c:\windows\syswow64\cryptbase.dll
Image c:\windows\syswow64\gdi32.dll
Image c:\windows\syswow64\kernel32.dll
Image c:\windows\syswow64\kernelbase.dll
Image c:\windows\syswow64\lpk.dll
Image c:\windows\syswow64\msctf.dll
Image c:\windows\syswow64\msvcrt.dll
Image c:\windows\syswow64\ntdll.dll
Image c:\windows\syswow64\ole32.dll
Image c:\windows\syswow64\profapi.dll
Image c:\windows\syswow64\psapi.dll
Image c:\windows\syswow64\rpcrt4.dll
Image c:\windows\syswow64\sechost.dll
Image c:\windows\syswow64\shell32.dll
Image c:\windows\syswow64\shlwapi.dll
Image c:\windows\syswow64\sspicli.dll
Image c:\windows\syswow64\user32.dll
Image c:\windows\syswow64\userenv.dll
Image c:\windows\syswow64\usp10.dll
Image c:\windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\comctl32.dll
Ipc -------------------------------
Ipc \BaseNamedObjects\__ComCatalogCache__
Ipc \BaseNamedObjects\{A3BD3259-3E4F-428a-84C8-F0463A9D3EB5}
Ipc \BaseNamedObjects\{A64C7F33-DA35-459b-96CA-63B51FB0CDB9}
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{6AF0698E-D558-4F6E-9B3C-3716689AF493}.2.ver0x0000000000000069.db
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{DDF571F2-BE98-426D-8288-1A9A39C3FDA2}.2.ver0x0000000000000002.db
Ipc \BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*cversions.2.ro
Ipc \BaseNamedObjects\RotHintTable
Ipc \BaseNamedObjects\windows_shell_global_counters
Ipc \RPC Control\actkernel
Ipc \RPC Control\epmapper
Ipc \RPC Control\plugplay
Ipc \Sessions\1\BaseNamedObjects\__ComCatalogCache__
Ipc \Sessions\1\BaseNamedObjects\{A3BD3259-3E4F-428a-84C8-F0463A9D3EB5}
Ipc \Sessions\1\BaseNamedObjects\{A64C7F33-DA35-459b-96CA-63B51FB0CDB9}
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{6AF0698E-D558-4F6E-9B3C-3716689AF493}.2.ver0x0000000000000069.db
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*{DDF571F2-BE98-426D-8288-1A9A39C3FDA2}.2.ver0x0000000000000002.db
Ipc \Sessions\1\BaseNamedObjects\C:*ProgramData*Microsoft*Windows*Caches*cversions.2.ro
Ipc \Sessions\1\BaseNamedObjects\C:*Users***************AppData*Local*Microsoft*Windows*Caches*{AFBF9F1A-8EE8-4C77-AF34-C647E37CA0D9}.1.ver0x0000000000000048.db
Ipc \Sessions\1\BaseNamedObjects\C:*Users***************AppData*Local*Microsoft*Windows*Caches*cversions.1.ro
Ipc \Sessions\1\BaseNamedObjects\ComPlusCOMRegTable
Ipc \Sessions\1\BaseNamedObjects\ProcmonExternalLoggerEnabled
Ipc \Sessions\1\BaseNamedObjects\RotHintTable
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_1284
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_560
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_736
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_DummyEvent_972
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_RPCSS_SXS_READY
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_DcomLaunch
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_Mutex1
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_RpcEptMapper
Ipc \Sessions\1\BaseNamedObjects\SBIE_BOXED_ServiceInitComplete_RpcSs
Ipc \Sessions\1\BaseNamedObjects\SboxSession
Ipc \Sessions\1\BaseNamedObjects\ScmCreatedEvent
Ipc \Sessions\1\BaseNamedObjects\windows_shell_global_counters
Ipc \WindowsErrorReportingServicePort
Ipc O \KernelObjects\MaximumCommitCondition
Ipc O \KernelObjects\SystemErrorPortReady
Ipc O \KnownDlls\advapi32.dll
Ipc O \KnownDlls\CFGMGR32.dll
Ipc O \KnownDlls\clbcatq.dll
Ipc O \KnownDlls\COMDLG32.dll
Ipc O \KnownDlls\DEVOBJ.dll
Ipc O \KnownDlls\gdi32.dll
Ipc O \KnownDlls\kernel32.dll
Ipc O \KnownDlls\KERNELBASE.dll
Ipc O \KnownDlls\LPK.dll
Ipc O \KnownDlls\MSCTF.dll
Ipc O \KnownDlls\MSVCRT.dll
Ipc O \KnownDlls\NSI.dll
Ipc O \KnownDlls\ole32.dll
Ipc O \KnownDlls\OLEAUT32.dll
Ipc O \KnownDlls\profapi.dll
Ipc O \KnownDlls\PSAPI.DLL
Ipc O \KnownDlls\rpcrt4.dll
Ipc O \KnownDlls\Setupapi.dll
Ipc O \KnownDlls\SHELL32.dll
Ipc O \KnownDlls\SHLWAPI.dll
Ipc O \KnownDlls\user32.dll
Ipc O \KnownDlls\USP10.dll
Ipc O \KnownDlls\WLDAP32.dll
Ipc O \KnownDlls\WS2_32.dll
Ipc O \KnownDlls32\advapi32.dll
Ipc O \KnownDlls32\CRYPTBASE.dll
Ipc O \KnownDlls32\gdi32.dll
Ipc O \KnownDlls32\kernel32.dll
Ipc O \KnownDlls32\KERNELBASE.dll
Ipc O \KnownDlls32\LPK.dll
Ipc O \KnownDlls32\MSCTF.dll
Ipc O \KnownDlls32\MSVCRT.dll
Ipc O \KnownDlls32\ole32.dll
Ipc O \KnownDlls32\OLEAUT32.dll
Ipc O \KnownDlls32\profapi.dll
Ipc O \KnownDlls32\PSAPI.DLL
Ipc O \KnownDlls32\rpcrt4.dll
Ipc O \KnownDlls32\SHELL32.dll
Ipc O \KnownDlls32\SHLWAPI.dll
Ipc O \KnownDlls32\SspiCli.dll
Ipc O \KnownDlls32\user32.dll
Ipc O \KnownDlls32\USERENV.dll
Ipc O \KnownDlls32\USP10.dll
Ipc O \RPC Control\AppV-ISV-d8d24034-69a0-44fa-991c-de712c73b87dAppvEnterprise_vcom_subsystem
Ipc O \RPC Control\AppV-ISV-d8d24034-69a0-44fa-991c-de712c73b87dAPPV-RSOD_SERVER
Ipc O \RPC Control\AppV-ISV-d8d24034-69a0-44fa-991c-de712c73b87dAPPV-VIRTMAN-NOTIFICATIONS
Ipc O \RPC Control\AppV-ISV-d8d24034-69a0-44fa-991c-de712c73b87dAPPV-VREG_SERVER
Ipc O \RPC Control\AppV-ISV-d8d24034-69a0-44fa-991c-de712c73b87dvfs_subsystem
Ipc O \RPC Control\C2RClientAPI_Server_System
Ipc O \RPC Control\ClickToRun_Pipeline
Ipc O \RPC Control\lsapolicylookup
Ipc O \RPC Control\LSARPC_ENDPOINT
Ipc O \RPC Control\lsasspirpc
Ipc O \RPC Control\SbieSvcPort
Ipc O \Security\LSA_AUTHENTICATION_INITIALIZED
Ipc O \Sessions\1\Windows\ApiPort
Ipc O \Sessions\1\Windows\SharedSection
Ipc O \ThemeApiPort
Pipe -------------------------------
Pipe \Device\HarddiskVolume1
Pipe \Device\KsecDD
Pipe \Device\MountPointManager
Pipe \Device\Ndis
Pipe \Device\NDMP10
Pipe \Device\NDMP11
Pipe \Device\NDMP12
Pipe \Device\NDMP13
Pipe \Device\NDMP4
Pipe \Device\NDMP5
Pipe \Device\NDMP7
Pipe \Device\NDMP8
Pipe \Device\NDMP9
WinCls -------------------------------
WinCls O OleMainThreadWndClass
WinCls O Shell_TrayWnd
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Wed Jan 17, 2018 1:41 pm
by Barb@Invincea
Hello SiDi,
I tested both x86 and x64 + Sbie 5.23.3 and did not encounter any problems.
Regarding a different path, my office x86 is correctly installed under Program Files x86. The link you provided seems to be related to Office Click-to-Run. Can you please open Word , go to "File --> Account ---> About Word" and copy the first line so that I can make sure we have the same version?
Mine right now reads "(...) Word 2013 (15.0.4997.1000) MSO (15.0.4997.1000) 32-bit" .
I noticed this entry on your Resource Access Monitor output:
c:\program files\microsoft office 15\root\office15\
c2r32.dll
So, if you are using click to run, and your installation path changed, follow these steps:
viewtopic.php?p=129487#p129487
If all fails, please fully remove your antivirus software from your VM and re-try . Sometimes disabling doesn't work.
If nothing else works, and you are still able to reproduce the problem, please provide a PML log:
Download procmon.exe from
https://docs.microsoft.com/en-us/sysint ... ds/procmon
Start procmon and reproduce the issue, then save the log and provide us the link (you will have to upload it to a file hosting website as they tend to be big files).
Regards,
Barb.-
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Thu Jan 18, 2018 9:00 am
by SiDi
Hi Barb,
here the link to the PML log:
https://we.tl/j1DtOVu29O
I removed the antivirus software, same problem. I don´t change the installation path of sandboxie.
The version of Word is : Microsoft Word 2013 (15.0.4997.1000) MSO (15.0.4997.1000) 32 -Bit.
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Thu Jan 18, 2018 1:24 pm
by Barb@Invincea
Hello SiDi,
The devs are reviewing the PML, however we'll need a bit more info:
Please provide a copy of your Sandboxie.ini (Typically on C:\Windows) , and a copy of your configuration settings :
Configure--> Edit Configuration --> Paste the contents here, highlight them and click on the "</>" button to format them in the forums.
Regarding Office 2013 C2R, it seems that MS has removed it from their downloads, so not sure I'll be able to test it. I am still researching.
Regards,
Barb.-
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Fri Jan 19, 2018 1:42 am
by SiDi
Hi Barb, here the config files with removed antivirus (F-secure):
https://we.tl/YEdrjncxYf
Code: Select all
[GlobalSettings]
Template=OfficeLicensing
Template=OfficeClickToRun
ActivationPrompt=n
TemplateReject=FSecure
[DefaultBox]
ConfigLevel=7
AutoRecover=y
BlockNetworkFiles=y
Template=qWave
Template=WindowsFontCache
Template=BlockPorts
Template=LingerPrograms
Template=Chrome_Phishing_DirectAccess
Template=Firefox_Phishing_DirectAccess
Template=AutoRecoverIgnore
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Favorites%
RecoverFolder=%Desktop%
BorderColor=#00FFFF,ttl
Enabled=y
[UserSettings_4BC00582]
SbieCtrl_UserName=administrator
SbieCtrl_BoxExpandedView=DefaultBox
SbieCtrl_NextUpdateCheck=1516887380
SbieCtrl_UpdateCheckNotify=n
SbieCtrl_ShowWelcome=n
SbieCtrl_WindowCoords=498,187,1234,551
SbieCtrl_ActiveView=40021
SbieCtrl_ProcessViewColumnWidths=250,70,300
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Sat Jan 20, 2018 12:06 pm
by jclarkw
Barb@Invincea wrote: ↑Thu Jan 18, 2018 1:24 pm
The devs are reviewing the PML, however we'll need a bit more info...
Hi, Barb -- I just tried this, and it failed for me too. Before I provide the full details you asked SiDi for (or maybe you have others you want from me), have the Devs made any progress on SiDi's issue?
I'm running Windows 7 SP1 64 bit and Office 2013,
apparently 64 bit (click-to-run version 15.0.4997.1000), on a Lenovo W530 laptop. Outlook was running fine in its own sandbox under Sandboxie 5.22, before the latest Microsoft Updates.
This morning, having not heard of anyone else having problems with Office 2013 under Sandboxie 5.23.3Beta, I
finally allowed Windows Update to install the latest updates (including the offending KB4056894 and a newer .NET roll-up). Now, when I click on my same old shortcut for Sandboxed Outlook, nothing happens except that the Sandboxie tray icon flashes once. No error messages are thrown. When I open the control window, the designated sandbox is still empty.
Outlook still works just fine outside the sandbox. I also tried directing Sandboxie (from the Control window) to open Outlook (using a desktop icon) directly inside the sandbox I had previously created for it. This shows that sandbox to fill and then empty again. Still no Outlook.
Any update would be greatly appreciated! -- jclarkw
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Mon Jan 22, 2018 3:51 am
by SiDi
New Week, new problems:
On one of our win7 pro sp1 x64 computers (without meltdown patches) and sandboxie version 5.20 last week everything works fine with office and sandboxie.
Today office 2013 updated from 15.0.4981.1001 to 15.0.4997.1000 and office won´t open anymore in a sandbox. On this Computer a office error message appear: Something went wrong. We couldn´t start your program. Please try starting it again.
Without sandboxie office starts normally. I tried to update sandboxie from 5.20 to 5.22 or 5.23.3 but this dos not help.
The only thing that helps is a systemrecovery to the point before the office update was installed. Then office starts normally with sandboxie 5.20 and 5.22. But this is only a workaround and no solution.
Maybe the problem is the office version 15.0.4997.1000. But why Barb, can´t reproduce the problem with this version? On my Computer with version 15.0.4971.1002 office starts in sandboxie.
Re: With Beta 5.23.3 no Office 2013 program will work?
Posted: Mon Jan 22, 2018 7:24 am
by jclarkw
After reading SiDi's post this morning, I checked Office Updates, and mine says the most recent is "January 9, 2018 15.0.4997.1000 KB 4058103". I don't know how to determine when this was actually installed, but it's likely that I never tried this with the earlier-working combination of Sandboxie 5.22 and no KB4056894... -- jclarkw