Please check that:
If the problem persists, please create a new issue on our bug tracker page.
Please attach the "WoR.log" file as well!
I've developed a tool for that purpose: https://www.worproject.ml/dldserv/?file=drvman_Debug.zip
It is unfinished and may have some annoying bugs, but I'm working to add this feature in the Windows on Raspberry imager.
Dism /Image:WINLETTER: /Get-Drivers
Dism /Image:WINLETTER: /Remove-Driver /Driver:OEMx.inf
Dism /Image:WINLETTER: /Add-Driver /Driver:PATHTOINF
WINLETTER = the Windows partition letter on your SD card (e.g. F)
OEMx.inf = the device driver that you want to remove, where x represents its number
PATHTOINF = path to the new driver (e.g. C:\WindowsPi\drivers\dwusb\dwusb.inf)
If you want to install a new device driver (not to update an existing one), you can follow the steps above but you don't have to remove any driver.
Please check that your Raspberry Pi 3 is running at maximum speed (1200 MHz for the B model, and 1400 MHz for the B+ model).
If it is running at 600 MHz, then:
Now your Raspberry Pi will boot at maximum speed, but don't expect any major improvement in Windows performance. You are still running full Windows 10 on a small, low-powered single-board computer.
This means that you're using the old "dwusb.sys" driver. You can get the new MCCI USB driver by downloading the latest drivers package from the "Downloads" page.
If you're using MCCI's driver and the USB ports are still not working, make sure to use the latest UEFI.
The DRIVER_POWER_STATE_FAILURE BSoD is caused by the old USB driver.
You can fix this error by installing the latest device drivers.
The INACCESSIBLE_BOOT_DEVICE BSoD appears when there is no SD driver installed.
You can fix this error by installing the "rpisdhc" and "bcm2836sdhc" device drivers. These are included in the latest WoA64_Drivers_RPi3 archive.
You're probably using an old version of the UEFI firmware. You can get the latest version from here .
How to fix this issue:
Now Windows should boot normally.
The UNSUPPORTED_PROCESSOR BSoD appears on old Windows builds.
You can fix this error by updating the operating system to a newer version. Windows client versions newer than 1803 should work.
The "Windows Setup could not configure Windows to run on this computer's hardware." error occurs when the BOOT partition does not have the boot flag set.
You can fix this error by setting the "Boot" partition as Active. This fix might not work after the first boot process.
The Windows on Raspberry imager does that automatically (starting from version 0.2).
You can't connect to any network device because there are no Ethernet or Wireless LAN drivers available at the
Also, the Ethernet adapter depends on the USB driver which is not working properly now.
Update: It is possible to get a network connection by emulating a modem: https://github.com/driver1998/bsp/wiki/Modem-Emulation-and-Networking
No, this is not possible. The drivers found in Windows IoT Core are compiled for ARM32, while Windows 10 is available only for ARM64.