Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system (#17344)

Discussions related to using VirtualBox on Windows hosts.

Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system (#17344)

Postby WRatzka » 24. Nov 2017, 18:55


[ModEdit; related ticket #17344]

Hi,
I am installing VirtualBox on Windows Clients automatically via a Client Management System and noticed, that starting with 5.2.0 the ProductId seen on an system where VirtualBox is installed, differs from the ProductId as stored in the MSI package.
Of course I can script my way around that. However, I wonder where that comes from...
Kind regards
Wolfgang Ratzka
WRatzka
 
Posts: 3
Joined: 24. Nov 2017, 17:56
Location: Marburg, Germany
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: quite some

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby kid-furious » 29. Nov 2017, 10:26

Hi,
Same problem here.
I'm also using a software deployment system and noticed that msi product code and uninstall code mismatch.
Since 5.2 version, msi building have a problem.

Example for x64 version (x86 has the same problem) :
VirtualBox-5.2.2-r119230-MultiArch_amd64.msi returns {9F5D10F9-A372-4B1E-BEB3-001B47E0C325}
If you look registry entry for windows installer inscription and uninstall key, this entry is {BB89B827-171F-47B2-938B-6594AABC9E5C}

Like all others windows installer files (msi), the product code and registry entries is always the same...
I'm also wondering what is the problem...
kid-furious
 
Posts: 4
Joined: 29. Nov 2017, 10:12

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby socratis » 29. Nov 2017, 10:55

Has it been the same for all previous versions? Or was it changing with every version/major release?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12746
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby kid-furious » 29. Nov 2017, 11:11

I've just noticed this problem starting with 5.2.0
No problems with 5.1.x
kid-furious
 
Posts: 4
Joined: 29. Nov 2017, 10:12

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby socratis » 29. Nov 2017, 11:39

That wasn't actually the question. The question was whether this UUID changes every time or it changed only in 5.2.x.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12746
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby kid-furious » 29. Nov 2017, 12:04

Ok.
This product code change each time there is a new msi build coming with a new virtualbox version.

Example :
Virtualbox x64 5.1.22 -> {8D5E4D4D-5E0C-4448-B018-5DDEF1E208D9}
Virtualbox x64 5.1.28 -> {11A88BD5-F059-4743-81D9-1432AC9C3D4E}
Virtualbox x64 5.2.2 -> {9F5D10F9-A372-4B1E-BEB3-001B47E0C325}

This is the normal way like all softwares provided with an msi installer.

The strange and unusual thing, since 5.2.0 virtualbox version, is that you can't retreive this product code in registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) after installation. But, instead you can find an other one.
MSI Installation file works well but it doesn't respect Windows Installer MSI rules.
kid-furious
 
Posts: 4
Joined: 29. Nov 2017, 10:12

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby socratis » 30. Nov 2017, 00:00

I talked to the developers, and they assured me that this area of the installer has not changed at all in the 5.2.x series. VirtualBox code is open source, so you could verify it for yourselves. And yes, the ProductID changes with each major/minor version.

VirtualBox uses the widespread WiX utility for its installers. This is not a widespread issue with VirtualBox, so I suspect that there is something specific with your setup that messes things. Don't ask me what that "something" could be. This is Windows we're talking about... ;)
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12746
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby kid-furious » 30. Nov 2017, 09:59

Thanks for your answer.
Like I said earlier msi installer does the job, but, since 5.2.0, product code and productId does not match.
Yes, I anderstand that it's not a Virtualbox issue. It's a building problem with Virtualbox msi installer.
No, I don't ask anything, I just point the fact , like the original poster of this thread, that something has changed with Windows Virtualbox installers. and msi packages files provided are not build correctly since 5.2.0 Virtualbox version.
To be honest, this is not doing you a favor not to tell you that making msi packages does not work like thousands of packages already made by other publishers around the world (4.x and 5.1 Virtualbox versions were well packaged). Now, you know...
kid-furious
 
Posts: 4
Joined: 29. Nov 2017, 10:12

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby WRatzka » 4. Dec 2017, 11:11

This is not a widespread issue with VirtualBox, so I suspect that there is something specific with your setup that messes things.


I see the effect on Windows 10 and on Windows 7 (both 64bit) and even when using the original installer instead of our customized installation script.
So there is little reason to believe that some local issue is at the bottom of this.
In fact only those users who distribute VirtualBox via a centralized client management tools, will notice this issue, as the common procedure
  1. extract ProductID from MSI
  2. install MSI
  3. check wether product with extracted ProductID is installed
will fail.

BTW: My workaround is to check for the Upgrade Code that stays the same between package versions.
WRatzka
 
Posts: 3
Joined: 24. Nov 2017, 17:56
Location: Marburg, Germany
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: quite some

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby socratis » 4. Dec 2017, 11:26

@WRatzka
I talked to the developers about this and they assured me that the code hasn't been touched in that area. But if you feel this to be an issue that needs to be addressed, you should head to the bug tracker and either search for an appropriate bug, or open a new bug report where you'll attach your logs and other vital information.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12746
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system

Postby WRatzka » 4. Dec 2017, 15:26

WRatzka
 
Posts: 3
Joined: 24. Nov 2017, 17:56
Location: Marburg, Germany
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: quite some

Re: Windows-Packages for 5.2.x: ProductId in MSI is not ProductId on installed system (#17344)

Postby socratis » 4. Dec 2017, 18:05

Thank you for this, I've added the ticket info in the first post and in the title.

PS. Nicely formatted ticket!
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12746
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 33 guests