Thursday, June 28, 2007 7:02 PM
bradley
A computer that is running ...stops responding...
http://support.microsoft.com/default.aspx?scid=kb;en-us;938204
A possible cause for the no rebooting after patches? We've been tracking an issue where we'll tell a machine to reboot via the WU/MU (reboot now) button and it will start to reboot and just hang.. so the RDP session has dropped but it hasn't finished rebooting. Annoying. One possible cause that someone thought was screensaver related.. and I spotted this on the KB site.... and it too points to an interaction with screensavers and what not...
Keep you posted....
A computer that is running Windows XP or Windows Server 2003 stops
responding when the system tries to trigger a restart after an
automatic update
View products that this article applies to. <#appliesto>
Article ID : 938204
Last Review : June 26, 2007
Revision : 1.0
SYMPTOMS
Consider the following scenario:
• You have a computer that is running Microsoft Windows XP or Microsoft Windows Server 2003.
• The computer is a member of a domain.
• You enable the *Interactive logon: Do Not require CTRL+ALT+DEL* policy on the computer.
• An automatic update is performed on the system.
• A screen saver is running during the automatic update.
When the system tries to trigger a restart after the automatic update, the computer stops responding (hangs). Additionally, to restart the computer, you must exit the screen saver program. To do this, you must either move the mouse or press a key on the keyboard. ........ (more in the KB)
(duplicate post due to server hardware issue...stay tuned for blog post at Yoda's blog for details)
Filed under: News
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")