Vista will not start after installing updates

[Guest]

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.

 

[Joseph Conway [MSFT]]

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.

 

[Guest]

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.

 

[Joseph Conway [MSFT]]

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.

 

[Guest]

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.

 

[Guest]

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?

 

[Joseph Conway [MSFT]]

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.

 

[Guest]

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.

 

[Joseph Conway [MSFT]]

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.

 

[Joseph Conway [MSFT]]

Thanks, let me know what happens. I think I am going to make these Windows
Updates a pet project here shortly to see what's going on and how we can
avoid it.

Joseph W. Conway, MCSE
Windows Server Group

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

 

[Guest]

Joseph,

Even when logged into the Administrator account, Vista will not permit me to
access/view either CBS.log (or CBS.persist.log in the same folder.) The first
file is 7.24 MB; the second 50.4 MB. The associated opening application is
Notepad. Tried Word 2007 as well without success.

 

[Joseph Conway [MSFT]]

Open an elevated command prompt and then use notepad to open it from within
that directory:

So: notepad cbs.log

Joseph W. Conway, MCSE
Windows Server Group

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

 

[Guest]

Joseph,

I have the text file with the information you requested but am not clear on
how to attach and get it to you through the IE Community Discussion Group.
An email to '(e-mail address removed)' with it as an attachment was
returned as undeliverable. Please advise.

There are many entries from ", Error" to the end of the CBS.log file. It's
779KB of text. This part of the log resulted from an attempted install done
today of the two problem KBs. Once again Windows stated that both had
installed successfully but on restarting, the history indicated both had
failed. Initially, at that point, Windows indicated that there were no
available updates. A minute later the two updates reappeared as available in
Windows update.

The CBS.log appears to be documenting the activity taking place during the
lengthy period that "Configuring Updates" is displayed.

 

[Joseph Conway [MSFT]]

Hmmm, not sure how to post it online, I use a different tool here
internally.

Send it to me here at work. Just take out the online in my email address.

As a note, in looking over some of these here, a lot of these have come
down to disk corruption. Do you (any of you) have any event 9/11/15/50/51
errors in the system event logs? Just curious.

Joseph W. Conway, MCSE
Windows Server Group

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

 

[Guest]

Done.

Have an occasional event 9 "The device, \Device\Ide\iaStor0, did not respond
within the timeout period". These do not obviously correlate with failed
installation attempts.

That event sequence, when both updates are attempted to be installed
together, has a few 4385 Event IDs, followed by multiple 4375s, followed by
two 20s documenting the respective KB installation failures with error
0x89970002;

Use two hard drives in a RAID1: configuration with an Intel (R) Matrix
Controller.

 

[Joseph Conway [MSFT]]

What were they for? If they were for something like a printer, then its
not a big deal. If they were problems with disk or ntfs, then thats an
issue.

If they are disk related, run chkdsk on the volume and then try to install
the updates again.

Joseph W. Conway, MCSE
Windows Server Group

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

 

[Guest]

Correction - the 20s error code is "0x80070002"
--
Wiseoopik - Ottawa, Canada

Done.

Have an occasional event 9 "The device, \Device\Ide\iaStor0, did not respond
within the timeout period". These do not obviously correlate with failed
installation attempts.

That event sequence, when both updates are attempted to be installed
together, has a few 4385 Event IDs, followed by multiple 4375s, followed by
two 20s documenting the respective KB installation failures with error
0x89970002;

Use two hard drives in a RAID1: configuration with an Intel (R) Matrix
Controller.
--
Wiseoopik - Ottawa, Canada

Hmmm, not sure how to post it online, I use a different tool here
internally.

Send it to me here at work. Just take out the online in my email address.

As a note, in looking over some of these here, a lot of these have come
down to disk corruption. Do you (any of you) have any event 9/11/15/50/51
errors in the system event logs? Just curious.

Joseph W. Conway, MCSE
Windows Server Group

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