Sidenote: does the need for a ~100Gb+ boot drive still apply? Wondering where that comes from now given the OS is "lighter" and can fit in around 10Gb.
Figured - it's just that the osg wiki tutorial hasn't been updated to reflect that fact and still lists "Boot drive larger than 100 GiB" in the prerequisites for the Target device. EDIT: little note for another bit not quite right - "expand -i Sources\Retail\AMD64\fre\*FM~*.cab -f:*FM.xml Sources\FMFiles\" will try to put the FM files into that folder... which fails as it isn't in Sources, it's in the 10X root according to the tree diagram of how it should appear. Append as appropriate and it'll work. Followed the wiki "tutorial" to the letter and still telling me the files are not present as previously. *SIGH*
Whether they work or not yet I haven't had time to check but this IS what appears to be the final piece of the puzzle for me and .ffu files are at least building out now! Good stuff!
Q: How to change default language? Replace en-us with target xx-xx in 10X\Tools\ReferenceOEMInput.xml?
Successfully made 20279.1002.201214-1532.fe_release_10x.ffu and 20279.1002.201214-1532.fe_release_10x.vhdx with added laptop drivers. Then converted 20279.1002.201214-1532.fe_release_10x.vhdx to Windows_10x.vhd using VBoxManage.exe. Code: Microsoft Windows [Version 10.0.19041.1] (c) 2019 Microsoft Corporation. All rights reserved. C:\Windows\system32>cd "C:\Program Files\Oracle\VirtualBox" C:\Program Files\Oracle\VirtualBox>VBoxManage.exe clonemedium "C:\20279.1002.201214-1532.fe_release_10x.vhdx" "C:\Windows_10x.vhd" --format VHD 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Clone medium created in format 'VHD'. UUID: 68a7cca8-f0d9-4bc9-abad-3633d57d87d8 Then booted Windows_10x.vhd in Oracle VM VirtualBox, booted up just find. STUCK AT: Let's connect you to a network To finish setup you'll need to connect to the internet. Unable to get wifi or ethernet connection working in Oracle VM VirtualBox.
If WiFi is not detected then you need to reboot the device or PC to recognize the WiFi. This is what the instruction given for Lumia 950XL https://forums.mydigitallife.net/threads/discussion-windows-10x.80781/page-8#post-1641871
Something like that: \EFI\grub\menu.lst title Boot /flash.vhd - UEFI Grub4dos SVBus RAMDISK - 3 GB find --set-root --ignore-floppies --ignore-cd /flash.vhd map --mem --top /flash.vhd (hd) chainloader (hd-1)
Another random tip: it may vary depending on drivers you include, but trying to apply the image seems that DISM will stop you with a fail on drives under approx 50Gb - presumably close to 45Gb as the temp image created during the process is around 44Gb. (So still not quite there for those of us hoping to force it onto the 32Gb Windows 10 tablets. Perhaps it could be recaptured somehow...)
Following the instructions for "apply to machine without 10x" seems to leave the physical drive non-booting after applying the .ffu to it...
Given it a few tries now and same result with a VHD. End up with one small partition of fat32 and the rest as "Other". Hm.
This way not work?: "All you need to do to native boot vhdx file is 1. Boot to Windows. 2. Attach vhdx file from disk management. 3. Note the drive letter of windows in attached vhd. 4. Type following bcdboot #:\windows where # is drive letter from step 3."
The problem is the file is clearly not being flashed properly somehow going by the strange partition layout. Whether its being run from a virtual disk physically booted or not won't matter.