[SOLVED] Windows 7 SP1 installation fails with Error Code 80073701

[maddi]

Hi there,

I try to install SP1 on my win7 x64 system which fails with error code 80073701:

Error CSI 0000010f (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #788295# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-SampleContent-Music-Deployment, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [97]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples", rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

I attached the CBS log and the log from the Readiness Tool.

I already fixed severals problems that where shown by the Readiness Tool before so that by now this log is clean and only one error in the CBS log remains. I both checked the registry and the windows folder for the faulty package: Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 - but only found this one: Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7600.16385

I hope you guys can help me out with this and if you need more information just let me know.

Thank you in advance!

Maddi

 

[niemiro]

Hello Maddi, and welcome to Sysnative!

How did you make the replacements of the corrupt payload files?

The reason why I say this is that I guess you had to alter file permissions to make the replacement. The permissions model changed dramatically with Windows Vista, and the reason I am mildly concerned is simply security. With Windows XP, permissions were a bit of a bolt on to the security model. They allowed system admins finer control over who could edit/whatever certain files. In Windows Vista, they are the security model. Permissions are far more complex, and the security of system files is now no longer tied into whether the active account is an admin (Microsoft know that too many people run as admin by default), but whether the current context (may not be the same as current user) has the right to alter that file. Permissions are restricted by ownership, ownership is restricted by administratorship. But when the permissions are reset, virtually any unknown script or user can change system files. So in theory at least, those files are now somewhat vulnerable.

I would like to first repair the permissions on these files, but I first need to know how you made the replacements (via a Linux live CD, via resetting all file permission for the entire drive, per folder, whatever really.

Richard

 

[maddi]

Hello Richard and thank you four your reply!

your guess is right. What I did was taking the ownership of the winsxs folder for my windows user (admin rights) and granting full security rights for administrators directly in windows. I did the same thing in the registry with the Component Bases Servicing folder.

Maddi

 

[maddi]

So what should I do now?

 

[maddi]

Meanwhile I did an Inplace Update of my Windows because I was really worried about the missing SP1 and all security update... now everything works fine while my settings and programs are kept :)