Shulou(Shulou.com)06/02 Report--

When I was working on the project recently, my German colleague said that during the test, I found that the VM prepared for external users was super slow to shut down or restart. If there is a problem, then solve the problem.

First of all, it is suspected that it has something to do with the network, because the machines tested by German colleagues are for external users, and the network uses external user proprietary networks. After a test, it took a few seconds to switch the VM network card to the company's intranet, shut down and restart. So it is initially determined that it is related to the network, but what is the specific reason? I still don't know.

Think about it carefully, if you want to find the root cause of the problem, you need to know where it got stuck when you shut down or restart, so is there any way to let the Windows system display the information of shutting down or restarting the whole process? So Google took a hand, and sure enough.

Open the registry and see if there is a VerboseStatus key under HKEY_LOCAL_MACHINE\ Software\ Microsoft\ Windows\ Currentversion\ Policies\ System. If not, create a VerboseStatus,value of type REG_DWORD and set it to 1, and click OK to save. See the following picture for details.

Now you can try to shut down or restart, and you will see the detailed shutdown process, what to do in the first step, what to do in the second part, which service to turn off in the third step, which process, and so on. When Windows starts, it also displays the detailed process, load xxx service, start xxxx service, load xxxx policy....

Well, at this time you will find out which step the system is stuck in and which step takes a long time.

My case is a display card in group policy,OK, so the problem must be on group policy. At this point, it's time to check the EventLog.

First of all, see if there is any detailed information under this path that you can refer to: Application and services log-> Microsoft-> Windows-> Diagnostics-Performance-> Operational

Second, take a look at: Windows Logs- > Application, there is no detailed information to refer to.

Based on the information on Eventlog, you will eventually find the root of the problem.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.