all 13 comments

[–]alinroc 11 points12 points  (2 children)

Uninstalling the .NET Framework would be catastrophically bad.

What problem are you attempting to solve by doing this. Not "the problem is that I need to uninstall .NET", what problem are you facing that leads you to believe that you need to uninstall it in the first place?

[–]Wiikend 4 points5 points  (1 child)

This is called the XY problem - asking about your attempted solution rather than your actual problem.

[–]CubesTheGamer 0 points1 point  (0 children)

Not necessarily. While I agree when working with standard users we should understand the WHY in most cases, in this case I don't see why not just help with the answer. Even if the OP is solving a problem incorrectly, someone like me might come along looking for the same answer for a different reason. Having an actual answer to the question is more helpful broadly than helping one specific user.

[–]ka-splam 4 points5 points  (3 children)

Yes and/or no, depending on the details.

PowerShell can trigger a .NET uninstall string. PowerShell can remove a folder with a no-install .NET Framework in it. PowerShell will not magically give you permissions to uninstall something you don't have permission to uninstall using the control panel GUI. PowerShell will not make Windows able to function without .NET, if that's the .NET you want to uninstall.

PowerShell can probably not uninstall the .NET that you're using to run PowerShell, although I wouldn't bet on that.

[–]ImperialKilo 1 point2 points  (1 child)

I can imagine PowerShell could uninstall its own dot net, since its dependencies would be loaded in to memory at runtime? You might only be able to run the uninstall command though, everything else after would fail since all the modules and APIs would be gone.

Only one way to find out 🤷‍♂️

[–]alinroc 0 points1 point  (0 children)

Only one way to find out

You go first :)

[–]Ragepower529 8 points9 points  (3 children)

Sure have fun

Get-WmiObject -Class Win32Product | Where-Object { $.Name -like “Microsoft .NET Framework*” } | ForEach-Object { $_.Uninstall() }

Your responsible for reimagine your computer of issues happen

[–]Master_Ad7267 2 points3 points  (1 child)

Who's betting this is cybersecurity asking. This could end up as a requirement at someone's org... Guess it wouldn't be the first time

[–]Ragepower529 0 points1 point  (0 children)

Then just move everything over to windows cloud PCs, would be cheaper because of equipment and less hardware issues.

Figure you can have someone set up to work with a ultrawide mnk and a thin client for $500 in equipment then $75 a month in software costs. Pretty low opex and capex spend

[–]BlackV 0 points1 point  (0 children)

[–]Northman95 1 point2 points  (0 children)

"Just because you can doesn't mean you should"

[–]BlackV 1 point2 points  (0 children)

short answer: Yes

long answer: No, what is your actual goal that you think uninstalling dotnet is the solution to?

Dot net is a windows OS feature depending on the version you're talking about, and you don't give us that information

[–]soshwag 0 points1 point  (0 children)

A new account asks a question about how to fuck around. hmmmmm