We'd love to hear about it! Click here to go to the product suggestion community
Windows: 2019-02 update for windows 10 version 1809 for x64-based Systems (KB4465065)
Sandboxie: 5.30 and 5.31.2 (64-bit)
Outlook: Microsoft office 2016 MSO (16.0.11901.20070) 32-bit
Today, I tried to invoke Outlook from Sandboxie control and nothing happens. No message or warning. I am able to invoke the chrome. I even tried Sandboxie 5.31.2 but no difference. I checked the Email reader configuration and indeed shows office outlook relevant apps have been added.
Any hint will be appreciated.
Any AVs installed? Any addons installed in Outlook?Does Outlook work outside Sandboxie? Does the issue follow you to a new Sandbox with default settings (and adding the emai reader option) ? Is office properly activated outside Sandboxie? (If it requires you to sign in/ enter a key, do so outside Sbie, then re-try launching it sandboxed).Do other Office apps present a similar issue? What are the exact repro steps?
In reply to Barb@Sophos:
I have been able to invoke Outlook within the Sandboxie with no issues since I installed the Sandboxie a number of years ago. The following configuration has been intact and I did not add anything else. It was working just fine until a couple of days ago.
1. No AV other than Windows defender.
2. The Outlook Addon is Grammarly. No other Addon.
3. Can invoke Outlook outside of Sandboxie with no problem.
4. The issue follows me to a new Sandbox with default settings (and adding the email reader option).
5. The office properly gets activated outside Sandboxie. No need to sign in or enter code.
6. I am able to open Powerpoint and Word within Sandboxie.
Thank you for your help.
In reply to Maxx Payne:
Please go to Control Panel --> Mail 32 and create a new Outlook profile.Set it as default and set up your email account.Launch Outlook outside Sandboxie to ensure the new profile is picked up/everything is updatedDelete the contents of your Sandbox (or preferably, create a new one) and try launching Outlook again using the new profile
Let me know the results.
Also, please provide the exact Windows version (Click start and type winver , paste the Version and build here)
I followed your instructions but the problem persists. Outlook launches successfully outside SBIE with the new profile. But refuses to come up Sandboxed using a brand new Sandbox with the proper Outlook apps selected (Email Readers).
Here is the complete environment and apps information:
What type of account are you using?
Can you test with a gmail account and let me know if that works (new profile please)?
I only use Outlook with Gmail only. Again, this was working perfectly fine and stopped suddenly. Something is stopping Outlook to be invoked within SBIE and there is NO error, warning or any kind of message.
I am truly sorry for wasting your valuable time on this matter. For some strange reason that I can not explain, the default app setting for the email in Windows 10 was set to null instead of Outlook. If I can recall correctly, the problem started after I updated the windows.
Apparently, if no default email program set in Windows and one attempts to open Email reader within SBIE, the request is ignored and SBIE does not let the user know that no default email app is set.
I think it will be a great enhancement if SBIE can detect this condition and notify the user accordingly.
Everything is running just fine as before.
Thank you so much for all your wonderful support.
I am glad to hear things are working now!
Sandboxie depends on the OS settings for these type of things (for your default browser, default email, etc). Not sure how did you end up with "null", sounds like an OS issue.
If you set the default email to any other app (other than Outlook), you will still be able to manually run Outlook in Sandboxie (but you wont' be able to invoke it by right-clicking --> Run Email Reader - This option invokes whatever the OS is set to) .
Thanks, Barb. I understand the situation and looks like the enhancement that I requested is not doable. I still believe if one initiates action within SBIE, a message indicating why the action can not be completed will be very useful. In my case when everything was working just fine and suddenly stops working. I can only attribute the problem to Windows Update.