How To Install .net 4.8 On Windows Server 2019

#1

activity-disengage-residuum

• 
• Members
• 2 posts
• OFFLINE

• Local time: 07:13 AM

Posted 21 September 2021 - 08:38 PM

Hi,

I've been struggling with a software installation that has seen united states of america restore several servers from backup. I've reached a indicate where I've replicated this trouble on a completely make clean installation:

- Install a new Windows Server 2019, Desktop Environment

- Use all Windows Updates.

- Install .net 4.8 directly from Microsoft: https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-web-installer

The server is now completely cleaved. Server Manager wont start. Several random services won't start. Consequence Viewer doesn't open.

At that place's a Microsoft thread here where two people reported this result a month ago:

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/windows-server-2019-and-net-4-8/m-p/2660319

And a Reddit thread: https://www.reddit.com/r/sysadmin/comments/ps1tni/net_48_seems_to_have_broken_server_2019/

I'm somewhat floored past this trouble. If things are broken as we're seeing, I'd expect a lot more noise, so I actually don't know where to go with this. I'1000 opening a Microsoft support case right at present, but I based on contempo cases it'll be a few weeks before a response.

Any suggest appreciated.

• Back to summit

BC AdBot (Login to Remove)

• 
• BleepingComputer.com
• Annals to remove ads

#2 action-undo-balance

action-disengage-balance

• Topic Starter


• 
• Members
• 2 posts
• OFFLINE

• Local time: 07:13 AM

Posted 22 September 2021 - 08:57 PM

Afterward many many hours of research on this I've gotten to the bottom of this. The consequence is this TLS 1.2 enforcement script:

https://docs.microsoft.com/en-usa/azure/agile-directory/hybrid/reference-connect-tls-enforcement#powershell-script-to-enable-tls-12

Only a few days ago this script was unlike - it wasn't wrapped in that "if" statement. Y'all tin see the commit hither:

https://github.com/MicrosoftDocs/azure-docs/commit/e2110e5c7c59359b4ffbcb120bcfa9e736f7d7c7#diff-fe074957cf8e301b788a062c973bc4248318e58492057dff730f1f86f2718f3e

The problem is this line:

New-Item 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319' -Force | Out-Nix

Which creates that path (if it doesn't be). If it does exist (which information technology does past default on Server 2019) it empties it.

• Back to height

#3 sflatechguy

sflatechguy

• 
• BC Advisor
• two,701 posts
• OFFLINE

• Gender: Male
• Local fourth dimension: 03:thirteen PM

Posted 25 September 2021 - 11:03 AM

You'd think they'd write some code to check if that registry cardinal already exists kickoff, and only run New-Item if it doesn't. The -Force option is conspicuously a problem also -- information technology will overwrite what is already there.

• Back to top

#4 LordHellFire

LordHellFire

• 
• Members
• 1 posts
• OFFLINE

• Local time: 08:xiii PM

Posted 13 March 2022 - 04:23 PM

Merely experienced this problem on ONE of our three DC'south. (commencement of march 2022)
Took me several days to find this post, which turned out to exist the exact same problem.
I accept to assume, since your posts are from september 2021 describing the error as being only there for a few days before Microsoft fixed it; that Microsoft made the same error once again.

I was unable to reinstall .net as it was already installed.

Simply I could run REPAIR using the /uninstall switch on the installer.

 - However, this problem did non get fixed, every bit the installer ONLY recreates the latest version regkey .

 - That means that any program dependent on an earlier version of .net, cannot run.

I was unable to run "Programs and Features" under APPS, as information technology is, every bit you may have guessed, dependent on a very early version of .net.

Now, Microsoft COULD get in much easier to fix this trouble by letting the REPAIR function of the .net installer recreate ALL previous versions worth of redirects in the registry, not only the newest version.

Also, a catchall for issues pertaining to programs dependent on older versions; if a program is dependent on an older version and the registry has no knowledge (encounter missing .reg below), run a check if a newer .net is incorrectly installed (expect for other clues to its being). If then, then ask to run a repair on .net, don't just try a new download.

To fix the problem, I had to manually import regkeys copied from my workstation.

Instant gear up. Could offset programs after that, but did restart the DC anyhow, just to brand certain all dependencies would start upwardly.

---

Windows Registry Editor Version five.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"AspNetEnforceViewStateMac"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0,Contour=Customer]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.one]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.ane,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.two]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2,Profile=Customer]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.five.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.v.two]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.v.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.six]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.half dozen.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.six.two]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.seven]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.vii.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.8]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\Default]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"AspNetEnforceViewStateMac"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1,Contour=Customer]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.two]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2,Contour=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3,Contour=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.five.ane]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.five.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.two]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.seven]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.one]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.eight]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\Default]

---

Hope this helps any other poor soul who stumbles onto this mail.

• Back to top

Source: https://www.bleepingcomputer.com/forums/t/758800/net-48-kills-server-2019/

Posted by: ramseythreake86.blogspot.com

Share this post