Windows 10 checking for updates slow install#
Windows 10 checking for updates slow driver#
Windows 10 checking for updates slow manual#

(WireGuard has its own virtual NIC, so we're technically not using our 'real' network card to access the DNS server on the far side of the tunnel.)

Windows 10 checking for updates slow driver#

Unfortunately, that didn't resolve the original DNS issue-which turns out to be some conflict between Windows 11 and the VirtIO network driver we're using.Д¬hanging the VM's network adapter to emulated Intel e1000 resolved the DNS issue-as does, hilariously, leaving the NIC as VirtIO and just using a DNS server on the far side of a WireGuard tunnel. Thankfully, Control Panel hasn't yet been done away with in Windows 11, and its tried-and-true network adapter configuration dialog works just as expected. Next question-is Control Panel still there? The second bug came while trying to troubleshoot the first-attempting to set IP address configuration directly using Windows 11's Settings dialog fails miserably, with a cryptic message to 'check one or more settings and try again.' There's nothing actually wrong with the settings-the dialog is just broken. Nevertheless, attempting to pingВ the same hostname directly fails, as do most attempts to browse with Edge or Chrome. But attempts to ping В fail! The confusion only gets worse when we use nslookupВ to query our DNS server directly-it answers our queries just fine. We can ping 8.8.8.8-Google's anycast DNS provider-without issue, so we know that general connectivity is fine both inside the LAN and outside of it. You can see the DNS resolver issues in the first screenshot above. It took almost no time to find our first and second nasty Windows 11 bugs-the DNS resolver was strangely and inconsistently broken, and the network configuration dialog under Settings was broken as well. During the reboot, we get the usual 'don't turn off your computer' message-but it's in a new font and possibly on a slightly different shade of blue background. Ironically, the first look anyone gets at Windows 11 itself right now is the dreaded BSOU (Blue Screen Of Updates)-after flighting our Windows 10 VM into the Dev channel and one very quick download, it rebooted.

Windows 10 checking for updates slow manual#

Although one of our test VMs is a 'daily driver' we rely on, it's sitting on top of a ZFS dataset-and we took a manual snapshot prior to the upgrade, for easy rollback. We had no real problems updating either a well-used Windows 10 VM or a brand-new one-but we strongly advise against upgrading to Windows 11 on a machine or VM that matters to you, unless you have a guaranteed method of recovery you both trust and are prepared to use. (If you're not already on Windows 10 20H2 or newer, you'll need to get throughВ that upgrade first.)

Windows 10 checking for updates slow install#

To install Windows 11 BuildВ 22000.51, you must begin with a fully patched and up-to-date Windows 10 installation, then flight it into the Dev channel, then upgrade it to Windows 11 via Windows Update.

The first disappointment we encountered with Windows 11 is a puzzling one-it can't (yet) be cleanly installed as a new operating system.