Windows 11 Insider Preview Build 22458 Install Problem

Windows Update
Windows Update

Update (September 22, 2021): Microsoft released Windows 11 Insider Preview Build 22463 to the Dev Channel and there was a fix: “Fixed an issue that caused some PCs to bug check with DRIVER_PNP_WATCHDOG error when attempting to update to a recent build.” That fix solved this problem, also.

Update (September 20, 2021): I updated to build 22458 with an NTFS formatted external USB 3.0 hard disk attached. But after the successful update, I plugged a M.2 SSD into the same USB 3.0 bus that had a working 4TB USB 3.0 hard disk and got the same errors as I describe below. I switched back to the Beta channel and updated successfully to 22000.194 with the all external drives connected.

TL;DR Windows Insider Build 22458 and the previous two builds (22454 & 22449) won’t install with a connected external USB 3.0 drive that has an APFS partition and NTFS partition.

On September 15, 2021, Microsoft released Windows 11 Insider Preview Build 22458 to the Dev Channel. I had switched back to the Beta Channel (22000.184) because my attempts to install the two previous developer releases (22449 and 22454) failed.

I switched back to the Developer Channel to try the new build and 22458 started installing but after the reboot, I was back at 22000.184. The two external USB 3.0 drives that I had connected during installation caused the problem. Disconnecting the drives then letting Windows Update install 22458 worked. But connecting the external USB 3.0 drives caused the same problems as the two previous builds.

I had Disk Manager open as I connected the two drives and they would show up without drive letters, then the Bluetooth keyboard and mouse would disconnect. The drives would disappear and reappear from Disk Manager and the Bluetooth would reconnect. After disconnecting the external drives 22458 worked as expected. I rolled back to 22000.184

Since I have a 5TB internal disk drive on the system SATA controller, I finally realized that I should try an external USB 3.0 drive formatted only NTFS. This drive worked with 22458 with no problems, so I am concluding that 22458 and the previous two Developer builds don’t like drives with non NTFS partitions (though I have not tried any Linux file systems).


I bought a MacBook Core 2 Duo about a week ago. I bought it CTO (Configure To Order) with 2GB of RAM because I wanted to run some version of Windows. My last Apple laptop was a PowerBook G4 12″ rev. A, so the Macbook is a big jump in performance.

The only problem I’ve had was the DVD drive. DVDs and CDs wouldn’t mount on the desktop, though the drive showed up in the System Profiler. I was able to boot from the install DVD and ran the hardware tests with no problems. I reset the PRAM and then DVDs showed up on the desktop.

Apple MacBook Core 2 Duo (black)

I installed Boot Camp and Windows Vista RC2 after it took me some time to figure out how to partition the 120GB HD into two Mac OS Extended partitions and one NTFS. I ended up using rEFlt for the boot menu and it works great. Vista runs with Aero on the Macbook’s Intel GMA 950 chipset. Performance is OK. The only problem is not being able write to the NTFS partition (reading works) when running OS X. Maybe someone will write a read-write file system similar to the NTFS for GNU/Linux.

I also installed Parallels (with a trial key) and Vista RC2. Even with 2GB RAM, system memory is paging out when Parallels is running so it seems that 3GB of system RAM would be ideal. Aero effects do not show up in Parallels with 2GB Macbook system RAM. Vista performance on Parallels seems to be about 75% of Vista on Boot Camp.

I used Michael Baltaks’ DoubleCommand and remapped the enter key to forward delete, so CTRL-ALT-DEL is now three keystrokes instead of four (fn-ctrl-option-delete).

I had no problems adding the MacBook, Boot Camp PC and Parallels PC to a Windows 2003 Server Active Directory. One thing I haven’t been able figure out is why a directory listing of a PC share is slower on the MacBook when I’m logged into the domain as opposed to logging onto the MacBook as a non-domain member.