Blocking older MSI setups - Revision history

Afrow UK: /* Method 2 (better) */

2013-04-04T12:26:31Z

Method 2 (better)

â† Older revision		Revision as of 12:26, 4 April 2013
Line 54:		Line 54:
	</highlight-nsis>		</highlight-nsis>
	As you can see it just creates a MSI compatible version number and saves it in the registry, where all installed MSI products are saved. The UpgradeCode is required to find the installed product: it just has one single string value named after the ProductCode.		As you can see it just creates a MSI compatible version number and saves it in the registry, where all installed MSI products are saved. The UpgradeCode is required to find the installed product: it just has one single string value named after the ProductCode.

			'''If you find it does not work, make sure your codes are valid. One way to do this is to use Process Monitor with a Process Name filter on msiexec.exe. I found it was reading the correct keys but still not detecting a new version as installed. However changing the ''Assignment'' value to 0x2 fixed it.'''

	That's it. If you now try to install the older MSI version, it will detect the UpgradeCode. Then it jumps to the written ProductCode and compares the version number with its own version. If the saved number is equal or higher, you should see a message that a newer version is already installed. What the setup really says to you depends on what you wrote into. ;-)		That's it. If you now try to install the older MSI version, it will detect the UpgradeCode. Then it jumps to the written ProductCode and compares the version number with its own version. If the saved number is equal or higher, you should see a message that a newer version is already installed. What the setup really says to you depends on what you wrote into. ;-)

Afrow UK: /* Method 1 (simple but nasty) */

2013-04-04T12:23:23Z

Method 1 (simple but nasty)

