SO, you did NOT choose to 'restart', you chose to 'install updates and
If my mate Jan sees this he will smile. A clean restart, and inspection of
logs/services, is required before performing further work.
SO, let's get out of this hole. Though MS give dire warning about doing
nothing until the updates have completed installation _most_ times it will
not break things. The most important files are those in use by the OS and if
the update process does not complete the instruction to the OS to replace
these files during startup is not _normally_ completed.
Before you do the reset button please sit in front of the server and use
alt-tab to switch between windows, there _may_ be a hidden dialogue box
waiting for input.
It's blatantly obvious but yes, if you cannot in some way complete the
update process a forced restart is your only option. Something that may be
worth considering is to restart in DSRM (Directory Services Restore Mode),
pls do NOT try 'safe mode', to see whether the server comes up, then restart
again in normal mode and it is _possible_ that things will repair
You are treading the edge. Forced restart _may_ (but in my experience is
unlikely) cause further problems. How's your backup status? and if you are
unsure of that is it possible for you to perform a backup NOW? Though such a
backup may also contain 'version conflicts' due to lack of completion of the
update process I expect the system restored from such would be usable.
"BadBoy House" <mrchrishouse@newsgroup> wrote in message
> Out of hours last night I chose to install the latest Windows updates
> (from Tuesday 8th September) on our SBS 2008 server.
> The server hadn't been rebooted for a month so I chose to shut down
> and restart. This in turn began installing the updates.
> For 12 hours now it's been on the shutdown type screen that says
> "Installing update 1 of 3..Please do not power off".
> It doesn't look like it's frozen - the activity circle thing is
> spinning round. Obviously the update has got stuck somehow.
> The server itself is functioning fine - users are all connected (it's
> the DC and also has Exchange).
> I don't see any alternative other than to do a power off (again out of
> hours). What I'm concerned about is the message telling me not to
> power off.
> Is it likely to cause any problems by killing the power and rebooting?