Windows on Radxa Dragon Q6A

We are excited to announce official Windows support for the Radxa Dragon Q6A! The first preview release is now available for testing. This build allows you to run Windows directly on your Q6A, unlocking new possibilities for the platform.

:warning: Important Notes:

Links:

Driver package: Q6A_WoS_DriverPackage_251205_testsigned.7z

Supported features and installation guide: Windows on Radxa Dragon Q6A - 251213.pdf

Changelog and known issues (Latest release - 2025/12/15)

5 Likes

UEFI firmware 251211 + Driver package 251205

Known issues:

  1. In some cases, installation may fail to finish with bugcheck KERNEL_SECURITY_CHECK_FAILURE (0x139). This is currently under investigation.
  2. RTC time may jump forward 300 years across reboots. Please manually set correct system time for now.

UEFI firmware 251214 + Driver package 251205

Changelog:

  1. Fixed an issue where a KERNEL_SECURITY_CHECK_FAILURE bugcheck could occur on the first boot after installation.
  2. Force sync UEFI variables after saving settings in UEFI setup.

Known issues:

  1. RTC time may jump forward 300 years across reboots. This will disrupt system services, cause high CPU usage and other issues. Please manually set correct system time for now.
  2. The onboard RTL8111K ethernet may drop out when the cpu usage is very high.
  3. Currently no driver is provided for onboard WiFi / Bluetooth.

In the current build state, Wi-Fi is not working. The Start menu does not open either. All CPU cores are loaded at nearly 100%.

Hi. There is a known issue with the RTC that causes the system date to be set hundreds of years in the future. This behavior disrupts system services and is the root cause of the high CPU usage and the interface issues you are experiencing.

As a temporary workaround, please manually set the correct date in PowerShell using the command below:

Set-Date -Date "12/14/2025 4:30 PM"

“Thanks, this helped! And what about the WiFi driver?”

Unfortunately, there is currently no Wi-Fi driver support. We recommend using an Ethernet connection for the time being.

UEFI firmware 251215 + Driver package 251205

Changelog:

  1. Fixed an issue where the system time may jump forward 300 years across reboots. All existing users are recommended to update to this release.
  2. Fixed an issue that prevents the UFS module from being detected correctly. It’s now possible to install Windows directly to UFS.

Known issues:

  1. The onboard RTL8111K ethernet may drop out when the cpu usage is very high (especially during Steam download). Official Realtek driver is also available but it can’t reach peak 1 Gbps download speed on this board.
  2. Currently no driver is provided for onboard WiFi / Bluetooth.
  3. If you need to boot from USB (Windows To Go), remove the QcXhciFilter6490 driver from the driver pack before driver installation.
1 Like

So will we have WiFi & BT driver in the future driver package? And will 16GB memory version of Q6A appear on the market for retail? 12GB memory may not enough for further application under Windows environment.

We are pushing AIC to release the WiFi/BT driver for WoA right now. As you know, not many vendors provide WiFi driver for WoA except Qualcomm.

4 Likes

Will there be any drivers for I2C?

I2C is already fully functional in Windows. Here are some demos:

1 Like

Does the Dragon Q6A + Windows support booting from an SSD (PCIe)?

Yes, it supports booting from NVMe, eMMC and UFS.

1 Like

Will radxa make a dragon cm q6a?

Yes, this is on the roadmap. The name would be CM-Q6.

1 Like

any plans for a q6b as well?

Can I get the UEFI source code?

AFAIK qcom’s UEFI is closed sourced.

I’m trying to install, and while the USB boots, it tells me Windows cannot be installed on any partition of my NVMe. I went into the Windows command line from the installer, erased and repartitioned the drive, but it still is giving the same error. Yes, it’s a GPT partition format. This is the official USB installer from the Microsoft Web site. Bitlocker, Secure Boot, TPM, etc were turned off in the Rufus burn. Any suggestions?

SOLVED: I had to delete the partition in the Win11 install interface, re-add it, then the installer created the (missing) extra MSR partition and I was good.