.NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6 - Advanced Installer Community
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

.NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

To reproduce:-
OS version: windows 10
Installed .NET version: 4.6
Advanced Installer version(s): 12.7.2 & 13.1
Prerequisite: preinstall, built in, .NET Framework 4.6.1

Expected: Installer spots prerequisite missing (and in our case throws up webpage)
Actual: Installer does nothing and continues

We have an installer using a (built in) preinstall prerequisite for .NET Framework 4.6.1 - (it is configured to though up a msdn website, and continue)
On Windows 10 with only 4.6 (original release) it fails to spot that 4.6.1 is missing and continues.
This works on earlier versions of the Windows OS.
I have tested with the most recent version of Advanced Installer (13.1)

Am I missing a special step for Windows 10 & 4.6.1 ? Or if this is a defect, can you suggest a work around ?

Speculating wildly I can see from looking at the msdn guidance (https://msdn.microsoft.com/en-us/librar ... aspx#net_d) I can see that Windows 10 has different version numbers for both 4.6 and 4.6.1 (and 4.6.2) ; could the built prerequisite registry search be out of date for Windows 10...?

Thank you,
James.
Last edited by jamesr on Mon Sep 05, 2016 12:05 pm, edited 1 time in total.
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

I didn't embed the url properly in the original post... Corrected now.

https://msdn.microsoft.com/en-us/librar ... aspx#net_d
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

W10 Log file suggests that the version is correctly detected but doesn't spot prereq missing
MSI (c) (A0!D0) [12:44:25:415]: PROPERTY CHANGE: Adding AI_DETECTED_DOTNET_VERSION property. Its value is '4.6'.
Action ended 12:44:25: AI_DetectSoftware. Return value 1.
-----------------------------------

W7 Logfile shows prereq missing & 4.6 detected
MSI (c) (D0:6C) [14:03:17:068]: PROPERTY CHANGE: Adding AI_MISSING_PREREQS property. Its value is '.NET Framework 4.6.1'.

...

MSI (c) (D0!F8) [14:03:17:665]: PROPERTY CHANGE: Adding AI_DETECTED_DOTNET_VERSION property. Its value is '4.6'.
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

A second (hidden) problem
.NET Framework 4.6 installed with Windows 10 = 393295

.NET Framework 4.6 installed on all other Windows OS versions = 393297

.NET Framework 4.6.1 installed on Windows 10 = 394254

.NET Framework 4.6.1 installed on all other Windows OS versions = 394271

In Advanced Installer 12.7.2

The built in .NET 4.6 pre-requisite requires the registry 'Release' value to be greater than 393296
The built in .NET 4.6.1 pre-requisite requires the registry 'Release' value to be greater than 394270

This has to be a defect in 12.7.2 as it claims to support Windows 10 (apologies if I didn't spot it in the documentation).

However in 13.1 this appears to have been fixed for NEW prerequisites, but not when opening/updating my project (with pre-existing pre-requisites) in 13.1

This is, perhaps, a defect all by itself, as the Windows 10 versions of .NET 4.6 & 4.6.1 will not be flagged as installed if initially constructed with version 12.7.2 even if upgraded to 13.1

In fact digging deeper I find that the perquisite for 4.5.1 will fail on windows 8.1 (value 378675, compared with a test of378757)
Mercifully there is only one value for 4.5.2

However, this does not explain my original problem where a requirement for 4.6.1 on a 4.6 is not flagged on windows 10 (as all 4.6 release versions are less than test value for 4.6.1)
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Hello,

I'm not sure why this happens. We have tested your installation scenario on a Windows 10 x64 machine with Net 4.6 installed, but we cannot replicate the behavior. The .Net 4.6.1 is triggered for installation. Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?
In Advanced Installer 12.7.2

The built in .NET 4.6 pre-requisite requires the registry 'Release' value to be greater than 393296
The built in .NET 4.6.1 pre-requisite requires the registry 'Release' value to be greater than 394270

This has to be a defect in 12.7.2 as it claims to support Windows 10 (apologies if I didn't spot it in the documentation).
Indeed, this was a issue in our previous Advanced Installer versions in what regards our predefined .Net 4.6 prerequisite. We apologize for the inconvenience. The value was updated starting with AI 12.8 version. Also we added this info in the release notes of Advanced Installer 12.8 version.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

In the absence of any feedback I have continued experimenting and can report the following:

I have built 3 basic installers using the wizard - exe installer, a .NET app, only installs 1 file (actually only a text file), launch requirement of .NET 4.6.1, pre-requisite of .NET 4.6.1
  1. Installer 1 - created and built using AI 13.1
  2. Installer 2 - created and built using AI 12.7.2
  3. Installer 3 - copy of aip from 2 built with 13.1
Tested on windows 10 with .NET 4.6
  1. Installer 1) WORKS!!! - prompts for missing pre-req, and if I skip the installer fails because of failed launch condition
  2. Installer 2) Fails - doesn't spot pre-req missing and installer fails because of failed launch condition
  3. Installer 3) Fails as per 2
