microsoft / microsoft/winget-cli

DSC Export creates duplicate IDs

Open
#6,353 0 comments 1 reaction 1 assignee View on GitHub

@JohnMcPMS is already working on this.

Since Jul 15, 2026.

Command-Configure Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Relevant area(s)

WinGet CLI

Relevant command(s)

winget configure

Brief description of your issue

I ran winget configure export --all -o <path> and attempted to use the exported file on a new machine. The file errored out with a duplicate ID error.

Steps to reproduce

Have WinGet Studio and WinGet Create installed, then run a DSC Export

Expected behavior

IDs would be checked for uniqueness

Actual behavior
PS C:\Users\kaleb> winget configure H:\CORSAIR-JLU545\winget-dsc-export-2026-07-05.winget --suppress-initial-details --accept-configuration-agreements --disable-interactivity
You are responsible for understanding the configuration settings you are choosing to execute. Microsoft is not responsible for the configuration file you have authored or imported. This configuration may change settings in Windows, install software, change software settings (including security settings), and accept user agreements to third-party packages and services on your behalf.  By running this configuration file, you acknowledge that you understand and agree to these resources and settings. Any applications installed are licensed to you by their owners. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages or services.
Microsoft.WinGetStudio/Settings [Settings-0]
  The configuration contains the identifier `Settings-0` multiple times.
Microsoft.WinGetCreate/Settings [Settings-0]
  The configuration contains the identifier `Settings-0` multiple times.
Some of the configuration was not applied successfully.
Environment
Winget v1.29.280 for both export and import; x64; Win11 Pro 25H2

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.