native VHD boot.
The "excellence" of native VHD boot is that for the first I don't have to any partitioning on host system, and that if I notice a new build does not work on my hardware, or if I just don't need the other dual boot OS anymore I simply boot to host main OS and delete the VM. It leaves no traces of of my secondary OS on host machine because the dual boot secondary OS was on a single VHD file.
Windows default boot files handle multi-boot to various linuxes just fine. Many fine how-tos on this, I like this one https://www.iceflatline.com/2009/09/...using-bcdedit/
RE: Insider Announcing Windows 10 Insider Preview Build 14905 for PC and Mobile - Page 15 - Windows 10 Forums
When I'm wrong I have to admit it: seems that I am the culprit, my actions caused my language settings to disappear.
I take the blame but would like to suggest that syncing your settings has a small flaw. I found out that when I allow all settings including language settings being synced, when I then install Windows on a new machine and use the same Microsoft Account, that new machine gets all other settings from existing machines except the language settings, which will be synced the other way around, from new machine to existing ones.
I install Windows 10 several times a week on Hyper-V virtual machines, testing install / customize / sysprep scenarios. I understood this with sync when it happened in front of my eyes just now. Switching a freshly installed Hyper-V vm to Microsoft Account, it found my account picture. synced theme, colours and such in a minute, getting all my settings from existing installations but apparently the languages are synced from the new install to old ones; at the same moment my host machine language settings were reset to those single display and input languages of new vm.
Bad phase in my insomnia, not really slept lately. I have difficulties to understand the above myself, explaining it really bad but I hope it makes some sense...