Geta windows iso image 2008 server or higher mount the image to the inbuilt image drive of windows server 2012 r2, proceed to add roles and features and select the dotnet framework 3.5 feature, click alternatives source to show the path name eg e:\sources\sxs and click install. This should work.
Downloading and mounting 2012 Server R2 install ISO is key, but we had to switch to the mounted drive letter\sources directory and load the NEWER R2 v9600 version of the DISM executable. Just mounting the ISO and specifying the /source location failed to complete or even initiate any progress of installation since Windows was using the version 9200 of DISM that apparently hates the /source switch but only reported as much inside the %systemroot%\Logs\DISM\dism.log.The error explicitly described /sources as and UNKNOWN switch and thus was doomed to silent failure without properly mounting the R2 source ISO.
@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?
The installation of .NET framework 4.6.2 has to be done on several production systems so, are the above-mentioned steps standard? I mean, could it create problem to install the same certificate on several systems? When the systems will be connected to the internet at some point, could it create conflict?
I recently ran into this issue with systems behind a firewall that didn't have internet access. I ran /extract on the .NET Framework 4.6.2 MSI and was able to run the x64 installer directly without the certificate check. Maybe not the "right" way to go, but it worked.
When you connect the system to the internet and do the update it could download a pack of trusted certificates. These certificates will be added to the trusted root store. Existing ones will simply be IMO simply replaced.
Ive been Fighting battles on all fronts trying to do a fresh Windows 7, install on the Dell and ran into the same problem... ( Net Framework 4.8 ) throws a ( Root Trust Certificate - Error ), at the start of the install just after it unpacks all the files and checks the host environment.
First I used ( 7-Zip ) [ freeware ], pointed it to the Net Framework installation file, and told it to extract...7-zip will create a folder (with matching name) containing all the extracted contents of the file.
Just wanted to say that I had a similar issue with trying to install .NET 4.7.2 on a Windows Server 2008 R2 box. I had to first upgrade it to Win 2k8r2 SP1, then add the prerequisite update for the d3ddecomplier.dll (KB4019990), THEN I had to load the certificate store as outlined above. It was only after all that that I was able to finally install .NET 4.7.2.
Had the same problem, almost. visual c++ error 0x800b010a could not find the certificates to download. Installed firefox and then retried to install c++ and problem fixed. Must be firefox browser installs these certificates.
This post will show you how to install .NET Framework 3.5 in Windows 11 offline from an installation media with DISM. By default, Windows 11 only includes .NET Framework 4.8. However, there are still a huge number of useful apps built against the .NET framework v3.5.
Such apps were created for Windows 7 and even for Windows Vista, where version 3.5 was available out of the box. Once you try to run such an app, you will see a prompt to install the missing component from the Internet.
This method has a number of disadvantages. First of all, it is your Internet traffic, and it can be limited. Secondly, the download process is not reliable and can fail. If your Internet connection is unstable, it turns into hell. Finally, you can simply work offline.
That's why it is important to know how to offline install .NET Framework 3.5 in Windows 11. You will only need an installation media of Windows 11, such as ISO file, bootable flash drive, or its DVD disk, so no Internet connection will be required.
Now you can run any older apps coded in C#,
VB.NET, and C++ that are built around older versions of the software platform. Note that .NET Framework 3.5 also includes .NET 2.0, which is also the runtime version.
Tip: You can easily find what versions of the .NET framework software you have installed using the following guide. It will give you ideas what apps will work on your computer without installing additional system components.
Finally, if you don't have the installation media for Windows 11, and also have no troubles with the Internet, you can give the online .NET Framework installation a try. Since we have already mentioned it in the post, let's review it for the sake of completeness.
i think you are taking a long root, no use to open terminal window. u just have to open the cmd with admin elevation then copy the below command and change the path for OS then hit enter. Its similar to windows 10
Tip: Winaero Twеaker is essential software for every Windows 10, Windows 8 and Windows 7 user. It allows you to customize the appearance and behavior of the operating system in a flexible way.
Try Winaero Twеaker now!
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!
I've got a machine running Windows 10 Enterprise 2015 LTSB. When I try to install the latest LabVIEW (2023Q3), I get an error that says the installer requires Windows 10 64-bit (version 1607) or newer. I've installed all Windows updates on this machine, so it's running the latest available. What can I do to get LabVIEW installed? Thanks in advance.
I guess one obvious question is: "Is your version of windows x64?" Sorry, sometimes it's the obvious questions that you forget about. Also, look here for more reasons why your version of Windows may not qualify.
Note that NI has online and offline installers. Online installers install the latest NIPM version which currently require 1607, so you likely need to download and install the offline version of our installers.
Thanks for the additional detail, Scott! Since I don't think I can download older versions of LabVIEW, I went down the path and upgraded to Windows 10 Enterprise 2019 LTSC, and then I was able to install LabVIEW 2023 without issue.
If the NI product you are installing uses Microsoft .NET 4.6.2, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.6.2 separately before you install NI software.
3a8082e126