Vista won't install updates (V4BizSP2)

Hi! Please help if you can. We have a little Lenovo (ex-IBM) laptop running Vista for Business SP2. While it HAS permitted a small number of updates, mostly when we run Windows Update it goes thru the effort for awhile and then says we need to update the Windows Update (itself). So, we click to do that. Then after awhile it returns to the initial screen (where you click to perform a Windows Update). So, we think everything is fine and that the Windows Update is (itself) udated and ready to go (do its job). SO, we click on it and... voila....the cycle repeats... with it eventually telling us we have to update the Windows Update (itself, again).

In checking (with installation history) what HAS been updated, usually nothing. The last updates that did get entered as successfully completed were last week, most then and since have been unsuccessful however.

We were told to download and install the windows update directly from the microsoft website. We did the download, it said it completed fine. It asked if we wanted to install it. We clicked yes. It worked on that awhile and then said the installation was unsuccessful.

??????????????????????

We have Vista for Business Service Pack 2, and Norton 360, and it is a 32 bit machine. Any help much appreciated, especially if it is super easy for computer-illiterates here! MuchoThanko!

Prepare below logs:

1.Run cmd.exe with administrative previlliges (right click on cmd.exe) as admin and type:

sfc /scannow

When it finish type in cmd.exe

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

on your desktop appear sfcdetails.txt file

2.Run Readiness Tool Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2
even if this tool don't solve problem it create CheckSur.log file in C:\Windows\Logs\CBS folder
3.Download firegenul Altair Technologies Ltd.
place firegenul.exe in C:\Windows\System32

next again run cmd.exe with admin previlliges and type:

firegenul

it creates report from WindowsUpdate.log and is saved to C:\Windows\System32 as FireGenReport.htm
4.Prepare log from VistaSysInfoTool http://www.vistax64.com/tutorials/176785-vistaforums-sysinfo-tool.html

all files sfcdetails.txt,CheckSur.log,firegenReport.htm and log from VistaSysInfo pack to ZIP format and attache to post

Hi! You are amazing! What a fascinating tour you have already provided us of this little tiny computer (it sure has a lot of stuff inside it! alas, largely error messages, ha ha!) Well, here are the :Dfiles you asked for. We sure do appreciate your hlep! Thanks!

I don't have good news for you.You have seriosly corrupted C:\Windows\WinSxS\Manifests folder

Found 8 errors
CSI Manifest All Zeros Total count: 8

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.4.7600.226_none_672645e7fba0c4cc.manifest
winsxs\manifests\x86_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.4.7600.226_none_a60ad922c4c1b083.manifest
winsxs\manifests\x86_microsoft-windows-w..date-adm.deployment_31bf3856ad364e35_7.4.7600.226_none_3f8331594521f9a6.manifest
winsxs\manifests\x86_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.4.7600.226_none_c2c51d03e34cf294.manifest
winsxs\manifests\x86_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_3eed8fc4903631e2.manifest
winsxs\manifests\x86_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.4.7600.226_none_e979223d5b9c821b.manifest
winsxs\manifests\x86_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.4.7600.226_en-us_07f591faa9b0a436.manifest
winsxs\manifests\x86_microsoft-windows-w..lient-ui.deployment_31bf3856ad364e35_7.4.7600.226_none_3f47314b6f3e4f53.manifest

Click to expand...

Neverless try to fix it.You have 50% chance it will work.


First try below:

I attached to post all request by Readiness Tool files,download them and unpack anywhere

1.Navigate to C:\Windows\WinSxS\Manifests,takeownership of this folder and add your account to have full control

//practical warning:when you will already takeownership of this folder and you will try add your account to have full control sometimes it may return error "Access denied" although theoreticly shouldn't -in this case close all permissions tab and reopen it again,probably your account you will have already full control if not repeat this step again.

2.Copy my files to this folder -if you have already any file then replace it.
3.Remove your account from permissions to Manifests folder
4.Restore ownership of Packages folder back to "NT Service\TrustedInstaller"

Useful links -please read these if you don't know about permissions:Take Ownership of file
TrustedInstaller - Restore as Owner
Folder Permissions

If you will have any problems to do this,then I'll give you instruction to do that throgh Vista DVD/recovery disk or livecd with linux.

Wow! Thanks thanks. We will read thru your instructions and try them out just as soon as we think we have mastered how to follow them correctly, tend to be a little slow on this end as i get olde
ha
thanks thanks. If any delay it will be because am trying to help an elderlly heart patient in another city and had to run up there... But will definitely plan to be back here soon and report to you on our progress with your instructions. Thanks thanks thanks thanks

