I generated an ARM64 workspace using this IoT ADK add on kit.
like:

PS C:\iot-adk-addonkit\Workspace>new-ws C:\RPI\iotcore\myrpi4arm64workspace Contoso arm64
New IoTWorkSpace available at C:\RPI\iotcore\myrpi4arm64workspace for arm64
Opening workspace : C:\RPI\iotcore\myrpi4arm64workspace\IoTWorkspace.xml
arm64 IoT Core kit version 10.0.17763.253 found
Corekit install path found OK
ADK_VERSION : 10.0.17763.1
IOTCORE_VER : 10.0.17763.253
BSP_VERSION : 10.0.0.0
ADDONKITVER : 7.0.210203.1200
HostOS Info : Microsoft Windows 10 Pro - 10.0.19043 - en-US
Error: Host OS Enterprise Edition required for using Security functions such as Device Guard
IOTWKSPACE  : C:\RPI\iotcore\myrpi4arm64workspace
OEM_NAME    : Contoso
BSP_ARCH    : arm64
BSPPKG_DIR  : C:\RPI\iotcore\myrpi4arm64workspace\Build\arm64\pkgs
MSPKG_DIR   : C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm64\fre
Copying Registry.Version
Copying Custom.Cmd
Copying Provisioning.Auto
Copying OEM.Sample
Copying Device.SystemInformation
Copying DeviceLayout.GPT4GB
Copying DeviceLayout.GPT8GB-R
Copying DeviceLayout.MBR4GB
Copying DeviceLayout.MBR8GB-R
Workspace ready!
IoTCorePShell arm64 10.0.0.0 Test
PS C:\RPI\iotcore\myrpi4arm64workspace>importpkg *
Copying Appx.Certs
Copying Custom.BCD
Copying Custom.OOBEApp
Copying Custom.Settings
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\Device.SystemInformation already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\DeviceLayout.GPT4GB already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\DeviceLayout.GPT8GB-R already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\DeviceLayout.MBR4GB already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\DeviceLayout.MBR8GB-R already exist.
Copying Recovery.GPT-BCD
Copying Recovery.GPT-BcdEdit
Copying Recovery.MBR-BCD
Copying Recovery.MBR-BcdEdit
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\Packages\Registry.Version already exist.
Copying Security.BitLocker
Copying Security.DeviceGuard
Copying Security.DeviceGuardTest
Copying Security.RootCerts
Copying Security.SecureBoot
Copying Security.SecureBootTest
Copying Settings.HotKey
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Source-arm64\Packages\OEM.Sample already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\ProdPackages\Custom.Cmd already exist.
Warning: C:\RPI\iotcore\myrpi4arm64workspace\Common\ProdPackages\Provisioning.Auto already exist.
Copying Recovery.WinPE
IoTCorePShell arm64 10.0.0.0 Test
PS C:\RPI\iotcore\myrpi4arm64workspace>importbsp RPi c:\Release\RPi_BSP_ARM64_Release.zip
Extracting BSP zip into the temporary directory C:\RPI\iotcore\myrpi4arm64workspace\BSPDIR
Processing C:\RPI\iotcore\myrpi4arm64workspace\BSPDIR\RPi
Error: Incorrect BSP arch. Found arm, expected arm64
IoTCorePShell arm64 10.0.0.0 Test
PS C:\RPI\iotcore\myrpi4arm64workspace>

This looks like it created my ARM64 workspace correctly.
I then imported all packages using the "importpkg *"
This also seems to have worked fine.
I then tried to import my "built for ARM64" BSP and got the failure "Incorrect BSP arch. Found arm, expected arm64"
I am not sure this is an ADK import problem or the fact I used the "binexport.ps1" script from the github
https://github.com/raspberrypi/windows-drivers

That script seems to have a hard coded path at line 30:

$bindir = $RootDir + "build\bcm2836\ARM\$buildconfig\"

I changed the "ARM" to "ARM64" and was able to generate to RPi_BSP_Release.zip but it has problems importing

I tried using the drivers
windows-drivers-master (1).zip
but every time I used the WoR flasher it just kept saying installation failed after getting to the installing drivers screen.

• Copy driver files to the driver store rather than Windows\System32\drivers
• Use device interfaces instead of hardcoded driver paths for:
  • bcm2836pwm
  • rpiq
  • vchiq

Hi, there is any way to enable dual screen support also if actualy there is no working driver video for a Pi 4?

For helping in build the driver video there are some resource (or documentation) about the work to do and the actual stete of the driver?

