Welcome to the QA Tech-Tips blog!

Some see things as they are, and ask "Why?"   I dream things that never were, and ask "Why Not".  
Robert F. Kennedy

“Impossible” is only found in the dictionary of a fool.  
Old Chinese Proverb

Monday, September 13, 2010

WindowsUpdate_80070103 - WindowsUpdate_dt000
Errors

Last post, I handed out one of my semi-famous "Hot Smokin' Weapon!" awards and I've been asked if I have a similar award for Stupidity Above and Beyond the Call of Duty.

Sorry.  I'm afraid I don't have one of those - at least not yet. . . .

If I DID have a "Smokin' Hole in The Foot" award, (Hey!  That's not a bad name!), today's post would definitely be a contender.

Today's post is about a Windows Update / Microsoft Update error:  WindowsUpdate 80070103 - WindowsUpdate dt000

According to Microsoft's KB article 952032:

This issue occurs if the following scenarios are true:
  • Windows Update or Microsoft Update tries to install a driver a second time for an additional piece of identical hardware such as a graphics adapter.
  • Windows Update or Microsoft Update tries to update a currently installed driver to an unsuitable version of that driver.
The "workaround" suggested by Microsoft is to "hide" the offending update so it does not get offered again.

. . . . Say WHAT?!

Strange, I thought that this was the entire reason behind Windows Update in the first place - it (supposedly) scans your system for needed updates, grabs them, and then installs them.

I would have thought it would have skipped it the 2nd time.  At least it caught itself and threw an error!

Oh, and by the way, if any of YOU would like to make naming suggestions for my "stupidity" award, please post them here and/or e-mail 'em to me.

What say ye?

Jim

3 comments:

  1. Windows Update is really important , I would like to have the chance of be a professional in this area,I really enjoyed your information , Do you know that , without the user needing to install them manually, or even be aware that an update is required.

    ReplyDelete
  2. thank you very much.... your help was more than welcome...

    ReplyDelete
  3. My assumption is that this might happen if a manufacturer's driver update (e. g., HP) is applied and Windows Update later attempts to install the same or an earlier version of the driver.

    ReplyDelete

Thanks for sharing your thoughts here at the QA Tech-Tips Blog!

Note:
This blog will not, repeat NOT, publish comments that contain ANY KIND OF HYPERLINK.

If your comment contains ANY KIND OF HYPERLINK it WILL BE DELETED.

Please read the article at How To Get Comments Approved On This Blog for additional information regarding this rule.

Thank you for understanding.

Jim (JR)