Another day, another bad patch from Microshaft!

I got bit by this, fortunately only by one client running Outlook 2010. They are MSP, just ate up their distributed monthly hours allowance. So I didn't make any money (they rarely call as it is). Surprised I didn't get more issues from this to be honest.
 
None of my MSP clients got hit by this, because I haven't patched anyone yet. I always wait a few days to roll out patches, unless there is word of a major exploit in the wild just for this reason. Don't need all my clients down because I auto update. What is the point of MANAGING patches if you just approve everything willy nilly?
 
Stupid question? How in MaxFocus can you tell which version of the patch they have? The Microshit KB article makes no mention of changes to the patch that I can tell. Only in the media and reddit have I seen reports of a NEW version of the patch. I still have it blocked until I can get conformation. I have opened a ticket with MaxFocus about it but you know how that can go....
 
Reply from Max Tech Support. They have not yet pushed the new version of the patch out. If you are using Max to push the patch you are still issuing the old one.
 
TAPtech said:
Me too.. is there some sort of "Bad MS Patch" RSS feed I can join?
Click to expand...

Heh...yeah. I'd put that on the morning check list right next to our clients daily backup logs. So you've read it by 0700.
Been about 2 hours or a little more since I forced out the fixed update to clients via N-Able. Clients calls have slowed down..at least none of our managed clients have called in the past two hours.
 
Had a few of these today as well. My managed clients are all good as I usaully hold back patches on them for a few days, however, that same manged client has a few "Roaming" Laptops for users that are off-site most often and are not WSUS'ing or Folder Redirecting and have "Regular Automatic Updates" going for them... bombed out every one of those Outlook installs. Easy fix, thank goodness.
 
nlinecomputers said:
Reply from Max Tech Support. They have not yet pushed the new version of the patch out. If you are using Max to push the patch you are still issuing the old one.
Click to expand...

I just filtered by date and selected "ignore" for all workstations and clients. I must have done something goofy in the past on this workstation, as this client is set to install patches tonight and should not have installed it... but this particular workstation had the site policy overridden and all days were checked! Whoops! So now I'm refilling their hours as it wouldn't have happened otherwise :confused:

Then, on stations that have the patch, you can run something like:

@echo off
wusa /uninstall /kb:3097877 /quiet /norestart
END
 
Thanks for posting this. Got slammed this morning with several different people from several different companies all complaining about outlook and this post saved us a lot of time. Just had to remove the update each time and it worked.
 
From MaxFocus Support:

New Comment: [Benjamin Owen] 11/12/2015 09:09:11 PM GMT



Nathan,

We were able to confirm the removal of the bad "first version" of the patch KB3097877 and the LanGuard Development Team ( Patch Management creators ) have started work on the second version and this is likely to be 3-4 days from now per our normal timeframe for testing and release patches.

Thanks,
Benjamin Owen
Senior Technical Support Specialist
 
TAPtech said:
Did he really need to mention "testing and release" in that response? Just seems like he's leaving the door open for an insult! o_O
Click to expand...
He is referring to GFI's LanGuard not Microsoft. It isn't setup to handle a patch released under the same KB#. They are going to have to figure out a way to remove the old one from the system, detect if the old is installed and force an update down the pike anyway. Plus many have flagged the pack on ignore and they want to make sure that it gets offered again. They probably are going to have in internally mark the patch KB3097877.1 or something in order to be able to distinguish between the two.
 
Another one of the patches this last week caused some havoc with all in one touch screen computers. I have heard it did this for a lot of
touch screen computers as well as touch drawing pads. After the update when you rebooted the computer it would hang at the blue
loading screen and just flash over and over again. I had one call for it and I did a restore point back a couple days and it worked. another
computer had the same exact thing but would not work with a restore point. I did some research and found that I could do a manual
removal of this particular update which was easy enough for me just had to get the command right.

you had to go into repair mode if possible go to the option for a command line and type this in
X being the drive letter... also you might get an error after this I had to go to the boot drive which was D: for this system and do the
command d:\>md temp (make directory) since there was no temp directory it would give an error that there was no room in the temp
directory
X:
dism /image:X:\ /remove-package /packagename:package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1 /scratchdir:X:\temp

I am surprised that it gives a smiley face for this but it should say packagename with a : and a P

I found the information for this here https://www.reddit.com/r/techsupport/comments/3seu7e/flashing_login_screen_windows_7/
 
You must log in or register to reply here.

Similar threads

callthatgirl
GoDaddy Microsoft 365 Pros and Cons
Replies
9
Views
8K
Your PCMD
Your PCMD
J
Outlook continually sends emails from one address to Junk Email
Replies
4
Views
1K
callthatgirl
callthatgirl
Galdorf
New windows 10 update prevents some machines from booting
2
Replies
34
Views
6K
Galdorf
Galdorf
TechLady
Another bad Windows 7 update (KB3022345)
Replies
5
Views
4K
TechLady
TechLady
4ycr
outlook 2013 crashing
Replies
13
Views
3K
allanc
A
Back
Top