docs
docs copied to clipboard
Can't find the Apps & Features dialog
Type of issue
Missing information
Description
Don't know if this is "missing information" or "wrong information". The page refers to the "Apps & features dialog". I've checked both Windows 10 and Windows 11, and I can't find that dialog. The Settings app has a page called "Apps > Installed apps", but that page does not display any of the installed dotnet runtimes.
On my Windows 11 Pro computer, this is the list of Settings pages under the Apps page. Note that I have "Installed apps", not "Apps & features".
Page URL
https://learn.microsoft.com/en-us/dotnet/core/install/remove-runtime-sdk-versions
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/install/remove-runtime-sdk-versions.md
Document Version Independent Id
090b8fbd-39e6-b754-e1da-890b1123f2c4
Article author
@adegeo
Metadata
- ID: 4efe9b33-ff9f-3b37-e8bd-a34c0a77bd1e
- Service: dotnet-fundamentals
- Sub-service: install
Thank you for reporting this. Yeah looks like Windows changed the design around 🫤 I'll add this to a sprint to get it fixed.
Thanks @adegeo. Just FYI, the Visual Studio Installer tells me to remove the .Net 7 Runtime because it is out of support (I think that's the right name... I'm doing this from memory). That led me to trying to figure out how to remove that runtime. The ".NET Uninstall Tool" (dotnet-core-uninstall) doesn't see that runtime and thus won't uninstall it. The "Installed Apps" app doesn't see any of the .Net runtimes. So, I'm still trying to figure out how to (1) determine if anything depends on .Net 7 Runtime, and (2) uninstall that runtime.
Sorry for the delay in responding @IndigoHealth
This is really wrong. I corrected these statements in the next comment. ~Visual Studio has its own copies of .NET it manages, and they don't apply system-wide. For example, if you used Visual Studio to install .NET 7, your system itself doesn't have and can't use .NET 7, only Visual Studio can. Unless you're working with anything .NET 7 in Visual Studio, you can remove it through the Visual Studio installer.~
- Open the Visual Studio Installer.
- Click Modify on the version of VS you want to update.
- Select Individual Components.
- Uncheck the items you want to remove.
- As you can see in the following screenshot, I too have it installed, I'm not worried about leaving it there. But I wouldn't create a new project targeting it.
I'm sorry, I was a bit wrong in my assumptions. I think I have old knowledge mixing with new behaviors. 😁
So, if you use Visual Studio to install the individual runtimes and the .NET SDK, you need to use VS to remove them. If you install them via the Windows Installer downloads (or the winget package manager) you use the Installed apps system (formerly add remove programs..) to remove them.
Regarding the SDK
There is only the .NET SDK to install via Visual Studio. This is the latest SDK (v8 right now) and it lets you compile and target all .NET versions, including older ones such as 5 or 7.
Regarding the Runtimes
While you can compile projects targeting older versions, you can't run them without the corresponding runtime. So those individual components for the runtime, like .NET 7.0 Runtime let you run apps targeting .NET 7. I would keep those installed so you can run those apps if you need to.
The error you likely saw was that you opened a project targeting .NET 7 and it was letting you know you're compiling to a runtime that is out of support and won't receive security updates.
If you target a .NET version that you don't have the corresponding runtime, VS will prompt you to install the runtime when you open that project.
The error you likely saw was that you opened a project targeting .NET 7
No. Sorry, I guess I wasn’t very clear. This is a warning that the visual studio installer gives me when I install the latest update. It tells me I should remove that runtime because it is out of support.
Bob
Sent from my iPhone. Bizarre, humorous, or nonsensical autocorrects are a "feature".
On Aug 13, 2024, at 12:18 PM, Andy (Steve) De George @.***> wrote:
The error you likely saw was that you opened a project targeting .NET 7
Secured by Paubox - HITRUST CSF certified https://www.paubox.com
Thank you! I think this is exactly what I was looking for. It sure would be nice if this information was easy to discover.
Bob
Sent from my iPhone. Bizarre, humorous, or nonsensical autocorrects are a "feature".
On Aug 13, 2024, at 11:46 AM, Andy (Steve) De George @.***> wrote:
Sorry for the delay in responding @IndigoHealthhttps://github.com/IndigoHealth
Visual Studio has its own copies of .NET it manages, and they don't apply system-wide. For example, if you used Visual Studio to install .NET 7, your system itself doesn't have and can't use .NET 7, only Visual Studio can. Unless you're working with anything .NET 7 in Visual Studio, you can remove it through the Visual Studio installer.
- Open the Visual Studio Installer.
- Click Modify on the version of VS you want to update.
- Select Individual Components.
- Uncheck the items you want to remove.
- As you can see in the following screenshot, I too have it installed, I'm not worried about leaving it there. But I wouldn't create a new project targeting it.
image.png (view on web)https://github.com/user-attachments/assets/9d1752a0-cf55-474d-b71e-d16e71d1fe39
— Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs/issues/42017#issuecomment-2286898282, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYUHGW4BJNJRBMZXJCUTULZRJH7HAVCNFSM6AAAAABL47FVUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBWHA4TQMRYGI. You are receiving this because you were mentioned.Message ID: @.***>
[https://get.paubox.com/hubfs/Email%20folder/green_lock_v2.png]Encryption verified by Pauboxhttps://www.paubox.com - HITRUST CSF Certified