Vista will not start after installing updates

I am using vista home premium, it has just installed the latest updates , but
it now boots , says please wait, configuring updates and then shutting
down.The computer then shuts down and reboots and follows the same cycle.

Boot off of media, use the recovery option and system restore back to
tomorrow. Then rescan for updates and reinstall them.

Joseph W. Conway, MCSE
Windows Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.

Found this thread as I was having the exact same problem on one of my
client PC's. I unplugged the power, removed the battery and let it sit
for a minute or two and it fixed the problem.

I hope the fix is just as easy for you.


--
lateralus

I have been having this problem as well. Turned off auto updates as it
happened Wednesday night; Thursday night and again this evening. I am
getting proficient with the system restore feature in Vista. Does anyone
know which of the current updates causes it? The O/S message says they all
installed successfully but then on restarting it goes into the "Please wait"
"Configuring Updates" "Shutting Down" reboot endless loop. FYI, Vista
appears to believe it is starting successfully each time this happens.
--
Wiseoopik - Ottawa, Canada


"lateralus" wrote:

>
> Found this thread as I was having the exact same problem on one of my
> client PC's. I unplugged the power, removed the battery and let it sit
> for a minute or two and it fixed the problem.
>
> I hope the fix is just as easy for you.
>
>
> --
> lateralus
>

I havent been able to pin this down as only a few people seem to be seeing
it here and there. The best way to test it (since I cant repro the issue
internally here) would be to install the updates one at a time until you
hit the issue, then note that update as the problem. If someone finds it,
please let me know and I will get the ball rolling interally.

Joseph W. Conway, MCSE
Windows Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.

I'll try the one at a time approach and advise. There were 9 "candidate"
updates in my queue as of yesterday. My O/S is also Vista 32 Home Premium.
--
Wiseoopik - Ottawa, Canada


""Joseph Conway [MSFT]"" wrote:

> I havent been able to pin this down as only a few people seem to be seeing
> it here and there. The best way to test it (since I cant repro the issue
> internally here) would be to install the updates one at a time until you
> hit the issue, then note that update as the problem. If someone finds it,
> please let me know and I will get the ball rolling interally.
>
> Joseph W. Conway, MCSE
> Windows Server Group
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Joseph, the results -

The "all installed successfully" notification from previous automatic and
manual bulk updates isn't borne out by the update history; it shows that KBs
939653, 941202, 933729, 886903, and 905866 failed to install successfully on
three previous attempts when installed together while the four other KBs in
the batch did so.

Going one at a time, was able to successfully install all of these but KBs
939653, 933729, and 886903 without any problems occurring.

KBs 939653 and 933729 appeared to install successfully individually but
required restarts; that led to the "Please Wait" "Configuring Updates"
sequence but eventually let the login continue. After doing so, on checking,
found both had individually failed to install correctly with the same error
code of "80070002".

Checking the update log showed that multiple automated attempts over the
summer/fall to install KB 929729 "Security Update for Microsoft .NET
Framework Version 1.1 Service Pack 1" had all failed with an error code of
"643". As a result, no attempt was made to install KB886903 which has the
same title. Both .NET Framework 1.1 and 3.0 appear in the listing of
installed programs. An attempt to uninstall/change 1.1 was unsuccessful, as
was an attempt to "reinstall" it from the Microsoft site.

All the KBs having problems with are "Important" Security Updates (IE7, .NET
Version 1.1, and Vista)

Your suggestions?
--
Wiseoopik - Ottawa, Canada


""Joseph Conway [MSFT]"" wrote:

> I havent been able to pin this down as only a few people seem to be seeing
> it here and there. The best way to test it (since I cant repro the issue
> internally here) would be to install the updates one at a time until you
> hit the issue, then note that update as the problem. If someone finds it,
> please let me know and I will get the ball rolling interally.
>
> Joseph W. Conway, MCSE
> Windows Server Group
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Thanks for the information, I will look into this.

The 80070002 is a file is missing error, so it sounds like the file isnt
getting pulled down properly. Let me see if anyone else internally has
seen this and I will see what else we can do.

Joseph W. Conway, MCSE
Windows Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks, Joseph.

Tonight I successfully installed the KB929729 update using the process Chris
Rowat came up with in his 12 Jul 2007, 3:49 PM UTC posting found at
http://forums.microsoft.com/msdn/showpost.aspx? in the string "Re: error
code # 643". This didn't correct the other two KB problems - they are still
stated as installing correctly in Window update but as failed in the update
history after rebooting with the 80070002 code.

The endless looping behaviour seems to have been a result of the multiple
failures in the batch installation. Although the IE7 and Vista updates fail,
when installed one at a time or together, they do not produce that behaviour
by themselves.
--
Wiseoopik - Ottawa, Canada


""Joseph Conway [MSFT]"" wrote:

> Thanks for the information, I will look into this.
>
> The 80070002 is a file is missing error, so it sounds like the file isnt
> getting pulled down properly. Let me see if anyone else internally has
> seen this and I will see what else we can do.
>
> Joseph W. Conway, MCSE
> Windows Server Group
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Thanks

Can you do me a favor and send me the following from your CBS.log (located
in Windows\Logs\CBS\CBS.log)

1. Go to the end of the log
2. Search up for the word "Plan"
3. Once you find Plan, search down for the word ", Error" (note thats
comma space Error)
4. Copy that section to the bottom of the log and post it here for me
(assuming its not crazy long, if it is add it to a text file and attach it
for me)

Thanks!

Joseph W. Conway, MCSE
Windows Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.