Solved Windows Update: Rogue Reboot
-
We push a server policy that forces the updates to download from WSUS but as Automatically Download but, let me chose when to install. If you don't choose when to install manually you'll end up with this stuff. I also have a GP to block non-domain admins from installing on all servers.
-
Just happened to find this from last night.
Windows update Update for Windows (KB3055343) requires a computer restart to complete the installation. (Command line: "C:\Windows\system32\wusa.exe "C:\Program Files (x86)\DesktopCentral_Agent\\patches\101697-Windows8.1-KB3055343-v2-x64.msu" /quiet /norestart") -
This is something that has been running through my brain all day...
And it just so happens that this update was released from MS on July 20.
We ran updates on the server on Sunday. and rebooted it then.
Why was it not installed then????
-
@g.jacobse said:
This is something that has been running through my brain all day...
And it just so happens that this update was released from MS on July 20.
We ran updates on the server on Sunday. and rebooted it then.
Why was it not installed then????
But was it download at that point? and if you have WSUS was it approved at that point.
Also often times you need to install updates three or four times after reboots, some have prerequisites and some can't be installed with others.
-
@thecreativeone91 said:
@g.jacobse said:
This is something that has been running through my brain all day...
And it just so happens that this update was released from MS on July 20.
We ran updates on the server on Sunday. and rebooted it then.
Why was it not installed then????
But was it download at that point? and if you have WSUS was it approved at that point.
Also often times you need to install updates three or four times after reboots, some have prerequisites and some can't be installed with others.
Also, did the update have a dependency that was not there until after the Sunday reboot. Thus causing it to now be a needed update?
-
Seems like this has come around again....
Server is receiving updates when the GPO is set to disable it.
-
Hey @scottalanmiller here is an example of a random reboot!
-
I have users on a nearly monthly occasion complain that they they tell the system to remind in 10 mins or 4 hours, and yet the machine will just randomly reboot while they are working.
-
ive had similar issues
Tried WSUS server through Group Policy. Never got it to work properly. gave it the finger.
Turned windows updates off through GPO policy settings and to not bother user. Machines still at random will reboot without notice due to updates. Or updates will still get installed.
Am I that incompetent?
-
This goes with @art_of_shred thread:
-
@Dashrender said:
I have users on a nearly monthly occasion complain that they they tell the system to remind in 10 mins or 4 hours, and yet the machine will just randomly reboot while they are working.
Are you using any sort of RMM product?
-
@BRRABill said:
@Dashrender said:
I have users on a nearly monthly occasion complain that they they tell the system to remind in 10 mins or 4 hours, and yet the machine will just randomly reboot while they are working.
Are you using any sort of RMM product?
ManageEngine I believe might be on it,.. but updates are pushed manually.
-
@gjacobse said:
ManageEngine I believe might be on it,.. but updates are pushed manually.
I asked because we use N-Able and they used to have an issue where the popup would show up, but it basically did nothing.
Their code rewrote all the update stuff.
-
Is there a reason this reboot is referred to as "red", or was that supposed to be rogue?
-
When you reboot, your users see red?
-
@scottalanmiller
Sometimes it's not just the users that seeredSysAdmins do too... -
@ntoxicator Are you sure the GPO is being applied?
-
Edited rouge to rogue. Makes a bit more sense now.
-
Any further progress on tracking this down?
-
Not entirely.
Both @art_of_shred and I have looked at it. It would appear though that updates were set to trigger.. and not to disable. So while another setting showed as being disabled, it would still trigger.
