#Local session manager windows 8
Before making changes to the registry, you should back up any valued data on the computer.Ī quick scout around the internet for this error found this article, Scoped Snapshots vmicvss Error 13 on Server 2012, Windows 8 Incorrect solution #1 Incorrectly editing the registry may severely damage your system. PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\ To resolve this, disable scoped snapshots by creating the following registry value on this computer: Windows cannot perform an online backup of this system because scoped snapshots are enabled. I finally looked into the event log and found that I was getting the following error every 45 seconds.
I have left the details here as it may help describe other problems. Everything below was my original investigation and attempt at resolving the problem, and it seemed to fix things but ultimately it was not the solution. Goes to show you can’t trust everything you read on the internet. Since doing this my logins via mstsc / rdp are normal again. Click next through the wizard and confirm removal.In the wizard find Remote access and deselect it.On the Manage menu, click Remove Roles and Features.To fix the problem uninstall remote access by: Somehow I had installed Remote Access? Don’t remember doing it, but there you have it in plain sight, so I must have installed it by accident. The item to note is the “Remote Access” configuration. On the server manager I notice the following: I would appreciate if anyone else can confirm this works for them. Now, my computer shuts down (to lost ping) in less than 10 seconds and I have not had a slow login since. I decided I could try living without this service, so I found the “Windows Remote Management” service disabled it and stopped it. This service is detailed here, Windows Remote Management (Windows) – MSDN If you did not intentionally stop the service, use the following command to see the WinRM configuration: The WinRM service is not listening for WS-Management requests. I noted that during the shut down there was a heap of “service x has shut down” messages, but then there was a 6 minute gap followed by a Warning message from the “Windows Remote Management” service, WinRM. It would take about 8 minutes before the packets were being dropped.Īfter one of these reboots, I opened event viewer and looked at the “System” logs. I tested this a few times, by pinging the server during a reboot and (ping -t), and waiting for lost packets. I applied some patches and needed to reboot the guest and had to wait 10 minutes. The issue of slow logins was also compounded recently with really slow shutdowns. I have changed nothing on the hyper-v host. I have left the sum total of the trouble shooting that I have done, in the previous solutions further down, but this latest solution seems to be the one. Ok, this problem has been driving me crazy, and each time I apply a “fix” I find a week later that I am back to having problems. I have now also noticed it is taking approx 10 minutes to shut down when performing a reboot. It got to the point where it was taking 4 or 5 attempts to login and costing about 15 minutes every morning.
A HyperV Virtual Machine that I had been using for over 1 year suddenly started slowing down when logging in via remote desktop.
0 kommentar(er)
