Wiki Link: [discussion:1733]
Unable to apply Hotfix to Server 2008 

May 14 2009 at 4:28 PM
Error Message: Windows Installer - The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade path.

System Environment:
Windows Server 2008
.NET CLR 3.0

Application Affected:
Unable to install System Center Virtual Machine Manager 2008 on target system.

Any help would be cool.

May 14 2009 at 4:46 PM
Updated information:

Just checked the Target System.

It's version of system.runtime.serialization.dll is 3.0.4506.648
The hotfix version, according to the documentation is 3.0.4506.44

So, it makes sense that it wouldn't update. But we need to find out how to resolve this.

Jun 7 2010 at 7:38 PM
Hi i'm having the same problem. My env is as follows:

Windows Server 2008 x64 SP2
.NET 3.5.30729 (3.5 SP1)
PowerShell 2.0

What i'm trying to do is run the following line in Powershell:

new-object System.Security.Cryptography.MD5CryptoServiceProvider

However the error is:

Exception calling ".ctor" with "0" argument(s): "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms."

After web searching I've come to this hotfix as detailed here:

http://support.microsoft.com/kb/935434

But like DylanPhillips mentioned, I get the following error:

The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

More about my environment:

C:\Windows\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\System.Runtime.Serialization.dll version is 3.0.4506.4037 (QFE.030729-4000).

Jun 17 2010 at 1:16 AM
Ok so I didn't know that the FIPs group policy setting was causing this and that the MD5 hashing algorithm is not FIPs certified.


Updating...
Page view tracker