thanks for your answers!

my understanding is that dism will just inject the patch but it is not 
installed.
anybody knows how this happens?

Von: [email protected] [mailto:[email protected]] Im 
Auftrag von Roland Janus
Gesendet: Sonntag, 13. September 2015 00:43
An: [email protected]
Betreff: RE: [mssms] OT: FYI - MS15-067 Windows 7 x64 Requires Two Reboots

I simply created a package with just those updates and use “dism /online …” 
before the software updates step.
They are for sure also in build & capture.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Freitag, 11. September 2015 15:19
To: [email protected]
Subject: RE: [mssms] OT: FYI - MS15-067 Windows 7 x64 Requires Two Reboots

Saw the same reports on Reddit a few weeks ago. You may want to go ahead and 
report a bug or open a case so Microsoft can take a look.

Daniel Ratliff

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kehl Reto
Sent: Friday, September 11, 2015 8:39 AM
To: '[email protected]'
Subject: AW: [mssms] OT: FYI - MS15-067 Windows 7 x64 Requires Two Reboots

another one:
https://support.microsoft.com/en-us/kb/3075222


as per https://support.microsoft.com/en-us/kb/2894518 (Task sequence fails in 
Configuration Manager if software updates require multiple restarts):

Note You can avoid this issue in System Center 2012 Configuration Manager 
Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1 
by using the new Retry option in the Install Updates task sequence step


I have “Number of times to retry”=3 but my Task Sequence still fails! (SCCM 
2012 R2 with SP1)


Von: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] Im Auftrag von sms sccm
Gesendet: Samstag, 18. Juli 2015 11:55
An: [email protected]<mailto:[email protected]>
Betreff: Re: [mssms] OT: FYI - MS15-067 Windows 7 x64 Requires Two Reboots

definitely:
https://support.microsoft.com/en-us/kb/3069762

Known issues with this security update

  *   After you install or uninstall this security update, you may have to 
restart the computer two times.

From: Rickym61<mailto:[email protected]>
Sent: Thursday, July 16, 2015 1:44 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] OT: FYI - MS15-067 Windows 7 x64 Requires Two Reboots

its definitely KB3069762 that has double reboots, I figured out why it didn't 
apply to us, need to have 2 updates installed, we mainly install only security 
updates unless we need to fix something, so it will only be offered if these 2 
updates are installed. https://support.microsoft.com/en-us/kb/2574819 & 
https://support.microsoft.com/en-us/kb/2592687

On 15 July 2015 at 15:27, Mike Dougherty 
<[email protected]<mailto:[email protected]>> wrote:
It looks like it was 3069762 that was applying in my environment on the 
machines I just spot checked that caused the double-reboot behavior.

I haven't dug into why machines would be getting one version of this update of 
this instead of the other.

On Wed, Jul 15, 2015 at 2:19 AM, Rickym61 
<[email protected]<mailto:[email protected]>> wrote:
Which update did you find had this behaviour?

https://support.microsoft.com/en-us/kb/3067904 or 
https://support.microsoft.com/en-us/kb/3069762
I just did our scheduled image update and added MS15-030 - KB3035017 in to the 
reference wim via dism, now its replaced :( although the replacment KB3067904 
didnt require 2 reboots, tested the update manually on both W7 x86\x64 and no 
double reboot, KB3069762 didnt apply for us.
Still on SCCM 2007 here.

On 14 July 2015 at 22:45, Mike Dougherty 
<[email protected]<mailto:[email protected]>> wrote:
Probably other OSes as well.

We only have Win7 x64 at the moment.

https://support.microsoft.com/en-us/kb/2894518 has not been updated at the time 
of this writing.










The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.



Reply via email to