pasobadviser.blogg.se

1. HOW TO UNINSTALL OUTLOOK ONLY FROM OFFICE 2010 HOW TO
2. HOW TO UNINSTALL OUTLOOK ONLY FROM OFFICE 2010 UPDATE

HOW TO UNINSTALL OUTLOOK ONLY FROM OFFICE 2010 HOW TO

For those asking about how to apply this, if you really wanted to you could copy and paste the below, (please ensure there are two line breaks at the end of it, I couldn't get this to appear in the code block) into a.

HOW TO UNINSTALL OUTLOOK ONLY FROM OFFICE 2010 UPDATE

The main reason I went down this route is that I had 50+ calls before 0900 all relating to the same issues across a wide variety of sites, some of which don't use WSUS and I figured a quick registry fix that would apply to users as they logged in was easier than the batch removal of an update after the fact. I'd probably suggest these keys be removed after Microsoft re-release the update. Please be aware that by putting these keys in, you are literally disabling the ability to use Safe Mode which can (rarely) be handy for diagnosing Outlook issues. That's likely why Microsoft have pulled it. Just to clarify, the update is definitely broken, it shouldn't be falling back to safe mode if it can't detect those keys. Gpupdate or reboot and close and re-open Outlook and it no longer opens in Safe Mode.Ī bunch faster (for me) than removing the update. SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Outlook\Security SOFTWARE\Microsoft\Office\14.0\Outlook\Security I've just tested a group policy across 3 different sites that creates the following registry keys.

They haven't taken into account the Wow6432Node key for 64bit machines running 32bit Office. Microsoft only mention HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook\Security\ in their article about the new behavior.