Closed hyperio546 closed 7 months ago
Oh and this is broken
Issue with your box I'm pretty sure, not winget. Running latest perfectly fine here. Had 11 do that before, something caused all non-system packages to just completely give the ghost, not sure what causes it unfortunately
Issue with your box I'm pretty sure, not winget. Running latest perfectly fine here. Had 11 do that before, something caused all non-system packages to just completely give the ghost, not sure what causes it unfortunately
Oh 🙁
@themoonmeetsthesun,
What operating system version are you using? Is it a stable release or an insider build?
We do include the license file in the GitHub releases, which is what the error appears to be related to, but I'm not sure that would resolve the problem if this is affecting the entire system.
Have you taken a look at our troubleshooting guide?
You could try submitting feedback via feedback hub so we can get logs and see if there is anything we can do.
It's difficult to explain It was originally windows 10 enterprise ltsc 2021 But after activation it became windows 10 iot something
But this is a serious issue. I think I have seen this same issue somewhere else too.
It was originally windows 10 enterprise ltsc 2021
For Windows SKUs that don't have a built-in Microsoft Store, you can follow the unofficial guide at https://github.com/microsoft/winget-cli/discussions/1956#discussion-3886961 to get it up and running.
If you've followed that guide and it still doesn't work then I would recommend you to rebuild your OS by using your Windows ISO image. You can do this by launching setup.exe
in File Explorer and run through the setup process. Make sure to choose "Keep personal files and apps".
Also, running WinGet on these SKUs should be considered experimental and unsupported so you may not always get the help you need.
Sometimes you may need to resort to a series of "hacks"—such as running WinGet unpackaged or manually creating the AEAs—to get it up and running.
But after activation it became windows 10 iot something
You will need to contact your company or organization and check with them if they gave you the wrong key for activation.
First of all its a vm Second I don't work anywhere Third it's tiny10 by ntdev who made it Fourth I use that for experiments because my laptop is shit
Soo I will try that once my main laptop finishes resetting and then I will come back with the results later.
First of all its a vm Second I don't work anywhere Third it's tiny10 by ntdev who made it Fourth I use that for experiments because my laptop is shit
Fifth it doesn't make sense for me to use the full windows 10 just for experimenting
tiny10 by ntdev
Tiny10 has limited/no support for AppX packages. You won't be able to use winget, unfortunately (unless you compile it yourself).
tiny10 by ntdev
Tiny10 has limited/no support for AppX packages. You won't be able to use winget, unfortunately (unless you compile it yourself).
Uhh really? Because I did get it working on another installation of it on another machine.
This issue is quite old we're now on WinGet 1.7 and this issue should be resolved.
This issue is quite old we're now on WinGet 1.7 and this issue should be resolved.
bro really closed it after 2 years 💀
Brief description of your issue
Winget doesn't work at all
Steps to reproduce
Install appinstaller and required dependencies And it won't start
Expected behavior
Winget to work
Actual behavior
Winget doesn't work
Environment