Method 1: Run System File Checker (SFC) and Check Disk (CHKDSK)ġ.Press Windows Key + X then click on Command Prompt(Admin).Ģ.Now type the following in the cmd and hit enter: Sfc /scannow Make sure to create a restore point just in case something goes wrong. But thankfully, there are quite a few methods by which this issue can be fixed in no time, so without wasting any time, let’s see how to Fix Windows 10 slow shutdown issue. Well, I get it, it’s quite annoying to wait 15 minutes to shutdown your PC and frankly, this will frustrate anyone. The main cause of this error seems to be corrupted Windows Files or Drivers which won’t let Windows shutdown completely.įew users are so annoyed that they are manually turning off their PC which isn’t recommended as it can damage your PC hardware. Well, if it takes just a few seconds then it’s normal but users are facing this issue where it takes 10-15 minutes to a complete shutdown. Even though the screen is turned off instantaneously but their hardware continues to run as the LED on power button remain on for few more minutes before turning off. Windows Security -> Device Security -> Core Isolation detailsĭon't forget to reboot the host after making any of these changes.7 Ways To Fix Windows 10 Slow Shutdown: Users are reporting a new issue with Windows 10 where it takes a long time to shut down completely. Note that you also might have to disable Memory Integrity. Workstation 16 Pro Error "Virtualized Intel VT-x/EPT is not supported on this platform.If you want to go back to Hyper-V mode again, then you can enable it like this: bcdedit /set hypervisorlaunchtype auto Reboot the system to activate your changes. In order to turn off ULM/Hyper-V mode, run the following command at the host in windows command-line with Administrator privileges: bcdedit /set hypervisorlaunchtype off Monitor mode CPL0 (Current Privilege Level 0) is required for VMware Workstation to be able to use their own hypervisor. Only when Monitor mode returns CPL0 it is running in ring 0, a.k.a. There's been other reports with snapshots being slow when running as ULM. Which means that you are running in User Level Mode and thus Workstation cannot use VMware's hypervisor, but instead it has to go through the Hypervisor API that Microsoft provides. From the log: T20:41:12.455Z In(05) vmx Monitor Mode: ULM
0 kommentar(er)
