Windows Update failing


  1. Posts : 2
    Windows 7 Ultimate x32
       #1

    Windows Update failing


    niemiro said:
    OK, so half an hour when to pot, and turned into 12 hours.

    Anyway, the overall reason is that a single file name can have multiple contents, and not all computers have every file.

    Well, the correct way is to extract a replacement file from the actual install, which makes sense.

    Right, there are two tutorials for System Update Readiness Tool logfiles, both of which are long, and both of which only brush the surface. If you are truly dedicated, read this! System Update Readiness Tool - CheckSur.log File Analyzis

    It is not an easy read. The author's first language is not English, and it can be hard to follow at times.

    However, it also teaches the basic, fundamental techniques. These are not longer used. Nowadays, we have automated tools (written by me ) to automate almost all scenarios, and tutorials for their use, usually reserved for apprentices in this field of study. If you are interested, send me a Private Message, and tell me which bits you are interested in. You are more than welcome to (and I am the author so I have the keys and rights)

    Right, let's do things the semi-manual way.

    Look again at your log. Take an example line.

    "Package_for_KB2559049~31bf3856ad364e35~amd64~~6.1.1.2.cat"

    Find which Knowledge Base (KB) article it belongs to, in this case KB2559049.

    Check that there are no other KBs in the log. For you, there are not. If there are, repeat the below for each one.

    Visit support.microsoft.com/kb/{number}, in this case support.microsoft.com/kb/2559049

    (TIP: In actual fact, it is faster to Google KB2559049)

    Select the download link for IT Professionals (none of the others will bring you to the correct page)

    Find the correct download link: Download Details - Microsoft Download Center - Cumulative Security Update for Internet Explorer 8 in Windows 7 x64 Edition (KB2559049)

    Understand now why I asked if you had IE8 or IE9?

    Download it.

    The above tutorial will show you how to extract it.

    However, that is really slow. If you want to be an efficient pro, follow this tutorial instead: Windows Update - Extract an Update

    Now use your extracted files to produce your fix. It will take ages!

    But look, I have a tool to automate the whole thing!

    Attachment 177660

    Attachment 177659

    Now that does save me a lot of time! It will analyse the log file, extract the update, create the fix, and .zip it up for me! I really no longer do any work at all! If you want a copy, please drop me a PM. And that goes for anybody reading this.

    Very soon, there will be a version of that tool which inexperienced users can use. It features a nice wizard, analyses the log file, downloads the required files from Microsoft servers, creates the fix, and fixes the machine, all in a simple to use Next->Next->Finish format. Now that is cool About 1 month away. Perfectly in time for any trends in Windows 8 update failures. I shall be hot off the mark for Windows 8!

    There are so many more programs of mine, tricks, and so much more to learn. If you are interested, ask or PM me! Anyway, onto the fix (which you hopefully understand a little better now)

    WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!
    @Crowface: Ignore the above :)

    Download the attached .zip file. Inside it, will be two folders, Packages and Manifests.

    Create these folders if they do not already exist: C:\Windows\Temp\CheckSur\Servicing\Packages\ and C:\Windows\Temp\CheckSur\winsxs\Manifests

    Extract Packs.zip onto your Desktop. Please place the contents of my Desktop\Packages in C:\Windows\Temp\CheckSur\Servicing\Packages\ and my Desktop\Manifests in C:\Windows\Temp\CheckSur\winsxs\Manifests.

    DO NOT place the .zip file in that folder, or the folders themselves. Make sure that a lot of files are in each of those Checksur folder. NOTE: For you there are no manifests. Just move on.

    Re-run the System Update Readiness Tool, and get me another copy of C:\Windows\Logs\CBS\CheckSUR.log.

    Also, please retest Windows Updates (with fingers slightly crossed, no matter how much we both know that that won't help! lol.)

    Thanks a lot!

    Richard
    AHHHH finally, someone or something that can help, niemiro, or Richard, i am having the same issue with my pc and am wondering if you could create a .zip fix for me to. I'm only new to the forum and odn't even know how to send a pm, so maybe you pm me first or send me your email address. I'll paste my checksur log here for you anyway. Thank you in advance for your help, Cris :)


    ps, the user friendly version of your program, when will that be publicly available? Or even the current version, if it ever will be made available?


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 13.0
    2011-10-04 20:22

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: —Þf}¢U$·~ÿ\ƒl~=Ø*ÀrtIqièàkOr‘Ó,‘¡‚0‚ *†H†÷
     1‚
    0‚
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 0‚"C *†H†÷
    *‚"40‚"01 0 +
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 510

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 320
    Found 3 errors
    CBS MUM Corrupt Total count: 3

    Unavailable repair files:
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
      My Computer


  2. Posts : 908
    Vista Home Premium x86 SP2
       #2

    cliddell93 said:
    AHHHH finally, someone or something that can help, niemiro, or Richard, i am having the same issue with my pc and am wondering if you could create a .zip fix for me to. I'm only new to the forum and don't even know how to send a pm, so maybe you pm me first or send me your email address. I'll paste my checksur log here for you anyway. Thank you in advance for your help, Cris :)


    ps, the user friendly version of your program, when will that be publicly available? Or even the current version, if it ever will be made available?


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 13.0
    2011-10-04 20:22

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: —Þf}¢U$·~ÿ\ƒl~=Ø*ÀrtIqièàkOr‘Ó,‘¡‚0‚ *†H†÷
     1‚
    0‚
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 0‚"C *†H†÷
    *‚"40‚"01 0 +
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 510

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 320
    Found 3 errors
    CBS MUM Corrupt Total count: 3

    Unavailable repair files:
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
    Hello Cris, and welcome to the Seven Forums!

    lol, my post came copied, spelling mistake and all!

    Don't worry about PMs or emails, I think you will find that posting like this works perfectly well :)

    "ps, the user friendly version of your program, when will that be publicly available? Or even the current version, if it ever will be made available?"

    Not in time for you unfortunately! The current one - about two weeks. The user friendly one - one to two months.

    However, in the mean time, we can still do things manually :)

    WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!
    @{USER}: Ignore the above :)

    Download the attached .zip file. Inside it, will be two folders, Packages and Manifests.

    Create these folders if they do not already exist: C:\Windows\Temp\CheckSur\Servicing\Packages\ and C:\Windows\Temp\CheckSur\winsxs\Manifests

    Extract Packs.zip onto your Desktop. Please place the contents of my Desktop\Packages in C:\Windows\Temp\CheckSur\Servicing\Packages\ and my Desktop\Manifests in C:\Windows\Temp\CheckSur\winsxs\Manifests.

    Note that for you there are no manifests, and so just ignore this step.

    DO NOT place the .zip file in that folder, or the folders themselves. Make sure that a lot of files are in each of those Checksur folder.

    Re-run the System Update Readiness Tool, and get me another copy of C:\Windows\Logs\CBS\CheckSUR.log.

    Also, please retest Windows Updates (with fingers slightly crossed, no matter how much we both know that that won't help! lol.)

    Thanks a lot!

    Richard
    Windows Update failing Attached Files
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x32
    Thread Starter
       #3

    thanks you so much Richard, for your help and also for a very speedy reply. one problem, the manifest folder in the packs.zip has nothing in it, be they hidden or otherwise. is this normal? im assuming not, but i no very little about the area of microsoft witchery so could you please shed some light, again, thanks, Cris :)

    EDIT: wow, i should learn to read properly haha, sorry i just seen the part that said there are no manifests for me, however, it still doesnt work for me
    Here is the new log for you



    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 13.0
    2011-10-04 20:22

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: —Þf}¢U$·~ÿ\ƒl~=Ø*ÀrtIqièàkOr‘Ó,‘¡‚0‚ *†H†÷
     1‚
    0‚
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 0‚"C *†H†÷
    *‚"40‚"01 0 +
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1: 510

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 320
    Found 3 errors
    CBS MUM Corrupt Total count: 3

    Unavailable repair files:
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    servicing\packages\Package_for_KB2562937~31bf3856ad364e35~x86~~6.1.1.0.cat
    Last edited by cliddell93; 09 Oct 2011 at 03:08.
      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 17:37.
Find Us