microsoft / microsoft/Microsoft-Fabric-workload-development-sample

[Bug] Workload upload fails on Windows: valid .nupkg rejected with “Please ensure you upload a valid .nupkg package" file”

Open
#267 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
58
Forks
39
PR merge metrics
No merged PRs in 30d

Description

Workload Manifest Schema Version

N/A

Description

After updating to Windows 11 OS Build 26200.8xxx, workload uploads can fail because the system may not correctly recognize .nupkg files during validation.

Error: “Please ensure you upload a valid .nupkg package file.”
✅Workaround (temporary)

On the machine used to upload the workload package:

  1. Open Registry Editor (regedit)
  2. Go to: HKEY_CLASSES_ROOT.nupkg
  3. Ensure:
    • (Default) = (value not set)
    • ContentType = not present (delete it if it exists)
Image
  1. Restart the machine (may be required) and retry the upload
Estimated fix date: 2026-05-03 (estimate; may change).
Steps to Reproduce
  1. Install the latest Windows updates so the device is running Windows 11 OS Build 26200.8xxx.
  2. In Microsoft Fabric Admin portal → Workloads → Upload workload, try uploading a valid .nupkg (NuGet) package.
Expected vs Actual Behavior
Expected behavior

Uploading a valid .nupkg workload package in Microsoft Fabric Admin portal → Workloads → Upload workload should succeed and the package should be accepted by the portal.

Actual behavior

After recent Windows updates (Windows 11 OS Build 26200.8xxx), the upload fails and the portal shows:
“Please ensure you upload a valid .nupkg package file.”

Relevant Logs / Error Codes

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the upload in the Microsoft Fabric Admin portal on Windows 11 OS Build 26200.8xxx with a valid .nupkg package, then compare behavior with the documented registry workaround. Done means the portal accepts the valid package without requiring that workaround; no source file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.