Error Code 800705B4

Truth Unknown · 13-09-2006

These are the details from Windows Update in Windows Vista RC1:
==========================================================
Creative - media - Creative Audigy Audio Processor (WDM)

Installation date: 9/12/2006 1:22 PM

Installation status: Failed

Error details: Code 800705B4

Update type: Recommended

Driver Update for Vista device support

More information:
http://winqual.microsoft.com/support/?driverid=12313553

More information:
http://support.microsoft.com/select/?target=hub
==========================================================

I have searched for a solution but found nothing. So does anyone have any
ideas?

On a side note, there seems to be some kind of problem with the creation of
these topics. This was the second time I tried posting this.

Drake Steele · 13-09-2006

I ran into the same issue with an update that showed up for my Sound Blaster
Live today (Sept. 13) - fails to install, with a similar error code (It's
80070103) and I likewise have found no solutions. HELP! (I can't get my
SBLive! 5.1 to install as anything other than "Creative Emu10K1 Audio (WDM)"
and had to use the xp drivers, which don't work spectacularly well - the
update today would be great - if it WORKED! *sigh*)

Robert Aldwinckle · 14-09-2006

"Drake Steele" <Drake Steele@discussions.microsoft.com> wrote in message
news:191AF05F-46D5-481A-B0EE-7C05B575D316@microsoft.com...
>I ran into the same issue with an update that showed up for my Sound Blaster
> Live today (Sept. 13) - fails to install, with a similar error code (It's
> 80070103)

The only thing "similar" about them is their category. 0x8007xxxx
generally seem to have something to do with Errors which have
a corresponding decimal number documented somewhere on MSDN.

> and I likewise have found no solutions. HELP!

Did you try a search? Let's take those two codes, prefix them with 0x
(so it's clear they are to represent hexidecimal values and not
something else--including in your case not a decimal value with those
same digits):

http://inetexplorer.mvps.org/archive/wuc.htm

(MSN search for
0x80070103 0x800705B4
)

<extracts>
0x800705B4 -2147023436 Error_Timeout

0x80070103 -2147024637 ERROR_NO_MORE_ITEMS:

</extracts>

I guess Error_Timeout is more or less self-explanatory
but what "items" are being referred to for your case?

Let's see if the MSDN has any more details on that.
In this case, since we have the Error code name we can search on that
otherwise we would search on 259 (the decimal equivalent of 0x0103):

Hmm... MSDN wasn't very helpful with that search.
Here are some from the KB which indicates that at least we are
on the right track:

http://support.microsoft.com/search/...=20&1033comm=1

(MSKB Boolean search for
ERROR_NO_MORE_ITEMS AND 259
)

but it's apparently not a specific error, just an indication that a problem
occurred in some program procedure (usually .NET?) or other.

IOW searching for information about your error code is showing us
that its meaning is going to be strongly dependent on the context
in which it occurred.

In order to get some context you should look in the install log that
will have been produced when the update was run, whether it worked
or not.

BTW this thread that you are jumping into with your Me too! is Vista specific.
If your case is also Vista specific you may have better luck posting in one of
the Vista specific newsgroups. This newsgroup is shared by all users of
Windows Update, not just Vista testers.

Truth Unknown · 14-09-2006

I did find the error number relevant to the driver I'm installing with, but
I could not find exactly what caused the error.

Robert Aldwinckle · 14-09-2006

(cross-post to Vista General added)
"Truth Unknown" <TruthUnknown@discussions.microsoft.com> wrote in message news:A2A0E3FB-87FD-4116-9108-2325602E234C@microsoft.com...
>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
---

**anonymouschild1** · 20-01-2009

Optional Update for Conexant - Audio - Conexant High Definition SmartAudio 221

It hasnt installed for 4 months now, and I got the file to install it. Information is below.

TITLE: Conexant HD-Audio SmartAudio 221

VERSION: 4.31.1.0 Rev. A
DESCRIPTION:
Venice audio driver 32 & 64 bits combined (version : 4.26.0.0)
Hermosa audio driver 32 & 64 bits combined (version : 4.31.1.0)

PURPOSE: Routine Release
SOFTPAQ NUMBER: SP37816
EFFECTIVE DATE: November 9, 2007
CATEGORY: Audio
SSM SUPPORTED: Yes

ENHANCEMENTS:
Venice & Hermosa combine drivers
Venice audio driver 32 & 64 bits combined (version :4.26.0.0)
Hermosa audio driver 32 & 64 bits combined (4.31.1.0)

FIXES:
1. Hermosa and Venice combined driver.
2. Fixed Mute button LED will change Red from Blue quickly during s3/s4.

PREREQUISITES:
N/A

HOW TO USE:
1. Download the Softpaq .EXE file to a directory on your hard drive.
2. Execute the downloaded file and follow the on-screen instructions.
3. Restart the notebook when the installation is complete.

Copyright © 2003 Hewlett-Packard Development Company, L.P.

When I try and install it from the file(that i downloaded from the site) I get this error message:

Driver Installation Failed: Could not find the MEDIA device for this driver.

My front headphone jacks dont work, and my mute button doesnt turn red.
I feel that is because this update is not installed.

help pelase?