What does configure --enable do? Why is it so slow? #5164
-
|
To be clear I understand that it ETA: I also find that using the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
When you install WinGet, by default it installs what is known as a Stub-package. In effect, this Stub is just the core functionality of WinGet and the minimal amount of libraries needed for it to run. When you use One way to avoid the long delay of As to why it takes an oddly long time to actually run a configuration, that I don't know |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, so it's downloading things off the internet! That explains a lot, thank you! Also, to be clear... applying a configuration to a single app isn't supposed to take several minutes, right? |
Beta Was this translation helpful? Give feedback.
-
|
Applying a configuration to a package will depend on how the resource is built. Without some specifics (ideally the configuration file), it's hard to tell how long it "should" take. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah that's fair. Here's the file. |
Beta Was this translation helpful? Give feedback.
When you install WinGet, by default it installs what is known as a Stub-package. In effect, this Stub is just the core functionality of WinGet and the minimal amount of libraries needed for it to run. When you use
winget configure --enable, WinGet downloads and installs the rest of the package - giving you the full WinGet package instead of just the Stub. Sincewinget configureis mostly for power-users, and the everyday user likely won't use it, the Stub package avoids file and data transfer unless the feature is actually going to be used.One way to avoid the long delay of
winget configure --enableis to directly install the Full MSIX package directly from the GitHub releases. Doing so …