Unable to install .net

Question

Unable to install .net

Handian Sudianto 7,301

I try install .net framework on my windows server 2019 but got below error even i have permission on the folde User's image

Then i try to extract the exe file and run the setup file and got below error. User's image

Try running netfx_core_x64 and got below error. Anyone know how to solve this erroer? User's image

0 comments

3 answers

Your answer

Answer 1

On Windows Server 2019, .NET Framework 4.x is built into the OS and isn’t installed by running the standalone web/offline installer. The message “You cannot use this setup program to install the .NET Framework” and the dialog from netfx_core_x64 (“.NET Framework 4 is already a part of this operating system, but it is currently turned off”) indicate that .NET is already present but disabled as a Windows feature.

To resolve the issue, enable the built‑in .NET Framework feature instead of running the EXE:

Open Server Manager → Manage → Add Roles and Features.
Go to Features.
For .NET Framework 4.x, select .NET Framework 4.x Features (for example, .NET Framework 4.7 Features on Server 2019) and all required sub‑features.
If the app also needs .NET Framework 3.5, enable .NET Framework 3.5 Features here as well. If installation fails with source‑file errors, use the Windows Server media and specify the \sources\sxs folder as the alternate source path as described in the .NET 3.5 installation article.
Complete the wizard and let the server install the feature, then reboot if prompted.

If the wizard reports that .NET 4.x is already installed, no further action is required for that version; focus on enabling any missing 3.5 feature if the application targets .NET 3.5 or earlier.

The initial “Unable to create or save new files in the folder into which the files are being extracted” dialog is only from the self‑extracting EXE and can be ignored once using Server Manager instead; .NET should not be deployed on Server 2019 via that EXE.

References:

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Danny Nguyen (WICLOUD CORPORATION) 7,345 Microsoft External Staff Moderator

Hi @Handian Sudianto ,

On Windows Server 2019, .NET Framework 4.7.2 is included with the OS. The key clue is your third screenshot: “Microsoft .NET Framework 4 is already a part of this operating system, but it is currently turned off.”

So the first thing to do is enable the built-in .NET Framework 4.x feature in Server Manager → Add Roles and Features → Features, or in Turn Windows features on or off.

After that:

If the application works, you can stop there.
If the application specifically requires .NET Framework 4.8, then install 4.8 separately after enabling the built-in framework.

Microsoft’s documentation for Windows/Windows Server shows that Windows Server 2019 includes .NET Framework 4.7.2, and 4.8 is the latest supported upgrade:

https://learn.microsoft.com/en-us/dotnet/framework/install/on-windows-and-server

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.

Thank you.

Handian Sudianto 7,301 Reputation points

2026-05-21T23:53:41.2133333+00:00

hi @Danny Nguyen (WICLOUD CORPORATION)

The .net framework was installed any maybe was turn in in the server manager
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-05-22T03:40:53.08+00:00

Hi @Handian Sudianto

Thank you for the follow up.

Since it's shown that it's already installed, please check which exact .NET Framework 4.x version is installed rather than trying to reinstall it. On Windows Server 2019, Microsoft documents that the OS includes .NET Framework 4.7.2, and 4.8 can be installed separately if required.

You can verify the installed version using the registry or PowerShell, following Microsoft’s guide:

https://learn.microsoft.com/en-us/dotnet/framework/install/how-to-determine-which-versions-are-installed

For example, run:

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

or in PowerShell:

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Release

Then compare the Release value with Microsoft’s version table.
Handian Sudianto 7,301 Reputation points

2026-05-22T05:53:42.7333333+00:00

Hello,

Here the result and confirmed that .net 4.7.2 was installed
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-05-22T08:57:28.1866667+00:00
The Release value 461814 means .NET Framework 4.7.2 is already installed, so there is no need to reinstall 4.7.2.

The next step is to check whether .NET Framework 4.8 may already have been installed as a Windows update. On Windows Server 2019, Microsoft notes that .NET Framework 4.8 is listed under Installed Updates in Control Panel as Update for Microsoft Windows (KB4486153).

