Why does Windows 11 setup not detect network in Proxmox?

The default Windows 11 installer often does not include the VirtIO network driver, so the VM reaches the Connect to a network screen with no adapter available.

Does oobe bypassnro skip network permanently?

No. It only allows you to continue setup without internet. You can install VirtIO tools after desktop login and networking will work normally.

Which VirtIO driver path is usually used for Windows 11 x64?

For manual NIC driver loading, NetKVM\\w11\\amd64 from the VirtIO ISO is the common path.

Fix Windows 11 Proxmox VirtIO network driver issue during setup

Summary: How to finish Windows 11 setup in Proxmox when no network adapter is detected, then install VirtIO guest drivers correctly.

Problem

You create a Windows 11 VM in Proxmox and boot the installer, but at Connect to a network no adapter appears.

Even after trying multiple VirtIO ISO releases (for example 0.1.248, 0.1.271, 0.1.285) and manually browsing to NetKVM\w11\amd64, setup still can block progress.

Why this happens

In many Proxmox deployments, the VM uses a VirtIO (paravirtualized) network adapter for best performance.
Windows 11 setup may not load that driver automatically during OOBE, so you cannot continue with the default online account flow.

Quick workaround to pass OOBE network requirement

At the Connect to a network screen:

Press Shift + F10 to open Command Prompt.
Run:

oobe\bypassnro

The VM reboots automatically.
Continue setup and choose the offline/local path (for example I don’t have internet).

This bypasses the immediate network requirement so installation can complete.

After you reach the Windows desktop:

Ensure the VirtIO ISO is still mounted to the VM CD/DVD drive.
Open the mounted ISO in File Explorer.
Run virtio-win-guest-tools.exe from the root of the ISO.
Install all recommended components.
Reboot the VM.

This installs the NIC driver and other guest drivers in one pass.

Verify network driver installed correctly

After reboot:

Open Device Manager.
Expand Network adapters.
Confirm a Red Hat VirtIO adapter is present and has no warning icon.
Run ipconfig /all in Command Prompt and verify an IP address is assigned.

If networking still does not work

Use this checklist:

1) Confirm Proxmox VM hardware settings

Network Device Model: preferably VirtIO (paravirtualized).
Bridge: attached to the correct bridge (commonly vmbr0).
VLAN tag: set correctly if your network requires VLANs.
Firewall: temporarily disable VM firewall rule for testing if needed.

2) Manually install NIC driver from Device Manager

If the guest tools installer did not bind the network driver:

In Device Manager, right-click unknown Ethernet controller.
Select Update driver > Browse my computer.
Browse to the VirtIO ISO path:

NetKVM\w11\amd64

Complete the wizard and reboot.

3) Test another VirtIO ISO release

If one ISO build is problematic in your environment, test another stable release and reinstall.

4) Check Proxmox host side networking

Verify the node bridge/uplink is healthy.
Check VM tap interface is up.
Confirm no ACL/firewall policy blocks DHCP or outbound traffic.

Optional fallback (for troubleshooting only)

As a temporary diagnostic step, switch VM NIC model from VirtIO to E1000, boot once, confirm network, then switch back to VirtIO after drivers are installed.
Do this only for troubleshooting because VirtIO is usually preferred for performance.

Recommended build order for future Windows 11 Proxmox VMs

Attach Windows 11 ISO and VirtIO ISO before first boot.
Complete setup with oobe\bypassnro if network is blocked.
Immediately install virtio-win-guest-tools.exe.
Reboot and verify Device Manager before installing additional software.

Result

Using Shift + F10 plus oobe\bypassnro gets you past the OOBE network gate, and installing virtio-win-guest-tools.exe after first login usually resolves the missing Proxmox VirtIO NIC driver issue cleanly.