MSI: Setup failed due to unexpected circumstances The error code is 80041002

Problem:

 When trying to install the new SCCM client 4.0.6487.2000  everything seems to start and go fine.....   but at the end of it you get the last two lines and it just stops.

 ----------------Start CCMSETUP.LOG----------------
Version: 4.0.6487.2000
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.
"Command line: ""C:\WINDOWS\system32\ccmsetup\ccmsetup.exe"" /runservice /config:MobileClient.tcf"
CCMHTTPPORT: 80
CCMHTTPSPORT: 443
CCMHTTPSSTATE: 0
CCMHTTPSCERTNAME:
FSP:
CCMFIRSTCERT: 0
Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf
Retry time: 10 minute(s)
MSI log file:
"MSI properties: INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"""
Source List
file://sccmserver.somedomain.biz/SMSClient
file://sccmserver/SMSClient
MPs:
SCCMSERVER.SOMEDOMAIN.BIZ
Updated security on object C:\WINDOWS\system32\ccmsetup\.
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent.
"Running as user ""SYSTEM"""
Detected 36580 MB free disk space on system drive.
DetectWindowsEmbeddedFBWF() Detecting OS Version
"Client OS Version is 5.1, Service Pack Version 2"
Client OS is not a supported Windows Embedded Platform
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.
Deleted file C:\WINDOWS\system32\ccmsetup\client.msi
Successfully ran BITS check.
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed.
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml
Successfully loaded ccmsetup manifest file.
"Adding file 'http://SCCMSERVER.SOMEDOMAIN.BIZ:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'."
Starting BITS download for client deployment files.
Download Update: 76883 out of 17847296 bytes transferred.
Successfully completed BITS download for client deployment files.
Successfully downloaded client files via BITS.
Updated security on object C:\WINDOWS\system32\ccmsetup\.
An MP does not exist on this machine.
No client is currently installed.
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
"MSI PROPERTIES are INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"" SMSPUBLICROOTKEY=0602000000A40000525341310004000001000100E3FE16910549BC7E5EE664FED18FA09085E3BA678C50BB2018D0E525A1295C2FFE7611C7B23EF1A0974744C9785CAC840CA5C1C12FD14B9D37BF62BD70A109F1537B8F1D66D979996FE9007EC8F6DD2E121182C55FC7B9E2E49DBFE3F56E6CFAEF3FF0C1EE6837D95A04ED8A45AD5B198687C372B43AA3D83316A655AB0EF4B8 INSTALL=ALL"
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed.
Running installation package
Package: C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi
Log: C:\WINDOWS\system32\ccmsetup\client.msi.log
" Properties: INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"" SMSPUBLICROOTKEY=0602000000A40000525341310004000001000100E3FE16910549BC7E5EE664FED18FA09085E3BA678C50BB2018D0E525A1295C2FFE7611C7B23EF1A0974744C9785CAC840CA5C1C12FD14B9D37BF62BD70A109F1537B8F1D66D979996FE9007EC8F6DD2E121182C55FC7B9E2E49DBFE3F56E6CFAEF3FF0C1EE6837D95A04ED8A45AD5B198687C372B43AA3D83316A655AB0EF4B8 INSTALL=ALL"
MSI: Action 15:21:14: INSTALL.
MSI: Setup failed due to unexpected circumstances The error code is 80041002
MSI: Action 14:54:01: Rollback. Rolling back action:


Installation failed with error code 1603
-------------------END LOG ----------------

Resolution:


Rebuild the WMI Repository by following the steps outlined in the following post
http://www.madanmohan.com/2010/10/rebuilding-wmi-repository.html