Fixed a typo in the command line. This actually almost worked. Tested on a DELL PowerEdge T100 with 4GB and Xeon E3110 which does NOT support SLAT and would not install the role through the GUI. After a couple of reboots, and installing the Hyper-V management tools (above command line only installs the role itself), I was able to create a virtual switch and a virtual machine. Attempting to boot the VM told me the hypervisor is not running. From the system log: Event ID 59 Hypervisor launch failed; Second Level Address Translation is required to launch the hypervisor. Pretty much exactly what I expected. The only thing DISM accomplishes is ability to install the thing that the GUI was smart enough to prevent.
Because it affects just the video performances, especially on HIGH proceed Nvidia cards, something which is marginal on most server applications. The question is why they decided to enforce it on 2016. Just stupid (or too "smart", sepending on the POV)
video performances? But what about Core editions? Wait. What about Hyper-V Core? (I am not good at Core. Or I'll have a test of it.)
Aside experimenting with my idea of installing a GUI directly on it, normally sysadmins are using it to install VM machines inside it. Those are affected by the lack of SLAT support, the server itself is affected as well, but often it even lacks a connected monitor , so no one cares about it.
With SLAT the Hypervisor is much faster. The Microsoft Remote Desktop Team once blogged about a test they did with SLAT and non SLAT Processors in a Terminalserver environment with Hyper-V. With SLAT the number of Terminalsessions possible increased from between 1.6 to 2.5. This is a nice increase.
Thanks. And MSFT aborted it just for the enhancement between 1.6 to 2.5? But what about my old machine? (No worries. I'm just curious.) T-S said that he tried to swap it from Server 2012 to Windows 8, and to no avail.
Whatever it is, should be up to the user/sysadmin to decide. The world is plenty of companies that has just 3/5/10 clients, but MS thinks that any company is a fortune 500 one with 10000 clients and an huge load of money to spend in SW and HW. The performance of HV on a non slat machine are more than acceptable in many scenarios, and the proof is that no HV server OS required the SLAT support until 2016. The mandatory requirement is understandable on client machines, given you actually use the host machine, but even there using the MS basic driver (instead of the proper one) on the host makes it usable, at least to watch some movies on YT.
I think It's just enforced via some product policy (tried the 2012 R2 packages on Win 8.1 and the still requires the slat) Also you can try the packages for WHS 2011 on Win7 on my signature, they install fine but still no Hypevisor running)
I can't disable SLAT alone for my ASUS_X99. When I disabled Virtualization, Server 2012 R2 Hyper-V could not be started.
anyone able to update via windows update when you removed these packages? Microsoft-OneCore-AllowTelemetry-Reduced-Default-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Feedback-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-FlightSettings-Package~31bf3856ad364e35~amd64~~10.0.14393.0 after removing those, tried many things to get windows update to be unstuck at downloading at 0%, nothing works, had to restore back to before i removed those packages and able to update. Please advise if there is a workaround to get windows update working again.
You can't update with Windows Update, the best you can do is download the update cab file and manually install it using the dism command Dism /online /add-package /packagepath:<updatefile.cab>