Windows home server 2011 hangs on shutdown

->>>> Click Here to Download <<<<<<<-

Privacy Policy Advertise Contact. All rights reserved. Stuck on windows home server setup. Page 1 of 1 [ 6 posts ] Previous topic Next topic Author Message chamkilla Post subject: Stuck on windows home server setup. Posted: Fri May 08, pm. Post subject: Re: Stuck on windows home server setup.

I've never dealt with this but recall seeing some posts on this issue. You might search around. My limited recollection was the solution had to do with either letting it be overnight and it'll come around or starting the recovery process with the network cable unplugged or unplugging it when it gets stuck and then at some point plugging the network cable back in.

Or, something about during servery recovery to decline update for now and then install them later once all set up and running. A have a few more services running, but it had this issue prior to the installation of those services. The common components between now and then are the hardware and the VM's.

I shutdown the VM's before rebooting and two of them hung because they were locked. I logged out the users, shutdown the machines, and rebooted. It took less than 5 minutes. I'll be configuring a GPO to log out users after x amount of idle time, locked or otherwise.

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.

Any direction to solve this issue would be appreciated. Windows Server R2 Best Answer. Verify your account to enable IT peers to see that you are a professional. Windows Server expert. If you disconnect the VM from the switch it will shutdown just fine. Reattach it to the switch and it will get stuck on stopping again. I've tried recreating the switch, but that doesn't seem to make a difference.

Even if you recreate it with a different name the problem persists. Same here. The only way I seemed to find a partial fix is by doing an export of the machine to a different server, then do a "live migration" back to its original server and that seemed to work in some case. I am also wondering it the issue is not related to the new Windows Backup feature that can backup virtual machines separately.

Can you people out there try to delete your virtual network adapters in the VMs and replace them with the "legacy network adapters"? Please report your findings here. Actually, yes, I have another idea I have been working with Microsoft on this issue.

Recreate a new virtual switch with a regular network adapter and uncheck option "Allow management operating system to share this network adapter".

It seemed to fix the issue completely even if this is only a workaround. However, be aware when unchecking the option: your "virtual network card" will disappear from Windows If you had a fixed IP address for this card it will still remain in use through the registry a bit complicated to manage but it works. I had the same issue, so I followed the lead from the above post and added a new network adapter to the system for administration and isolated the VM's. Machines now have no issue shutting down.

This issue only arose after setting up remote access with VPN. I suspect that is the combination which caused the issue. I suspect that disabling remote access may have solved the problem, but did not go down that road. Does anyone know if this has been resolved since this last post. I do not like having to disable the virtual Ethernet adapter everytime I need to reboot a machine.

Also, it seems to be the same for creating checkpoints too. I am seriously considering another network card, purely for Hyper-V if this does indeed fix the problem.

Still not fixed as of last week. I am seeing the same problem. I re-created the Virtual switch and it appeared to be happy for a while, but it has gone bad again.

Not happy! Other Hyper-V server has no problem with same config. Looks like a software issue of some sort. I reinstalled Windows Server fresh same pc, and this time I loaded remote access last, and only choose to install VPN and not remote access, and still same issue.

I'm also convinced its a nic driver issue. I updated to latest on Broadcom site.. Uninstalling the Remote Access role from the host allowed the VM to completely stop. This is clearly a bug. Did you ever apply the hotfix with any luck? Also do you mind if I ask what type of blade? I applied fix a while ago and it does not work for me. Removing the remote access role is the only fix I have found so far.

I have tried different drivers, teaming, no-teaming, different load-balancing algorithms, etc etc. The Only time the machine shuts down is when Management is disabled, but this only works for a short time then I have to hard reset the host. Removed RAS from this host and the issue went away. So looks like conflict with Remote Access Services.

If this post helps to resolve your issue, please click the "Propose as Answer" If you find it helpful , mark it as helpful by clicking on "Vote as Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster. If you need an expert migration consultant to assist your organization feel free to contact me directly.

Hi folks, does anybody have opened a case with Microsoft?! My servers have the same issue. This must be fixed!!! My case is the same: I have Remote Access Services and I must, but when I stoped it the service "Routing and Remote Access" , the virtual machines spent just a few seconds to shutdown or reboot.

There is a workaround if you have more than one NIC in the machine. NIC 2 will only be used for Hyper V. I have a Windows Server guest running on a Server Hyper-V host and it has been slow to login and slow to shut down. I found that there was about a 6 minute delay between system events in the log, and when it did respond it was with a warning from the " WinRM " service, the Windows remote management service.

You did not specified if you has disabled "WinRM" service in the host or in the guest. Or in both. Remember that if you disable the "WinRm" service, you will not be able to manage the system remotely by, for example, any console inside the "Server Manager". But i t may not even be an issue no having WinRM.

I wrote a blog post on the issue I have been trying to resolve, where I was a little more descriptive. As for the management of this server, it is actually a development box, so does not need the same level of remote management as a production box, so from my perspective I have not had any issues with having the WinRM service turned off.

I have the same problem, WinRM service turned off - not solve the problem. As soon as RRAS is removed it behaves normally again. How infuriating!! Just to be clear. Did you change the system failure settings on the host server or the guest VMs? I have some Linux guest clients that exhibit exactly the same behavior. When one of my VMs gets stuck at stopping, they all will. So I may be able to shut down VMs 4 or 5 times perfectly.

Then one will get stuck and once it does, all VMs on that server will get stuck when I shut them down or restart them. In my environment, only Windows Server has this issue of being hung on shutdown. Not Linux, not Windows Server R2 and below, they all shutdown and reboot perfectly. I tried the suggested fix, and that worked strangely.

I had this issue lately on my Server. Restart was not an option!!! Now for the odd part. Recently I created a new test host and a test vm1 DC.