Posts Tagged ‘.NET Framework’

Run .NET framework 1.1 apps and programs in Windows 8

Recently, I tried to run the .NET framework 1.1 supported application in Windows 8.1. As you may not know .NET Framework 1.1 is not supported on the Windows 8 or Windows Server 2012 operating system. In some cases, the .NET Framework 1.1 is specifically identified as required for an application to run. In those cases, you should contact your independent software vendor (ISV) to have the application upgraded to run on the .NET Framework 3.5 SP1 or later version.
But there are cases (very often) when the software version is old and you do not have the upgraded version of the software. In my case, I tried to install the package and got the following error message: “Setup cannot continue because this version of the .NET Framework is incompatible with a previously installed one“.

There are two methods to fix this issue.
Method 1 – install .NET Framework 3.5
For some users all those apps which need .NET Framework 1.1 to run can work properly with .NET framework 3.5. So, you can optionally download .NET 3.5 and install it but make sure you can turn off 4.0 framework and other versions if you have it apart from 3.5. So you have to turn off .NET 4.0 and leave on .NET 3.5 – in my case, it didn’t solve the issue.

Method 2 – manually install .NET Framework 1.1
Download Microsoft .NET Framework 1.1 redistributable package (dotnetfx.exe). Make sure the setup file is saved as dotnetfx.exe. Download Microsoft .NET Framework 1.1 Service Pack 1 (NDP1.1sp1-KB867460-X86.exe). Make sure that the file is renamed and saved as dotnetfxsp1.exe, so that the rest of the steps can be followed easily. Move both installation files into the same directory (for example c:\dotnet).
This method involves recompiling the .NET framework 1.1 and then installing .NET Framework 1.1 with slipstreamed/integrated SP1 by running netfx.msi which will created in the working folder after running the following commands (run command prompt in admin mode and run the following command one by one):

dotnetfx.exe /c:"msiexec.exe /a netfx.msi TARGETDIR=C:\DotNet"

after it is installed

dotnetfxsp1.exe /Xp:C:\DotNet\netfxsp.msp


msiexec.exe /a c:\DotNet\netfx.msi /p c:\DotNet\netfxsp.msp

I hope one of the above method will work for you to run any app or program. Make sure to restart your PC after following any of the above methods.


Microsoft .NET Framework 4 fails to install due to “The setup cannot run in compatibility mode” error.

2012-06-25 14 comments

I was having this issue trying to install the full version of .NET v4.0 on Windows 2008R2. No matter what I tried: changing compatibility modes, running as administrator – I’ve got “The setup cannot run in compatibility mode” error. I received the message whether I tried to install OR uninstall it (Using add/remove programs).

Here is how you could resolve this issue:
1. Download the full installer (dotNetFx40_Full_x86_x64.exe) from here Microsoft site.
2. Extract it into a new folder using WinRAR or 7-Zip, for example “c:\downloads\dotNetFx40_Full_x86_x64\”.
3. Once extracted, you need to edit 3 files, all “ParameterInfo.xml”. Following from the example folder in step two, the three files are located:


EDIT ALL three files, do NOT edit one and copy it to the other folders – they are different and this won’t work. In each file, you’re looking for a block of code that looks like this:

<BlockIf DisplayText="#(loc.Blocker_in_OS_Compatibility_Mode)" ID="AppCompatMode">
<IsInOSCompatibilityMode />

Remove these these 5 lines from each file to disable the compatibility mode check. Remember to save.

4. Once that is done, open a DOS prompt in Administrator Mode and run the setup utility located in the “dotNetFx40_Full_x86_x64” folder created above. You need to tell it what architecture you’re on. If you’re running 32-bit Windows, use:

setup /x86

If you’re using 64-bit windows, use:

setup /x64

It should bring up the installer and continue normally without receiving the compatibility mode error. I suspect other installers suffering from this error might be able to be modified in a similar way.