Who this guide is for
If you are preparing maintenance media for a supported Qualcomm Snapdragon Windows ARM64 PC, start with the uqitong ARM website and its tutorial directory. This article introduces our own product's documentation and preparation requirements. It is a first-party product guide, not an independent review.
The official illustrated tutorial demonstrates creation and startup on a Snapdragon ThinkPad T14s Gen 6. That example does not establish compatibility with every ARM device. For a conventional Intel or AMD computer, use the relevant x86/x64 product documentation. Identify the target computer before choosing a download.
Prepare a USB drive you can erase
The official creation guide recommends a USB drive of at least 16 GB and states that creation erases the selected drive. Save its existing files elsewhere and open some important copies to verify them. Erasing the USB drive and later formatting a computer's system partition are separate operations with separate targets to confirm.
You need a Windows computer that can run the creation tool and the target ARM computer for the final boot check. Disconnect unrelated USB drives and external hard disks to reduce selection errors. The capacity, disk number and drive letter in a tutorial screenshot are examples, not values to copy onto your own setup.
Use the official download and the right mode
Get the appropriate language edition from the current official download area and read its support and release information. Screenshots document a particular version and may be older than the available download. If security software raises a warning, investigate the source, signature and warning details rather than blindly disabling protection.
Follow the mode intended to write a physical USB drive. Adding a maintenance environment to the local boot menu or generating a standalone ISO serves a different purpose. You do not need a Windows installation image just to create maintenance media; prepare a matching ARM64 image separately if you also intend to reinstall Windows.
Check the selected device before writing
Match the disk number, device name, capacity and drive letter with the USB drive you are prepared to erase. Read the second data-loss prompt and proceed only after confirming both the target and its backup. If the device list changes, check again rather than relying on your earlier selection.
Keep the connection and power stable while the tool writes the drive. Do not unplug it or force the application to close. Safely eject it when instructed. Seeing a data partition in File Explorer alone does not verify the boot structure; testing on the target computer is the next step.
Boot the target computer from the USB drive
Connect the drive and consult the computer manufacturer's instructions for its temporary boot menu. Choose the entry matching your USB device. Startup keys differ between brands and models; the ThinkPad procedure in the tutorial is one example, not a universal keyboard shortcut.
After reaching uqitong ARM PE, check the desktop, keyboard and mouse, and whether the storage needed for your maintenance task is visible. Record the computer model, tool version and USB model. Creation, a usable boot entry and a working maintenance environment together establish a usable maintenance drive for that computer.
Continue only with the task you need
For routine maintenance, you can stop after verifying the drive. Reinstalling Windows requires the separate installation guide and a fresh check of the image architecture, backup and target partition. For Ubuntu, use the relevant tutorial to investigate the particular device's support and installation requirements.
If startup fails, record what happened and check the USB port, boot entry and creation result before consulting the manufacturer. Do not change unfamiliar firmware security settings simply to make an entry appear. Back up the data partition before rebuilding maintenance media, and never make it the only copy of important files.
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.