Please check that:
If it fails at the
Installing drivers stage, then there's probably an issue with the Windows installation on your PC. In this case, you can try to:
If you want to do the latter, you'll first have to download and install a copy of the Windows ADK, then add the following path:
adkInstallPath\Assessment and Deployment Kit\Deployment Tools\ARCH\DISM to the settings.ini file.
adkInstallPath with the path where you've installed the ADK. (it's
C:\Program Files (x86)\Windows Kits\10 by default)
arch with the architecture of your machine (
Try temporarily disabling any anti-virus software. Windows Defender is known to slow down the process quite significantly. If this doesn't help, then the target drive may be too slow.
OK, but flashing Raspberry Pi OS or any other Linux distro is waaaaay faster. Are you really telling me that the drive is slow?
Sort of. Linux distros for Raspberry Pi usually come packaged in the
.img format, which is a sector-by-sector copy of a disk drive. In other words, someone has shared an image of their SD card. (which, by the way, is an illegal thing to do for Windows, due to copyright reasons)
Now, why is this faster to install?
It's faster to install because an
.img file is copied sequentially to your drive. Very cheap or old devices usually have decent sequential speed, but poor random I/O performance. The latter is what matters for Windows images, as they're file-based rather than sector-based.
We have an issue tracker page just for that.
Make sure to attach the latest/relevant
*.log file from the
logs directory of WoR. (you can sort them by modified date in Explorer)
We've seen this happen on drives that are too slow (e.g.: SD cards that are not A1-rated or better). The only solution is getting a drive that has better random I/O speeds.
For now, the insider builds do work. But this may change in the future.
Windows 11 build 25163 is the last one than can boot on the Raspberry Pi.
Recent insider builds no longer work as they make extensive use of the new atomic instructions introduced in ARMv8.1.
The UEFI now supports Secure Boot, and software TPM 2.0 may also be implemented in the future. But there's a new ARMv8.1 CPU requirement which the Raspberry Pi doesn't meet (it has ARMv8.0). In theory this could be addressed in the firmware by trapping atomic operations to EL2 and translating them to ARMv8.0 code, but it's not really feasible.
Boards with less than 4 GB of RAM will also encounter the RAM requirement.
The checks are currently present only in
setup.exe, but our imager replaces it when doing a clean installation.
Feature updates depend on
setup.exe, so you'll have to bypass those checks. More details here: How to perform OS updates.
See the Getting Windows Images guide.
Download the latest driver package ZIP for your Raspberry Pi model from: https://github.com/worproject/RPi-Windows-Drivers/releases
To update the drivers from another computer (recommended):
Dism /Image:E: /Add-Driver /Driver:"PathToDrivers" /Recurse /ForceUnsigned
PathToDriverswith the path to the extracted driver package.
E:with the letter of the Windows partition on your Raspberry Pi boot drive.
To update the drivers directly on your Raspberry Pi (might lead to crashes):
pnputil.exe /add-driver "PathToDrivers\*.inf" /subdirs /install /reboot(the device may reboot)
PathToDriverswith the path to the extracted driver package.
There's a tool that can help you do that: Boot partition mount utility
The "Windows Setup could not configure Windows to run on this computer's hardware." error usually occurs when the power was interrupted during the first boot process.
This can be fixed by re-installing the image.
You can find the current hardware support status here: https://github.com/worproject/RPi-Windows-Drivers#status
And no, we don't have an estimated time of arrival (ETA) for anything.
Some outdated guides may tell you to use winpatch. This is no longer required and will break the USB driver.
We don't currently know the exact cause of this issue, but we've seen it happen on slow SD cards / USB drives. So make sure to try a faster storage drive.
Note: sequential speeds don't matter as much as random I/O ones do.
Your PC most probably has an x86 Intel/AMD processor, while Raspberry Pi has a totally different CPU architecture.
Only ARM64 drivers are supported on Windows 10 ARM64.
We highly suggest asking the hardware vendor for ARM64 drivers. If enough people contact them, they may prioritize the request.
Manual download (see the Windows Desktop ARM target): https://ftdichip.com/drivers/d2xx-drivers/
Manual download: http://www.wch.cn/downloads/CH341SER_ZIP.html
Controllers that show up as a standard serial port, like Arduino boards with ATmega16u2, should work too.
You can also use the built-in serial pins on the GPIO header if you have the latest driver package installed.
https://drive.google.com/drive/folders/1KSCIgzjdhCeZzxsGFZu2t2lyduq2jO65 (made by @emp4u2)
Examples of adapters with this chipset: NETGEAR WG111v2
Other chipsets are NOT currently supported, but feel free to try anyway.
Yes. Most of them should work.
Yes, you can run most x86 apps on Windows 10 ARM64.
x64 app support is currently available in the latest insider builds of Windows, and it's significantly faster than the x86 layer.
Use the PiMon app from the Downloads page.
Some apps may not work as expected, and we can't really do anything about it. Please contact the app developer / hardware vendor for support.
Raspberry Pi Configuration->
Advanced Configurationand change
Limit RAM to 3 GBto
This mostly depends on the speed of your boot drive.
Something may have went wrong if:
It depends on the speed of your internet connection, CPU and storage, thus we cannot tell you an average time.
In case this still doesn't solve the issue and you're not able to figure out the cause, UUPDump has a Discord server linked in the header of their website. People there may be able to help you.
You can also join the community servers for this project.
This is a common issue with scripts from https://uup.rg-adguard.net. They fail / forget to unmount a WIM image.
To fix this, identify the stubborn mount folder, then execute the following command in a Command prompt window running as Administrator:
dism /unmount-image /mountdir:"YourStubbornMountDir" /discard
Not yet. While the CPU supports it, the UEFI doesn't properly inform the OS about this.
Enabling the Virtual Machine Platform will leave the system in an unbootable state!
It works on the Compute Module 3.
Compute Module 4 (with or without eMMC) is know to freeze at the UEFI boot screen. See: https://github.com/pftf/RPi4/issues/146
Even if you manage to get it booting on the CM4, USB support will require an 1 GB RAM limit. PCIe also won't work.
If it needs any additional installation in Linux, then it will likely not work. The fan control services / scripts must be ported to Windows.
If it's a simple PWM fan, the UEFI can toggle it on boot. You just need to enable this functionality in the UEFI setup menu and connect the PWM signal pin accordingly.
With a regular license key.
Windows licenses are NOT architecture-specific, so you can use any key that you'd normally use on your PC.
See: https://www.raspberrypi.org/forums/viewtopic.php?p=1706253#p1706253 (some things in that post are outdated, like USB needing patches & such, but the legal aspect is still relevant today)
Also see the replies on this thread: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=318599.
tl;dr: It's as legal as running Windows on your PC.
We don't share any copyrighted files. You can generate Windows images from files publicly available on Microsoft servers.