HI! WELL, your instructions resulted in the system updating a whole pile of files (that it could not successfully update before your fix).
One file remains downloaded but Unsuccessfullly Updated.
it is KB973687 update for Vista 1.2M, said to be an important update.
It generated "unknown error" code 800B0100
however, when I checked what that meant, it seemed to know
---
it told us to install System Update Readiness Tool KB947821. We did that.
We then rebooted and tried to install KB973687 Update for Vista, again.
Same problemo.
The CBS.CheckSUR and CBSCheckSUR.persist logs are set forth below, as I think (novice that I may be) that maybe these may help you see what we need to do ?
I have to leave for awhile today to help an elderly sick friend....
but will obviously check back quickly here on my return
You have fixed this little laptop 95% of the way I think...tho Microsoft says this one last update is still important....?
Thanks thanks thanks
lots below:


Checking System Update Readiness.
Binary Version 6.0.6002.22202
Package Version 6.0
2010-01-17 08:40
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_bthmtpenum.inf_31bf3856ad364e35_0.0.0.0_none_23d1b875dc1c1425 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.bthmtpenum Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdfs.inf_31bf3856ad364e35_0.0.0.0_none_49c6cb2f1ac5fe37 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdfs Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdmtp.inf_31bf3856ad364e35_0.0.0.0_none_43743b50cedad977 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtp Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdmtphw.inf_31bf3856ad364e35_0.0.0.0_none_1c1880257795310c Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtphw Package registry presence failed, possibly an orphaned package on package watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 1732
Found 4 errors
CBS Watchlist Component Missing Total count: 4

and the second one:

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22202
Package Version 6.0
2009-12-20 08:12
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.4.7600.226_none_672645e7fba0c4cc.manifest x86_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.4.7600.226_none_672645e7fba0c4cc
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.4.7600.226_none_a60ad922c4c1b083.manifest x86_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.4.7600.226_none_a60ad922c4c1b083
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..date-adm.deployment_31bf3856ad364e35_7.4.7600.226_none_3f8331594521f9a6.manifest x86_microsoft-windows-w..date-adm.deployment_31bf3856ad364e35_7.4.7600.226_none_3f8331594521f9a6
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.4.7600.226_none_c2c51d03e34cf294.manifest x86_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.4.7600.226_none_c2c51d03e34cf294
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_3eed8fc4903631e2.manifest x86_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_3eed8fc4903631e2
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.4.7600.226_none_e979223d5b9c821b.manifest x86_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.4.7600.226_none_e979223d5b9c821b
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.4.7600.226_en-us_07f591faa9b0a436.manifest x86_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.4.7600.226_en-us_07f591faa9b0a436
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_microsoft-windows-w..lient-ui.deployment_31bf3856ad364e35_7.4.7600.226_none_3f47314b6f3e4f53.manifest x86_microsoft-windows-w..lient-ui.deployment_31bf3856ad364e35_7.4.7600.226_none_3f47314b6f3e4f53
Summary:
Seconds executed: 424
Found 8 errors
CSI Manifest All Zeros Total count: 8
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.4.7600.226_none_672645e7fba0c4cc.manifest
winsxs\manifests\x86_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.4.7600.226_none_a60ad922c4c1b083.manifest
winsxs\manifests\x86_microsoft-windows-w..date-adm.deployment_31bf3856ad364e35_7.4.7600.226_none_3f8331594521f9a6.manifest
winsxs\manifests\x86_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.4.7600.226_none_c2c51d03e34cf294.manifest
winsxs\manifests\x86_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_3eed8fc4903631e2.manifest
winsxs\manifests\x86_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.4.7600.226_none_e979223d5b9c821b.manifest
winsxs\manifests\x86_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_7.4.7600.226_en-us_07f591faa9b0a436.manifest
winsxs\manifests\x86_microsoft-windows-w..lient-ui.deployment_31bf3856ad364e35_7.4.7600.226_none_3f47314b6f3e4f53.manifest

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22202
Package Version 6.0
2010-01-17 08:40
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_bthmtpenum.inf_31bf3856ad364e35_0.0.0.0_none_23d1b875dc1c1425 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.bthmtpenum Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdfs.inf_31bf3856ad364e35_0.0.0.0_none_49c6cb2f1ac5fe37 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdfs Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdmtp.inf_31bf3856ad364e35_0.0.0.0_none_43743b50cedad977 Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtp Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_wpdmtphw.inf_31bf3856ad364e35_0.0.0.0_none_1c1880257795310c Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtphw Package registry presence failed, possibly an orphaned package on package watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 1732
Found 4 errors
CBS Watchlist Component Missing Total count: 4



thanks thanks and if any additional logs or whatever are needed just let us know
thanks thankks

In researching the current minor problem of only one update not installing after downloading (recalling that about two dozen updates would not install before your kind assistance.. thanks thanks thanks....)... we see that while update KB973687 is stated by Micros**t to be an "important update" -- it actually does nothing much for the user directly (it does something to control net congestion at some remote site somewhere else). Therefore, we are going to relax about installing this particular update for the present time..... and count our blessings that Flavius has so very very kindly got the basic updating function working here again. THANK YOU SIR! Thank you!

It will be very hard.Error possibly an orphaned package on package watchlist is very difficult to eliminate and nobody know exactly how to fix apart trivial solution repair installation http://www.vistax64.com/tutorials/88236-repair-install-vista.html
or restore system if you have any good check point http://www.vistax64.com/tutorials/76256-system-restore-undo.html

