Choose the release and language at the source
Open Microsoft's official ARM64 download page and read the release, language choices and requirements it currently lists. Bookmarking that page is more useful than keeping a temporary download address because the available image can change.
Confirm that the target computer is ARM64, rather than simply running 64-bit Windows. Then establish whether you are creating a supported virtual machine, running Setup inside an existing Windows installation or preparing bootable media for a physical PC. Each purpose has different requirements to check.
Distinguish an ISO from manufacturer recovery media
A general Windows ISO contains operating-system installation files. Manufacturer recovery media is prepared for particular hardware and normally includes a suitable recovery environment and drivers. Microsoft's Arm ISO guidance recommends using the computer manufacturer's recovery media for physical devices.
If you want to return an existing computer to working condition, first check whether its manufacturer supplies recovery media for the exact model or serial number. To use a general ISO, investigate the model's boot, input, storage and network requirements before proceeding.
Prepare drivers and a way to get online
Two ARM64 PCs can have different driver needs. Microsoft explains that some devices require manufacturer drivers in the installation media before they can boot correctly. Reaching Windows Setup is also not proof that every device will work after installation.
Keep the required drivers and recovery instructions somewhere accessible. Decide how you will obtain drivers if Wi-Fi is unavailable. If that plan depends on an Ethernet adapter or dock, confirm that it is supported in the target environment; the presence of an Ethernet socket alone is not enough.
Verify the image against the official hash
After the download finishes, find the SHA-256 value for the selected release and language on Microsoft's page. PowerShell's Get-FileHash command can calculate the local ISO's hash. Comparing it with the corresponding official value helps detect a damaged or altered download.
Record the source page, filename, download date and result. Different languages or releases can have different hashes, so a value copied from an old article may not apply. A plausible file size is a useful preliminary check, but it does not establish that the image is intact.
Check backups and destinations before creating media
Back up important files from the USB drive and target computer, then confirm that those backups can be read. Keep any recovery information required for encrypted devices. Check the destination separately when creating the USB and when installing Windows, so a backup drive is not selected for erasure.
Follow Microsoft's and the PC manufacturer's applicable instructions for media creation. This article does not provide hardware-requirement bypasses or recommend drivers from another model. Until model support is clear, you can still complete the download, verification and documentation steps without changing the installed system.
Judge success by a working computer
A verified download, a created USB drive and a successful installation are different milestones. After installation, check networking, sound, input, displays, sleep and resume, and your regular peripherals. Complete an actual work task before deciding that the PC is ready for use.
For development virtual machines, check the virtualization platform too. Microsoft states that Hyper-V on an x64 host does not support ARM64 virtual machines. Selecting the right ISO is only one part of selecting a supported environment.
Sources and verification
This article draws on published documentation and editorial guidance. Unless explicitly stated, it does not report our own hardware tests. Sources checked: September 27, 2026.