[Misdetech of the version]: Microsoft.DotNet.DesktopRuntime.6 #3004
Comments
TheBossMagnus
added
the
Issue-Bug
ghost
added
the
TheBossMagnus
changed the title
|
if you |
|
no one is listed |
|
I missed the "<" indicating "less than 6.0.5". We didn't have a manifest for the version installed on the system, so it was determined to be less than the earliest manifest. I'm not sure why 6.0.17 isn't showing up in list. |
|
@mthalman do you have any ideas on this one? |
|
Be aware of the difference in major version here between what is installed and the upgrade version. It's showing 5.0.17 as installed and 6.0.7 as the upgrade version. Those are different major versions. It shouldn't attempt to recognize that as an upgrade because they have different package IDs: Microsoft.DotNet.DesktopRuntime.5 versus Microsoft.DotNet.DesktopRuntime.6. @denelon - Why would it be crossing package IDs like this? |
|
It's likely that we don't have the manifests for the older versions with the "AppsAndFeatures" keys, so heuristics are trying to detect which package might match. @JohnMcPMS can you confirm or deny? |
|
There is a manifest for the 5.0.17 version: https://github.com/microsoft/winget-pkgs/blob/master/manifests/m/Microsoft/DotNet/DesktopRuntime/5/5.0.17/Microsoft.DotNet.DesktopRuntime.5.installer.yaml. It was the one and only version of it that was published before becoming EOL. |
What about under |
|
|
I'm wondering if this is an artifact from before the packages were split out into the new identifiers. |
fixed |
|
Great call @Trenly! |
|
Sorry for reopening, but, as you can see, the issues repeat appearing for each update. |
I think that is a different issue entirely. If you look closely, it is downloading and installing the x64 package, when it is the x86 package that is reporting an upgrade is available. This new behavior seems to be very similar to microsoft/winget-pkgs#2243 As a workaround, try running |
|
|
|
maybe install instead of upgrade? Forgot upgrade doesn't have the --architecture switch |
|
|
Oops; Looks like I messed up the command itself facepalm. It isn’t |
|
Related to: |
|
Sorry for the late response...
|
|
I'm having a similar problem – winget is mixing up two completely different versions of .NET runtime, I have both in their latest versions (3.1.28 and 6.0.8 respectively): |
|
I have the same issue with @finn-cz : Besides I also had the issue that winget trying to upgrade Microsoft ASP.NET Core 6.0.8 - Shared Framework (x86) by downloading x64 version. I solved it by downloading and installing x86 version manually. Since some old projects may need 3.x, uninstall is not an option. |
|
I'm also facing something around this: but |
Same boat. |
I also see always an upgrade, but 6.0.20 is now latest 6 version: List shows correct 6 and 7 identifier: But on a different Window 10 system it works fine |
Not sure why it defaults to 6 with pretty much the same command, except filtering on something different. The |
|
After installing the .net8 Desktop Runtime, the issue is solved: |
|
@MagicAndre1981 Not really. It might not show available versions in this list, but running |
no, it shows nothing to upgrade as .net6 is now Microsoft.DotNet.DesktopRuntime.6, .net7 is Microsoft.DotNet.DesktopRuntime.7 and .net8 is Microsoft.DotNet.DesktopRuntime.8 so every version is now seperate. only wired thing is that Microsoft.DotNet.Runtime.6 in the list |
|
For me it looks like this: What version of winget are you using? EDIT: Just upgraded to |
|
I'm using 1.6.3133 on Windows 10 22H2 |
|
How did you install .net8 runtime? Via winget? |
|
yes, I installed it after updating 6 and 7. And after this I ran |
|
I installed it after manually downloading the installer. Now, after installing again via winget I still get this: So, there's a difference in how you install it, clearly. This has also be mentioned in this thread. It will probably come back for you when updating via Windows Update. Alas, the issue isn't resolved. |
|
@MagicAndre1981 Interestingly, my workplace Windows 10 computer looks as clean as yours. |
it worked on all PCs/VMs except 1 laptop. And here it suddenly worked after installing .net 8 . This whole matching is confusing |
|
I just had this weird behaviour, when trying to upgrade from 6.0.22 to 6.0.25. winget upgrade winget upgrade Microsoft.DotNet.DesktopRuntime.6 winget upgrade I seems to download the correct URL, at the Apps & features also shows the hopefully correct version for .NET Runtime: Not sure this fit here, if not please feel free to move this to a new issue if needed. |
|
i have this |
alright the winget uninstall Microsoft.DotNet.DesktopRuntime.6 didn't work the first time so i closed cmd and started again, had to click again on some yes and it's gone now. i know what that means, but seriously, who still needs .NET desktop runtime anyway? |
this is required to run .net 6 WinForms/WPF apps. If you only run cli tools you can use the normal .net runtime |
i will wait until some program begs me to install Microsoft.DotNet.DesktopRuntime.6 . there is version 8 already just like java 22 so i don't give a damn about ms products. except handbrake |
|
Running the following command, should solve the problem: |
|
Nope. Unfortunately not. |
Hey there! Thanks for the heads up. If you're running into trouble with "Microsoft.DotNet.DesktopRuntime.X," here's a quick fix you might want to try. Just swap out 'X' with the version you're working with:
When I said these steps "should" work, I meant it's not a one-size-fits-all. There might be some exceptions due to different setups. About the downvote, I get where you're coming from. Feedback is gold, especially if something didn't pan out as expected. If it's just the one person's experience, I'm keen to hear more, especially if anyone else tried and hit a snag. It helps everyone figure things out together. If you gave it a shot and it's still a no-go, could you share what went wrong? More details could help us all get to the bottom of this faster. Cheers for jumping in on this, and looking forward to hearing from you! |
|
Well, apparently I had to uninstall first. And after reinstalling |
|
can someone paste the solution again plz? |
|
Uninstall dotnet-desktop-6, reinstall dotnet-desktop-6. |
|
Still the same problem. |
|
i'll skip it on unigetUI |
Please confirm these before moving forward
Category of the issue
Other
Brief description of your issue
The version detected by Winget is 6.0.5
Anyway, the installed and lastest is 6.0.7
Steps to reproduce
..
Actual behavior
If i upgrade the app get reinstalled for no reason
Expected behavior
..
Environment
Screenshots and Logs
WinGet-2022-07-27-16-58-26.048.log
WinGet-2022-08-01-16-18-59.865.log
The text was updated successfully, but these errors were encountered: