(cross-post to Vista General added)
"Truth Unknown" <> wrote in message news:A2A0E3FB-87FD-4116-9108-...
>I though i was using a Windows Vista Newsgroup, because that's what I'm
> seeing. http://70.103.16.165/~hostfile/winvistanewsgroups.jpg
This is something that we have been complaining about that site.
That menu does not distinguish between links to Vista specific
newsgroups and shared newsgroups.
From a post yesterday addressed to an MS responder
<quote>
I really think there should be another separator and grouping label
added in front of the last 5 newsgroups in the list currently labeled
"Windows Vista Newsgroups". We still have Vista users expressing
surprise in those shared newsgroups that non-Vista discussions
predominate. I think an appropriate label would have prepared them
to accept that they would be seeing non-Vista discussions there before
actually seeing them.
</quote>
>
> Here is my Windows Update log:
> http://70.103.16.165/~hostfile/windowsupdate.log
Great! This shows that you have been getting several different error codes
while trying to install driver updates.
To see this more clearly either browse through your log
doing finds for REPORT EVENT or browse separately the summary file
%windir%\SoftwareDistribution\ReportingEvents.log
>
> I did find the error number relevant to the driver I'm installing with, but
> I could not find exactly what caused the error.
More details of your perceptions would help I think.
E.g. notice that one of the drivers that you are apparently having trouble
installing was actually already installed a couple of days earlier.
<example>
2006-09-10 20:01:24:225 872 8ec Report REPORT EVENT: {A14241EE-B3B3-487F-B723-C4262DCDD2D4} 2006-09-10 20:01:07:037-0600 1 183 101
{9EB71DCE-A020-451F-9F89-2A74056D4533} 103 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully
installed the following update: Creative - media - Creative Audigy Audio Processor (WDM)
</example>
Also, other drivers failed to install but then just are no longer reported.
Did you do something manual instead to avoid having to involve AU
any further with their installation?
Finally, since the downloads are all done and the failures are all
failures of installs to complete we may be looking at the wrong
diagnostics to understand *why* the installs are failing.
Try looking for any diagnostic files created by the installs.
E.g. in XP I would do that either by running FileMon while running
the install or by using Explorer Search Companion to find all files
which were modified on the day of the update which I would then
order by Date Modified, thus sorting them by timestamp.
That allows you to scroll to the set of files which changed during
the update which usually includes some kind of install log.
BTW since the installs are downloaded (usually somewhere in
%windir%\SoftwareDistribution\Download ) you may be able to run them
manually. That could have the effects 1) of being able to see if there are
any more symptoms as a result of trying that and 2) perhaps allow you
to do it using a more powerful account. E.g. throughout the log there are
references to "elevated non admin" which I'm wondering may not be
strong enough to install drivers. E.g. perhaps you could do it with the
real Administrator account and see if there is either success or any
different negative symptoms that way.
Alternatively, if you find the same drivers offered via Windows Update
you could try downloading and installing them from there. Often manual
updates succeed where automatic ones fail.
Because I am not using Vista I am cross-posting this reply to
Vista General to give your thread better visibility among other Vista users.
HTH
Robert Aldwinckle
---
Similar Threads
Linear Mode