• With rpiuxflt installed and uaspstor enabled, booting from UAS drives connected to USB 3.0 results in an INACCESSIBLE_BOOT_DEVICE BSoD.
  Connecting the drives after Windows has booted (from SD for example) works fine in this case. (I haven't done any stress testing yet, so they might as well fail under load).

• With rpiuxflt installed and uaspstor disabled, booting from UAS drives connected to USB 3.0 works fine.

• Without rpiuxflt + the 3 GB RAM limit enabled in UEFI and uaspstor enabled, users have reported that USB 3.0 boot from UAS drives works fine (though I'm personally not able to replicate the success in this case, as my drive keeps on hanging Explorer and anything trying to access it, so booting from it is out of the question).

UAS drives connected to USB 2.0 and non-UAS ones connected to any port work flawlessly in every scenario.

Maybe we can take advantage of this workaround once it becomes available? It could fix a couple of issues people are currently experiencing with our USB filter driver.

The PL011 clock can be obtained from ACPI.
For mini UART, we can get the core clock using the mailbox interface (rpiq).

I'm using WoR Project to have Windows 11 insider on my Pi, are there any GPU drivers?

Is there a location that builds the zips for use? I am struggling to build the libraries and get the right combination of tools and SDKs. I just want to download the ARM64 version RPi BSP, but that doesn't seem to be an option. Could you please publish these as releases on this repo? I am trying to build a Win 10 IOT RPi 4 ARM64 FFU and that needs the RPi BSP ARM64 drivers.

A few users have reported that the device fails to start.
Recent boards may be using a different / newer PHY than the one found on the Pi 4 or older 400s.

From WinDbg:

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000014, Device removed without disconnecting interrupts
Driver failed to disconnect interrupts when the device was
removed.
Arg2: ffffe00b37049b20, PDO.
Arg3: 0000000000000008
Arg4: 0000000000000000

All drivers based on https://github.com/microsoft/Windows-driver-samples/tree/master/sd/miniport/sdhc exhibit this issue.

Recent updates to the final release of Windows seem to cause a driver reset during the first boot, so users are not able to complete the installation process.

bcmgenet is written using the NetAdapterCx API, which is unstable and already had breaking changes for 2 times.
@alotipac, the creator of the driver, has pushed some fixes to his fork of the old ms-iot repo: https://github.com/alotipac/rpi-iotcore/commits/rpi4-insider that make the driver work on the latest insider builds too (although it is unstable and significantly slower on builds 21301+).

We cannot merge those changes as Github Actions only provide the 19041 SDK/WDK, so CI builds will fail. The fixes are also not backwards compatible, meaning that we'd have to build 3 versions of the driver (and possibly more than that if Microsoft breaks the API again).

As a temporary workaround (until the API becomes stable), we could bundle our own version of NetAdapterCx with the driver, thus making it work with older versions of Windows too.

Device raspberry pi 4 4GB running windows 11 last public release.

Are there any plans to fully support Windows 10 (IoT?) on the Raspberry Pi 4?

The sequential R/W speeds max out at around 23-24 MB/s with a SanDisk Ultra UHS-I A1 card.
The chip can do much better than this, but it is currently constrained by the following issues:

• DMA is disabled because sdbus doesn't honor the _DMA method in ACPI, so it's not able to do the required address translation without a lower filter driver.

• UHS-I support is disabled because the controller can't switch the voltage in a standard way, so it's always running at 3.3V.

Boot stalls as soon as UEFI loads bootloader EFI application or shortly after it as there is not even a windows spinner loading. It just gets stuck.

it also appears to affect other armv8.0 devices as i seen armv8.2 devices boot it fine.

hi,
after build iso successfully using worproject get bellow error in windows 11 and windows 10.
This disc contains a "UDF" file system and requires an operating system that supports the ISO-13346 "UDF" file system specification.
thank you

This is being used by rpiwav to generate analog audio.

The first change is that now there are two PWM peripherals (and PWM0, which is the only PWM peripheral currently described in ACPI, can't be muxed to the audio jack pins anymore).

From what I've seen, the addresses for PWM0 haven't changed, but the driver now fails to do DMA (even with the range being limited at the first 1 GB).

Hello, I'm a beginner. Today, when I tried to compile the driver, I found that there were some errors in the compilation process of some drivers, which could not be solved. I hope I can get help from big brother here（ If you send it in the wrong place, please forgive me

The error message is as follows: (Build Error Driver Project List)
1：rpiq
2：SerPL011
3：vchiq
4：vchiq_arm_kern
5：vcos_win32_kern
6：vcos_win32_kern_generic

"rpiq" and "SerPL011" driver project：I also disable the 'Spectre' of 'rpiq & SerPL011', However, other errors are displayed after disabling. This error should be an error during link.
error message list:
1: 严重性 代码 说明 项目 文件 行 禁止显示状态
错误 LNK2001 无法解析的外部符号 __stdio_common_vswprintf rpiq C:\Users\Administrator\Desktop\windows-drivers\drivers\mailbox\bcm2836\device.obj 1

2:严重性 代码 说明 项目 文件 行 禁止显示状态
错误 LNK1120 1 个无法解析的外部命令 rpiq C:\Users\Administrator\Desktop\windows-drivers\build\bcm2836\ARM64\Release\Output\rpiq.sys 1

image:

"vcos_win32_kern_generic" driver project：I also disable the 'Spectre' of 'vcos_win32_kern_generic', However, other errors are displayed after disabling. This error should be an error during link.
error message list:
1：严重性 代码 说明 项目 文件 行 禁止显示状态
错误 C2011 “timespec”:“struct”类型重定义 vcos_win32_kern_generic C:\Users\Administrator\Desktop\windows-drivers\drivers\misc\userland\interface\vcos\win32\vcos_platform.h 139

I tried to delete this structure, but I couldn't solve it。

Im using win11 preview using WOR. There is not wifi driver right now on the other hand Bluetooth working.

Is there any plan to get wifi for

I need some example code for setting GPIOs under windows 11 raspberry PI4

for the

https://github.com/raspberrypi/windows-drivers/tree/master/drivers/gpio)/[bcm2836](https://github.com/raspberrypi/windows-drivers/tree/master/drivers/gpio/bcm2836

driver

VS does not find this file and another one. Any solutions?
I'm actually new doing these things

The ACT led starts blinking 8 times in a pattern when the driver is loaded, indicating a VCHI error.
It doesn't respond to any commands afterwards (tested using some of the ported userland apps here: https://github.com/ms-iot/userland)

I recall seeing the hello_jpeg sample work on ARM32 (RPi 3), but subsequent runs resulted in either the driver hanging or a bug check.