microsoft / microsoft/vscode-powerquery-sdk
MakePQX Verify fails with FileLoadException
@mattmasson is already working on this.
Since May 12, 2026.
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
0.7.1
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
Windows 11
VSCode version
1.118.0
PQSdkTool Path
unsure
Bug Description
When I run MakePQX verify test.pqx it fails with this exception:
System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.Threading.Tasks.Extensions, Version=4.2.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
at System.Text.Json.JsonSerializer.Serialize[TValue](TValue value, JsonSerializerOptions options)
at Microsoft.Mashup.MakePQX.Program.<>c__DisplayClass4_4.<Main>b__8()
at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
at Microsoft.Mashup.MakePQX.Program.Main(String[] args)
Steps to Reproduce
- Build .mez file using the extension
- Use
MakePQX packto create a .pqx file - Use
MakePQX signto sign the .pqx file - Run
MakePQX verify test.pqx
Actual Experience
FileLoadException occurs upon running MakePQX verify test.pqx.
Expected Experience
No response
Additional Context
I downloaded version 2.145.5 of the Microsoft.PowerQuery.SdkTools nuget package and used that version of MakePQX and it worked without throwing an exception. I haven't tried every version between 2.145.5 and 2.153.3, but I know for sure that 2.150.3 and 2.153.3 have this same issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.