(cross-post added to Vista Perf & Maint)
"aptlinc1" wrote in message

....
When windows update automatically checks for updates, I'm offerd this update.


That's your problem.



Any answers. If I do the stand alone method how do I get it to show up in my
installed updates folder?


That is not your problem. If the update is installed manually that is not the way
to check it. Use Add/Remove Programs (or whatever Vista calls it now).
Is it listed there? Then chances are that the manual install did work and at worst
the modules which it tried to update were blocked somehow, e.g. by a security
program. BTW have you booted in the interim? That might make the update finish
even if a boot isn't forced and then make WU see that the update is on. (WU checks
the current versions of the actual modules involved before it requests an update.
It doesn't rely on just the log of update activity.)

You could use the list of modules and versions in the update's KB article to give
even more confidence that the update really has been installed correctly.

Unfortunately I think that diagnostics to help automate that analysis are scant.
Activating verbose logging might give better clues about why WU thinks the
update is not applied (ref KB902093). Also I have noticed that some updates
have been putting extra information into the Event log that previously wasn't there,
so try looking for clues in there too.

Oh. (I just thought of something that I would try looking at in Vista to possibly
simplify this.) See if Vista has improved on XP's anemic and unusable
View, System History command (in msinfo32.exe)? Ideally that would show
you the changed modules and their details in the order that they were updated,
which would make matching them up with the KB articles' manifests a piece of cake.
(I can dream can't I? eg)

BTW I'm cross-posting this to a Vista newsgroup to give this discussion
more visibility to readers who may actually use Vista and have installed this update.


Good luck

Robert Aldwinckle
---


KB038194 stability update was a late August offering that generated an 80070002
error code on my vista ultimate system.
All the other updates offerd at that time are registered in my istalled
updates folder.

For some reason i cannot get this update to register successfully even after:
1. stop the update service
2. delete dataStore info from software dist. folder
3.delete download folder files in software distr. folder
4. restart windows update.
5. check for updates and it's offered, downloaded, successful, restart
computer.
6. After restart the message that this download was unsuccessful.

I went to the help and support website and downloaded the regular Vista
stand alone offerring (not the Vista x64 offerring).
I ran the stand alone package and the update was successful.

I restarted my computer and checked the update history folder. The update is
suppossedly successful. However, this update does not show up in the
installed updates folder.

When windows update automatically checks for updates, I'm offerd this update.

Any answers. If I do the stand alone method how do I get it to show up in my
installed updates folder?
Aptlinc1

Aptlinc1 wrote:

Robert,
Your input has been helpful, but still no success?

What I didn’t realize was by ignoring this update (KB938194) I was,
inadvertently, preventing the October updates.

Before your reply, I e-mailed an inquiry (10/ 08/2007) to Microsoft to see
what the problem was and am waiting for a reply. I had gone to the verbose
method (KB902093) to get a better handle on what was going on, just prior to
your reply. My logs are what Microsoft is looking at now. Good luck to
Microsoft!

However, I decided because of your reply, to try the 80070002 method again.
That’s when I realized that October’s updates were not coming through or that
this update was preventing them.

Solution: I declined the KB938194 offering and every other update succeeded.
If I didn’t decline the KB938194 offering, no new update would take. I left
this KB938194 update to last and tried to automate the update. No Success.

Here is a copy of the verbose log (KB902093) just after the other successful
October updates by declining this update. Microsoft should be able to make
more sense of it if you get it to the right people:

2007-10-10 02:57:59:183 1512 e6c AU Setting AU scheduled install time to
2007-10-10 07:00:00
2007-10-10 02:57:59:183 1512 e6c AU Auto-approving update for download,
updateId = {498283F4-5885-4A1A-8BD2-ED024AA85F59}.101, ForUx=0, IsOwnerUx=0,
HasDeadline=0, IsMinor=0
2007-10-10 02:57:59:183 1512 e6c AU Auto-approved 1 update(s) for download
(NOT for Ux)
2007-10-10 02:57:59:183 1512 e6c AU #############
2007-10-10 02:57:59:183 1512 e6c AU ## START ## AU: Download updates
2007-10-10 02:57:59:183 1512 e6c AU #########
2007-10-10 02:57:59:183 1512 e6c AU # Approved updates = 1
2007-10-10 02:57:59:187 1512 e6c AU AU initiated download, updateId =
{498283F4-5885-4A1A-8BD2-ED024AA85F59}.101, callId =
{9C32AF9B-BA45-4392-B40C-F40E8EB7C3A1}
2007-10-10 02:57:59:187 1512 e6c AU Setting AU scheduled install time to
2007-10-10 07:00:00
2007-10-10 02:57:59:210 1512 e6c AU # Pending download calls = 1
2007-10-10 02:57:59:210 1512 e6c AU ## SUBMITTED ## AU: Download updates
2007-10-10 02:57:59:230 1512 12d4 DnldMgr *************
2007-10-10 02:57:59:230 1512 12d4 DnldMgr ** START ** DnldMgr: Downloading
updates [CallerId = AutomaticUpdates]
2007-10-10 02:57:59:230 1512 12d4 DnldMgr *********
2007-10-10 02:57:59:230 1512 12d4 DnldMgr * Call ID =
{9C32AF9B-BA45-4392-B40C-F40E8EB7C3A1}
2007-10-10 02:57:59:230 1512 12d4 DnldMgr * Priority = 1, Interactive = 0,
Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2007-10-10 02:57:59:230 1512 12d4 DnldMgr * Updates to download = 1
2007-10-10 02:57:59:230 1512 12d4 Agent * Title = Update for Windows
Vista (KB938194)
2007-10-10 02:57:59:230 1512 12d4 Agent * UpdateId =
{498283F4-5885-4A1A-8BD2-ED024AA85F59}.101
2007-10-10 02:57:59:230 1512 12d4 Agent * Bundles 1 updates:
2007-10-10 02:57:59:230 1512 12d4 Agent *
{BDE9F941-456F-44FB-A87F-B5EAC1FEA2E6}.101
2007-10-10 02:57:59:230 1512 12d4 DnldMgr *********** DnldMgr: Regulation
Refresh [Svc: {7971F918-A847-4430-9279-4A52D1EFE18D}] ***********
2007-10-10 02:57:59:230 1512 12d4 DnldMgr Contacting regulation server for 1
updates.
2007-10-10 02:57:59:253 1512 12d4 Misc Validating signature for
C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\wuredir.cab:
2007-10-10 02:57:59:292 1512 12d4 Misc Microsoft signed: Yes
2007-10-10 02:57:59:296 1512 12d4 DnldMgr Regulation server path:
http://www.update.microsoft.com/v6/U...egulation.asmx.
2007-10-10 02:58:10:699 1512 12d4 DnldMgr Per-Update:
bde9f941-456f-44fb-a87f-b5eac1fea2e6 at rate 500
2007-10-10 02:58:10:699 1512 12d4 DnldMgr * Regulation call complete.
0x00000000
2007-10-10 02:58:10:699 1512 12d4 DnldMgr *********** DnldMgr: New download
job [UpdateId = {BDE9F941-456F-44FB-A87F-B5EAC1FEA2E6}.101] ***********
2007-10-10 02:58:10:699 1512 12d4 DnldMgr Regulation:
{7971F918-A847-4430-9279-4A52D1EFE18D} - Update
BDE9F941-456F-44FB-A87F-B5EAC1FEA2E6 is "PerUpdate" regulated and can NOT
download. Sequence 3291 vs AcceptRate 500.
2007-10-10 02:58:10:699 1512 12d4 DnldMgr * Update is not allowed to
download due to regulation.
2007-10-10 02:58:10:699 1512 12d4 DnldMgr Regulation:
{7971F918-A847-4430-9279-4A52D1EFE18D} - Update
BDE9F941-456F-44FB-A87F-B5EAC1FEA2E6 is "PerUpdate" regulated and can NOT
download. Sequence 3291 vs AcceptRate 500.
2007-10-10 02:58:10:699 1512 12d4 DnldMgr Regulation:
{7971F918-A847-4430-9279-4A52D1EFE18D} - Update
BDE9F941-456F-44FB-A87F-B5EAC1FEA2E6 is "PerUpdate" regulated and can NOT
download. Sequence 3291 vs AcceptRate 500.
2007-10-10 02:58:10:699 1512 12d4 Agent *********
2007-10-10 02:58:10:699 1512 12d4 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2007-10-10 02:58:10:699 1512 12d4 Agent *************
2007-10-10 02:58:10:699 1512 e6c AU AU checked download status and it
changed: Downloading is paused
2007-10-10 02:58:33:985 1512 3fc AU Launched new AU client for directive
'Forced Reboot', session id = 0x1
2007-10-10 03:00:09:993 1512 3fc AU Forced install timer expired for
scheduled install
2007-10-10 03:00:09:993 1512 3fc AU UpdateDownloadProperties: 1 download(s)
are still in progress.
2007-10-10 03:00:09:993 1512 3fc Agent Setting download properties on call
9C32AF9B-BA45-4392-B40C-F40E8EB7C3A1: priority=1, interactive=0, owner is
system=1, proxy settings=1, proxy session id=-1
2007-10-10 03:00:09:994 1512 3fc AU Setting AU scheduled install time to
2007-10-11 07:00:00
2007-10-10 03:02:02:565 1512 3fc AU AU received handle event


"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"aptlinc1" wrote in message

....
When windows update automatically checks for updates, I'm offerd this update.


That's your problem.



Any answers. If I do the stand alone method how do I get it to show up in my
installed updates folder?


That is not your problem. If the update is installed manually that is not the way
to check it. Use Add/Remove Programs (or whatever Vista calls it now).
Is it listed there? Then chances are that the manual install did work and at worst
the modules which it tried to update were blocked somehow, e.g. by a security
program. BTW have you booted in the interim? That might make the update finish
even if a boot isn't forced and then make WU see that the update is on. (WU checks
the current versions of the actual modules involved before it requests an update.
It doesn't rely on just the log of update activity.)

You could use the list of modules and versions in the update's KB article to give
even more confidence that the update really has been installed correctly.

Unfortunately I think that diagnostics to help automate that analysis are scant.
Activating verbose logging might give better clues about why WU thinks the
update is not applied (ref KB902093). Also I have noticed that some updates
have been putting extra information into the Event log that previously wasn't there,
so try looking for clues in there too.

Oh. (I just thought of something that I would try looking at in Vista to possibly
simplify this.) See if Vista has improved on XP's anemic and unusable
View, System History command (in msinfo32.exe)? Ideally that would show
you the changed modules and their details in the order that they were updated,
which would make matching them up with the KB articles' manifests a piece of cake.
(I can dream can't I? eg)

BTW I'm cross-posting this to a Vista newsgroup to give this discussion
more visibility to readers who may actually use Vista and have installed this update.


Good luck

Robert Aldwinckle
---


KB038194 stability update was a late August offering that generated an 80070002
error code on my vista ultimate system.
All the other updates offerd at that time are registered in my istalled
updates folder.

For some reason i cannot get this update to register successfully even after:
1. stop the update service
2. delete dataStore info from software dist. folder
3.delete download folder files in software distr. folder
4. restart windows update.
5. check for updates and it's offered, downloaded, successful, restart
computer.
6. After restart the message that this download was unsuccessful.

I went to the help and support website and downloaded the regular Vista
stand alone offerring (not the Vista x64 offerring).
I ran the stand alone package and the update was successful.

I restarted my computer and checked the update history folder. The update is
suppossedly successful. However, this update does not show up in the
installed updates folder.

When windows update automatically checks for updates, I'm offerd this update.

Any answers. If I do the stand alone method how do I get it to show up in my
installed updates folder?
Aptlinc1