Hi folks
One of the problems with clean installing Beta insider release is that it now needs an internet connection to set up properly. This then begs the question especially if installing via Dism.exe /Apply-Image that if running from a VM it can't connect to the internet because the network driver isn't available - can be problematic especially if you use wifi connections or special fast USBC->LAN adaptors.
One way round this is to see if you can set in the VM virtual hardware a bog standard NIC that typically comes with windows -- a good one for LAN type things is to use realtech ethernet rtl8139 so you can complete the setup. Then you can add the correct drivers etc from the hardware menu (update driver etc).
For those who still want to use a local account on the build -- at the enter microsoft account enter nobody@nobody.com and pw "Boll--ks". You'll get message "OOPS something went wrong. Just click next and it will carry on setting up a local account as before. Note this is for a Clean install.
I'm using bridged networking to the "Real hardware" on the host but the VM sees a realtech rtl 8139 NIC which works. On some VM platforms you might have to edit the config file manually to set the NIC virtual hardware.

Now ready to update proper drivers using the virtual hardware equivalents such as guest tools additions / vmware tools / intel display adapter etc etc. Which is where those pci devices, and system devices will get fixed. The main thing is to get a bootable system - then "All things are possible" !!!!.
Cheers
jimbo
One of the problems with clean installing Beta insider release is that it now needs an internet connection to set up properly. This then begs the question especially if installing via Dism.exe /Apply-Image that if running from a VM it can't connect to the internet because the network driver isn't available - can be problematic especially if you use wifi connections or special fast USBC->LAN adaptors.
One way round this is to see if you can set in the VM virtual hardware a bog standard NIC that typically comes with windows -- a good one for LAN type things is to use realtech ethernet rtl8139 so you can complete the setup. Then you can add the correct drivers etc from the hardware menu (update driver etc).
For those who still want to use a local account on the build -- at the enter microsoft account enter nobody@nobody.com and pw "Boll--ks". You'll get message "OOPS something went wrong. Just click next and it will carry on setting up a local account as before. Note this is for a Clean install.
I'm using bridged networking to the "Real hardware" on the host but the VM sees a realtech rtl 8139 NIC which works. On some VM platforms you might have to edit the config file manually to set the NIC virtual hardware.

Now ready to update proper drivers using the virtual hardware equivalents such as guest tools additions / vmware tools / intel display adapter etc etc. Which is where those pci devices, and system devices will get fixed. The main thing is to get a bootable system - then "All things are possible" !!!!.
Cheers
jimbo
Last edited:
My Computer
System One
-
- OS
- Windows XP,7,10,11 Linux Arch Linux
- Computer type
- PC/Desktop
- CPU
- 2 X Intel i7