You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using OSDCloud on my Windows 11 ARM VM and any function that is using the Get-AdkPaths function fails due to unable to find the file etfsboot.com which doesn't exist in the ADK folder C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\arm64\Oscdimg.
I see that Get-AdkPaths has the Arch parameter defined which currently uses the default value $Env:PROCESSOR_ARCHITECTURE which based on the host OS but since I'm using ARM64, this value is used thus failing to resolve the etfsboot.com file.
I manually set this value to AMD64 for now after which the path resolves to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg which bypasses the issue because the file does exist there and I'm making an ISO for x64 hardware anyway but I wonder if this could be fixed one way or the other.
The text was updated successfully, but these errors were encountered:
I'm using OSDCloud on my Windows 11 ARM VM and any function that is using the Get-AdkPaths function fails due to unable to find the file etfsboot.com which doesn't exist in the ADK folder C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\arm64\Oscdimg.
I see that Get-AdkPaths has the Arch parameter defined which currently uses the default value $Env:PROCESSOR_ARCHITECTURE which based on the host OS but since I'm using ARM64, this value is used thus failing to resolve the etfsboot.com file.
I manually set this value to AMD64 for now after which the path resolves to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg which bypasses the issue because the file does exist there and I'm making an ISO for x64 hardware anyway but I wonder if this could be fixed one way or the other.
The text was updated successfully, but these errors were encountered: