WineHQ

.NET Framework

.NET Framework 4.0, released on 2011-02-21.

Application Details:

Version: 4.0
License: Free to use
URL: http://msdn.microsoft.com/netf...
Votes: 6
Latest Rating: Gold
Latest Wine Version Tested: 3.0-rc6

Maintainers: About Maintainership

Free Download Microsoft .NET Framework 4 (Standalone Installer) (48.1 MB)Direct download Free Download Microsoft .NET Framework 4 (Web Installer) (868 KB) Free Download Microsoft .NET Framework 4 (Standalone Installer)

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

  1. Installation
  2. Verification passed (.NET Framework Setup Verification Utility)
  3. Programs which requires this framework  are able to run without any issues

What does not

---

Workarounds

What was not tested

Everything else besides What works section.

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

1. Install wine-staging then open terminal in your home directory and type commands listed below: rm -fr ~/.wine export WINEARCH=win32 export WINEPREFIX="/home/USER/.wine" winecfg 1a. Replace USER with your USERNAME 1b. In winecfg set Windows version to Windows 7 2. Visit https://github.com/Winetricks/winetricks and grab winetricks from there 2a. In your home directory create folder called Winetricks 2b. Open above folder in terminal 2c. Type wget -r -c -N https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks then chmod +x winetricks 3. Open winetricks (type sh winetricks in terminal) and navigate to the default wineprefix -> Installation of Windows DLL or component, find dotnet4 and mark it for installation. 4. Installer will install all .NET Frameworks including 4 version

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowKDE neonJan 17 20183.0-rc6Yes Yes YesGoldInvictus Tiberius 
ShowFedora 24 x86_64Apr 16 20172.2-stagingYes Yes GoldLuc Absil 
CurrentUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Sep 28 20161.9.19Yes Yes Goldan anonymous user 
ShowMac OS X 10.10 "Yosemite"Aug 17 20151.7.47Yes Yes Goldan anonymous user 
ShowUbuntu 14.04 "Trusty" i386 (+ variants like Kubuntu)Dec 07 20141.7.31No, but has workaround Yes Bronzean anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected
12401 NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API for managed assembly installation need reparse point/junction API support, i.e. DeviceIoCtl(FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_POINT) STAGED View
15670 .NET applications that make use of System.IO.IsolatedStorage crash (missing "HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\" registry subkey) STAGED View
32323 Netflix (Silverlight 4.x) and several .NET Framework 3.x/4.0 WPF apps require either Arial or Verdana to be installed STAGED View
33506 Microsoft Expression Design 4 (Free Version) crashes when quickly populating main menu items (dropdown sub-menu drawing) NEW View
36461 Multiple .NET 4.0 applications fail on startup, WPF message dispatcher unexpectedly receives messages during 'CoWaitForMultipleHandles' call with 'COWAIT_ALERTABLE' flag (Visual Studio 2010, BgmHkClient) NEW View
43408 Quest 5.7.x (.NET 4.0 WPF app) crashes on direct access of MIL4 (Media Integration Layer, wpfgfx_v0400.dll) to internal bitmap struct/class impl (depends on exact layout) NEW View
44562 .NET 4.x - rundll32.exe - Error messages when running any application or starting wine after update UNCONFIRMED View

Show all bugs

HowTo / Notes

Get winetricks!

You need to install winetricks first (see more details here). This tool make easier to install and configure many things on your wine-prefix. Your distribution probably comes with a package to install it but it could likely be outdated, so, to be safe, download the latest version:

$ wget  'https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks'
$ chmod +x ~/winetricks
Automated installation through winetricks

Last update: 2019-01-05


It is recommended to use a new Wine prefix (but not necessary, depending on your applications). "$HOME/winedotnet" is the path for the prefix on which .NET will be installed; you can change it to whatever you want:

$ env WINEPREFIX=$HOME/winedotnet wineboot --init

If Wine prompts for installing Mono, click Cancel.

Then you can install .NET Framework (and optionally install corefonts):

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks dotnet40 corefonts

To perform instead a silent (no GUI) installation, append the --unattended argument:

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks --unattended dotnet40 corefonts

Use dotnet40 to install .NET Framework 4.0. If you want to install another version of 4.x series, change it for one of the following list:

dotnet45   to install .NET Framework 4.5
dotnet451  to install .NET Framework 4.5.1
dotnet452  to install .NET Framework 4.5.2
dotnet46   to install .NET Framework 4.6
dotnet461  to install .NET Framework 4.6.1
dotnet462  to install .NET Framework 4.6.2
dotnet47   to install .NET Framework 4.7 (currently not supported by winetricks)
dotnet471  to install .NET Framework 4.7.1 (currently not supported by winetricks)
dotnet472  to install .NET Framework 4.7.2 (currently not supported by winetricks)

... And so on. For example, if you want to install .NET Framework 4.5.2:

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks --unattended dotnet452 corefonts

If this doesn't work or you need to install a version not supported by winetricks, try manual installation (explained below).

Manual installation (Step 1)

Again, start with a new Wine prefix:

$ env WINEPREFIX=$HOME/winedotnet wineboot --init

Then try to install .NET 4.0 through winetricks:

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks dotnet40 corefonts

If it success and you want to install a higher 4.x version, go to Step 2 (next How-To). If it doesn't work (very unlikely) keep reading.


Ensure wine-mono is not installed on your Wine prefix:

$ env WINEPREFIX=$HOME/winedotnet wine uninstaller --remove '{E45D8920-A758-4088-B6C6-31DBB276992E}'

Change reported version to Windows XP. After it, download and install .NET 4.0:

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks winxp
$ wget 'http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe'
$ env WINEPREFIX=$HOME/winedotnet wine ~/dotNetFx40_Full_x86_x64.exe

Open winecfg dialog:

$ env WINEPREFIX=$HOME/winedotnet winecfg

Once there, go to "Libraries" tab and add a new library substitution called "mscoree". Then, edit it and set it to "Native (Windows)". Close the dialog by pressing OK.

Manual installation (Step 2)

Change reported version to Windows 7:

$ env WINEPREFIX=$HOME/winedotnet ~/winetricks win7

Now you can download and execute the installer for the desired version of .NET (install only the highest version you need):

  • .NET Framework 4.5:
    $ wget 'http://download.microsoft.com/download/b/a/4/ba4a7e71-2906-4b2d-a0e1-80cf16844f5f/dotnetfx45_full_x86_x64.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/dotnetfx45_full_x86_x64.exe /q
  • .NET Framework 4.5.1:
    $ wget 'https://download.microsoft.com/download/1/6/7/167F0D79-9317-48AE-AEDB-17120579F8E2/NDP451-KB2858728-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP451-KB2858728-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.5.2:
    $ wget 'http://download.microsoft.com/download/E/2/1/E21644B5-2DF2-47C2-91BD-63C560427900/NDP452-KB2901907-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP452-KB2901907-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.6:
    $ wget 'https://download.microsoft.com/download/C/3/A/C3A5200B-D33C-47E9-9D70-2F7C65DAAD94/NDP46-KB3045557-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP46-KB3045557-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.6.1:
    $ wget 'https://download.microsoft.com/download/E/4/1/E4173890-A24A-4936-9FC9-AF930FE3FA40/NDP461-KB3102436-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP461-KB3102436-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.6.2:
    $ wget 'https://download.microsoft.com/download/F/9/4/F942F07D-F26F-4F30-B4E3-EBD54FABA377/NDP462-KB3151800-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP462-KB3151800-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.7:
    $ wget 'https://download.microsoft.com/download/D/D/3/DD35CC25-6E9C-484B-A746-C5BE0C923290/NDP47-KB3186497-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP47-KB3186497-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.7.1:
    $ wget 'https://download.microsoft.com/download/9/E/6/9E63300C-0941-4B45-A0EC-0008F96DD480/NDP471-KB4033342-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP471-KB4033342-x86-x64-AllOS-ENU.exe /q
  • .NET Framework 4.7.2:
    $ wget 'https://download.microsoft.com/download/6/E/4/6E48E8AB-DC00-419E-9704-06DD46E5F81D/NDP472-KB4054530-x86-x64-AllOS-ENU.exe'
    $ env WINEPREFIX=$HOME/winedotnet wine ~/NDP472-KB4054530-x86-x64-AllOS-ENU.exe /q


Verify .NET Framework installation using .NET Framework Setup Verification Tool (Microsoft)

Last update: 2019-01-06


To verify .NET Framework installation(s) you can use the .NET Framework Setup Verification Tool from Aaron Stebner (Microsoft) which checks for proper installation of .NET assemblies and registry entries:

$ wget 'https://msdnshared.blob.core.windows.net/media/2018/05/netfx_setupverifier_new.zip'
$ unzip netfx_setupverifier_new.zip
$ env WINEPREFIX=$HOME/winedotnet wine ~/netfx_setupverifier.exe

Select the .NET Framework version you want to verify and evaluate the log file manually if verification failed.

fixme:shell:URL_ParseUrl failed to parse ...

URL_ParseUrl FIXME messages on console when running/installin­g .NET apps are harmless and can be safely ignored. Example console output:

fixme:shell:URL_ParseUrl failed to parse L"mscorlib"
­
Manually trigger rebuild of the Global Assembly Cache (GAC) after .NET Framework installation

Use the following command to manually trigger GAC rebuild after .NET Framework installation (or if WINEPREFIX changed due to Wine update):

$ wine "c:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\ngen.exe" update

Some errors while loading dependent modules that are not GAC'd yet are expected and can be ignored.­

The application requested process termination through System.Environment.FailFast

If a .NET application exits with the following message in console:

err:eventlog:ReportEventW ...
Description: The application requested process termination through System.Environment.FailFast(string message).\n
Message: Unrecoverable system error.\n
Stack:\n
at System.Environment.FailFast(System.String)\n
at MS.Internal.Invariant.FailFast...

Some of Wine's truetype fonts are still not in shape of being a complete replacement for Windows ones, causing errors.

You must use 'winetricks corefonts' recipe to work around this problem!

System.Window.Markup.XmlParseException when starting .NET apps

If a .NET application exits with the following message in console:

err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:rpc:RpcBindingSetAuthInfoExW unsupported AuthnSvc 10

You are missing the samba/winbind component which is essential for certain Wine functionality.

Please install winbind with your distribution package manager!

To run this application, you first must install one of the following versions of the .NET Framework: .NETFramework,Version=v4.0

If you encounter this error, the .NET4 app basically requests .NET 4.0 Full Framework. The default for .NET 4.0 Framework is "Client Profile".

Workaround: If your .NET4 application is called "foo.exe", rename "foo.exe.config" to something different and run again.

If this file is missing the CLR assume that your app is targeting NET4 Client Profile by default (which should work out in most cases).­

This links explains the differences and implications: Microsoft MSDN blog

Comments

Back