The DDA packages are already installed. Likely the feature is controlled by a kernel policy, SKUwitch to a server SKU should be more than enough to get it working.
Thank you for another solution acer-5100. I will try this out on the existing Windows 10 IoT Enterprise 2021 installation on the machine I'm dealing with and report back. This would be ideal but I guess I'd have to stay on the Server 2022 SKU for a VM to keep booting. Only one way to find out I guess. My intention here is a bit of a long shot. I want to nest a KVM solution like Proxmox, pass through an Optimus 1660 Ti on a laptop (it support VT-d) and use vgpu_unlock or LibVF.IO to virtualise it.
Remember the "likely" part. It's just a guess for now. If it works, yes you have to stay on server SKU, but once you have the SKUwitch thing in place, you can go back and forth, using just one command and one reboot. So not a big problem
if sku controlled try windows 10/11 rdsh aka windows enterprise multiple desktop she use server install type with client features
Worth a try, given it quick to test (just insert the right key and reboot), if it works you are OK. If doesn't work you can't be sure, it's because the kernel policies or because some missing package other than DDA ones. Some server features are connected just to the kernel type, some others are tied to specific kernel policies. For example proper servers have the virtually unlimited SMB connections, RDSH is limited to 20 just like clients.