Conclusions so far
  1. Two (possibly related errors) in installer created with 12.7.2 - Failure to spot missing pre-req, and wrong .NET version numbers in pre-req test
  2. Looks fixed in 13.1 (if you created a new installer)
  3. If you have an existing installer project just upgrading to 13.1 won't fix it, the .aip file is unmodified and building it with new version doesn't fix anything
So What now?
It looks you (Advanced Installer) need to determine the scope of the problem(s), and then provide guidance on how to build a working installer.
I can probably update production to 13.1, but I will need instruction on how to modify the project because I do not want to be creating a new installer from scratch.

Cheers,
James.
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

I posted more information below without seeing your post - the installer must be initially created with 12.7.2

If you wish, I can send the 3 basic installers and .aip and log files - but they're trivial to create from scratch

Thanks for looking at this,
James.
Daniel wrote:Hello,

I'm not sure why this happens. We have tested your installation scenario on a Windows 10 x64 machine with Net 4.6 installed, but we cannot replicate the behavior. The .Net 4.6.1 is triggered for installation. Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?
In Advanced Installer 12.7.2

The built in .NET 4.6 pre-requisite requires the registry 'Release' value to be greater than 393296
The built in .NET 4.6.1 pre-requisite requires the registry 'Release' value to be greater than 394270

This has to be a defect in 12.7.2 as it claims to support Windows 10 (apologies if I didn't spot it in the documentation).
Indeed, this was a issue in our previous Advanced Installer versions in what regards our predefined .Net 4.6 prerequisite. We apologize for the inconvenience. The value was updated starting with AI 12.8 version. Also we added this info in the release notes of Advanced Installer 12.8 version.

All the best,
Daniel
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Hi,

I have emailed a zip of three trivial installers/logs/.aip that demonstrate the problem with this topic title in the subject, and explanation in the email text.

Regards,
James.
Daniel wrote: Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Hello James,

Indeed, when the .Net 4.6.1 prerequisite is added in your setup project using the AI 12.7.2 and then you upgrade your project to AI 13.1, the prerequisite is not updated to the fixed settings and thus the problem persists. We apologize for the inconvenience. In this case, to fix your .Net 4.6.1 prerequisite, all you will have to do will be to update its install condition.

Just go, to "Prerequisites" page, select the .Net 4.6.1 prerequisite, go to "Install Conditions" tab and in the "Install Conditions" section double click on the configured search. Update it like this:
  • Criteria: Registry value with specified content
    Registry Value: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release
    Value: 394253
    Comparison: Greater than
As you can see only the value should be updated to 394253.

Let us know if this helped.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Hi Daniel,

Thanks for your response.

I will try this shortly an report back, but I'm confused why this will make a difference to my problem as both the incorrect 394270, and the correct 394253 are greater than the W10 .NET 4.6 registry value of 393295 => should it not spot the prerequisite anyway?

I agree that the value needs to be updated anyway to prevent the follow on problem of prompting for .NET 4.6.1 when it is already installed

Cheers,
James.
Daniel wrote:Hello James,

Indeed, when the .Net 4.6.1 prerequisite is added in your setup project using the AI 12.7.2 and then you upgrade your project to AI 13.1, the prerequisite is not updated to the fixed settings and thus the problem persists. We apologize for the inconvenience. In this case, to fix your .Net 4.6.1 prerequisite, all you will have to do will be to update its install condition.

Just go, to "Prerequisites" page, select the .Net 4.6.1 prerequisite, go to "Install Conditions" tab and in the "Install Conditions" section double click on the configured search. Update it like this:
  • Criteria: Registry value with specified content
    Registry Value: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release
    Value: 394253
    Comparison: Greater than
As you can see only the value should be updated to 394253.

Let us know if this helped.

All the best,
Daniel
jamesr
Posts: 9
Joined: Mon Sep 05, 2016 11:37 am

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Well I can report the following:
  1. Editing/Correcting the .NET registry release value does NOT fix the issue (using either 12.7.2 or 13.1)
  2. Deleting and re-adding the pre-requisite (using 13.1) fixes it
  3. The root of the 12.7.2 problem appears to be that when selecting a 4.6.1 pre-req it does NOT select Windows 10 as a supported OS for the pre-req. Appears fixed in 13.1 which selects it. Adding this supported OS and modifying the .NET release version will fix it
One of these probably counts as a fix.

Regards,
James.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: .NET 4.6.1 prerequisite not triggered on Windows 10 with only 4.6

Hello James,

Yes, you are right. Besides updating the .Net registry value you should also select Windows 10 in the "Supported Windows Versions" list of the prerequisite. This was my fault, I forgot to mention this too. Please accept my apologies for this.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”