.NET Framework troubleshooting: How to set registry key HKLM\Software\Microsoft\.NETFramework\InstallRoot to point to the .NET Framework install location

Question

I'm attempting to uninstall Malwarebytes using their uninstaller tool.

Running it displayed:

.NET Updates not found

.NET 4.0 Updates are required, but not detected on this machine.

Please check for the latest .NET updates using Windows Update and then try again.

The Windows version / build:  1909 (OS Build 18363.1139)

When the NET Framework troubleshoot was ran it displayed:

HPSF_Tasks.exe - .NET Framework Initialization Error

Please set registry key

HKLM\Software\Microsoft.NETFramework\InstallRoot to point to the .NET Framework install location

Using regedit the path to HKLM\Software\Microsoft.NETFramework was seen.

InstallRoot was not seen.

1. How do you set the registry key if InstallRoot is not seen?
2. What is the .NET Framework install location?

These were displayed below .NETFramework:

Advertised

AssemblyFolders

NGen

NGenQueue

policy

Security

v2.0.50727

v3.0

v4.0.30319

Windows Presentation Foundation

These were the logs that the tool displayed that it was sending to Microsoft:

C:\windows\windowsupdate.log

C:\windows\logs\cbs\cbs.log

C:\Users\a\AppData\Local\Temp\FixDotNet.log

C:\Users\a\AppData\Local\Temp\NetFxSetupEvents.txt

C:\Users\a\AppData\Local\Temp\dd_netfxrepairtool(1)_decompression_log.txt

C:\Users\a\AppData\Local\Temp\dd_netfxrepairtool(2)_decompression_log.txt

C:\Users\a\AppData\Local\Temp\dd_netfxrepairtool_decompression_log.txt

C:\Users\a\AppData\Local\Temp\Microsoft .NET Framework Repair Tool_20210125_084646814.html

C:\Users\a\AppData\Local\Temp\Microsoft .NET Framework Repair Tool_20210125_084929381.html

C:\Users\a\AppData\Local\Temp\Microsoft .NET Framework Repair Tool_20210125_223423722.html

C:\Users\a\AppData\Local\Temp\FixDotNet_HKCR_Installer.regdump

C:\Users\a\AppData\Local\Temp\FixDotNet_HKLM_Installer.regdump

Some images:

Answer 1

How to set registry to point to the .NET Framework install location remains unknown.

The problem was fixed by performing an in place upgrade repair.