Deploy W7 SP1 and registry problems?

[Kingskawn]

I've got some weird things going on. An errorcode I never saw. Error code 14090 which is a registry error.

 

All this when deploying servicepack 1 of Windows 7 x86. The command I use is: windows6.1-KB976932-X86.exe /quiet /nodialog /norestart

It works fine with all other machines but not this one. Does somebody received this error too?

 

A snippet from the execmgr.log;

 

Content is available for program sp1_install. execmgr 02/04/2012 13:16:08 18896 (0x49D0)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 02/04/2012 13:16:08 18896 (0x49D0)
Executing program windows6.1-KB976932-X86.exe /quiet /nodialog /norestart in Admin context execmgr 02/04/2012 13:16:08 18896 (0x49D0)
Execution Manager timer has been fired. execmgr 02/04/2012 13:16:08 17144 (0x42F8)
Execution Request for package ALD002C3 program sp1_install state change from WaitingContent to NotifyExecution execmgr 02/04/2012 13:16:08 18896 (0x49D0)
Checking content location C:\Windows\system32\CCM\Cache\ALD002C3 .6.System for use execmgr 02/04/2012 13:16:08 18896 (0x49D0)
Successfully selected content location C:\Windows\system32\CCM\Cache\ALD002C3 .6.System execmgr 02/04/2012 13:16:08 18896 (0x49D0)
Executing program as a script execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Successfully prepared command line "C:\Windows\system32\CCM\Cache\ALD002C3 .6.System\windows6.1-KB976932-X86.exe" /quiet /nodialog /norestart execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Command line = "C:\Windows\system32\CCM\Cache\ALD002C3 .6.System\windows6.1-KB976932-X86.exe" /quiet /nodialog /norestart, Working Directory = C:\Windows\system32\CCM\Cache\ALD002C3 .6.System\ execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Created Process for the passed command line execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Raising event:
[sMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "ALD20A6B";
ClientID = "GUID:FF83D13E-792F-4351-B8FB-F61A741CB735";
CommandLine = "\"C:\\Windows\\system32\\CCM\\Cache\\ALD002C3 .6.System\\windows6.1-KB976932-X86.exe\" /quiet /nodialog /norestart";
DateTime = "20120402111609.470000+000";
MachineName = "STTEST04";
PackageName = "ALD002C3 ";
ProcessID = 16228;
ProgramName = "sp1_install";
SiteCode = "ALD";
ThreadID = 18896;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\ALD002C3 .6.System\\";
};
execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Raised Program Started Event for Ad:ALD20A6B, Package:ALD002C3 , Program: sp1_install execmgr 02/04/2012 13:16:09 18896 (0x49D0)
Program exit code 14090 execmgr 02/04/2012 13:16:17 18088 (0x46A8)
Looking for MIF file to get program status execmgr 02/04/2012 13:16:17 18088 (0x46A8)
Script for Package:ALD002C3 , Program: sp1_install failed with exit code 14090 execmgr 02/04/2012 13:16:17 18088 (0x46A8)
Raising event:
[sMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramErrorEvent
{
AdvertisementId = "ALD20A6B";
ClientID = "GUID:FF83D13E-792F-4351-B8FB-F61A741CB735";
DateTime = "20120402111617.738000+000";
ExitCode = "14090";
MachineName = "STTEST04";
PackageName = "ALD002C3 ";
ProcessID = 16228;
ProgramName = "sp1_install";
SiteCode = "ALD";
ThreadID = 18088;
UserContext = "NT AUTHORITY\\SYSTEM";
};
execmgr 02/04/2012 13:16:17 18088 (0x46A8)
Raised Program Error Event for Ad:ALD20A6B, Package:ALD002C3 , Program: sp1_install execmgr 02/04/2012 13:16:17 18088 (0x46A8)
Execution is complete for program sp1_install. The exit code is 14090, the execution status is FailureNonRetry execmgr 02/04/2012 13:16:17 17144 (0x42F8)

[Peter33]

Try running this tool manually on the faulty system.

[Kingskawn]

Try running this tool manually on the faulty system.

 

Thanks Peter but it didn't work out. The KB947821 fixed some 439 error on 457 but I received the same error when launching SP1. Even after a "sfc /scannow"

 

Error: ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE(0x8007370a)

[Peter33]

Well, that's bad. Sounds like the side by side assemblies are kinda messed up. Maybe caused by a snapshot installation.

We had also 2 machines where the tool didn't work. Ended up with a reimaging because i did'nt want to waste to many time on it.

[Kingskawn]

Yes in this case it's better to reinstall the machine completely. Thanks for your help