So at this point I would suggest:

If the application needs 4.7.2 or earlier, .NET is already installed.

If it needs 4.8, check Installed Updates for KB4486153 first.

If KB4486153 is not present, then install .NET Framework 4.8 separately.

Reference:

https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0
Handian Sudianto 7,301 Reputation points

2026-05-22T14:07:13.61+00:00

Hi..

No KB4486153 installed and if you see my initial post i got error when manually install the .net 4.8
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-05-25T08:43:37.54+00:00
I tested this on a fresh Windows Server 2019 and the .NET Framework 4.8 offline installer completed successfully, so this does not look like a general Windows Server 2019 issue.

I also tested extracting the installer and running netfx_core_x64 directly. Even on a server where 4.8 had already installed successfully, that internal package still showed the message about “.NET Framework 4 is already part of this operating system, but it is currently turned off.” Because of that, I would not use that message by itself as a reliable indicator of whether .NET 4.x is actually installed or enabled.

On my test server, after 4.8 installed successfully, that value became 528049, which corresponds to .NET Framework 4.8.

At this point I would focus on things specific to that machine, such as:

a pending reboot

Windows Update / servicing not being fully up to date

checking for and installing the latest Windows updates

if needed, reapplying any missing or failed Windows servicing updates

whether the installer EXE is being run in compatibility mode

whether the official 4.8 offline installer is being used

or whether antivirus / endpoint protection / policy is interfering with the prerequisite check

Hopefully these checks can point to some helpful clues. Hope to hear from you soon.
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-05-27T10:25:34.8333333+00:00

Hi, just checking in. Does anything come up on your end? If you still want to look into this, feel free to reach out as I am happy to help.
Handian Sudianto 7,301 Reputation points

2026-05-27T14:22:51.92+00:00

Hi..

Reboot the server is not help, still get same error after rebooted.

Still find other way to can install the .net successfully.
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-05-28T11:00:30.2166667+00:00
Thank you for the follow up. I'm sorry that we haven't been able to identify the root cause so far.

When you said:

“Still find other way to can install the .net successfully”

do you mean you already found another way to install it successfully, or do you mean you are still looking for another way?

If you already installed it another way, please share how you installed it and what this command shows after that:

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Release

please check these:

The current Release value from HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

Make sure the installer EXE is not running in Compatibility Mode (right-click installer > Properties > Compatibility)

Check if Windows still has any pending or failed updates

Check if antivirus, endpoint protection, AppLocker, or policy is blocking the installer before setup starts

That should help show whether .NET 4.8 is already installed another way, or whether something on the server is blocking the installer.
Handian Sudianto 7,301 Reputation points

2026-05-29T07:48:46.8633333+00:00

Hi.

I'm not yet find the solution, here the result of the command

Release

461814
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-06-01T10:45:21.9333333+00:00
Hi @Handian Sudianto

Thanks for confirming. Since the Release value is still 461814, the server is still reporting .NET Framework 4.7.2.

Try these checks:

Make sure you are using the official .NET Framework 4.8 offline installer, not the extracted MSI/package.

Make sure the installer is not running in Compatibility Mode: Right-click installer > Properties > Compatibility.

Check Windows Update and install any pending or failed updates.

Run these repair commands:

DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

After that, reboot the server and try the .NET Framework 4.8 offline installer again.

If it still fails after all of these checks, then the server may have a deeper Windows servicing/component store issue. In that case, you may need to consider reinstalling Windows Server 2019.
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-06-03T07:06:53.8366667+00:00

Hi, just checking in. Do you have any update on this post?
Danny Nguyen (WICLOUD CORPORATION) 7,345 Reputation points Microsoft External Staff Moderator

2026-06-05T04:16:07.5733333+00:00

As we haven’t heard back from you for a while, we’ll go ahead and close this thread for now.

If you still need assistance later or any additional information comes up, feel free to reach out.

Thank you for your understanding.