Known issue: pac code commands fail in PAC CLI v2.5.1 and v2.6.3

[eschavez]

We have identified an issue affecting PAC CLI code commands in version 2.5.1.

When running any pac code command, users may encounter the following error:
Sorry, the app encountered a non-recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Session Id: , Exception Type: System.IO.FileNotFoundException

As a mitigation, we recommend installing an earlier version of PAC CLI (v2.4.1). This can be done by uninstalling the currently installed CLI and reinstalling a previous version using your preferred installation method - Installation instructions here.

We are investigating the root cause of the issue and will provide updates on this thread as more information becomes available.

[eschavez]

Update — April 13, 2026

We have a partial fix to share. PAC CLI version 2.6.3 resolves the pac code command failures, but only when installed via the MSI installer (Windows). The .NET tool (dotnet tool install) version of 2.6.3 remains affected and is not yet fixed.

Current recommendation:

• Windows users: Switch to the MSI installer. First uninstall any existing dotnet tool version, then install via MSI:

  dotnet tool uninstall --global Microsoft.PowerApps.CLI.Tool
  

  Then download and install the MSI: https://aka.ms/PowerAppsCLI
  👉 Full MSI install instructions

  Once installed, run pac install latest to get 2.6.3.

• Non-Windows users / .NET tool users: The dotnet tool version is not yet fixed. Please continue using v2.4.1 as the interim workaround:

  dotnet tool uninstall --global Microsoft.PowerApps.CLI.Tool
  dotnet tool install --global Microsoft.PowerApps.CLI.Tool --version 2.4.1
  

  👉 .NET tool install instructions

We are continuing to investigate the root cause for the .NET tool path and will post another update here once resolved. Apologies for the continued disruption.

[eschavez]

Update — PAC CLI v2.6.4

Version 2.6.4 resolves the issue with the .NET installer. If you were affected, upgrading to v2.6.4 should restore normal functionality.

Thank you for your patience while this was being addressed.

[wmCmo]

Thank you for fixing this so promptly.