SCOM hotfixes won't install

This posting with the solutions is based on the input of Kevin Holman. Therefore all credits go to him.

However, since this issue can be a bit tedious and is one SCOM users can easily bump into, I have decided to post this case on my blog as well. With this posting the 'internetpresence' of this issue AND the solution will be raised, enabling SCOM users to find more easily the answer for this issue.

Issue
When one installs a certain SCOM hotfix, the installation states it was succesful. However, when one checks the dll's which had to be replaced, these are still of the older version. When one checks the MomPatch.LOG file, there will be an errorstatement, like this one:


Cause
Certain hotfixes for SCOM which have been previously installed have modified some registry entries which the OpsMgr installation uses.

Microsoft knows about this issue and is fixing the Hotfixes. Therefore it is recommended to download the most recent hotfixes. Older hotfixes, downloaded some weeks ago can better be disgarded.

However, one can still bump into issue. Errormessages can be displayed as well, like this one:

Product: System Center Operations Manager 2007 -- Error 1334.The file
File196.2FD07918_9082_437D_99BC_FD43602A4625 cannot be installed because the file cannot be found in cabinet file Data.Cab. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

The workaround is easy, but can be tricky since one has to edit the registry. Have you SCOM RTM installed and later on installed SP1? There are some extra things to reckon with. Even more so, when the server is x64 based, one has to look for other strings (GUIDS) as well. This posting describes what to do in all these situations.

Solution
Open the registry. Go to HKCR\Installer\Products\DF6E5EFF035E66C49971553D96AA0E4D\Patches.Backup this key (patches) by exporting it.

DO NOT FORGET THIS !!!

So far so good. These two steps are the same for every situation. Now the different steps are coming:

One has SCOM with SP1 installed (not first SCOM RTM and later on SP1 afterwards, but directly 'out-of-the-box' SCOM with SP1 included), follow these steps:

Once backed up... delete the REG_SZ GUIDS, and then open the "Patches" REG_MULTI_SZ key, and delete all guids from there.

Only an empty Patches multi string value should remain

When you run the setup, all should work. Import afterwards the key and all should be well.

One has SCOM RTM installed and later on SP1 and has done so on a x64 box, follow these steps:

Leave these two GUIDS in place:
727B3A3ADCF2D1945BFF1FD34105570A (this references MOM2007QFEPreSP1.msp)

88817A55B3D84652468BCF9B1E587B78F (this references MOM2007SP1.msp for AMD64)

These GUIDS must remain in the Patches multi string

When you run the setup, all should work. Import afterwards the key and all should be well.

One has SCOM RTM installed and later on SP1 and has done so on a x86 box, follow these steps:

Leave these two GUIDS in place:
727B3A3ADCF2D1945BFF1FD34105570A (this references MOM2007QFEPreSP1.msp)

8CABA70B215243145A51419A9073262F (this references MOM2007SP1.msp for x86)

These GUIDS must remain in the Patches multi string

When you run the setup, all should work. Import afterwards the key and all should be well.