Re: [NTSysADM] Random reboots Win7 and 10

Wed, 31 Jan 2018 12:49:36 -0800

https://support.office.com/en-us/article/Fixes-or-workarounds-for-recent-issues-in-Outlook-for-Windows-ecf61305-f84f-4e13-bb73-95a214ac1230?ui=en-US&rs=en-US&ad=US


ISSUE

After installing the January Update for MSI versions of Outlook, attachments are removed when forwarding emails in plain text.

STATUS: FIXED

To fix this issue, please download update 4011123 from the download center.

Information for this issue is also provided in Attachments are removed when forwarding plain text emails.

On 1/31/2018 12:30 PM, Sean Chapman wrote:

Ok so I use solarwinds patch manager and we recently found that KB4011626 causing problems with Outlook 2016 not including attachments when forwarding.  I THINK the reboots are because I set the approval for that patch to uninstall.  Why its rebooting every day now and only on some machines I don’t know.

 

From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley
Sent: Wednesday, January 31, 2018 1:36 PM
To: [email protected]
Subject: Re: [NTSysADM] Random reboots Win7 and 10

 

On workstations the registry keys to enable the patch are on by default.  That patch is just a exe of the registry keys to undo the patch.  Also that patch doesn't kick a reboot.

The reboot behavior of the buggy microcode is just that... the systems spontaneously reboot.  His screen is more like a script in the background.

 

On 1/31/2018 10:57 AM, Matt Hebbel wrote:

Right, I should have extended my thinking a bit. The way I read those release notes from MS was that a different, older, version of microcode from one of the chip manufacturers was causing unexpected reboots and other unstable behavior, which prompted the release from MS based on their internal testing. I wasn’t sure if the microcode that was related had been deployed within their org, possibly causing the random reboot behavior he was seeing that this OOB patch was supposed to improve. In the end I felt it was worth a read, though with that said did I misunderstand/misread the point of that article/patch?

 

Matt

_____________________________
From: Susan Bradley <[email protected]>
Sent: Wednesday, January 31, 2018 12:40 PM
Subject: Re: [NTSysADM] Random reboots Win7 and 10
To: <[email protected]>



Doesn't kick a reboot, has to be downloaded from the catalog.

That "reads" like a script somewhere.

 

On 1/31/2018 10:20 AM, Matt Hebbel wrote:

Not sure where you are within your org on Spectre patching, but you may want to read the details below about a very recent out of band patch from the last couple days:

 

 

Matt

From:[email protected] <[email protected]> on behalf of Sean Chapman <[email protected]>
Sent: Wednesday, January 31, 2018 11:45:49 AM
To: [email protected]
Subject: [NTSysADM] Random reboots Win7 and 10

 

Hey all,

 

Been going crazy today trying to find out why a lot of our PCs are rebooting on people with a 2 minute warning.  It seems like it should be easy to track down but I cant find anything solid on whats causing it.  This has happened for some users 2 days in a row now.  Event viewer shows the following:

 

The process wininit.exe (*PC_NAME*) has initiated the restart of computer *PC-NAME* on behalf of user *DOMAIN ADMIN ACCOUNT* for the following reason: Other (Planned)

Reason Code: 0x80000000

Shutdown Type: restart

Comment: On behalf of user *DOMAIN ADMIN ACCOUNT*, a shutdown/reboot request was made for the following reason: Other (Planned)

 

 

The users are prompted with the following message

 

 

 

 

 

 







~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The information contained in this communication and all accompanying documents from Coilcraft may be confidential and/or legally privileged, and is intended only for the use of the recipient(s) named above. If you are not the intended recipient you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and destroy the original message or accompanying materials and any copy thereof. If you have any questions concerning this message, please contact the sender.



 


Reply via email to