[Bug]: Windows cannot boot on RK3576 with latest Armbian IoT (stuck at “Windows for Docker”)

[Xingsandesu]

Operating system

nanopi-r76s:windows:% lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 25.11.0-trunk.38 trixie Release: 13 Codename: trixie

Description

Environment
Device: r76s
SoC: RK3576 (big.LITTLE architecture)
OS: Armbian IoT (latest build)
Kernel: 6.1.115-vendor-rk35xx
Docker version: Docker version 28.5.2, build ecc6942
Docker Compose version: Docker Compose version v2.40.3
Image used: dockur/windows-arm:latest
Description
After starting the container with docker compose up, the Windows virtual machine boots partially and stops at the “Windows for Docker” splash screen. The web VNC interface (http://:8006) shows only the black screen with the blue cube logo, and the system never progresses to the Windows setup or login screen.

Docker compose

services:
  windows:
    image: dockurr/windows
    container_name: windows
    environment:
      VERSION: "10e"
      RAM_SIZE: "8G"
      CPU_CORES: "4"
      LANGUAGE: "Chinese"
    devices:
      - /dev/kvm
      - /dev/net/tun
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 3389:3389/tcp
      - 3389:3389/udp
    volumes:
      - ./windows:/storage
    restart: always
    stop_grace_period: 2m
    privileged: true

Docker log

windows  | ❯ Starting Windows for Docker v5.12...
windows  | ❯ For support visit https://github.com/dockur/windows-arm
windows  | ❯ CPU: Cortex A53 | RAM: 13/16 GB | DISK: 197 GB (ext4) | KERNEL: 6.1.115-vendor-rk35xx...
windows  | 
windows  | ❯ Warning: Your CPU architecture is below ARMv8.1, and does not support Windows 11 build 24H2 and up.
windows  | ❯ Your CPU has a big.LITTLE architecture, will use only cores 4,5,6,7.
windows  | ❯ Booting Windows using QEMU v10.0.3...
windows  | BdsDxe: skipped Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0)
windows  | BdsDxe: loading Boot0001 "UEFI QEMU QEMU USB HARDDRIVE 1-0000:00:01.0-3" from PciRoot(0x0)/Pci(0x1,0x0)/USB(0x2,0x0)
windows  | BdsDxe: starting Boot0001 "UEFI QEMU QEMU USB HARDDRIVE 1-0000:00:01.0-3" from PciRoot(0x0)/Pci(0x1,0x0)/USB(0x2,0x0)
windows  | ❯ Windows started successfully, visit http://127.0.0.1:8006/ to view the screen...

Screenshots (optional)

[kroese]

Does it work with Windows 11 or also not?

[Xingsandesu]

Yes. it also cannot launch on Windows 11.

windows  | 4980736K ........ ........ ........ ........ 94%  543K 6m39s
windows  | 5013504K ........ ........ ........ ........ 95%  469K 5m55s
windows  | 5046272K ........ ........ ........ ........ 95%  499K 5m9s
windows  | 5079040K ........ ........ ........ ........ 96%  567K 4m23s
windows  | 5111808K ........ ........ ........ ........ 97%  553K 3m37s
windows  | 5144576K ........ ........ ........ ........ 97%  541K 2m51s
windows  | 5177344K ........ ........ ........ ........ 98%  465K 2m5s
windows  | 5210112K ........ ........ ........ ........ 98%  519K 78s
windows  | 5242880K ........ ........ ........ ........ 99%  537K 31s
windows  | 5275648K ........ ........ .....            100%  455K=2h6m
windows  | 
windows  | ❯ Extracting Windows 11 bootdisk...
windows  | ❯ Extracting Windows 11 environment...
windows  | ❯ Extracting Windows 11 setup...
windows  | ❯ Extracting Windows 11 image...
windows  | ❯ Adding drivers to image...
windows  | ❯ Adding win11arm64.xml for automatic installation...
windows  | ❯ Building Windows 11 image...
windows  | ❯ Creating a 64 GB growable disk image in raw format...
windows  | ❯ Your CPU has a big.LITTLE architecture, will use only cores 4,5,6,7.
windows  | ❯ Booting Windows using QEMU v10.0.3...
windows  | BdsDxe: skipped Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0)
windows  | BdsDxe: loading Boot0001 "UEFI QEMU QEMU USB HARDDRIVE 1-0000:00:01.0-3" from PciRoot(0x0)/Pci(0x1,0x0)/USB(0x2,0x0)
windows  | BdsDxe: starting Boot0001 "UEFI QEMU QEMU USB HARDDRIVE 1-0000:00:01.0-3" from PciRoot(0x0)/Pci(0x1,0x0)/USB(0x2,0x0)
windows  | ❯ Windows started successfully, visit http://127.0.0.1:8006/ to view the screen...