Windows 7 x64 SP1 Updating Failing


  1. Posts : 3
    Windows 7 Professional x64
       #1

    Windows 7 x64 SP1 Updating Failing


    Hey guys, been messing with this one all day.
    Sourced a lot of information on the net and it looks like it comes down to needing to find the missing files from these logs and hoping that fixes the issue.

    I tried to source the files from local machines with no luck so reaching out to you guys, who I imagine must have a huge database of these by now :)

    I would have a bit more info for you but this is a users computer and have already taken enough of his work time troubleshooting today so I have the logs that I emailed myself attached.

    The error I remember was "No Signature" when I tried a stand alone update, and with the Windows Update it was a generic error code related to missing files.


    Code:
    Summary:
    Seconds executed: 1212
     Found 34 errors
      CSI Manifest All Zeros Total count: 28
      CBS MUM Corrupt Total count: 3
      CBS Catalog Corrupt Total count: 3
    
    Unavailable repair files:
    	winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_cb285ee688aa009a.manifest
    	winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_6f09c362d04c8f64.manifest
    	winsxs\manifests\msil_windowsbase_31bf3856ad364e35_6.1.7600.20658_none_97a251cfa9f9bf71.manifest
    	winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_cc28a17e399280f3.manifest
    	winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_700a05fa81350fbd.manifest
    	winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_ccad701952b2d4b8.manifest
    	winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_708ed4959a556382.manifest
    	winsxs\manifests\amd64_presentationcore_31bf3856ad364e35_6.1.7600.16542_none_084e4684a9878ea8.manifest
    	winsxs\manifests\x86_presentationcore_31bf3856ad364e35_6.1.7600.16542_none_ac2fab00f12a1d72.manifest
    	winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_b40f0fc47a79b870.manifest
    	winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_57f07440c21c473a.manifest
    	winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_86a84af193626297.manifest
    	winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_2a89af6ddb04f161.manifest
    	winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_cc11679639b12365.manifest
    	winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_6ff2cc128153b22f.manifest
    	winsxs\manifests\msil_windowsbase_31bf3856ad364e35_6.1.7600.16542_none_971d833490d96bac.manifest
    	winsxs\manifests\msil_presentationframework_31bf3856ad364e35_6.1.7600.16542_none_76b62ec655328f6e.manifest
    	winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_cc96363152d1772a.manifest
    	winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_70779aad9a7405f4.manifest
    	winsxs\manifests\x86_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_acb4799c0a4a7137.manifest
    	winsxs\manifests\amd64_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_08d3151fc2a7e26d.manifest
    	winsxs\manifests\msil_presentationframework_31bf3856ad364e35_6.1.7600.20658_none_773afd616e52e333.manifest
    	winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_872d198cac82b65c.manifest
    	winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_2b0e7e08f4254526.manifest
    	winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_b38a4129615964ab.manifest
    	winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_576ba5a5a8fbf375.manifest
    	winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_caa3904b6f89acd5.manifest
    	winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_6e84f4c7b72c3b9f.manifest
    	servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
    	servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
    	servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
    	servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    	servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    	servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
    	servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    I'll post a fix protocol for these files a bit later. It looks to me as if the machine may have had this problem for a considerable time - the affected patch was released in 2009 if I remember rightly.

    There are likely to be a LOT of updates to install once this is fixed :)
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    I've uploaded afile - vxuaa.zip - to my SkyDrive at Noel's SkyDrive

    Please downloadand save it.

    Right-click onthe downloaded file, and select Extract all…

    Extract to thedefault location - which will create a new folder vxuaain the same place.

    Open this folder- there should be two folders inside it (Manifests,and Packages)



    Copy the content of the Packages folder to thefolder

    C:\Windows\Temp\CheckSur\Servicing\Packages



    Andthe content of the manifestsfolder (.manifest files) into this folder:



    C:\Windows\Temp\CheckSur\Winsxs\Manifests



    Nowrun the CheckSUR tool again (it may take a while)
    Reboot


    Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.

    Then rin an SFC /SCANNOW, and post the CBS.log file.
      My Computer


  4. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #4

    Much appreciated, when I get back to work on Monday I will take initiative and see if this fixes everything up.

    And yeah this guy worked for the company for like 7 years, he sat on this forever before reporting it to IT and I took the ticket to fix it. Without your help it would have been impossible to source those files lol.

    I wonder if there is a good way for me to get a database of my own incase something like this happens again, most IT guys would just re-image the computer but I hate taking the easy way out.
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    In a corporate environment reimaging is the cost-effective solution. ;-)
      My Computer


  6. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #6

    Looks like everything is updating now. Just has SP1 go through. So hope there is no more issues getting up to the current updates.

    Thanks for all the help!
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #7

    Great!- good luck.
    Please post the new CheckSUR and CBS logs when you can :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:18.
Find Us