Error whilst uninstalling .NET 6 SDK - api-ms-win-core-path-l1-1-0.dll is missing
See original GitHub issueDescribe the bug
An error dialog shows up whilst uninstalling .NET 6 SDK, saying that api-ms-win-core-path-l1-1-0.dll
is missing. The uninstallation still proceeds though, and appears to be successful.
To Reproduce
- On a Windows machine (mine is Windows 7 x64)
- Install .NET 6 SDK 6.0.200
- Uninstall .NET 6 SDK 6.0.200
- Error dialog will show up
Exceptions (if any)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Remove the .NET runtime and SDK
This article describes how to uninstall .NET. You'll need to determine which versions of the .NET Runtime and SDK are currently installed, ...
Read more >Unable to uninstall .NET Core SDK install with visual studio ...
1 Answer. To uninstall sdk versions that were installed via the Visual Studio installer you need to modify your installation using the ...
Read more >NETSDK1045: The current .NET SDK does not support ...
This error occurs when the build tools can't find the version of the .NET SDK that's needed to build a project. This is...
Read more >Fixing my .NET 6 SDK installation after ... - Alexander Zeitler
NET 6 SDK was installed using the dotnet6 package from Ubuntu. ... Next sudo apt update && sudo apt install dotnet-sdk-7.0 : no...
Read more >Unable to locate the .NET SDK: The Reasons - Hamid Mosalla
First things first, removing some low hanging fruits. First wee need to see if the Sdk is actually installed. Navigate to C:\Program Files\ ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve fixed this for 6.0.4xx
Ok, I can repro this (Win7 Enterprise). I also noticed that the executable reports itself as “Microsoft .NET Framework”, which is definitely not true.