if you really want you can try this.

Error "possibly an orphaned package..." means the keys in Component Based Servicing there are but missing files in C:\Windows\Servicing\Packages and C:\Windows\WinSxS which address to this key.If these keys address to any hotfixes then you can try remove these phrases and if you will have luck after restarting system will reinstall these corrupted hotfixes again and all errors disappear but possible is also situation unable to run system after restarting .

Before start to do anything make sure you have already Vista DVD or if you don't have Vista DVD download & burn special recovery disk http://www.vistax64.com/tutorials/141820-create-recovery-disc.html

1.Clear all files from CBS folder

Run cmd.exe with admin rights (right click on cmd.exe as admin) and type

del C:\Windows\Logs\CBS\*.*

2.Download PsTools PsTools
and extract from this pack psexec.exe file and place it in C:\Windows\System32
3.Again run cmd.exe with admin rights (right click on cmd.exe as admin) and type

psexec -s -i -d regedit

Above command will run regedit from SYSTEM account (not from your own account),next in registry find these keys:

HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_bthmtpenum.inf_31bf3856ad364e35_0.0.0.0_none_23d1b875dc1c1425

HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdfs.inf_31bf3856ad364e35_0.0.0.0_none_49c6cb2f1ac5fe37

HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdmtp.inf_31bf3856ad364e35_0.0.0.0_none_43743b50cedad977

HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdmtphw.inf_31bf3856ad364e35_0.0.0.0_none_1c1880257795310c

(FYI: HKLM=HKEY_LOCALE_MACHINE)

and for all above give SYSTEM account full control (but don't change the owner of these keys,it is unneccessary!The owner of these keys is SYSTEM account and it is OK).When SYSTEM account will have full control for all these keys remove following things:

in HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_bthmtpenum.inf_31bf3856ad364e35_0.0.0.0_none_23d1b875dc1c1425

remove string Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.bthmtpenum

in HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdfs.inf_31bf3856ad364e35_0.0.0.0_none_49c6cb2f1ac5fe37

remove string Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdfs

in HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdmtp.inf_31bf3856ad364e35_0.0.0.0_none_43743b50cedad977

remove string Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtp

in HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_wpdmtphw.inf_31bf3856ad364e35_0.0.0.0_none_1c1880257795310c


remove string Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~x86~~7.0.6002.18112.wpdmtphw

Here you are example how it look one these key


3.Restart computer.I hope so your system will survive this operation .If you cannot run system then you have to restore system System Restore Undo (METHOD I from this link) - the best way choose the oldest checkpoint.If your systym will still allive again run Readiness Tool and try install hotfixes.if you still can't update then attache to post new CheckSur.log file.

Good luck!

OH MY GAWD! THANK YOU THANK U THANK YOU!

But alas, any full screen of incredibly complex computer instructions which end in the advisory .. "I hope your computer survives this!"

has to be given a little thought, before leaping in.......
ha!

I am only the 15 year old kid who aced all the Graduate Division computer courses back in the 1960's..... causing the university to take the whole computer department and move it into the undergraduate school. Ha! Then 2 top-school EEngr degrees with national honors. etc. OK.... brevity. brevity.

With that as background, I am still amazed at Flavius' detailed knowledge of this stuff! Congratuations Flavius, you are an incredibly competent person!

I need to review this stuff. Back with you as soon as I can do this. THANKS again for being so very very helpful. It is most kind of you.
TGIF

wow...Flavius I have been having a similar problem on a family members computer and I have no idea how to fix it. I can't even run CheckSur.log to check the computer. I can't run updates, I can't use explorer. I managed to put a copy of FireFox on the computer and that is the only way to access the web.

Any help is greatly appreciated. Oddly enough I have a Lenovo ideapad.

novicetech said:

wow...Flavius I have been having a similar problem on a family members computer and I have no idea how to fix it. I can't even run CheckSur.log to check the computer. I can't run updates, I can't use explorer. I managed to put a copy of FireFox on the computer and that is the only way to access the web.

Click to expand...

I'm sorry but your damages are too big to try fix manaully ,probably you have to replace half system (see yourself your own sfcdetails.txt).It's no strange here you can't run Readiness Tool.If you can try system restore (of course it will work only if you have any good checkpoint) ,if you can't run system restore on allive system boot special recovery disk http://www.vistax64.com/tutorials/141820-create-recovery-disc.html (OPTION I)
boot it and use system restore http://www.vistax64.com/tutorials/76256-system-restore-undo.html (METHOD I)

Any help is greatly appreciated. Oddly enough I have a Lenovo ideapad.

Click to expand...

If system restore also fail practically in your case there is no way only reinstall OS.If you really want you can buy separetly Vista DVD and make repair installation http://www.vistax64.com/tutorials/88236-repair-install-vista.html or better buy Windows 7 DVD and do upgrade Upgrade Install with Windows 7 - Windows 7 Forums