[CLI] EastUS region causing issue on loading models

[PantsBandit]

I'm running Foundry Local 1.2.1 core and SDK and the new .10 CLI release. I have tried the older CLI version which loads the CPU and GPU models but not NPU. QNNExecutionProvider loads and the Foundry log file does not include any errors.

Snapdragon(R) X2 Elite Extreme - X2E94100 - Qualcomm(R) Hexagon(TM) NPU
30.0.220.11010
2026-01-26

I read through the various other closed issues that are similar and tried everything they included to no avail. At this point I am stuck.

[samuel100]

Thanks for raising an issue @PantsBandit. What happens if you list using a filter:

foundry model ls --device npu

?

We have an issue at the moment where there are no detailed logs (see #790). My guess is that the EP has not downloaded and/or registered correctly. Do you have organisation Windows Update policy that could block a Windows update? Do you have any Windows Updates that are currently scheduled to be updated and are blocking the EP download?

See https://learn.microsoft.com/en-us/windows/ai/new-windows-ml/execution-provider-errors for more details on unblocking WindowsML issues.

[PantsBandit]

Alright, I figured out my problem.
I initially encountered the issue where the model list would not load, which led me to this issue https://github.com/microsoft/Foundry-Local/issues/752. I used the JSON file from the fix. Actually taking the time to review the JSON file identified the fact that it does not include the NPU models!
I deleted the JSON file and tried to reload the model list which still continued to fail. In your response to the above issue you mention automatic region detection, I am east coast, so I installed my VPN and connected to California.
It appears changing my region fixed my problem as I was able to successfully load the model list which now includes NPU models.

Turning off the VPN and restarting Foundry, the model list command still works fine with no errors in the log.
I'm happy to provide additional information if needed, otherwise please close this issue.

Thanks!

edit: Clarified how the issue 752 was one of my initial problems back when I started trying to get Foundry to work.

[samuel100]

Many thanks for the update @PantsBandit. On our side we need to bump the Foundry Local SDK version in the CLI to 1.2.1, which has an enhanced fallback methodology that would have resolved your issue. I am going to update the title of the issue to align with the eastus issue and keep it open until we bump to 1.2.1.

Related to #757