This happens to some machines at the company but not all. and only happens after outlook gets updates every week. Updates go out weekly via a very basic default gpo in the AD administrative template. the only fix i have for each machine is to go to each effected machine and to remove the outlook update(s) that caused the problem. Then i go to refresh and 'hide' those updates. This always remedies each effected machine for a time, until updates come out again. then after a week to a month, it all happens again on the same machines. I'm also thinking since the updates are controlled by gpo, that maybe actual 'hiding' of the culprit updates is being overwritten by the gpo, making my hiding up those updates in vein. 

Here is the image attachement of the outlook issue:
pmUsLU.png

Any advice would be helpful as this is a constant, ongoing, and annoying issue. i've read and searched, for any other instances in which another person may have experienced the same thing and found nothing on this. 
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answer Chosen by the Author

0
KB3097877 released on the 10th was causing this. The patch has been re-released on the 12th with the same patch number. I can see it is available in KACE. 
8f00P7.png
Answered 11/17/2015 by: Hrkljus
Orange Belt

Please log in to comment

Answers

0
FYI - This has happened for us too. It's the M$ patch that's the issue. We just uninstalled the patch for now.
Answered 11/16/2015 by: h2opolo25
Red Belt

Please log in to comment
This content is currently hidden from public view.
Reason: Member has been banned from the site
For more information, visit our FAQ's.

0
Uninstall the kb dated Nov. 10 and install the one from Nov. 12. 
Answered 11/18/2015 by: Hrkljus
Orange Belt

Please log in to comment
-2
Have you tried rebuilding one of these machines? Not ideal, I know, but...

Alternatively, why not make a copy of one of the machines into a VM, take it off the domain, rename it and then add it back (so you can still send it GP stuff, etc.) Snapshot each stage (Paranoid? Me?) then use this "new" machine to test your updates. That way, you can work at your pace without hindering the user in any way. Oh and do I need to say "ProcMon, ProcMon, ProcMon!"?
Answered 11/16/2015 by: VBScab
Red Belt

  • excellent idea man! Thanks!
Please log in to comment
Answer this question or Comment on this question for clarity