Failed to download or register the following EPs: VitisAIExecutionProvider. / and no NPU models showing #558

Activity

1. PCAssistSoftware commented on Apr 2, 2026

   

   Darren Rose (PCAssistSoftware)

   on Apr 2, 2026

   Author

   More actions

   Any chance of a response on this issue?
2. bmehta001 commented on Apr 10, 2026

   

   bmehta001

   on Apr 10, 2026

   Contributor

   More actions

   Hi Darren Rose (@PCAssistSoftware), Can you please check the most recent log in your ~/.aitk folder for lines with VitisAIExecutionProvider and confirm if you see any errors?

   If so, try running the following commands in Powershell as an administrator to ensure the VitisAI EP and any artifacts are fully deleted?

   Get-AppxPackage -AllUsers "*.EP.*"  | Select-Object -ExpandProperty PackageFullName
    
   Get-AppxPackage -AllUsers "*.EP.*" | ForEach-Object {
      try {
          remove-AppxPackage -Package $_.PackageFullName -AllUsers
          Write-Host "Removed package: $($_.PackageFullName)"
      } catch {
          Write-Warning "Failed to remove package: $($_.PackageFullName). Error: $_"
      }
   }
   
   remove-appxpackage uup://product/Windows.Workload.ExecutionProvider.VITISAI.amd64
   

   Then, foundry service restart should attempt to re-download and register the EPs. Hopefully, that will fix the VitisAI EP registration issue.
3. PCAssistSoftware commented on Apr 13, 2026

   

   Darren Rose (PCAssistSoftware)

   on Apr 13, 2026

   Author

   More actions

   Sorry for delay was on holiday

   Extract of entries from one of the log files:

   Information: Microsoft.Neutron.OpenAI.Provider.WinAppSDKEpDetector[0]
   05:17:38.57 0 Provider 2/2: VitisAIExecutionProvider is in NotReady state. Downloading and ensuring provider is ready.
   Information: Microsoft.Neutron.OpenAI.Provider.WinAppSDKEpDetector[0]
   05:17:38.63 0 Provider VitisAIExecutionProvider download and ensuring ready attempt: Success
   Information: Microsoft.Neutron.OpenAI.Provider.WinAppSDKEpDetector[0]
   05:17:38.66 0 Provider 2/2: VitisAIExecutionProvider is now in Ready state. Now registering provider.
   Information: Microsoft.Neutron.OpenAI.Provider.WinAppSDKEpDetector[0]
   05:17:38.66 0 Provider 2/2: VitisAIExecutionProvider is successfully autoregistered and has ended in Ready state. It is installed at C:\Program Files\WindowsApps\MicrosoftCorporationII.WinML.AMD.NPU.EP.1.8_1.8.53.0_x64__8wekyb3d8bbwe\ExecutionProvider\onnxruntime_providers_vitisai.dll. Download validation status: Certified
   Information: Microsoft.Neutron.OpenAI.Provider.WinAppSDKEpDetector[0]

   output from script running as admin:

   remove-appxpackage uup://product/Windows.Workload.ExecutionProvider.VITISAI.amd64
   WindowsWorkload.EP.AMD.VitisAI.1.8_1.8.53.0_x64__8wekyb3d8bbwe
   MicrosoftCorporationII.WinML.AMD.GPU.EP.1.8_1.8.51.0_x64__8wekyb3d8bbwe
   MicrosoftCorporationII.WinML.AMD.NPU.EP.1.8_1.8.53.0_x64__8wekyb3d8bbwe
   WARNING: Failed to remove package: . Error: Access is denied.

   Deployment Remove operation with target volume C: on Package WindowsWorkload.EP.AMD.VitisAI.1.8_1.8.53.0_x64__8wekyb3d8bbwe from: failed with error 0x80070005. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
   Removed package: MicrosoftCorporationII.WinML.AMD.GPU.EP.1.8_1.8.51.0_x64__8wekyb3d8bbwe
   Removed package: MicrosoftCorporationII.WinML.AMD.NPU.EP.1.8_1.8.53.0_x64__8wekyb3d8bbwe

   output from foundry commands after doing above:

   C:\Windows\System32>foundry service init
   Successfully downloaded and registered the following EPs: VitisAIExecutionProvider.
   Valid EPs: CPUExecutionProvider, WebGpuExecutionProvider, VitisAIExecutionProvider

   C:\Windows\System32>foundry service restart
   Restarting service...
   🔴 Service is stopped.
   🟢 Service is Started on http://127.0.0.1:58330/, PID 4524!

   C:\Windows\System32>foundry model list --filter device=npu
   Alias Device Task File Size License Model ID

   qwen2.5-coder-0.5b NPU chat, tools 0.52 GB apache-2.0 qwen2.5-coder-0.5b-instruct-vitis-npu:2

   phi-4-mini-reasoning NPU chat 2.78 GB MIT Phi-4-mini-reasoning-vitis-npu:2

   qwen2.5-0.5b NPU chat, tools 0.52 GB apache-2.0 qwen2.5-0.5b-instruct-vitis-npu:3

   qwen2.5-coder-1.5b NPU chat, tools 1.25 GB apache-2.0 qwen2.5-coder-1.5b-instruct-vitis-npu:2

   phi-4-mini NPU chat, tools 3.60 GB MIT phi-4-mini-instruct-vitis-npu:2

   qwen2.5-coder-7b NPU chat, tools 4.73 GB apache-2.0 qwen2.5-coder-7b-instruct-vitis-npu:2

   qwen2.5-7b NPU chat, tools 5.20 GB apache-2.0 qwen2.5-7b-instruct-vitis-npu:2

   phi-3-mini-128k NPU chat 2.13 GB MIT phi-3-mini-128k-instruct-vitis-npu:2

   deepseek-r1-7b NPU chat 5.58 GB MIT DeepSeek-R1-Distill-Qwen-7B-vitis-npu:2

   phi-3-mini-4k NPU chat 2.13 GB MIT Phi-3-mini-4k-instruct-vitis-npu:2

   mistral-7b-v0.2 NPU chat 4.07 GB apache-2.0 Mistral-7B-Instruct-v0-2-vitis-npu:2

   So it now seems to be working, as I can both see and run models on NPU

   Thank you for responding

   👍React with 👍1Reacted by bmehta001
4. bmehta001

   self-assigned this

   on Apr 15, 2026
5. bmehta001 commented on Apr 15, 2026

   

   bmehta001

   on Apr 15, 2026

   Contributor

   More actions

   Great! I should have suggested to run foundry service stop before running the script to delete EPs as administrator, to avoid the WARNING: Failed to remove package: . Error: Access is denied message and make sure that there are no resources still bound to Foundry Local and thus not deleted.

   However, since you are now able to run VitisAI models on NPU successfully, it seems that enough stale files were deleted to fix the download and registration of the Vitis AI EP, so I will close this issue.
6. bmehta001

   closed this as completedon Apr 15, 2026
7. Nick Brady (nicholasdbrady)

   added a commit that references this issue on Apr 26, 2026

   fix: Foundry Local agent reliability + telemetry pipeline (#28)

   ...

   df12d55