Clean installing beta insider release in a VM where wifi or other nic needs drivers


jimbo45

Well-known member
Power User
VIP
Local time
3:39 PM
Posts
2,372
Location
Hafnarfjörður IS
Visit site
OS
Windows XP,7,10,11 Linux Arch Linux
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.


Screenshot_20221002_124459.png


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

cereberus

Well-known member
Pro User
VIP
Local time
3:39 PM
Posts
3,270
Visit site
OS
Windows 10 Pro + others in VHDs
Overcomplicating things.

You only need an internet connection for dev builds during oobe phase but you can bypass this using the oobe\bypassnro method.

In any case, how many people would have access to a vm if they never had internet access in first place.

With Hyper-V, you do not even need to set up anything - just use the default switch.

The only minor issue is vm is then behind a NAT firewall which makes it more difficult to connect via a remote rdp session.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

jimbo45

Well-known member
Power User
VIP
Thread Starter
Local time
3:39 PM
Posts
2,372
Location
Hafnarfjörður IS
Visit site
OS
Windows XP,7,10,11 Linux Arch Linux
Overcomplicating things.

You only need an internet connection for dev builds during oobe phase but you can bypass this using the oobe\bypassnro method.

In any case, how many people would have access to a vm if they never had internet access in first place.

With Hyper-V, you do not even need to set up anything - just use the default switch.

The only minor issue is vm is then behind a NAT firewall which makes it more difficult to connect via a remote rdp session.
Hi there
But if you are using dism.exe /Apply-Image how to you even get to an oobe phase to set that up !!!!!!!.

Using setup.exe makes it do-able but I fail to see how I can use oobe method when all I have is a std blank hdd and going to install the image on it with dism.exe - unless your idea is to modify the wim.install file -- that IMO is vastly more complicated to do, especially if multiple images on the install iso.

The problem isn't the Internet itself but getting access to the "Virtual NIC" drivers in the first place for the setup phase at initial / ist boot when you get all those silly questions. If you simply re-boot at that point it starts again. You don't get access to "Windows" until setup is complete.

On other builds you just click "I don't have Internet" and you could continue setup with what Ms euphemistically calls "Limited" experience" -- I'd suggest a more apt titl;e would be "Enhanced experience". Then when setup is complete you simply install the "Virtual NIC" drivers from your "VM tools" type of iso whether vmware (VMtools) or whatever and it all starts working properly.

Using an ethernet device as Bridged (gives proper connectivity between host and guest)

Screenshot_20221003_131017.png

The Virtual NIC device needs to be of a type Windows has as default and the one I mentioned works but is not very fast --it does the job so the windows OOBE phase can complete. Then at "Real ist boot" - for fast efficiency and maximum traffic through the bridged interface the virtio driver (or whatever your VM system has for maximum network efficiency you can install the proper relevant virtual NIC adapter for your VM and Host combination.

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

cereberus

Well-known member
Pro User
VIP
Local time
3:39 PM
Posts
3,270
Visit site
OS
Windows 10 Pro + others in VHDs
Hi there
But if you are using dism.exe /Apply-Image how to you even get to an oobe phase to set that up !!!!!!!.

Using setup.exe makes it do-able but I fail to see how I can use oobe method when all I have is a std blank hdd and going to install the image on it with dism.exe - unless your idea is to modify the wim.install file -- that IMO is vastly more complicated to do, especially if multiple images on the install iso.

The problem isn't the Internet itself but getting access to the "Virtual NIC" drivers in the first place for the setup phase at initial / ist boot when you get all those silly questions. If you simply re-boot at that point it starts again. You don't get access to "Windows" until setup is complete.

On other builds you just click "I don't have Internet" and you could continue setup with what Ms euphemistically calls "Limited" experience" -- I'd suggest a more apt titl;e would be "Enhanced experience". Then when setup is complete you simply install the "Virtual NIC" drivers from your "VM tools" type of iso whether vmware (VMtools) or whatever and it all starts working properly.

Using an ethernet device as Bridged (gives proper connectivity between host and guest)

View attachment 41363

The Virtual NIC device needs to be of a type Windows has as default and the one I mentioned works but is not very fast --it does the job so the windows OOBE phase can complete. Then at "Real ist boot" - for fast efficiency and maximum traffic through the bridged interface the virtio driver (or whatever your VM system has for maximum network efficiency you can install the proper relevant virtual NIC adapter for your VM and Host combination.

Cheers
jimbo
Huh?

"But if you are using dism.exe /Apply-Image how to you even get to an oobe phase to set that up !!!!!!!."

DISM knows nothing about internet, when you create the installation. The first time you run the vhdx file after dism, it boots onto oobe and the sequence is the same.

I just tested this on Host pc by turning off internet, and used dism to install windows to a blank vhdx, created a boot entry, and first time I accessed vhdx file, it booted to oobe, and I had to run oobe\bypassnro, clicking internet link. Windows was installed perfectly, and I created boot entry

I have not tested it, but I am willing to bet if you set up dism installation using accounts setup via an autounattend xml file, it will just work, bypassing oobe.

At no point was I ever connected to internet.

To do this in Hyper-V is a slightly more complicated, as you also have to create an EFI partition and using a bcdboot command to create a vhdx that will boot in Hyper-V. But it will still boot into oobe unless you have an autounattend xml file.

At no point do you need to connect to internet to install Windows using dism. So your point about having to set up nics correctly is irrelevant. Of course, you still need to be able to share a host NIC somehow to get internet in the vm, but that is no different to any Hyper-V installation.


EDIT - did it in Hyper-V as well with no internet, and added boot files to pre-prepared vhdx file containing EFI partition as well as the C drive.

Booted into vm, and it jumped to oobe, and then used oobe\bypassnro and then it booted into full windows.

Now here is the really neat thing - I had not enabled secure boot or TPM and it runs fine as well.

So using dism bypasses the tpm and secure boot checks!
 
Last edited:

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

jimbo45

Well-known member
Power User
VIP
Thread Starter
Local time
3:39 PM
Posts
2,372
Location
Hafnarfjörður IS
Visit site
OS
Windows XP,7,10,11 Linux Arch Linux
It works -- I was having a problem in getting into a command console to run the oobe command . Lack of knowlege and I didn't even think it was possible. !!!

It's not intuitive at all on how to run commands from within the oobe phase . Seems obvious in retrospect. !!!!! Shift +F10 in OOBE !!!!! then OK.

Anyway we all learn something every day !! Thanks !!

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

Latest Support Threads

Top Bottom