You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
After installing dotnet 9 run time 9.0.2 it write a record in registery.
Please see 👍
After uninstalling dotnet 9 run time 9.0.2 from control panel the record in registery still exist.
Steps to Reproduce
Install dotnet runtime 9.
It has record in resgistry.
Uninstall the dotnet runtime 9
THe record in registry not deleted.
Link to public reproduction project repository
...
Version with bug
9.0.0 GA
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
9.0.30 SR3
Affected platforms
Windows
Affected platform versions
.....
Did you find any workaround?
.....
Relevant log output
......
The text was updated successfully, but these errors were encountered:
danies8
changed the title
Dotnet Run time 9 not clean from registery when unistalling it
Dotnet Runtime 9 not clean from registery when unistalling it
Mar 23, 2025
danies8
changed the title
Dotnet Runtime 9 not clean from registery when unistalling it
Dotnet Runtime 9 not clean from registry when unistalling it
Mar 23, 2025
Do you have any other .NET versions installed? The host is the only component that's shared across all .net instances and I thought that even if you uninstalled a particular sdk or runtime, we wouldn't revert the host. CC @joeloff to confirm.
Description
Hi,
After installing dotnet 9 run time 9.0.2 it write a record in registery.
Please see 👍
After uninstalling dotnet 9 run time 9.0.2 from control panel the record in registery still exist.
Steps to Reproduce
Link to public reproduction project repository
...
Version with bug
9.0.0 GA
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
9.0.30 SR3
Affected platforms
Windows
Affected platform versions
.....
Did you find any workaround?
.....
Relevant log output
The text was updated successfully, but these errors were encountered: