new features in Windows 10 prevents Virtual Machines based on VMware Workstation or Virtual Box from starting.
Typical Errors are:
- VirtualBox: VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT or VT-x is not available (VERR_VMX_NO_VMX)
error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
- VMware Workstation: VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard
when the network profile of a Windows PC is set to public, there are firewall restrictions enabled which could prevent accessing the Computer from network. For example Windows Remoting.
Unfortunately in some cases the profile cannot be switch by the Network Gui(s) of windows.
these are the steps to enable Windows Powershell remoting secured by TLS
Check your Network connection profile. Set-WSManQuickConfig expects that the Network profile is at least private or domain.
in these days powershell modules are often installed from a (NuGet) Repository and not by a Setup program.
In companies may exists computers which does not have an active internet connection.
But how to install the modules on these devices?
VMware does not longer provide Setups for installing PowerCli.
If you want to use the latest version of the PowerCli you have to install the modules from a NuGet Repository. This requires at least Version 5 of the powershell.