VMware (Workstation or Player) and Device/Credential Guard are not compatible.

If you’ve tried running a VM on VMWare’s Workstation or Player on a Windows PC, you may have run into the following error:

“VMware Workstation (or VMWare Player) and Device/Credential Guard are not compatible. VMware Player can be run after disabling Device/Credential Guard. Please visit http://www.wmware.com/go/turnoff_CG_DG for more details.”

Yeah – that site isn’t too helpful. Visit it if you want. Itwill further direct you to Microsoft’s page: https://support.microsoft.com/en-us/help/3204980/virtualization-applications-do-not-work-together-with-hyper-v-device-g

The problem is, all the additional sites weren’t too helpful either. Some say uninstall the Hyper-V additional features – which might work, but in my case I hadn’t ever installed them – while others say just try opening a command prompt (in Administrator mode) and entering bcdedit /set hypervisorlaunchtype off and the restarting your machine. Which disables Hyper-V from starting any VMs (if you had it installed) but if you don’t have Hyper-V installed it does nothing.

Other sites (such as https://www.tenforums.com/tutorials/68935-enable-disable-credential-guard-windows-10-a.html) suggest a myriad of options such as gpedit.msc settings (which weren’t set on my PC) or regedit settingg (which also weren’t effective.)

But one list of commands was. Note that Microsoft considers this a security override and leaves your computer open to external bad guys to make a change to something or other. Just letting you know in advance. Hopefully if you’re working with VMs you already know enough to not leave your files and settings unsecured, but caveat emptor.

Anyhow – execute the following commands from the command prompt (with Administrator privileges). Note: Below it says to mount the volume as drive X. If you already have a drive X – use another drive letter that isn’t already in use.

mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Then reboot. Upon reboot you will see a text box window asking if you want to disable Device Guard or Credential Guard, and to confirm you do by pressing the F3 or Windows button/key. Confirm you do by pressing the appropriate key, and once Windows boots up, you can run VMWare VMs without the error.

One additional note: VirtualBox does not seem to have this conflict, so if you can run your VM in VirtualBox and don’t want to disable the Device/Credential Guard, this might be a preferred alternative.

Install Windows using UEFI from a USB flash drive

*Update*

Windows 10 now has a new USB install tool which is supposed to work with UEFI. It is the Windows 10 Media Creation Tool.

It can also be accessed from Microsoft’s Windows 10 page.


Original post below:

If you’ve tried installing Windows in the recent past (since Windows 7), you’ve likely gone the install from USB flash drive route. It is faster and more convenient than DVD, and sometimes necessary as many smaller laptops and hybrid tablets don’t have optical drives. Likely you’ve used the very simple (if now somewhat anachronistically named) Windows 7 USB/DVD Download tool (found HERE). This tool – which works for Windows 8, Windows 10, as well as Server 2008 or Server 2012 and later – creates a bootable USB flash drive and copies the install files from the Windows boot ISO.

All is good if you’re using a legacy BIOS or hybrid BIOS/UEFI. The challenge is when you use a UEFI only. The USB flash drive created by this tool likely will not be recognized as a bootable device by the UEFI boot process. Yay for new and improved technology.

I recommend using the Rufus program with the excellent steps provided by Windows Eight Forums here.

Warning: The first time I did this I followed the instructions and set the file type to FAT32, which is basically required for UEFI to load the drivers needed to boot and install Windows. However, upon selecting the ISO I wanted to use, it changed the file type back to NTFS. I didn’t notice this. I made the drive, went to boot, and nothing. Still didn’t recognize the USB flash drive as a bootable device. When I put the USB stick back into my laptop, I noticed it was NTFS formatted. Odd – I know I selected FAT32 as per the instructions. When going through the creation process again, I saw it make the change.

So make sure after you select the ISO to use for the USB install drive creation that you re-select FAT32 as the format option.

 

 

Mouse button / touchpad button response has delay after typing (Windows 8+/Windows 10)

Many people using laptops with touchpads for gaming (even just Facebook) complain about not being able to press keys and move their “player/character” with the touchpad simultaneously.

This is not the same problem.

The problem about being able to (for example) press the “W” key to move forward, while changing direction using the touchpad is typically a driver issue, where the touchpad is disabled automatically when they keyboard is used. The intent is to prevent inadvertent movement of the cursor by the typist if his/her hand accidentally brushes the touchpad while typing. This problem is (relatively) easily fixed by unchecking the “disable touchpad while typing” setting in your touchpad’s settings.

Recently my son noticed on Minecraft that there was a new problem. When he would be using the keypad to move, or even for a half-second after he quit using the keys, the mouse buttons would be non-responsive. This has significant detrimental effect in any player-vs-player (PvP) or first person shooter (FPS) game. (OK – any serious gamer isn’t using a touchpad, but this is Minecraft.)

The answer wasn’t anywhere in the touchpad driver settings. It is a Windows 8 / WIndows 8.1 “fix” for us. (Thankssssss for that.)

The solution is

  1. Go to “Settings” (move your mouse to the upper right corner, then click on the Settings charm),
  2. At the bottom of the screen section for Settings, click on “Change PC Settings.”
  3. Now click on “PC and devices” (should be near the top left in the PC Settings window.
  4. Click on “Mouse and touchpad” (about halfway down the left side settings in the PC and devices window.
  5. On the right, typically the last selection is labeled “Touchpad.” Under there is a sentence that reads ” To help prevent the cursor from accidentally moving while you type, change the delay before clicks work.”  Yeah. Because I’m always banging my keys so hard that I mash the mouse buttons too. Anyhow, change the box below it to “No delay (always on)” to fix this…fix that Microsoft blessed us with.

MouseClickDelay-1024x558