Microsoft .net Framework 3.5 Is Not Installed

[Michael]

NET 4.5 is not a side-by-side version, it replaces the assemblies for 4.0. Much like .NET 3.0, 3.5 and 3.5SP1 replaced the assemblies for 2.0. And added some new ones. The CLR version is still 4.0.30319. You only care about the reference assemblies, they are in c:\program files\reference assemblies.

Whilst the above answers are correct its worth noting that MSBuild has changed and it no longer ships with the .net framework, it comes either stand alone or with visual studio. As a result it's binaries have moved... so the one you get under the 4.0.303619 directory is actually the old one!

I've just been caught out by this - I found automatic binding redirects were only working when running from VisualStudio but not when running msbuild from the command line... the clue was that binding redirects were added in VS 2013 (for that read .net framework 4.5). If you open up a vs command prompt you'll see it now gets it from program files as the other article mentions. Whereas I was using a batch file on my path which linked to the old version.

Knowing your framework version has advantages. Firstly, compatibility with software. Some programs require specific versions of the framework. Knowing which versions you have helps prevent compatibility issues when installing new software.

The Microsoft .NET Framework is a high-powered software development platform. It helps developers create a variety of applications. It offers a full set of tools, components, and runtime environments for building, deploying, and running apps on Windows-based systems.

Developers use the .NET Framework to make desktop apps, web apps, mobile apps, games, and more. The framework simplifies the development process by providing pre-built parts and functionalities that are easy to add to applications.

I recently experienced an issue with an application due to the wrong version of .NET Framework installed. By using Registry Editor and following this method, we were able to quickly identify and solve the problem by updating it. This just shows how useful this method is!

Note: Customers using Windows Server Updates Services (WSUS), or any other update management tools can import the .NET Framework 4.8.1 product from the Microsoft Update Catalog. Also note that .NET Framework 4.8.1 is already included by default as part of newer versions of Windows, starting with Windows 11 22H2.

The .NET Framework 4.8.1 (KB5011048) is available for download from: Download .NET Framework Free official downloads (microsoft.com) for supported versions of Windows and is also included with Visual Studio 17.3 and Windows 11 22H2, and their corresponding newer versions.

Enterprise customers may have client machines that connect directly to the public Windows Update servers. In such cases, an administrator may want to prevent the .NET Framework 4.8.1 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 setting and prevent the .NET Framework 4.8.1 from being offered to those devices. More information about how to use this blocker registry key can be found in the following Microsoft Knowledge Base article KB5027101: How to temporarily block the installation of the .NET Framework 4.8.1.

If you have already downloaded and installed the .NET Framework 4.8.1 originally released, you do not need to install the upcoming product update for .NET Framework 4.8.1. However, you do want to keep your device up to date for the latest .NET Framework security and reliability updates through the Windows Update, Windows Server Update Services (WSUS) and Microsoft Update Catalog channels.

Will the updated .NET Framework 4.8.1 have the same KB numbers, title, and detection Release key values as the product originally released to Microsoft Download Center and Visual Studio 17.3+?

We know that some percentage of customers have other constraints that make it difficult if not impossible to update their .NET once and have a need to stay on a single version of .NET for the lifetime of their product. So for these customers we would suggest staying on .NET Framework. As you know we continue to support the .NET Framework with the latest security and reliability fixes and we will continue to support this for as long as .NET Framework remains a part of Windows (effectively forever). Though the downside with the approach is they cannot take advantage of the latest features available in modern .NET but not in .NET Framework.

Please also consider, that even major releases of .NET (Core) are in most parts backwards-compatible. You can check -us/dotnet/core/compatibility/8.0 for what Binary incompatible and Behavioral changes exist that would affect running the .NET 7 targeted code with the .NET 8 runtime.

ArcGIS Pro 3 requires .Net Framework 6.0 (64 bit) but there are MANY versions available. ESRI also specifies that a Windows Installer must be used (why?). It appears the installer that most would use, Microsoft Windows Desktop Runtime 6.0.x is not enough to get ArcGIS Pro to work. One actually needs Download ASP.NET Core 6.0 Runtime (v6.0.16) - Windows x64 Installer (microsoft.com) as well.

