1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Windows update error code 800B0100

Discussion in 'Windows Vista' started by Jim, Jun 7, 2009.

Page 1 of 2
  1. Jim

    Jim Guest

    Trying to do a Windows update my laptop but having problems.

    Update stops with message:-
    Code 800B0100 - Windows Update encountered an unknown error

    I tried the System Update Readiness Tool (CheckSUR) as advised on the
    Microsoft link but did not help - still getting the error.

    I am using Vista Home Premium (32 bit) SP1

    I can only see this Vista group on my news server - is there a better on
    elsewhere for these problem types?

    Thanks


    --

    Jim
     
    Jim, Jun 7, 2009
    #1
  3. Tae Song

    Tae Song Guest

    "Jim" <jim@nospam.net> wrote in message
    news:4a2b8ed4$1@extreme.x-privat.org...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Trying to do a Windows update my laptop but having problems.
    >
    > Update stops with message:-
    > Code 800B0100 - Windows Update encountered an unknown error
    >
    > I tried the System Update Readiness Tool (CheckSUR) as advised on the
    > Microsoft link but did not help - still getting the error.
    >
    > I am using Vista Home Premium (32 bit) SP1
    >
    > I can only see this Vista group on my news server - is there a better on
    > elsewhere for these problem types?
    >
    > Thanks
    >
    >
    > --
    >
    > Jim
    ><!--colorc--><!--/colorc-->

    Run SFC /SCANNOW

    If SFC says there are problems let me know.
     
    Tae Song, Jun 7, 2009
    #2
  4. Mick Murphy

    Mick Murphy Guest



    The above Vista Forums are the ones to use.
    --
    Mick Murphy


    "Jim" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Trying to do a Windows update my laptop but having problems.
    >
    > Update stops with message:-
    > Code 800B0100 - Windows Update encountered an unknown error
    >
    > I tried the System Update Readiness Tool (CheckSUR) as advised on the
    > Microsoft link but did not help - still getting the error.
    >
    > I am using Vista Home Premium (32 bit) SP1
    >
    > I can only see this Vista group on my news server - is there a better on
    > elsewhere for these problem types?
    >
    > Thanks
    >
    >
    > --
    >
    > Jim
    >
    >
    > <!--colorc--><!--/colorc-->
     
    Mick Murphy, Jun 7, 2009
    #3
  5. Jim

    Jim Guest

    --


    --

    Jim
    "Tae Song" <tae_song@hotmail.com> wrote in message
    news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Jim" <jim@nospam.net> wrote in message
    > news:4a2b8ed4$1@extreme.x-privat.org...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Trying to do a Windows update my laptop but having problems.
    >>
    >> Update stops with message:-
    >> Code 800B0100 - Windows Update encountered an unknown error
    >>
    >> I tried the System Update Readiness Tool (CheckSUR) as advised on the
    >> Microsoft link but did not help - still getting the error.
    >>
    >> I am using Vista Home Premium (32 bit) SP1
    >>
    >> I can only see this Vista group on my news server - is there a better on
    >> elsewhere for these problem types?
    >>
    >> Thanks
    >>
    >>
    >> --
    >>
    >> Jim
    >><!--colorc--><!--/colorc-->
    >
    > Run SFC /SCANNOW
    >
    > If SFC says there are problems let me know.
    >
    >
    >
    >
    ><!--colorc--><!--/colorc-->
    Thanks

    Yes did produce errors, a 40KB log file!!

    -
     
    Jim, Jun 7, 2009
    #4
  6. Tae Song

    Tae Song Guest

    "Jim" <jim@nospam.net> wrote in message
    news:4a2ba224@extreme.x-privat.org...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >
    > --
    >
    >
    > --
    >
    > Jim
    > "Tae Song" <tae_song@hotmail.com> wrote in message
    > news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >> "Jim" <jim@nospam.net> wrote in message
    >> news:4a2b8ed4$1@extreme.x-privat.org...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Trying to do a Windows update my laptop but having problems.
    >>>
    >>> Update stops with message:-
    >>> Code 800B0100 - Windows Update encountered an unknown error
    >>>
    >>> I tried the System Update Readiness Tool (CheckSUR) as advised on the
    >>> Microsoft link but did not help - still getting the error.
    >>>
    >>> I am using Vista Home Premium (32 bit) SP1
    >>>
    >>> I can only see this Vista group on my news server - is there a better on
    >>> elsewhere for these problem types?
    >>>
    >>> Thanks
    >>>
    >>>
    >>> --
    >>>
    >>> Jim
    >>><!--colorc--><!--/colorc-->
    >>
    >> Run SFC /SCANNOW
    >>
    >> If SFC says there are problems let me know.
    >>
    >>
    >>
    >>
    >><!--colorc--><!--/colorc-->
    > Thanks
    >
    > Yes did produce errors, a 40KB log file!!
    >
    > -
    >
    >
    ><!--colorc--><!--/colorc-->

    Did SFC say there were problems it couldn't repair? 40KB CBS.log is
    unusually small, unless you meant 40MB.

    If it says there were problems SFC couldn't fix, delete the CBS.log and run
    SFC /SCANNOW again. You'll end up with a much smaller CBS.log. Copy it and
    open the copy and look for a section that says... repairing 3 components ...
    where 3 could be a different number depending on how many problems SFC scan
    found.

    Text falling the repairing components section should tell you which
    components could not be repaired.
     
    Tae Song, Jun 7, 2009
    #5
  7. Planters

    Planters Guest

    Jim wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Trying to do a Windows update my laptop but having problems.
    >
    > Update stops with message:-
    > Code 800B0100 - Windows Update encountered an unknown error
    >
    > I tried the System Update Readiness Tool (CheckSUR) as advised on the
    > Microsoft link but did not help - still getting the error.
    >
    > I am using Vista Home Premium (32 bit) SP1
    >
    > I can only see this Vista group on my news server - is there a better on
    > elsewhere for these problem types?
    >
    > Thanks<!--colorc--><!--/colorc-->

    Maybe, you should run Vista's System File Checker to see if there are
    corrupted files that is causing the update to abort.
     
    Planters, Jun 7, 2009
    #6
  8. Tae Song

    Tae Song Guest

    "Tae Song" <tae_song@hotmail.com> wrote in message
    news:5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Jim" <jim@nospam.net> wrote in message
    > news:4a2ba224@extreme.x-privat.org...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >>
    >> --
    >>
    >>
    >> --
    >>
    >> Jim
    >> "Tae Song" <tae_song@hotmail.com> wrote in message
    >> news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> "Jim" <jim@nospam.net> wrote in message
    >>> news:4a2b8ed4$1@extreme.x-privat.org...
    >>>> Trying to do a Windows update my laptop but having problems.
    >>>>
    >>>> Update stops with message:-
    >>>> Code 800B0100 - Windows Update encountered an unknown error
    >>>>
    >>>> I tried the System Update Readiness Tool (CheckSUR) as advised on the
    >>>> Microsoft link but did not help - still getting the error.
    >>>>
    >>>> I am using Vista Home Premium (32 bit) SP1
    >>>>
    >>>> I can only see this Vista group on my news server - is there a better
    >>>> on elsewhere for these problem types?
    >>>>
    >>>> Thanks
    >>>>
    >>>>
    >>>> --
    >>>>
    >>>> Jim
    >>>>
    >>>
    >>> Run SFC /SCANNOW
    >>>
    >>> If SFC says there are problems let me know.
    >>>
    >>>
    >>>
    >>>
    >>><!--colorc--><!--/colorc-->
    >> Thanks
    >>
    >> Yes did produce errors, a 40KB log file!!
    >>
    >> -
    >>
    >>
    >><!--colorc--><!--/colorc-->
    >
    > Did SFC say there were problems it couldn't repair? 40KB CBS.log is
    > unusually small, unless you meant 40MB.
    >
    > If it says there were problems SFC couldn't fix, delete the CBS.log and
    > run SFC /SCANNOW again. You'll end up with a much smaller CBS.log. Copy
    > it and open the copy and look for a section that says... repairing 3
    > components ... where 3 could be a different number depending on how many
    > problems SFC scan found.
    >
    > Text falling the repairing components section should tell you which
    > components could not be repaired.<!--colorc--><!--/colorc-->

    Falling = following
     
    Tae Song, Jun 7, 2009
    #7
  9. Peter Foldes

    Peter Foldes Guest

    Jim

    Error message when you try to use the Windows Update or Microsoft Update Web
    sites to install updates: "0x800B0100"





    --
    Peter

    Please Reply to Newsgroup for the benefit of others
    Requests for assistance by email can not and will not be acknowledged.

    "Jim" <jim@nospam.net> wrote in message news:4a2b8ed4$1@extreme.x-privat.org...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Trying to do a Windows update my laptop but having problems.
    >
    > Update stops with message:-
    > Code 800B0100 - Windows Update encountered an unknown error
    >
    > I tried the System Update Readiness Tool (CheckSUR) as advised on the
    > Microsoft link but did not help - still getting the error.
    >
    > I am using Vista Home Premium (32 bit) SP1
    >
    > I can only see this Vista group on my news server - is there a better on
    > elsewhere for these problem types?
    >
    > Thanks
    >
    >
    > --
    >
    > Jim
    >
    ><!--colorc--><!--/colorc-->
     
    Peter Foldes, Jun 7, 2009
    #8
  10. Peter Foldes

    Peter Foldes Guest

    Tae Song

    Hog Wash. For Windows Update error's and any other ones using the CBS .log is like
    trying spit against the wind. Would you kindly stop using this method in most of
    your posts.It does not help.
    If you cannot research the issue properly then do not do it all . Thank You

    --
    Peter

    Please Reply to Newsgroup for the benefit of others
    Requests for assistance by email can not and will not be acknowledged.

    "Tae Song" <tae_song@hotmail.com> wrote in message
    news:5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Jim" <jim@nospam.net> wrote in message news:4a2ba224@extreme.x-privat.org...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >>
    >> --
    >>
    >>
    >> --
    >>
    >> Jim
    >> "Tae Song" <tae_song@hotmail.com> wrote in message
    >> news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> "Jim" <jim@nospam.net> wrote in message news:4a2b8ed4$1@extreme.x-privat.org...
    >>>> Trying to do a Windows update my laptop but having problems.
    >>>>
    >>>> Update stops with message:-
    >>>> Code 800B0100 - Windows Update encountered an unknown error
    >>>>
    >>>> I tried the System Update Readiness Tool (CheckSUR) as advised on the Microsoft
    >>>> link but did not help - still getting the error.
    >>>>
    >>>> I am using Vista Home Premium (32 bit) SP1
    >>>>
    >>>> I can only see this Vista group on my news server - is there a better on
    >>>> elsewhere for these problem types?
    >>>>
    >>>> Thanks
    >>>>
    >>>>
    >>>> --
    >>>>
    >>>> Jim
    >>>>
    >>>
    >>> Run SFC /SCANNOW
    >>>
    >>> If SFC says there are problems let me know.
    >>>
    >>>
    >>>
    >>>
    >>><!--colorc--><!--/colorc-->
    >> Thanks
    >>
    >> Yes did produce errors, a 40KB log file!!
    >>
    >> -
    >>
    >>
    >><!--colorc--><!--/colorc-->
    >
    > Did SFC say there were problems it couldn't repair? 40KB CBS.log is unusually
    > small, unless you meant 40MB.
    >
    > If it says there were problems SFC couldn't fix, delete the CBS.log and run SFC
    > /SCANNOW again. You'll end up with a much smaller CBS.log. Copy it and open the
    > copy and look for a section that says... repairing 3 components ... where 3 could
    > be a different number depending on how many problems SFC scan found.
    >
    > Text falling the repairing components section should tell you which components
    > could not be repaired. <!--colorc--><!--/colorc-->
     
    Peter Foldes, Jun 7, 2009
    #9
  11. Tae Song

    Tae Song Guest

    "Peter Foldes" <okf22@hotmail.com> wrote in message
    news:OSmJjt25JHA.4332@TK2MSFTNGP06.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Tae Song
    >
    > Hog Wash. For Windows Update error's and any other ones using the CBS .log
    > is like trying spit against the wind. Would you kindly stop using this
    > method in most of your posts.It does not help.
    > If you cannot research the issue properly then do not do it all . Thank
    > You
    >
    > --
    > Peter<!--colorc--><!--/colorc-->

    It worked for me when I couldn't get SP2 to install. I went through CBS.log
    and found the problems and removed them from the registry. I installed SP2,
    no problems.
     
    Tae Song, Jun 7, 2009
    #10
  12. kidA

    kidA Guest

    Tae Song;1028160 Wrote: <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "Peter Foldes" <okf22@hotmail.com> wrote in message
    > news:OSmJjt25JHA.4332@TK2MSFTNGP06.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > Tae Song
    > >
    > > Hog Wash. For Windows Update error's and any other ones using the CBS<!--colorc--><!--/colorc-->
    > .log <!--coloro:green--><span style="color:green <!--/coloro-->
    > > is like trying spit against the wind. Would you kindly stop using<!--colorc--><!--/colorc-->
    > this <!--coloro:green--><span style="color:green <!--/coloro-->
    > > method in most of your posts.It does not help.
    > > If you cannot research the issue properly then do not do it all .<!--colorc--><!--/colorc-->
    > Thank <!--coloro:green--><span style="color:green <!--/coloro-->
    > > You
    > >
    > > --
    > > Peter<!--colorc--><!--/colorc-->
    >
    > It worked for me when I couldn't get SP2 to install. I went through
    > CBS.log
    > and found the problems and removed them from the registry. I installed
    > SP2,
    > no problems.<!--colorc--><!--/colorc-->

    TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    dreaded 0x80070490 error - tried the TAE registry open heart surgery and
    wham I'm now downloading much needed vista updates..

    Here's my steps: downloaded the update readiness tool from Microsoft
    ("checkSUR" - google it). After running it I found 2 registry errors
    (look in "/windows/logs/checkSUR.log" to see the results):

    "Checking packages.
    (f) CBS Registry
    Error 0x80070002 Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    to get CurrentState
    (f) CBS Registry
    Error 0x80070002 Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    to get Visibility

    Checking component store
    Summary:
    Seconds executed: 1032
    Found 2 errors"

    So off I goes into the registry (having done full system restore & reg
    backup) and delete all references to (in my case):

    "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"

    Jumped into windows update - clicked update & (after a while) bang -
    there are 29 updates for me to download - YIPPEE.

    NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM Vista
    Business)

    Hope it works for you!
     
    kidA, Jun 8, 2009
    #11
  13. Jim

    Jim Guest

    "Tae Song" <tae_song@hotmail.com> wrote in message
    news:5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Jim" <jim@nospam.net> wrote in message
    > news:4a2ba224@extreme.x-privat.org...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >>
    >> --
    >>
    >>
    >> --
    >>
    >> Jim
    >> "Tae Song" <tae_song@hotmail.com> wrote in message
    >> news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> "Jim" <jim@nospam.net> wrote in message
    >>> news:4a2b8ed4$1@extreme.x-privat.org...
    >>>> Trying to do a Windows update my laptop but having problems.
    >>>>
    >>>> Update stops with message:-
    >>>> Code 800B0100 - Windows Update encountered an unknown error
    >>>>
    >>>> I tried the System Update Readiness Tool (CheckSUR) as advised on the
    >>>> Microsoft link but did not help - still getting the error.
    >>>>
    >>>> I am using Vista Home Premium (32 bit) SP1
    >>>>
    >>>> I can only see this Vista group on my news server - is there a better
    >>>> on elsewhere for these problem types?
    >>>>
    >>>> Thanks
    >>>>
    >>>>
    >>>> --
    >>>>
    >>>> Jim
    >>>>
    >>>
    >>> Run SFC /SCANNOW
    >>>
    >>> If SFC says there are problems let me know.
    >>>
    >>>
    >>>
    >>>
    >>><!--colorc--><!--/colorc-->
    >> Thanks
    >>
    >> Yes did produce errors, a 40KB log file!!
    >>
    >> -
    >>
    >>
    >><!--colorc--><!--/colorc-->
    >
    > Did SFC say there were problems it couldn't repair? 40KB CBS.log is
    > unusually small, unless you meant 40MB.
    >
    > If it says there were problems SFC couldn't fix, delete the CBS.log and
    > run SFC /SCANNOW again. You'll end up with a much smaller CBS.log. Copy
    > it and open the copy and look for a section that says... repairing 3
    > components ... where 3 could be a different number depending on how many
    > problems SFC scan found.
    >
    > Text falling the repairing components section should tell you which
    > components could not be repaired.<!--colorc--><!--/colorc-->

    Yes I did mean 40MB.

    Can't progress this further for a couple of weeks as it was on my brother's
    machine. He was over for the weekend and I will catch up with him when I
    see him next.

    Thanks for your help.



    --

    Jim
     
    Jim, Jun 8, 2009
    #12
  14. Jim

    Jim Guest

    "Peter Foldes" <okf22@hotmail.com> wrote in message
    news:%23Vn6oq25JHA.4116@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Jim
    >
    > Error message when you try to use the Windows Update or Microsoft Update
    > Web sites to install updates: "0x800B0100"
    >
    >
    >
    >
    >
    > --
    > Peter
    >
    > Please Reply to Newsgroup for the benefit of others
    > Requests for assistance by email can not and will not be acknowledged.
    >
    > "Jim" <jim@nospam.net> wrote in message
    > news:4a2b8ed4$1@extreme.x-privat.org...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Trying to do a Windows update my laptop but having problems.
    >>
    >> Update stops with message:-
    >> Code 800B0100 - Windows Update encountered an unknown error
    >>
    >> I tried the System Update Readiness Tool (CheckSUR) as advised on the
    >> Microsoft link but did not help - still getting the error.
    >>
    >> I am using Vista Home Premium (32 bit) SP1
    >>
    >> I can only see this Vista group on my news server - is there a better on
    >> elsewhere for these problem types?
    >>
    >> Thanks
    >>
    >>
    >> --
    >>
    >> Jim<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->


    Can't progress this further for a couple of weeks as it was on my brother's
    machine. He was over for the weekend and I will catch up with him when I
    see him next.

    However, I tried this already but did not help.

    Thanks for your help.




    --

    Jim
     
    Jim, Jun 8, 2009
    #13
  15. Darrell Gorter[MSFT]

    Darrell Gorter[MSFT] Guest

    Hello Tae,
    This would probably be useful in helping identify the files reported as
    corrupted when using SFC

    you may want to use this line from an elevated cmd prompt to get all the
    SFC entries
    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

    more info in this article.
    928228 How to analyze the log file entries that the Microsoft Windows
    Resource Checker (SFC.exe) program generates in Windows Vista


    Thanks,
    Darrell Gorter[MSFT]

    This posting is provided "AS IS" with no warranties, and confers no rights
    --------------------
    | >From: "Tae Song" <tae_song@hotmail.com>
    | >References: <4a2b8ed4$1@extreme.x-privat.org>
    <E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com>
    <4a2ba224@extreme.x-privat.org>
    <5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com>
    | >In-Reply-To: <5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com>
    | >Subject: Re: Windows update error code 800B0100
    | >Date: Sun, 7 Jun 2009 08:20:00 -0400
    | >Lines: 1
    | >Message-ID: <A1286402-C252-48B3-810E-2F719EB6508C@microsoft.com>
    | >MIME-Version: 1.0
    | >Content-Type: text/plain;
    | > format=flowed;
    | > charset="Windows-1252";
    | > reply-type=response
    | >Content-Transfer-Encoding: 7bit
    | >X-Priority: 3
    | >X-MSMail-Priority: Normal
    | >Importance: Normal
    | >X-Newsreader: Microsoft Windows Live Mail 14.0.8064.206
    | >X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8064.206
    | >X-MS-CommunityGroup-PostID: {A1286402-C252-48B3-810E-2F719EB6508C}
    | >X-MS-CommunityGroup-ThreadID: 19707D5A-8F52-4C51-ADAC-6DB1BF453281
    | >X-MS-CommunityGroup-ParentID: 5548CA64-CDB6-4753-9894-D65E533212EE
    | >Newsgroups: microsoft.public.windows.vista.general
    | >Path: TK2MSFTNGHUB02.phx.gbl
    | >Xref: TK2MSFTNGHUB02.phx.gbl
    microsoft.public.windows.vista.general:406529
    | >NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
    | >X-Tomcat-NG: microsoft.public.windows.vista.general
    | >
    | >
    | >"Tae Song" <tae_song@hotmail.com> wrote in message
    | >news:5548CA64-CDB6-4753-9894-D65E533212EE@microsoft.com...
    | >>
    | >> "Jim" <jim@nospam.net> wrote in message
    | >> news:4a2ba224@extreme.x-privat.org...
    | >>>
    | >>>
    | >>> --
    | >>>
    | >>>
    | >>> --
    | >>>
    | >>> Jim
    | >>> "Tae Song" <tae_song@hotmail.com> wrote in message
    | >>> news:E7FCBC56-A185-42D4-85EE-636CDC010FA4@microsoft.com...
    | >>>>
    | >>>> "Jim" <jim@nospam.net> wrote in message
    | >>>> news:4a2b8ed4$1@extreme.x-privat.org...
    | >>>>> Trying to do a Windows update my laptop but having problems.
    | >>>>>
    | >>>>> Update stops with message:-
    | >>>>> Code 800B0100 - Windows Update encountered an unknown error
    | >>>>>
    | >>>>> I tried the System Update Readiness Tool (CheckSUR) as advised on
    the
    | >>>>> Microsoft link but did not help - still getting the error.
    | >>>>>
    | >>>>> I am using Vista Home Premium (32 bit) SP1
    | >>>>>
    | >>>>> I can only see this Vista group on my news server - is there a
    better
    | >>>>> on elsewhere for these problem types?
    | >>>>>
    | >>>>> Thanks
    | >>>>>
    | >>>>>
    | >>>>> --
    | >>>>>
    | >>>>> Jim
    | >>>>>
    | >>>>
    | >>>> Run SFC /SCANNOW
    | >>>>
    | >>>> If SFC says there are problems let me know.
    | >>>>
    | >>>>
    | >>>>
    | >>>>
    | >>>>
    | >>> Thanks
    | >>>
    | >>> Yes did produce errors, a 40KB log file!!
    | >>>
    | >>> -
    | >>>
    | >>>
    | >>>
    | >>
    | >> Did SFC say there were problems it couldn't repair? 40KB CBS.log is
    | >> unusually small, unless you meant 40MB.
    | >>
    | >> If it says there were problems SFC couldn't fix, delete the CBS.log
    and
    | >> run SFC /SCANNOW again. You'll end up with a much smaller CBS.log.
    Copy
    | >> it and open the copy and look for a section that says... repairing 3
    | >> components ... where 3 could be a different number depending on how
    many
    | >> problems SFC scan found.
    | >>
    | >> Text falling the repairing components section should tell you which
    | >> components could not be repaired.
    | >
    | >Falling = following
    | >
    | >
     
    Darrell Gorter[MSFT], Jun 8, 2009
    #14
  16. Tae Song

    Tae Song Guest

    ""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
    news:p7Zw9hK6JHA.2060@TK2MSFTNGHUB02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hello Tae,
    > This would probably be useful in helping identify the files reported as
    > corrupted when using SFC
    >
    > you may want to use this line from an elevated cmd prompt to get all the
    > SFC entries
    > findstr /c:"[SR]" %windir%logscbscbs.log >sfcdetails.txt
    >
    > more info in this article.
    > 928228 How to analyze the log file entries that the Microsoft Windows
    > Resource Checker (SFC.exe) program generates in Windows Vista
    >
    >
    > Thanks,
    > Darrell Gorter[MSFT]
    ><!--colorc--><!--/colorc-->

    Thank you, I will use it at earliest possibly opportunity.
     
    Tae Song, Jun 8, 2009
    #15
  17. Tae Song

    Tae Song Guest

    "kidA" <kidA.3tihef@no.email.invalid> wrote in message
    news:kidA.3tihef@no.email.invalid...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > Tae Song;1028160 Wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    >> "Peter Foldes" <okf22@hotmail.com> wrote in message
    >> news:OSmJjt25JHA.4332@TK2MSFTNGP06.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >> > Tae Song
    >> >
    >> > Hog Wash. For Windows Update error's and any other ones using the CBS<!--colorc--><!--/colorc-->
    >> .log<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >> > is like trying spit against the wind. Would you kindly stop using<!--colorc--><!--/colorc-->
    >> this<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >> > method in most of your posts.It does not help.
    >> > If you cannot research the issue properly then do not do it all .<!--colorc--><!--/colorc-->
    >> Thank<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >> > You
    >> >
    >> > --
    >> > Peter<!--colorc--><!--/colorc-->
    >>
    >> It worked for me when I couldn't get SP2 to install. I went through
    >> CBS.log
    >> and found the problems and removed them from the registry. I installed
    >> SP2,
    >> no problems.<!--colorc--><!--/colorc-->
    >
    > TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    > dreaded 0x80070490 error - tried the TAE registry open heart surgery and
    > wham I'm now downloading much needed vista updates..
    >
    > Here's my steps: downloaded the update readiness tool from Microsoft
    > ("checkSUR" - google it). After running it I found 2 registry errors
    > (look in "/windows/logs/checkSUR.log" to see the results):
    >
    > "Checking packages.
    > (f) CBS Registry
    > Error 0x80070002
    > Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    > to get CurrentState
    > (f) CBS Registry
    > Error 0x80070002
    > Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    > to get Visibility
    >
    > Checking component store
    > Summary:
    > Seconds executed: 1032
    > Found 2 errors"
    >
    > So off I goes into the registry (having done full system restore & reg
    > backup) and delete all references to (in my case):
    >
    > "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"
    >
    > Jumped into windows update - clicked update & (after a while) bang -
    > there are 29 updates for me to download - YIPPEE.
    >
    > NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM Vista
    > Business)
    >
    > Hope it works for you!
    >
    ><!--colorc--><!--/colorc-->

    I glad you got it working! Cross posting to microsoft.public.windowsupdate
    for proof this is how to troubleshoot many Windows Update problem.
     
    Tae Song, Jun 10, 2009
    #16
  18. Harry Johnston [MVP]

    Harry Johnston [MVP] Guest

    Ouch! Removing those registry entries sounds like a very dangerous move.
    There's no telling what the side-effects could be.

    I haven't used Vista enough to know what the correct way to fix this class of
    problem is, but I very much doubt this is it.

    kidA: I recommend backing up your files and doing a full reinstall (not a
    repair) of your operating system.

    Tae: if you have Microsoft documentation to support use of this procedure,
    please provide the appropriate links.

    Harry.

    Tae Song wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "kidA" <kidA.3tihef@no.email.invalid> wrote in message
    > news:kidA.3tihef@no.email.invalid...<!--colorc--><!--/colorc-->
    <!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
    >> TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    >> dreaded 0x80070490 error - tried the TAE registry open heart surgery and
    >> wham I'm now downloading much needed vista updates..
    >>
    >> Here's my steps: downloaded the update readiness tool from Microsoft
    >> ("checkSUR" - google it). After running it I found 2 registry errors
    >> (look in "/windows/logs/checkSUR.log" to see the results):
    >>
    >> "Checking packages.
    >> (f) CBS Registry
    >> Error 0x80070002
    >> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >> to get CurrentState
    >> (f) CBS Registry
    >> Error 0x80070002
    >> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >> to get Visibility
    >>
    >> Checking component store
    >> Summary:
    >> Seconds executed: 1032
    >> Found 2 errors"
    >>
    >> So off I goes into the registry (having done full system restore & reg
    >> backup) and delete all references to (in my case):
    >>
    >> "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"
    >>
    >> Jumped into windows update - clicked update & (after a while) bang -
    >> there are 29 updates for me to download - YIPPEE.
    >>
    >> NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM Vista
    >> Business)
    >>
    >> Hope it works for you!
    >>
    >><!--colorc--><!--/colorc-->
    >
    > I glad you got it working! Cross posting to
    > microsoft.public.windowsupdate for proof this is how to troubleshoot
    > many Windows Update problem.<!--colorc--><!--/colorc-->
     
    Harry Johnston [MVP], Jun 11, 2009
    #17
  19. Tae Song

    Tae Song Guest

    "Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
    news:uHD$lXv6JHA.4404@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Ouch! Removing those registry entries sounds like a very dangerous move.
    > There's no telling what the side-effects could be.
    >
    > I haven't used Vista enough to know what the correct way to fix this class
    > of problem is, but I very much doubt this is it.
    >
    > kidA: I recommend backing up your files and doing a full reinstall (not a
    > repair) of your operating system.
    >
    > Tae: if you have Microsoft documentation to support use of this procedure,
    > please provide the appropriate links.
    >
    > Harry.
    >
    > Tae Song wrote:
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >> "kidA" <kidA.3tihef@no.email.invalid> wrote in message
    >> news:kidA.3tihef@no.email.invalid...<!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    >>> dreaded 0x80070490 error - tried the TAE registry open heart surgery and
    >>> wham I'm now downloading much needed vista updates..
    >>>
    >>> Here's my steps: downloaded the update readiness tool from Microsoft
    >>> ("checkSUR" - google it). After running it I found 2 registry errors
    >>> (look in "/windows/logs/checkSUR.log" to see the results):
    >>>
    >>> "Checking packages.
    >>> (f) CBS Registry
    >>> Error 0x80070002
    >>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>> to get CurrentState
    >>> (f) CBS Registry
    >>> Error 0x80070002
    >>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>> to get Visibility
    >>>
    >>> Checking component store
    >>> Summary:
    >>> Seconds executed: 1032
    >>> Found 2 errors"
    >>>
    >>> So off I goes into the registry (having done full system restore & reg
    >>> backup) and delete all references to (in my case):
    >>>
    >>> "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"
    >>>
    >>> Jumped into windows update - clicked update & (after a while) bang -
    >>> there are 29 updates for me to download - YIPPEE.
    >>>
    >>> NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM Vista
    >>> Business)
    >>>
    >>> Hope it works for you!
    >>>
    >>><!--colorc--><!--/colorc-->
    >>
    >> I glad you got it working! Cross posting to
    >> microsoft.public.windowsupdate for proof this is how to troubleshoot many
    >> Windows Update problem.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->


    Editing the registry by hand is always dangerous, which is why I tell them
    to back up the entries before deleting them.

    For whatever reason, sometimes there will be system file(s) installed that
    doesn't match up with the what it says in the registry.

    My theory is there is in some cases if you do a point restore, some system
    files are replaced with a previous version.

    Registry keys are changed back to work with these system files, however the
    entries for the latest system files that used to be installed is not
    deleted. Since they are kept for record purposes only.

    When you run System File Checker, it looks at these records in the registry
    and uses the LATEST system file entry which does not match with the system
    file you have installed because the system restored an older version.

    Windows Update runs the same kind of check on the system files, before
    attempting to install updates.

    This is why I ask people to run SFC to isolate which entries are no longer
    valid. Assuming this is caused by System Restore, it SHOULD delete or flag
    the entries as no longer installed when it replaces a new system file with
    an older one.

    As far as I can tell it does not do this, so what I am doing is having
    people go in and manually delete the invalid entries.

    Does that make sense?
     
    Tae Song, Jun 12, 2009
    #18
  20. Harry Johnston [MVP]

    Harry Johnston [MVP] Guest

    Tae Song wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Editing the registry by hand is always dangerous, which is why I tell
    > them to back up the entries before deleting them.<!--colorc--><!--/colorc-->

    Not really adequate IMO since problems may develop later, by which time there
    won't be any way to tell what caused them.

    However, since MowGreen has found a reference to a MS engineer recommending the
    same procedure, that's moot now. :)

    Harry.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
    > news:uHD$lXv6JHA.4404@TK2MSFTNGP04.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Ouch! Removing those registry entries sounds like a very dangerous
    >> move. There's no telling what the side-effects could be.
    >>
    >> I haven't used Vista enough to know what the correct way to fix this
    >> class of problem is, but I very much doubt this is it.
    >>
    >> kidA: I recommend backing up your files and doing a full reinstall
    >> (not a repair) of your operating system.
    >>
    >> Tae: if you have Microsoft documentation to support use of this
    >> procedure, please provide the appropriate links.
    >>
    >> Harry.
    >>
    >> Tae Song wrote:
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> "kidA" <kidA.3tihef@no.email.invalid> wrote in message
    >>> news:kidA.3tihef@no.email.invalid...<!--colorc--><!--/colorc-->
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>> TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    >>>> dreaded 0x80070490 error - tried the TAE registry open heart surgery
    >>>> and
    >>>> wham I'm now downloading much needed vista updates..
    >>>>
    >>>> Here's my steps: downloaded the update readiness tool from Microsoft
    >>>> ("checkSUR" - google it). After running it I found 2 registry errors
    >>>> (look in "/windows/logs/checkSUR.log" to see the results):
    >>>>
    >>>> "Checking packages.
    >>>> (f) CBS Registry
    >>>> Error 0x80070002
    >>>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>>> to get CurrentState
    >>>> (f) CBS Registry
    >>>> Error 0x80070002
    >>>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>>> to get Visibility
    >>>>
    >>>> Checking component store
    >>>> Summary:
    >>>> Seconds executed: 1032
    >>>> Found 2 errors"
    >>>>
    >>>> So off I goes into the registry (having done full system restore & reg
    >>>> backup) and delete all references to (in my case):
    >>>>
    >>>> "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"
    >>>>
    >>>> Jumped into windows update - clicked update & (after a while) bang -
    >>>> there are 29 updates for me to download - YIPPEE.
    >>>>
    >>>> NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM Vista
    >>>> Business)
    >>>>
    >>>> Hope it works for you!
    >>>>
    >>>>
    >>>
    >>> I glad you got it working! Cross posting to
    >>> microsoft.public.windowsupdate for proof this is how to troubleshoot
    >>> many Windows Update problem.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
    >
    >
    > Editing the registry by hand is always dangerous, which is why I tell
    > them to back up the entries before deleting them.
    >
    > For whatever reason, sometimes there will be system file(s) installed
    > that doesn't match up with the what it says in the registry.
    >
    > My theory is there is in some cases if you do a point restore, some
    > system files are replaced with a previous version.
    >
    > Registry keys are changed back to work with these system files, however
    > the entries for the latest system files that used to be installed is not
    > deleted. Since they are kept for record purposes only.
    >
    > When you run System File Checker, it looks at these records in the
    > registry and uses the LATEST system file entry which does not match with
    > the system file you have installed because the system restored an older
    > version.
    >
    > Windows Update runs the same kind of check on the system files, before
    > attempting to install updates.
    >
    > This is why I ask people to run SFC to isolate which entries are no
    > longer valid. Assuming this is caused by System Restore, it SHOULD
    > delete or flag the entries as no longer installed when it replaces a new
    > system file with an older one.
    >
    > As far as I can tell it does not do this, so what I am doing is having
    > people go in and manually delete the invalid entries.
    >
    > Does that make sense?<!--colorc--><!--/colorc-->
     
    Harry Johnston [MVP], Jun 14, 2009
    #19
  21. Tae Song

    Tae Song Guest

    "Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
    news:uDB99OV7JHA.5180@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Tae Song wrote:
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    > > Editing the registry by hand is always dangerous, which is why I tell
    > > them to back up the entries before deleting them.<!--colorc--><!--/colorc-->
    >
    > Not really adequate IMO since problems may develop later, by which time
    > there won't be any way to tell what caused them.
    >
    > However, since MowGreen has found a reference to a MS engineer
    > recommending the same procedure, that's moot now. :)
    >
    > Harry.
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >> "Harry Johnston [MVP]" <harry@scms.waikato.ac.nz> wrote in message
    >> news:uHD$lXv6JHA.4404@TK2MSFTNGP04.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Ouch! Removing those registry entries sounds like a very dangerous
    >>> move. There's no telling what the side-effects could be.
    >>>
    >>> I haven't used Vista enough to know what the correct way to fix this
    >>> class of problem is, but I very much doubt this is it.
    >>>
    >>> kidA: I recommend backing up your files and doing a full reinstall (not
    >>> a repair) of your operating system.
    >>>
    >>> Tae: if you have Microsoft documentation to support use of this
    >>> procedure, please provide the appropriate links.
    >>>
    >>> Harry.
    >>>
    >>> Tae Song wrote:
    >>>
    >>>> "kidA" <kidA.3tihef@no.email.invalid> wrote in message
    >>>> news:kidA.3tihef@no.email.invalid...
    >>>
    >>>>> TAE YOUR A HERO!, after nearly 5 months of zero updates due to the
    >>>>> dreaded 0x80070490 error - tried the TAE registry open heart surgery
    >>>>> and
    >>>>> wham I'm now downloading much needed vista updates..
    >>>>>
    >>>>> Here's my steps: downloaded the update readiness tool from Microsoft
    >>>>> ("checkSUR" - google it). After running it I found 2 registry errors
    >>>>> (look in "/windows/logs/checkSUR.log" to see the results):
    >>>>>
    >>>>> "Checking packages.
    >>>>> (f) CBS Registry
    >>>>> Error 0x80070002
    >>>>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>>>> to get CurrentState
    >>>>> (f) CBS Registry
    >>>>> Error 0x80070002
    >>>>> Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000 failed
    >>>>> to get Visibility
    >>>>>
    >>>>> Checking component store
    >>>>> Summary:
    >>>>> Seconds executed: 1032
    >>>>> Found 2 errors"
    >>>>>
    >>>>> So off I goes into the registry (having done full system restore & reg
    >>>>> backup) and delete all references to (in my case):
    >>>>>
    >>>>> "Package_27_for_KB937286~31bf3856ad364e35~x86~en-US~6.0.1.18000"
    >>>>>
    >>>>> Jumped into windows update - clicked update & (after a while) bang -
    >>>>> there are 29 updates for me to download - YIPPEE.
    >>>>>
    >>>>> NO 3hr Vista Upgrade (Which I couldn't do because I have dell OEM
    >>>>> Vista
    >>>>> Business)
    >>>>>
    >>>>> Hope it works for you!
    >>>>>
    >>>>>
    >>>>
    >>>> I glad you got it working! Cross posting to
    >>>> microsoft.public.windowsupdate for proof this is how to troubleshoot
    >>>> many Windows Update problem.<!--colorc--><!--/colorc-->
    >>
    >>
    >> Editing the registry by hand is always dangerous, which is why I tell
    >> them to back up the entries before deleting them.
    >>
    >> For whatever reason, sometimes there will be system file(s) installed
    >> that doesn't match up with the what it says in the registry.
    >>
    >> My theory is there is in some cases if you do a point restore, some
    >> system files are replaced with a previous version.
    >>
    >> Registry keys are changed back to work with these system files, however
    >> the entries for the latest system files that used to be installed is not
    >> deleted. Since they are kept for record purposes only.
    >>
    >> When you run System File Checker, it looks at these records in the
    >> registry and uses the LATEST system file entry which does not match with
    >> the system file you have installed because the system restored an older
    >> version.
    >>
    >> Windows Update runs the same kind of check on the system files, before
    >> attempting to install updates.
    >>
    >> This is why I ask people to run SFC to isolate which entries are no
    >> longer valid. Assuming this is caused by System Restore, it SHOULD
    >> delete or flag the entries as no longer installed when it replaces a new
    >> system file with an older one.
    >>
    >> As far as I can tell it does not do this, so what I am doing is having
    >> people go in and manually delete the invalid entries.
    >>
    >> Does that make sense?<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

    It's no where near as dangerous than using a registry cleaner.

    You could always attempt to put the entries back after a few successful
    updates and run SFC again to check if they are still causing a problem.
     
    Tae Song, Jun 15, 2009
    #20
Page 1 of 2

Share This Page