â† Older revision		Revision as of 12:23, 4 April 2013
Line 11:		Line 11:
	== Method 1 (simple but nasty) ==		== Method 1 (simple but nasty) ==
	The Microsoft Installer remembers all installed products in the registry (HKLM\Software\Classes\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It's because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this		The Microsoft Installer remembers all installed products in the registry (HKLM\Software\Classes\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It's because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this
	<pre>{12345678-1234-1234-1234-~~1234567989012~~}</pre>		<pre>{12345678-1234-1234-1234-123456798901}</pre>
	What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this		What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this
	<pre>~~87654321432143212143214365870921~~</pre>		<pre>87654321432143212143214365979810</pre>
	You should find this code if the MSI product is installed. Now remove the old version and create a registry key named after this "twisted" ProductCode (s. above). If you then try to reinstall the older MSI version you should see an error message that this is not possible.		You should find this code if the MSI product is installed. Now remove the old version and create a registry key named after this "twisted" ProductCode (s. above). If you then try to reinstall the older MSI version you should see an error message that this is not possible.

Kichik: Reverted edits by 127.0.0.1 to last version by 72.29.211.50

2013-01-22T18:20:56Z

Reverted edits by 127.0.0.1 to last version by 72.29.211.50

â† Older revision		Revision as of 18:20, 22 January 2013
Line 1:		Line 1:
	~~perfectly~~.		{{PageAuthor\|MathiasSimmack}}
	It ~~informational resource~~, I'~~ll bookmark~~ it and ~~visit~~ it ~~again~~!
			== Description ==
			You may have read these two articles about removing MSI installations:

			[[Uninstalling a previous MSI]]<br>
			[[Removing MSI packages with MSI related functions]]

			Okay the MSI version is gone. But the user could reinstall it. You should make sure that this is not possible if your NSIS version is newer.

			== Method 1 (simple but nasty) ==
			The Microsoft Installer remembers all installed products in the registry (HKLM\Software\Classes\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It's because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this
			<pre>{12345678-1234-1234-1234-1234567989012}</pre>
			What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this
			<pre>87654321432143212143214365870921</pre>
			You should find this code if the MSI product is installed. Now remove the old version and create a registry key named after this "twisted" ProductCode (s. above). If you then try to reinstall the older MSI version you should see an error message that this is not possible.

			And yes: if you want to block different MSI releases you need all ProductCodes and you have to create a key for each version.

			== Method 2 (better) ==
			If you were clever you included an upgrade check in your MSI file. What does it mean? Before installing, the MSI setup is looking for other related products. And it should cancel if it finds the same or a newer version already installed.

			Did you do something like this? Perfect. Then you first need a '''new''' fresh ProductCode. This is absolutely different from method 1 (s. above). You '''MUST NOT''' use a code, another MSI version used before. (Or you're back at method 1.) So please create a new GUID and remove the parenthesises and hyphens.

			Then you need the '''original''' UpgradeCode that you used in your older MSI setups. It's another GUID and it should be the same in your product family (1.0 -> 1.x -> 2.0 -> ...). You also have to "distort" it that it looks like the ProductCode (s. method 1 on how to do it).

			Now call the macro "WRITE_FAKE_MSICOMPONENTS" and set the ProductCode, the UpgradeCode and the 4 digits of your current version number (Major.Minor.Release.Build) as parameters. For example:
			<highlight-nsis>!insertmacro WRITE_FAKE_MSICOMPONENTS \
			"3DD65B80F4E711D7A48800E07DA59103" \
			"18AF4D6DB8206D1139D10000C1108ABC" \
			1 2 3 4</highlight-nsis>
			Your current version number must be higher than all older releases or the MSI upgrade check won't work. Here is the macro code:
			<highlight-nsis>

			!macro BUILD_MSICOMPATIBLE_VERNUM MAJOR MINOR RELEASE BUILD RESULT
			StrCpy ${RESULT} "0"

			IntOp $R0 ${MAJOR} * 0x1000000
			IntOp $R1 ${MINOR} * 0x10000
			IntOp $R2 ${RELEASE} * 0x100

			IntOp ${RESULT} ${RESULT} + $R0
			IntOp ${RESULT} ${RESULT} + $R1
			IntOp ${RESULT} ${RESULT} + $R2
			IntOp ${RESULT} ${RESULT} + ${BUILD}
			!macroend

			!macro WRITE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE MAJ MIN REL BUILD
			!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0
			WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Version" $0
			WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Assignment" 0x1
			WriteRegStr HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""
			!macroend
			</highlight-nsis>
			As you can see it just creates a MSI compatible version number and saves it in the registry, where all installed MSI products are saved. The UpgradeCode is required to find the installed product: it just has one single string value named after the ProductCode.

			That's it. If you now try to install the older MSI version, it will detect the UpgradeCode. Then it jumps to the written ProductCode and compares the version number with its own version. If the saved number is equal or higher, you should see a message that a newer version is already installed. What the setup really says to you depends on what you wrote into. ;-)

			Please use the next macro called "REMOVE_FAKE_MSICOMPONENTS" to remove these MSI entries. Set the ProductCode and UpgradeCode as parameters
			<highlight-nsis>!insertmacro REMOVE_FAKE_MSICOMPONENTS \
			"3DD65B80F4E711D7A48800E07DA59103" \
			"18AF4D6DB8206D1139D10000C1108ABC"
			</highlight-nsis>
			And here is the code:
			<highlight-nsis>!macro REMOVE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE
			DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}"
			DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}"
			!macroend
			</highlight-nsis>
			Mathias.

			(btw: I'm sorry but my English is not as good as it could be. I hope this article is understandable.)

			[[Category:Other Products Version Detection Functions]]

127.0.0.1: yoGVFdwpoqwMcDiCUw

2013-01-22T09:44:08Z

yoGVFdwpoqwMcDiCUw

â† Older revision		Revision as of 09:44, 22 January 2013
Line 1:		Line 1:
	~~{{PageAuthor\|MathiasSimmack}}~~		perfectly.
			It informational resource, I'll bookmark it and visit it again!
	~~== Description ==~~
	~~You may have read these two articles about removing MSI installations:~~

	~~[[Uninstalling a previous MSI]]<br>~~
	~~[[Removing MSI packages with MSI related functions]]~~

	~~Okay the MSI version is gone. But the user could reinstall it~~. ~~You should make sure that this is not possible if your NSIS version is newer.~~

	~~== Method 1 (simple but nasty) ==~~
	The Microsoft Installer remembers all installed products in the registry (HKLM\Software\Classes\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It~~'s because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this~~
	~~<pre>{12345678-1234-1234-1234-1234567989012}</pre>~~
	What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this
	~~<pre>87654321432143212143214365870921</pre>~~
	You should find this code if the MSI product is installed. Now remove the old version and create a registry key named after this "twisted" ProductCode (s. above). If you then try to reinstall the older MSI version you should see an error message that this is not possible.

	~~And yes: if you want to block different MSI releases you need all ProductCodes and you have to create a key for each version.~~

	~~== Method 2 (better) ==~~
	~~If you were clever you included an upgrade check in your MSI file. What does it mean? Before installing~~, ~~the MSI setup is looking for other related products. And it should cancel if it finds the same or a newer version already installed.~~

	Did you do something like this? Perfect. Then you first need a '''new''' fresh ProductCode. This is absolutely different from method 1 (s. above). You '''MUST NOT''' use a code, another MSI version used before. (Or you'~~re back at method 1.) So please create a new GUID and remove the parenthesises and hyphens.~~

	~~Then you need the '''original''' UpgradeCode that you used in your older MSI setups. It's another GUID and~~ it ~~should be the same in your product family (1.0 -> 1.x -> 2.0 -> ...). You also have to "distort" it that it looks like the ProductCode (s. method 1 on how to do it).~~

	~~Now call the macro "WRITE_FAKE_MSICOMPONENTS" and set the ProductCode, the UpgradeCode~~ and ~~the 4 digits of your current version number (Major.Minor.Release.Build) as parameters. For example:~~
	~~<highlight-nsis>!insertmacro WRITE_FAKE_MSICOMPONENTS \~~
	~~"3DD65B80F4E711D7A48800E07DA59103" \~~
	~~"18AF4D6DB8206D1139D10000C1108ABC" \~~
	~~1 2 3 4</highlight-nsis>~~
	~~Your current version number must be higher than all older releases or the MSI upgrade check won't work. Here is the macro code:~~
	~~<highlight-nsis>~~

	~~!macro BUILD_MSICOMPATIBLE_VERNUM MAJOR MINOR RELEASE BUILD RESULT~~
	~~StrCpy ${RESULT} "0"~~

	~~IntOp $R0 ${MAJOR} * 0x1000000~~
	~~IntOp $R1 ${MINOR} * 0x10000~~
	~~IntOp $R2 ${RELEASE} * 0x100~~

	~~IntOp ${RESULT} ${RESULT} + $R0~~
	~~IntOp ${RESULT} ${RESULT} + $R1~~
	~~IntOp ${RESULT} ${RESULT} + $R2~~
	~~IntOp ${RESULT} ${RESULT} + ${BUILD}~~
	~~!macroend~~

	~~!macro WRITE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE MAJ MIN REL BUILD~~
	~~!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0~~
	~~WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Version" $0~~
	~~WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Assignment" 0x1~~
	~~WriteRegStr HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""~~
	~~!macroend~~
	~~</highlight-nsis>~~
	~~As you can see~~ it just creates a MSI compatible version number and saves it in the registry, where all installed MSI products are saved. The UpgradeCode is required to find the installed product: it just has one single string value named after the ProductCode.

	That's it. If you now try to install the older MSI version, it will detect the UpgradeCode. Then it jumps to the written ProductCode and compares the version number with its own version. If the saved number is equal or higher, you should see a message that a newer version is already installed. What the setup really says to you depends on what you wrote into. ;-)

	~~Please use the next macro called "REMOVE_FAKE_MSICOMPONENTS" to remove these MSI entries. Set the ProductCode and UpgradeCode as parameters~~
	~~<highlight-nsis>!insertmacro REMOVE_FAKE_MSICOMPONENTS \~~
	~~"3DD65B80F4E711D7A48800E07DA59103" \~~
	~~"18AF4D6DB8206D1139D10000C1108ABC"~~
	~~</highlight-nsis>~~
	~~And here is the code:~~
	~~<highlight-nsis>!macro REMOVE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE~~
	~~DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}"~~
	~~DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}"~~
	!~~macroend~~
	~~</highlight-nsis>~~
	~~Mathias.~~

	~~(btw: I'm sorry but my English is not as good as it could be. I hope this article is understandable.)~~

	~~[[Category:Other Products Version Detection Functions]]~~

72.29.211.50: Added Assignment = 0x1 registry value in Product Key (Necessary for blocking MSI's for my Win7 x64)

2012-01-24T23:22:31Z

Added Assignment = 0x1 registry value in Product Key (Necessary for blocking MSI's for my Win7 x64)

â† Older revision		Revision as of 23:22, 24 January 2012
Line 49:		Line 49:
	!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0		!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0
	WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Version" $0		WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Version" $0
			WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Assignment" 0x1
	WriteRegStr HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""		WriteRegStr HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""
	!macroend		!macroend

98.207.95.83: /* Method 1 (simple but nasty) */ fix another location to be HKLM

2010-06-09T21:33:15Z

Method 1 (simple but nasty): fix another location to be HKLM

â† Older revision		Revision as of 21:33, 9 June 2010
Line 10:		Line 10:

	== Method 1 (simple but nasty) ==		== Method 1 (simple but nasty) ==
	The Microsoft Installer remembers all installed products in the registry (~~HKCU~~\Software\MS\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It's because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this		The Microsoft Installer remembers all installed products in the registry (HKLM\Software\Classes\Installer\Products). You need the original ProductCode of your MSI setup. You cannot find it in the registry? It's because the code is saved in a "twisted" format. A ProductCode is a GUID and looks like this
	<pre>{12345678-1234-1234-1234-1234567989012}</pre>		<pre>{12345678-1234-1234-1234-1234567989012}</pre>
	What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this		What's to do? The first three field must be written with the last character first (1234 -> 4321) and the last two fields must be exchanged byte-wise (1234 = 12 34 -> 21 43 = 2143). Then remove the parenthesises and hyphens and you will get something like this

98.207.95.83: Change location to be HKEY_LOCAL_MACHINE based so all users get it

2010-06-09T21:31:59Z

Change location to be HKEY_LOCAL_MACHINE based so all users get it

â† Older revision		Revision as of 21:31, 9 June 2010
Line 31:		Line 31:
	1 2 3 4</highlight-nsis>		1 2 3 4</highlight-nsis>
	Your current version number must be higher than all older releases or the MSI upgrade check won't work. Here is the macro code:		Your current version number must be higher than all older releases or the MSI upgrade check won't work. Here is the macro code:
	<highlight-nsis>~~!define MSIKEY "Software\Microsoft\Installer"~~		<highlight-nsis>

	!macro BUILD_MSICOMPATIBLE_VERNUM MAJOR MINOR RELEASE BUILD RESULT		!macro BUILD_MSICOMPATIBLE_VERNUM MAJOR MINOR RELEASE BUILD RESULT
Line 48:		Line 48:
	!macro WRITE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE MAJ MIN REL BUILD		!macro WRITE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE MAJ MIN REL BUILD
	!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0		!insertmacro BUILD_MSICOMPATIBLE_VERNUM ${MAJ} ${MIN} ${REL} ${BUILD} $0
	WriteRegDword ~~HKCU~~ "~~${MSIKEY}~~\Products\${TURNPCODE}" "Version" $0		WriteRegDword HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}" "Version" $0
	WriteRegStr ~~HKCU~~ "~~${MSIKEY}~~\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""		WriteRegStr HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}" "${TURNPCODE}" ""
	!macroend		!macroend
	</highlight-nsis>		</highlight-nsis>
Line 63:		Line 63:
	And here is the code:		And here is the code:
	<highlight-nsis>!macro REMOVE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE		<highlight-nsis>!macro REMOVE_FAKE_MSICOMPONENTS TURNPCODE TURNUCODE
	DeleteRegKey ~~HKCU~~ "~~${MSIKEY}~~\Products\${TURNPCODE}"		DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\Products\${TURNPCODE}"
	DeleteRegKey ~~HKCU~~ "~~${MSIKEY}~~\UpgradeCodes\${TURNUCODE}"		DeleteRegKey HKEY_LOCAL_MACHINE "Software\Classes\Installer\UpgradeCodes\${TURNUCODE}"
	!macroend		!macroend
	</highlight-nsis>		</highlight-nsis>

Deguix: "read" -> "have read"

2005-07-15T22:03:35Z

"read" -> "have read"

â† Older revision		Revision as of 22:03, 15 July 2005
Line 2:		Line 2:

	== Description ==		== Description ==
	You may read these two articles about removing MSI installations:		You may have read these two articles about removing MSI installations:

	[[Uninstalling a previous MSI]]<br>		[[Uninstalling a previous MSI]]<br>

Deguix at 22:01, 15 July 2005

2005-07-15T22:01:31Z

â† Older revision		Revision as of 22:01, 15 July 2005
Line 5:		Line 5:

	[[Uninstalling a previous MSI]]<br>		[[Uninstalling a previous MSI]]<br>
	[[~~removing~~ MSI packages with MSI related functions]]		[[Removing MSI packages with MSI related functions]]

	Okay the MSI version is gone. But the user could reinstall it. You should make sure that this is not possible if your NSIS version is newer.		Okay the MSI version is gone. But the user could reinstall it. You should make sure that this is not possible if your NSIS version is newer.

Deguix: Added
.

2005-07-15T21:59:35Z

Added <br>.

â† Older revision		Revision as of 21:59, 15 July 2005
Line 4:		Line 4:
	You may read these two articles about removing MSI installations:		You may read these two articles about removing MSI installations:

	[[Uninstalling a previous MSI]]		[[Uninstalling a previous MSI]]<br>
	[[removing MSI packages with MSI related functions]]		[[removing MSI packages with MSI related functions]]