Hi @RichardDaniels Thanks for submitting this idea to improve the documentation. The requirements do state that ".NET Desktop Runtime 6.0.5 or a later patch release" is required: -app/latest/get-started/arcgis-pro-system-requirements.htm

The 6.0.5 link goes here: -us/download/dotnet/thank-you/runtime-desktop-6.0.5-windows-x64-installer. Clicking on that will directly download the correct minimum required version to run ArcGIS Pro 3.x. The 'a later patch release' does point to the overall download page, as I believe you're alluding to, because there will continue to be patch releases to that version of .NET that we can't link to from the doc before they exist.

When you say Windows Desktop Runtime..." do you mean ".NET Desktop Runtime..." which is what is indicated in the documentation? And links here: -us/download/dotnet/6.0 It looks like when that is downloaded and installed on the machine, it displays as Microsoft Windows Desktop Runtime - 6.0.16 (x64), so we're probably talking about the same thing.

I have a machine with ArcGIS Pro 3.1.1 and previously had 6.0.14 on it. You can see from the screenshot above that I just installed 6.0.16 and Pro opens and works fine. So unfortunately if that is not working for you, I don't think that it is a problem that a documentation update will fix.

I understand the desire for the documentation to tell the user exactly what is needed, but as noted above, there are multiple and sometimes frequent patch updates issued by Microsoft. Also the system requirements are just that, the minimum requirement to run the software in a supported manner. That minimum (.NET Desktop Runtime 6.0.5) is linked to explicitly and downloaded automatically without the user needing to make a decision or research the latest .NET 6.0.x patch available.

We're discussing this with the documentation team to see if there is an opportunity to improve how this is described and delivered in the system requirements topic. For the issue of Pro not working with certain versions of .NET as you've indicated above, we can't address that through documentation. Please troubleshoot with technical support.

During installation of ArcGIS Pro 3.3, if we detect that .NET 8 is not present on the machine we will provide a message - in that message we are including a hyperlink to the .NET 8 download page as a response to this feedback. We hope that helps in situations like this one.

Thank you for updated the documentation. I would say that our issue was not a 'one-off', we have over 1800 machines in our environment with ArcGIS Pro and ArcGIS Desktop and it took several days to track down the correct version of .Net 6 to install.

One of the things you can do to check the .NET Framework versions on your machine is to run an elevated command prompt with the command reg query "HKLM\SOFTWARE\Microsoft\Net Framework Setup\NDP" /s. This will report all installed versions, and there might be a considerable number (don't delete any). Search the list for the latest and make sure it meets the criteria of Garmin Express. A search seems to indicate that .NET Framework 4.7.2 is needed. Microsoft also has a .NET Repair Tool that might be worth running. It can be found at www.microsoft.com/.../details.aspx

Even though .NET is installed, is it enabled to run? The attached graphic shows what is enabled om my Win 10 machine. Note that if you make changes, you likely have to reboot for them to take effect.

I can't speak as to why .NET Framework 3.5 may be needed by Garmin Express and I'm not about to uninstall it from my PC to do a test. My Win 10 machine is running the exact version you are running and from all appearances .NET 3.5 is needed by something. Microsoft does not recommend uninstalling old versions of .NET, but having said that there is evidence that if you do and a specific app needs a specific .NET version, the user will be prompted. So apparently since you are being prompted, some need perhaps does exist. If you go to the area that turns Windows features ON/OFF is 3.5 (assuming it exists) enabled?

Welcome to the community!

Sorry that your .NET framework is indicating it is already installed. This sounds more like a Microsoft registry issue. Could you try running the Microsoft installation repair tool? This should allow you to clear up registry errors and install the .NET framework, which you can find on Microsoft's website.

The important thing is to share your installation log file.. Not saying @matthew.d information is not useful but you could be spending time doing stuff that doesn't resolve the issue. Not sure where you got your suggestion from but did they ever look at your log file?

Helpful Links:

AutoCAD Videos AutoCAD Crashes or Freezes AutoCAD Customer Council AutoCAD System Requirements Prepare your computer for download Autodesk Virtual Agent Clean Uninstall Steps for Setting-Up Student Software

3a8082e126