After updating a Windows 8.1 machine that had Hyper-V running, none of the VMs could access any networking: Windows 10 build 1511 completely broke the vSwitch infrastructure.
This is what I had to do:
- Reinstall network devices using netcfg –d command (Source: Fix network connection issues – Windows Help)
- Reboot host
- Create a new vSwitch in Hyper-V (as the old one was gone)
- Remove the network adapters of the VMs (they were in a limbo state)
- Add new network adapters to the VMs connecting them to the correct vSwitch.
This was the umpteenth time Hyper-V let me down, so in the future I’m back to VMware or Virtual Box.
Windows 10 also broke Everything Search Engine and UBCD4Win.
And Windows 10 moved a lot of things away from the Control Panel, which means that things that basically worked for more than a decade are now gone. For instance, Windows updates now must be run with a shortcut like this:
Note that’s for a DUTCH system. For a US-English system of course the shortcut is different:
This feels like “1998 wants its VBA translated languages back”.
Of course I could get around this by building a table translatingto a text language code from the numeric language code* from the below command, but that’s not the point: Windows 10 makes life harder.
reg query “hklm\system\controlset001\control\nls\language” /v Installlanguage
returns codes like 0407, 0409, 040D, 0413, etc.
*: Heck if Microsoft cannot even update their 2002 Table of Language Culture Names, Codes, and ISO Values Method [C++] and has trouble keeping the various .NET version pages updated**, how could I?
**: these are the only .NET versions the table is documented