Monday 9 September 2013

SCCM 2012 Client Failed to install - ExitCode: 1603

The following script was created from much frustration with the SCCM Client not installing on workstations and servers.  Errors were all over the map, from MSI errors to 1603 in the ccmsetup.log file.
The following errors were noted:
  • "File C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603"
  • InstallFromManifest failed 0x80070643
  • "CcmSetup failed with error code 0x80070643"

Turns out the root cause was WMI corruption, so this little batch script worked great. 

Tested on XP, Windows 7, Server 2003, Server 2003R2, Server 2008, Server 2008R2.

This is the "shotgun" approach to repairing WMI.  Do not reboot your computer immediately after running this, as the WMI is rebuilding in the background.   I manually ran the SCCM Client install about 1 minute after the batch file completed, and it completed successfully. (Yay - another 30 seconds of success!  Now on to my next task...)

Format: BATCH

Copy and paste the text into a batch file.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
For /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
net start winmgmt
for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s
exit

14 comments:

  1. wow great, this script works! I am trying to understand how it work, Thanks a lot! (Sorry for my bad English)

    ReplyDelete
    Replies
    1. It is a re-build of the workstation's WMI engine.

      Delete
  2. There is no use to run that batch file also since it's not installing for me even i tried thrice also

    ReplyDelete
  3. WORKS! WORKS! every other win2k3 server I try and install the sccm 2012 client on, push or pull, seem to fail with this error!!!

    THANK YOU

    ReplyDelete
  4. Holy Cow! I just tried this on a 2008 R2 machine that has been giving me problems and it worked. Thank you for this. Beats searching the registry manually etc. and sc deleting services.

    ReplyDelete
  5. It does not work for windows 2003 r2, and 2012 sccm client

    ReplyDelete
  6. The fix is to install the updated version of Visual C++ 2013 Redistributable. Please test and let us know.
    https://support.microsoft.com/en-us/help/3179560/update-for-visual-c-2013-and-visual-c-redistributable-package

    ReplyDelete
  7. I had a couple of systems with 2008 SP2 (not R2) that both reported 1603. The VC++ 2013 above fixed that problem.

    ReplyDelete
  8. Worked for me, but I needed to let it sit a little longer before retrying. Thanks Matthew!

    ReplyDelete