Burn and .NET Framework 4.8 #6713
-
Hi Wix Community! TLDR: Two web installers, 1 working, 1 not working. Cannot understand the problem. This might turn out to be a "non-wix-question", but anyways. We have an installer that requires the users machine to have .NET Framework 4.8 installed. So I created a Wix Bundle and included a web installer for the .NET Framework as
this worked well, at least for a while. Before I continue I would like to say, that I wrote this code more than half a year ago, at which point we tested the installer on the target systems (Windows 7, 8, 10 etc). One week ago we got a customer report that their installer was failing with the reported error: So I booted up the virtual machine for Windows 7 (same snapshot) as I used when I first verified the installer, and to my surprise I got the same error. Looking in the log I found the following rows
So I extracted the .NET installer (i.e. npd48-web.exe) from the bundle to run it alone to see if I could get more information. In the log for npd48-web.exe installer I find this
In the log it tries 3 more times before the installer fails. Each time it fails at verify the signature, and we can see the same reported message So I try the obvious, setting the system clock. But at the time of writing this post the clock seemed to match my timezone and time To further investigate the problem I decided to download a new web installer from Microsoft's website (I downloaded the one we use today from the same place) and tried running that one instead. To my surprise that installer worked. So here I am with two version of the net 48 web installer, the one we have (not working) The workaround right now is to switch the non-working to the working installer, but I'm afraid that the now working installer will stop working in the future as well. Do you guys have any idea what the problem could be or maybe what the next step could be? I'm still new to Wix (~1 year experience) and I might have overlooked something here. Like should I use a web installer like I do? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Very likely this issue: A little while back, Microsoft decided to release all the .NET Framework binaries with new signatures at the same URLs. This broke everyone validating the .NET Framework thumbprint, including existing Burn bundles. It was pretty disruptive. We had to help a couple of FireGiant customers navigate emergency updates. Could it happen again? Yes. Microsoft could choose to make a breaking change and post it to the same URL. Will they? They didn't do it for many years, never was clear why they did it this time. |
Beta Was this translation helpful? Give feedback.
Very likely this issue: A little while back, Microsoft decided to release all the .NET Framework binaries with new signatures at the same URLs. This broke everyone validating the .NET Framework thumbprint, including existing Burn bundles. It was pretty disruptive. We had to help a couple of FireGiant customers navigate emergency updates.
Could it happen again? Yes. Microsoft could choose to make a breaking change and post it to the same URL. Will they? They didn't do it for many years, never was clear why they did it this time.