.Net 4.8.1 app doesn't start because Windows says .Net 4.8.1 is not installed

Jorge Anjos 20

We have an app that was built to be run by .Net 4.8.1 x86 . This app is installed in a Windows Server 2022 Datacenter Azure Edition. When we launch the app, a message box is shown by the OS, saying: "This application requires one of the following versions of the .NET Framework: .NETFramework,Version=v4.8.1 Do you want to install this .NET Framework version now? The Server Manager states that .Net 4.8.1 is already installed, but anyway I clicked the button on that message box, that directed me to the Microsoft downloads site, where I downloaded the setup, and then installed it. The setup app goes all the way through and in the end it says: "Installation is complete. .NET Framework 4.8.1 has been installed." Still, always the same error message box appears when I try again to run the app. The app initially was .Net 4.6.2, and on that framework version, it ran with no issues. When it was still in .Net 4.6.2, we had the following line in the appConfig file:

    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.2" />

Of course now it says:

    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8.1" />

Can you help us on this issue? I ran out of ideas, and as it's a production server, I don't want to mess around with it too much.

Jiale Xue - MSFT 46,466 Reputation points Microsoft Vendor

2024-01-23T03:29:04.89+00:00

Hi @Jorge Silva , Welcome to Microsoft Q&A, Have you restarted the server after installing .net 4.8.1? Will your program run locally after updating?
Jorge Anjos 20 Reputation points

2024-01-23T09:33:31.6266667+00:00

Yes, I restarted the server, but the problem continued.
Jorge Anjos 20 Reputation points

2024-01-23T17:59:37.7433333+00:00

I read the following article: https://developercommunity.visualstudio.com/t/NET-Framework-481-installation-fails/10228681?space=21&q=remove+additional+files+false+on+linux&entry=problem Can I assume that this specific OS (Windows Server 2022 Datacenter Azure Edition) does not support this specific .Net (4.8.1) ?
Jiale Xue - MSFT 46,466 Reputation points Microsoft Vendor

2024-01-24T01:13:08.45+00:00

Hi @Jorge Silva , I've turned it into an answer, in order to help more people solve this problem, you can mark it as an answer.
Jorge Anjos 20 Reputation points

2024-01-24T10:06:23.49+00:00

Thanks. One last question: can you tell me in which Windows SKUs this .net 481 is supported?
Deleted

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

Roberto Bonini 0

If this is still an issue for you, please look a the following article.

From here(https://developercommunity.visualstudio.com/t/This-application-requires-one-of-the-fol/1614708?space=21&q=The+following+are+not+valid+user+ids)

Enabling TLS 1.2 seems to resolve the issue.

New-Item 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319' -name 'SystemDefaultTlsVersions' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-Item 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -name 'SystemDefaultTlsVersions' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'Enabled' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force | Out-Null
New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'Enabled' -value '1' -PropertyType 'DWord' -Force | Out-Null
New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force | Out-Null
Write-Host 'TLS 1.2 has been enabled.'

Accepted answer

Jiale Xue - MSFT 46,466 Reputation points Microsoft Vendor

2024-01-24T01:11:46.48+00:00

Hi @Jorge Silva , Welcome to Microsoft Q&A,

Your issue has been confirmed as a known behavior.

It will extend applicability to all existing Server 2022 SKUs in an upcoming release. The specific question link is:https://developercommunity.visualstudio.com/t/NET-Framework-481-installation-fails/10228681?space=21&q=remove+additional+files+false+on+linux&entry=problem。

Best Regards,

Jiale

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Pedro Gonçalves 25 Reputation points

2024-03-13T15:43:21.8233333+00:00

Hi Jiale,

The post at https://developercommunity.visualstudio.com/t/NET-Framework-481-installation-fails/10228681?space=21&q=remove+additional+files+false+on+linux&entry=problem is from December 2022, and https://developercommunity.visualstudio.com/user/39416 said "This is a known behavior. We expect to expand the applicability to all existing Server 2022 SKUs in an upcoming release.".

So, we are in March 2024, more than one year after, and the issue seems to be unfixed.
Are Microsoft really thinking of solve this in upcomming realeases or not?

Or when saying "upcomming releases" meen future versions of Windows Server but not 2022?

Regards,

Pedro

Roberto Bonini 0 Reputation points

2024-08-29T11:55:38.1833333+00:00

Hi @Jiale Xue - MSFT

Is there an update as to when this fix rolled put? Or if rhere are enay steps that we need to take?

I have this issue on the Windows Server 2022 Datacenter Azure Edition VM as the linked issue and its still a problem.

Its a brand new VM.

Thanks,

Roberto
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

3 additional answers

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
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
Roberto Bonini 0 Reputation points

2024-08-29T14:05:39.9466667+00:00

Please see if you still have this issue.

https://developercommunity.visualstudio.com/t/This-application-requires-one-of-the-fol/1614708?space=21&q=The+following+are+not+valid+user+ids

TLS 1.2 needs to be enabled.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

.Net 4.8.1 app doesn't start because Windows says .Net 4.8.1 is not installed

3 additional answers

Your answer