Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Error 1642 when deploying to clients

Status
Not open for further replies.

SuperSteve

Member
Messages
24
Reaction score
1
Points
3
Hi all

We have recently updated our sccm r2 console to sp1 as we need to deploy to some windows 10 clients. In doing so we have attempted a redeployment of the sccm client and all have come back reporting an error of 1642. Not just windows 10 pro clients, but 8.1 pro and win 7 pro.

I am unable to find the information I need on the web to try and resolve this and a typical log file from Microsoft can be very off putting as a lot of the information doesn't make sense.

I have attached the log file just in case anyone can understand it and offer me some advice.
 

Attachments

Hi Steve,
Have you check clientmsi.log for the client issue

Error : 1642 = 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.

Are those clients really running a x86 OS?
 
Hi Maunil

I can't find the clientmsi.log on the workstation.

The clients are x64 and we definitely deployed the x64 bit update version although the installation paths of both versions are ...

\\sips-sccm\SMS_(SiteCode)\hotfix\KB2882125\Client\i386\configmgr2012ac-sp1-kb2882125-i386.msp

\\sips-sccm\SMS_(SiteCode)\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp

If I run either one manually I get the same error....
 
The download for KB2882125 contains an msi that has to be installed on the primary site(s). It's not intended to be installed on the clients. Installing KB2882125 on the siteserver creates a new ConfigMgr package though and that one is intended to be installed on the clients!
or
ConfigMgr kicked of the installation of the patch, but the product to be patched was not found on the machine.
 
Status
Not open for further replies.

Forum statistics

Threads
7,133
Messages
27,860
Members
18,151
Latest member
TonyGTR
Back
Top