@Yoann same issue here. Clean install of Windows Server 2019 latest build, install .NET Framework offline installer 4.8, reboot and boom. Many native control panels, like Server Manager, requesting some 4.0.... version of .NET framework instead, failing to load.
I had the same issue and received zero help or support from Microsoft. Dell support googled and read back to me everything I had googled and tried already. Importing the above registry information fixed it without a reboot.
@DavidSherrill This is the exact fix! For us, our RMM tool stopped working on a server 2019 standard server. It's services wouldn't start. Event Viewer complained about .net. Also server manager wouldn't open with the exact message you mentioned. Applying this fixed it all. thanks!!
YOU ARE AN ABSOLUTE LEGEND! THANK YOU! THIS IS THE ONLY SOLUTION THAT WORKED! Every other solution I've googled of this problem has been some variation of "turn net framework on/off in the "turn windows features on or off" app" or "reinstall the newest version of .net" or "did you try restarting your computer?" (OF COURSE I TRIED RESTARTING MY COMPUTER!! DO THEY THINK I'M AN INFANT??)
Please excuse my novice status displayed in this question, but does one simply copy/paste the text in your registry update file, and does the resulting text file require the line number entries as displayed in your post?
01/14/2020: This post has been updated with information about the Microsoft .NET Framework 4.8 for Windows Updates released on January 14, 2020 via Windows Update/WSUS/Catalog to include the servicing fixes since the .NET Framework 4.8 August 2019 Windows Update. Apart from the servicing fixes, there is no change in the .NET Framework 4.8 product from the August 13th, 2019 Windows update. Please see the FAQ section below for additional information about this refresh and the Cumulative update blogposts for details on the servicing fixes.
We are happy to announce that Microsoft .NET Framework 4.8 has been refreshed and is now available on Windows Update, Windows Server Update Services (WSUS) and Microsoft Update (MU) Catalog. This release includes all quality and reliability fixes since the .NET Framework 4.8 initial release.
The updated .NET Framework 4.8 installers (which include the additional quality and reliability fixes) are available for download. * Web Installer* Offline Installer* Developer Pack Installer* All Packages
WPF: * Fixed a handle leak during creation of a Window in WPF applications that are manifested for Per Monitor DPI V2 Awareness. This leak may lead to extraneous GC.Collect calls that can impact performance in Window creation scenarios. [845699, PresentationFramework.dll, Bug]* Fixed a regression caused by the bug fix involving bindings with DataContext explicitly on the binding path. [850536, PresentationFramework.dll, Bug]* Fixed crash due to ArgumentNullException when loading a DataGrid containing a ComboBox while automation is active. For example, when navigating Visual Studio to the Text Editor\C#\Code Style\Naming page in Tools\Options. [801039, PresentationFramework.dll, Bug] You can see the complete list of improvements for .NET Framework 4.8 in the .NET Framework 4.8 release notes.
WSUS administrators will see this update in their WSUS admin console. The update is also available in the MU Catalog for download and deployment. When you synchronize your WSUS server with Microsoft Update server (or use the Microsoft Update Catalog site for importing updates), you will see the updates for .NET Framework 4.8 published for each platform.
Enterprises may have client machines that connect directly to the public Windows Update servers rather than to an internal WSUS server. In such cases, an administrator may have a need to prevent the .NET Framework 4.8 from being deployed to these client machines to allow testing of internal applications to be completed before deployment.
In such scenarios, administrators can deploy a registry key to machines and prevent the .NET Framework 4.8 from being offered to those machines. More information about how to use this blocker registry key can be found in the following Microsoft Knowledge Base article KB4516563: How to temporarily block the installation of the .NET Framework 4.8.
If you had not deployed .NET Framework 4.8 product from August 2019 or now wish to deploy the .NET Framework 4.8 product in your organization then please continue to approve the new update and let the old update expire. The January 2020 update just replaces the older update and has been refreshed with the latest servicing fixes as of January 14th, 2020. Apart from the servicing fixes, there is no change in the .NET Framework 4.8 product from the August 13th, 2019 Windows update.
If you have installed the Microsoft .NET Framework 4.8 for Windows updates from August 2019, you do not need to install these updates from January 2020 otherwise please download and install the latest from the catalog. The Update titles and KB numbers remain the same as in August.
Namrata. I have a similar question. We have a computer that has both the .NET Framework 4.7.2 Runtime AND the .NET Framework 4.7.2 Developer Pack installed on it. If i install the .NET Framework 4.8 Runtime on that computer, do i still need to install the .NET Framework 4.8 Developer Pack as well? Or does the runtime installer upgrade both? I would guess that i need to install both the Runtime and the Developer Pack for version 4.8. Because the runtime would not have components that are only in the Developer Pack. Right?
Additional question suggestion for the FAQ:
Q: Will it break Exchange?
A: Probably. Consult the Exchange .Net supportability matrix at -us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#microsoft-net-framework and heed the warnings at -update-bound-to-break-your.html
Yes the D3DCompiler package is a pre-req but its included as part of the Windows update for Win 7 SP1 and installed accordingly. If you need to install the standalone package, you can download it from the Microsoft Update Catalog site. There is more information about this package available in this support article.
It is not yet showing up on WSUS for 2016 and 2019, I only see the updates. It is only showing up for 2012 R2, along with the updates, where it set to be important so it installed by default last month.
Basically, after installing .NET 4.8 on Windows Server 2019 and rebooting, you are no longer able to input IPs that have 3 digits in any of the octets, into the Create Cluster Wizard (after installing Failover Clustering). Are you aware of this bug? Can you please create a KB article on it?
I am running the .NET 3.5 offline installer on windows 8.1 from Microsoft .NET Framework 3.5 Service pack 1 (Full Package) . Though, when I run this exe, it still prompts me to install from windows update. The same thing happens with the pre-service pack installer.
I was unable to DISM for this because the sxs folder diddnt exist on my 8.1 DVD so I did a search and found the update on the DVD, its under \support\framework_3.5\I ran that and it updated it, works fine.Brian.
When running Windows update, I get an error code of 800F0831. In the system logs, I get event ID 20. If I run the offline installer, I get installation did not succeed. .net framework 4.7.2 has not been installed because HResult 800F0831.
I know this isnt an answer to fixing this through the normal channels but if you need this installed now you can try the offline installer Microsoft .NET Framework 4.7.2 offline installer for Windows - Microsoft Support
Microsoft released the final version of the .NET Framework 4.8 on April 18, 2019. The new version is available as both web installer and offline installer. Since Microsoft prefers distribution via the web installer, it is difficult to find working offline installer links.
The .NET Framework is offered as web and offline installers. The core difference is that the web installer requires an active Internet connection during installation as it needs to download components from Microsoft servers.
Use this link to download the official .NET Framework 4.8 Language Packs for offline installation. The language packs include translated error messages and user interface text; the text is displayed in English if no language pack is installed.
The Microsoft .NET Framework 4.8 is a new version of Microsoft's popular framework. It includes new features, fixes, and improvements compared to previous versions.
Microsoft released the .NET Framework 4.8 for Windows 7 Service Pack 1, Windows 8.1, and Windows 10, and all server platforms starting with Windows Server 2008 R2 Service Pack 1 (means Server 2012 R2, 2016, and 2019 are supported as well).
The changelog on the Microsoft Docs website highlights new features and changes in the new release. The log is quite technical in nature and intended for programmers who use the framework more than it is for Windows users and administrators who install it.
New features in .NET Framework 4.8 include high-DPI improvements such as improved support for Windows Forms interoperation in high-DPI WMF applications on platforms that support mixed-mode DPI scaling or support for Per-Monitor V2 DPI Awareness.
Another batch of Microsoft disk-clutter and complexity. Why? So programs may call some functions if programmers want to use it rather than write their own. It all means more complexity, more potential security risks and more patching. Where does it end!
The Rhino installer is responsible for making sure your Windows installation has everything it needs to run Rhino. This includes the .NET framework and Microsoft Visual C++ Runtime redistributable packages. Because many computers already have these packages, they are not embedded in the installer. They are downloaded as needed during installation.
Note: For network-wide deployment and using an offline LAN Zoo, the necessary data is presented when you try to add a license to that Zoo. For a Zoo-specific write-up of the preceding instructions, see _offline
c80f0f1006