Unstick a reboot when PsKill doesn’t work

Posted on

A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about Unstick a reboot when PsKill doesn’t work was one problem in server stack that need for a solution. Below are some tips in manage your windows server when you find problem about windows, rdp, , , .

I tried to remote into a server today and got stuck during login. So I tried to reboot with:

shutdown -r -m \computername -t 10 -f

And nothing seemed to happen. So I tried it again and got:

computername: A system showdown is in progress.(1115)

So googling around for ways to unstick it, I came across this which suggested using PSKill. So I downloaded PSTools and tried:

PsKill \computername winlogon

But now that just sticks at:

Starting PsKill service on computername...

Now what? Any suggestions from here?

What state is the machine currently at physically? Can you view the display?
If it has already stopped the user profile service and logged the account off you either need to wait or force the machine to power off. If it has not you can issue a shutdown -a this will abort the shutdown and you can try again, before doing this check the eventlogs for any possible cause of the delay, as a note set the -t option to 0 unless you want to wait 10 seconds for the shutdown to happen of course.

The answer for me was to simply wait 2+ hours for system updates to complete.

I just encountered a similar situation and it turned out to be due to just standing up a new server that had a million patches to download and install.

Initial reboot was requested via start menu->restart and it logged me out but then I was unable to log back in. No error messages from RDP but it would just close the session even when I tried the mstsc /console trick.

I was able to pskill winlogon but it still wouldn’t reboot.

None of the shutdown -r -f or shutdown -a commands would do anything except tell me a shutdown was already in progress.

Then I found the real cause by issuing a VERBOSE tasklist command tasklist /S RemotePcName /V and noticing that TiWorker.exe task was rapidly accumulating total CPU time. This is the TrustedInstaller worker process which indicated that there was some kind of patching going on. TiWorker would count up for a while, then complete whatever it was installing and move on to the next TiWorker process counting up from 00:00 CPU time again.

If I didn’t see actual activity on TiWorker.exe I would’ve assumed the system was just in a completely broken state and I would have needed to find a VM cluster administrator to force a reboot, which would have probably interrupted some patch installers that could lead to issues down the road.

Leave a Reply

Your email address will not be published.