[prev in list] [next in list] [prev in thread] [next in thread]
List: patchmanagement
Subject: Re: [patchmanagement] Issue with July updates
From: Albrecht Tielsch <albrecht.tielsch () anat ! uni-freiburg ! de>
Date: 2018-07-30 8:01:09
Message-ID: e0c4fbfb-5d79-5bcb-fc15-c3c4e0faaab8 () anat ! uni-freiburg ! de
[Download RAW message or body]
thank you for the translation.
And yes, as I don't have one, I had to ask :-)
Best
Albrecht
Am 26.07.18 um 18:13 schrieb Job Cacka:
> I don't have a Microsoft TAM, but I believe it means Technical Account
> Manager.
>
> Job
>
> -----Original Message-----
> From: Albrecht Tielsch [mailto:albrecht.tielsch@anat.uni-freiburg.de]
> Sent: Thursday, July 26, 2018 7:49 AM
> To: Patch Management Mailing List
> Subject: Re: [patchmanagement] Issue with July updates
>
> sorry for my request, but as I try to avoid abbreviations for some
> reason, and it's weird with this mess of acronyms, at least I can't get
> what TAM might be:
>
> https://acronyms.thefreedictionary.com/TAM
>
> what out of this list would have fit here ?
> And wherefrom all you guys and ladies know what the people are talking
> about using all those acronyms ... ?
>
>
> Thanks in advance and
> Best
> Alrbecht
>
>
> Am 20.07.18 um 19:40 schrieb Cain, Steven:
> > I fixed it for them. "We had an incredible year, surpassing $100
> > billion in revenue as a result of our teams' relentless focus on
> > customer success in the cloud and the trust customers in the cloud are
> > placing in Microsoft," said CEO Satya Nadella”
> >
> > *From:*Heaton, Joseph@Wildlife [mailto:Joseph.Heaton@wildlife.ca.gov]
> > *Sent:* Friday, July 20, 2018 12:13 PM
> > *To:* Patch Management Mailing List
> > *Subject:* RE:[patchmanagement] Issue with July updates
> >
> > Don’t they run the same risk by publishing a “fix”? Anyway, not trying
> > to cause an argument, just venting. Due to the issues lately with
> > updates, I found this more than a little humorous from a Redmond
> > Magazine e-mail I just received:
> >
> > "We had an incredible year, surpassing $100 billion in revenue as a
> > result of our teams' relentless focus on customer success and the trust
> > customers are placing in Microsoft," said CEO Satya Nadella”
> >
> > Wow, over $100 Billion, with a B, and focused on customer success?
> > Obviously, Mr. Nadella hasn’t been involved in patching lately.
> >
> > *From:* Brian McMahon <brian.mcmahon@asml.com>
> > *Sent:* Friday, July 20, 2018 7:32 AM
> > *To:* Patch Management Mailing List
> > <patchmanagement@listserv.patchmanagement.org>
> > *Subject:* RE:[patchmanagement] Issue with July updates
> >
> > Why didn’t Microsoft put out a new, fixed cumulative for each of the OSes?
> >
> > Mainly because they can’t crank out a QA test of the updates so quickly.
> > It’s easy to say ‘just rebuild the cumulative update’, but in practice
> > it is a complex process of testing to prevent following up a disaster
> > with a second disaster. The problem with netio.sys/tcpip.sys was
> > impacting less than 1% of all systems around the world, what they put
> > out was a fix that can be applied and will be rolled into the cumulative
> > update next month.
> >
> > Brian McMahon
> >
> > ASML-US IT
> >
> > *From:* Heaton, Joseph@Wildlife <Joseph.Heaton@wildlife.ca.gov
> > <mailto:Joseph.Heaton@wildlife.ca.gov>>
> > *Sent:* Friday, July 20, 2018 6:42 AM
> > *To:* Patch Management Mailing List
> > <patchmanagement@listserv.patchmanagement.org
> > <mailto:patchmanagement@listserv.patchmanagement.org>>
> > *Subject:* RE:[patchmanagement] Issue with July updates
> >
> > What doesn’t make sense to me is this:
> >
> > Why didn’t Microsoft put out a new, fixed cumulative for each of the OSes?
> >
> > Why leave a broken update out there, that you have to install, in order
> > to be able to install the “fix”?
> >
> > For those of us that hadn’t really started our patching process, this
> > seems crazy. I can’t, in good conscience, go to my boss and tell him
> > that we need to apply patches that are going to break our servers, then
> > apply a “fix” that will make everything all better.
> >
> > Plus, the issue in the CU isn’t the only issue this month. Apparently
> > the new .NET broke some stuff too? That is just AWESOME!
> >
> > *From:* Hanna, Dean <Dean.Hanna@fisglobal.com
> > <mailto:Dean.Hanna@fisglobal.com>>
> > *Sent:* Wednesday, July 18, 2018 5:28 PM
> > *To:* Patch Management Mailing List
> > <patchmanagement@listserv.patchmanagement.org
> > <mailto:patchmanagement@listserv.patchmanagement.org>>
> > *Subject:* RE:[patchmanagement] Issue with July updates
> >
> > The complete list of patches to fix this “Stop error” are…
> >
> > ·KB4345418
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345418&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=YIZ
> TvQwTQGzW%2FrZ0bT8QBafCesuTggjQ65NhtzcmOGM%3D&reserved=0>:
> > 2018-07 Cumulative Update for Windows 10 Version 1607 and Server 2016
> >
> > ·KB4345419
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345419&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=6wm
> D7dTM%2FfDE4RinMEe1flMwt%2F%2FdonOqsAtZNWhcHuw%3D&reserved=0>:
> > 2018-07 Cumulative Update for Windows 10 Version 1703
> >
> > ·KB4345420
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345420&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=nHM
> Bo7BbHADmcmYNyQo35J7q8%2FYmCv2AWgRPtGDs4iM%3D&reserved=0>:
> > 2018-07 Cumulative Update for Windows 10 Version 1709 and Server 2016
> >
> > ·KB4345421
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345421&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=iwJ
> QUNt8VqsO9x%2B%2FcTgtSlhRMxgH8RFOtTQW67wYPxI%3D&reserved=0>:
> > 2018-07 Cumulative Update for Windows 10 Version 1803 and Server 2016
> >
> > ·KB4345424
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345424&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=hsd
> ko42qwcIppy9E0Sgtc55Gf3sMwATq37abxz%2BcxR4%3D&reserved=0>:
> > 2018-07 Update for Windows 8.1 and Server 2012
> >
> > ·KB4345425
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345425&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=dTT
> XtNjFp%2Fxf8ZYW86ZKLIgMao%2FWNjnv4kEEebDnNZA%3D&reserved=0>:
> > 2018-07 Update for Windows Server 2012
> >
> > ·KB4345455
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345455&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=dJr
> WNNlwdnXohYDBF4hrS%2BRlYtz7EezT%2FaG3pSl3H%2Fw%3D&reserved=0>:
> > 2018-07 Cumulative Update for Windows 10 Version 1507
> >
> > ·KB4345459
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345459&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=Gux
> bK6i2wDL0%2FifYrLmQm%2FphLt8TjL1LYaLh1oW4ylc%3D&reserved=0>:
> > 2018-07 Update for Windows 7 and Server 2008
> >
> > ·KB4345397
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fkb%2F4345397&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463
> e8060d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=SUp
> h7Um%2FaYRcOGrzwbJFZNFcyTvgwl%2B%2BEi3tg1KGbMY%3D&reserved=0>: 2018-07
> > Update for Windows Server 2008
> >
> > Thanks.
> >
> > Note: I will be out of the office August 3^rd – August 10^th
> >
> > D. Dean Hanna
> >
> > IT Security Analyst Senior, Patch Management Engineer
> >
> > Managed Risk Services (MRS) / Vulnerability Management Center (VMC)
> >
> > *T:*602.337.3368
> > *C*: 480.340.3673
> > *E*: dean.hanna@fisglobal.com <mailto:dean.hanna@fisglobal.com>
> >
> > *FIS | Empowering the Financial
> > World***cid:image001.png@01D112FA.C4A77D90
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.face
> book.com%2FFIStoday&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463e8060d840
> 24d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=7esjacqMxTMk
> 0ur8V%2BzDK7UnCO21eyu0mpkWzJIqRfg%3D&reserved=0>cid:image002.png@01D112FA.C4
> A77D90
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.
> com%2FFISGlobal&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463e8060d84024d6
> 0408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=C71cahGcw7vwrM8V
> SG8VOA5lIEhr%2FUtcstNxbsU4b48%3D&reserved=0>cid:image003.png@01D112FA.C4A77D
> 90
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.link
> edin.com%2Fcompany%2Ffis&data=01%7C01%7Cbrian.mcmahon%40asml.com%7Cd8463e806
> 0d84024d60408d5ee4c7d3c%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=2NxOXuD
> %2BVqGExnojgqd3CI9hb7NlJN%2BBjCOO8iBXiWM%3D&reserved=0>**
> >
> > 50_3
> >
> > *From:* Brett Pound [mailto:brett.pound@innessco.com]
> > *Sent:* Tuesday, July 17, 2018 4:35 PM
> > *To:* Patch Management Mailing List
> > <patchmanagement@listserv.patchmanagement.org
> > <mailto:patchmanagement@listserv.patchmanagement.org>>
> > *Subject:* RE:[patchmanagement] Issue with July updates
> >
> > And just for completeness in this thread only, there were new updates
> > released ~24 hours ago, that address the 0xD1 stop error.
> >
> > Eg:
> >
> >
> https://support.microsoft.com/en-us/help/4345418/windows-10-update-kb4345418
>
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fen-us%2Fhelp%2F4345418%2Fwindows-10-update-kb4345418&data=02
> %7C01%7Cdean.hanna%40fisglobal.com%7Ccc37087dc3274e2ad63708d5ec43dc08%7Ce3ff
> 91d834c84b15a0b418910a6ac575%7C0%7C0%7C636674698574911823&sdata=4k8iBrxdmZi%
> 2FsuHlD0VtQFnrcqogbMbPTx4AMjmN4jA%3D&reserved=0>
> >
> >
> https://support.microsoft.com/en-us/help/4345424/improvements-and-fixes-wind
> ows-8-1-and-server-2012-r2
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fen-us%2Fhelp%2F4345424%2Fimprovements-and-fixes-windows-8-1-
> and-server-2012-r2&data=02%7C01%7Cdean.hanna%40fisglobal.com%7Ccc37087dc3274
> e2ad63708d5ec43dc08%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C63667469857
> 4911823&sdata=SRgApo4FrSCsyVMm%2BjipeMJwfWvm2cjb5OZ%2BNhMxRAA%3D&reserved=0>
>
> >
> >
> >
> https://support.microsoft.com/en-us/help/4345459/stop-error-0xd1-after-a-rac
> e-condition-occurs-in-windows-7-service-pac
> >
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.
> microsoft.com%2Fen-us%2Fhelp%2F4345459%2Fstop-error-0xd1-after-a-race-condit
> ion-occurs-in-windows-7-service-pac&data=02%7C01%7Cdean.hanna%40fisglobal.co
> m%7Ccc37087dc3274e2ad63708d5ec43dc08%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%
> 7C0%7C636674698574921841&sdata=rjYq%2BlDVcDtmFaHbJk5ubPX1YIfCFKS%2B4%2BYSubz
> UMoo%3D&reserved=0>
> >
> >
> > *From:* Heaton, Joseph@Wildlife <Joseph.Heaton@wildlife.ca.gov
> > <mailto:Joseph.Heaton@wildlife.ca.gov>>
> > *Sent:* Wednesday, 18 July 2018 1:52 AM
> > *To:* Patch Management Mailing List
> > <patchmanagement@listserv.patchmanagement.org
> > <mailto:patchmanagement@listserv.patchmanagement.org>>
> > *Subject:* [patchmanagement] Issue with July updates
> >
> > I just replied to another thread, but it seemed kind of buried, and off
> > topic for that thread. I reached out to my TAM, based on a post here,
> > saying there were issues with this month’s patches. This was the reply:
> >
> > “I reached out to the security team and found out there is a known issue
> > with two KBs - KB4338824 and KB4338815 introduce a race condition that
> > affects applications that sustain high network traffic.
> >
> > Microsoft has stated the Symptom as “After installing this update, some
> > devices running network monitoring workloads may receive the 0xD1 Stop
> > error because of a race condition.”. The solution to this issue is
> > “Currently, there is no workaround for this issue. Microsoft is working
> > on a resolution and estimates a solution will be available mid-July”.”
> >
> > The KBs referenced are the 2012R2 monthly updates, both security only,
> > and the quality rollup.
> >
> > Hope this helps with determining whether or not to patch this month.
> >
> > Joe Heaton
> >
> > Information Technology Operations Branch
> >
> > Data and Technology Division
> >
> > CA Department of Fish and Wildlife
> >
> > 1700 9^th Street, 3^rd Floor
> >
> > Sacramento, CA 95811
> >
> > Desk: 916-323-1284
> >
> > The information contained in this message is proprietary and/or
> > confidential. If you are not the intended recipient, please: (i) delete
> > the message and all copies; (ii) do not disclose, distribute or use the
> > message in any manner; and (iii) notify the sender immediately. In
> > addition, please be aware that any message addressed to our domain is
> > subject to archiving and review by persons other than the intended
> > recipient. Thank you.
> >
> > -- The information contained in this communication and any attachments
> > is confidential and may be privileged, and is for the sole use of the
> > intended recipient(s). Any unauthorized review, use, disclosure or
> > distribution is prohibited. Unless explicitly stated otherwise in the
> > body of this communication or the attachment thereto (if any), the
> > information is provided on an AS-IS basis without any express or implied
> > warranties or liabilities. To the extent you are relying on this
> > information, you are doing so at your own risk. If you are not the
> > intended recipient, please notify the sender immediately by replying to
> > this message and destroy all copies of this message and any attachments.
> > Neither the sender nor the company/group of companies he or she
> > represents shall be liable for the proper and complete transmission of
> > the information contained in this communication, or for any delay in its
> > receipt.
> >
>
--
Albrecht Tielsch
Institut für Anatomie und Zellbiologie
Albert-Ludwigs-Universität Freiburg
Albertstraße 17
79104 Freiburg
Tel.: +49 761 203 5078
---
PatchManagement.org is hosted by Shavlik
The content on the email list is intended for assisting administrators. If you would \
like to use any of this content in a blog or media publication, please contact the \
owners of the list for approval.
To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic