Skip to main content

Credential Guard/Device Guard preventing Workstation VMs to power on Windows 10

Like most people we all have VMware workstation on our laptops so that we can test new software or changes before going live. Recently my company enabled Credential Guard/Device Guard and it stopped my VMs from powering on. There is an article from VMware which documents how to turn off Credential Guard/Device Guard which works like a treat. Do follow all the steps especially if you have bit locker enabled on your laptop. If you don't remove Hyper-V correctly then you will get the famous blue screen.

KB article to help disable Credential Guard/Device Guard
https://kb.vmware.com/s/article/2146361

KB article from Microsoft to help if you do encounter a blue screen of death
https://support.microsoft.com/en-ie/help/3189068/restart-failure-if-device-guard-or-credential-guard-isn-t-disabled-cor 

Update : The VMware KB article now refers you to this Microsoft article where it guides you on how to turn on/off Credential Guard manually or via a powershell script which you can download. Please remember if you are running this fix on a workstation that has domain GPO applied then you may need to check with your GPO admins that they are not re-applying the credential guard settings again via GPO. 

Microsoft Credential Guard Article
https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage

Comments

Post a comment

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net