ConfigMgr 2012 R2 Client Failes to Install on HP EliteBook laptops with Synaptics Touchpad drivers

Question

I've come across a fairly frustrating issue that has been taking up way too much of my time that past week or so. The issue started a little after some of our larger sites were migrated from SCCM 2007 to SCCM 2012. I started getting complaints that one of
our technical workstations (HP 8770w) was not deploying properly. I started investigating the issue and the problem involved the removal of the old ConfigMgr 2007 client and install of the new SCCM 2012 R2 client.
The Windows 7 x64 OS WIM that I am using is one that was migrated from the 07 to 2012 environment and it has been working fine. During the Setup Windows and ConfigMgr step the old client is removed and the new one for the 2012 environment installs. There
has not been any issues with this, but I feel something has changed now that we are deploying the 2012 R2 client.
Back to the issue, what happens is that the ConfigMgr client fails to uninstall the old client. Looking in the client.msi_uninstall file you will see that it is unable to locate a couple of SCCM 2007 configmgr client patches that were installed so it can
uninstall it. I get the "Couldn't find local patch ''. Looking for it at its source." line in the uninstall file. When I look for that under HKEY_CLASSES_ROOT\Installer\Patches the ENTIRE directory structure is empty. There is not a single item
listed under patches.
Since the only thing that happens in between the pushing down of the WIM and installing the configmgr client is the drivers that is where I started to look. I started over with the basics (disk and network driver) and it was able to complete the OSD process
(like the other 30+ models we currently support). I added drivers one by one having the system re-image each time. When I got to the Synaptics TouchPad drivers the issue would return. I've tried around 5 different drivers offered from the vendor and they
all result in the same behavior.
I'm still actively troubleshooting how to FIX this issue, but I have no idea why this is going on. I thought I would share with the community on this issue and see if anyone else has observed this VERY odd behavior.
Here is a snippet from the client.msi_uninstall log:
=== Verbose logging started: 1/15/2014  22:59:34  Build type: SHIP UNICODE 5.00.7601.00  Calling process: D:\_SMSTaskSequence\OSD\GAS000EF\ccmsetup.exe ===
MSI (c) (6C:BC) [22:59:34:264]: Resetting cached policy values
MSI (c) (6C:BC) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (c) (6C:BC) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (6C:BC) [22:59:34:264]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (6C:BC) [22:59:34:264]: Grabbed execution mutex.
MSI (c) (6C:BC) [22:59:34:264]: Cloaking enabled.
MSI (c) (6C:BC) [22:59:34:264]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (6C:BC) [22:59:34:264]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:264]: Running installation inside multi-package transaction {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
MSI (s) (00:80) [22:59:34:264]: Grabbed execution mutex.
MSI (s) (00:D4) [22:59:34:264]: Resetting cached policy values
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (s) (00:D4) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (00:D4) [22:59:34:405]: SRSetRestorePoint skipped for this transaction.
MSI (s) (00:D4) [22:59:34:405]: End dialog not enabled
MSI (s) (00:D4) [22:59:34:405]: Original package ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: Package we're running from ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2609EDF1-34C4-4B03-B634-55F3B3BC4931}'.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (00:D4) [22:59:34:420]: MSCOREE not loaded loading copy from system32
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: User policy value 'DisableMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {D478B8EE-EE0A-4004-980B-4D55533EE3C2} 3: 
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {D478B8EE-EE0A-4004-980B-4D55533EE3C2} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} 3: 
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: SequencePatches starts. Product code: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}, Product version: 4.00.6487.2000, Upgrade code: {252DA259-82CA-4177-B8D0-49C78937BA3E}, Product language 1033
MSI (s) (00:D4) [22:59:34:420]: SequencePatches returns success.
MSI (s) (00:D4) [22:59:34:420]: Final Patch Application Order:
MSI (s) (00:D4) [22:59:34:420]: Other Patches:
MSI (s) (00:D4) [22:59:34:420]: Internal Exception during install operation: 0xc0000005 at 0x000007FEFDBF35E1.
MSI (s) (00:D4) [22:59:34:420]: WER report disabled for silent install.
MSI (s) (00:D4) [22:59:34:420]: Internal MSI error. Installer terminated prematurely.
MSI (s) (00:D4) [22:59:34:420]: MainEngineThread is returning 1603
MSI (s) (00:80) [22:59:34:420]: No System Restore sequence number for this installation.
Unexpected Termination
MSI (s) (00:80) [22:59:34:420]: User policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (00:80) [22:59:34:420]: Restoring environment variables
MSI (c) (6C:BC) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (6C:BC) [22:59:34:420]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/15/2014  22:59:34 ===

Answer 1

@Narcoticoo
I've not used the tool. This issue has also expanded since the original title as I'm getting the same behavior with the driver package that does not include the Touchpad driver anymore. I'm currently going back to just the network and storage driver to see
if it works or not.
However, this is the bigger issue I have:
I have an older build called Build 5.7 internally. Using that WIM and the same driver package (original one that has the Touchpad driver included) it works without issue. Never had a problem.
The new build is called Build 6.0 internally. This WIM and the same driver package has not been working at all.
We support about 35 models with our current Windows 7 x64 image and I am having the same failure issue on four different HP models. They are the 8770w, ZBook 17, Z600 and Z820. The majority of the other systems are Dell devices. Just for transparency sakes,
nothing Dell specific is in the core WIM that is captured.
So, Build 5.7 can deploy just fine on all pieces of hardware with their old driver packages. The new Build 6.0 intalls on almost every platform fine with their old driver packages. These four HP systems are nothing but trouble though. I've opened a case
with HP to see if they have noticed anything internally. I'm not too hopeful, but at least it is something. Maybe there is some odd conflict with a newer Windows patch or some odd dependency on older HP drivers. The new image has .NET 4.5.1, IE 10 and so forth.