I'm getting this on my laptop. WXP SP2. Have deleted internet temporaries,
history, etc.
Still no go.
Can anybody suggest a fix?
TIA
Adam
I'm getting this on my laptop. WXP SP2. Have deleted internet temporaries,
history, etc.
Still no go.
Can anybody suggest a fix?
TIA
Adam
I got this when installing MS updates (XP SP2) for option hardware hp color
LaserJet 9500 MFP (DOT4). It was on the custom list, I didn't have that
hardware (or driver, I guess), but decided to install it anyway. it failed
with same code as you. According to
http://inetexplorer.mvps.org/archive...date_codes.htm, 0x800F020B
error means 'device instance does not exist'. That seemed to apply to me so I
then tagged that update as 'Do not show'(?) and ignored it.
Maybe they (HP? M$?) need to be contacted anyway about suggesting
inappropriate updates!
If you DO have that hardware, then I guess HP may be the people to contact.
Well, it's really weird. A device instance DOES exist -- I can't imagine MS
would be touting the update if it didn't. I don't know the significance of
DOT4 -- seems to be used as a PORT identifier and my device uses a STD TCP/IP
port.
I wonder if it's really those "Universal" drivers HP is trying to peddle?
Those don't look very appealing IMHO since they interfere with the Windows
"look and feel". But then, so does VISTA so I guess they're entitled. :)
I have exactly the same problem - same operating system, same update, same
error code. Like Adam, I do not have this particular printer - although I do
have other HP printers (2).
I also tagged the update as "Do not show", which worked for a few days.
Then, it reappeared again. Consequently, my system has attempted, and
failed, to install this update on numerous occasions. I wish the suppress
marker would work.
--
Bob
"Adam Selene" wrote:
>
>
> "Brewmanz" wrote:
>
> > "Adam Selene" wrote:
> > > I'm getting this on my laptop. WXP SP2. Have deleted internet temporaries,
> > > history, etc.
> > > Still no go.
> > > Can anybody suggest a fix?
> > > TIA
> > > Adam
> >
> > I got this when installing MS updates (XP SP2) for option hardware hp color
> > LaserJet 9500 MFP (DOT4). It was on the custom list, I didn't have that
> > hardware (or driver, I guess), but decided to install it anyway. it failed
> > with same code as you. According to
> > http://inetexplorer.mvps.org/archive...date_codes.htm, 0x800F020B
> > error means 'device instance does not exist'. That seemed to apply to me so I
> > then tagged that update as 'Do not show'(?) and ignored it.
> > Maybe they (HP? M$?) need to be contacted anyway about suggesting
> > inappropriate updates!
> > If you DO have that hardware, then I guess HP may be the people to contact.
> > HTH
>
> Well, it's really weird. A device instance DOES exist -- I can't imagine MS
> would be touting the update if it didn't. I don't know the significance of
> DOT4 -- seems to be used as a PORT identifier and my device uses a STD TCP/IP
> port.
>
> I wonder if it's really those "Universal" drivers HP is trying to peddle?
> Those don't look very appealing IMHO since they interfere with the Windows
> "look and feel". But then, so does VISTA so I guess they're entitled. :)
> Thanks,
> AS
I suggest that you go to the HP site at http://www.hp.com/ and ensure that
you instal the latest drivers for whichever HP printers that you do have.
This should prevent an update being detected in the future.
I had done that already - and all HP drivers are up to date.
I started a live chat with Hewlett Packard tech support. Toatally useless!
Their recommended solution was to disable Microsoft Update!!
I am yet another victim of exactly the same thing as Adam. I also have the
device. One thing that I did notice was that I can no longer set any of the
properties in the printer dialog any more (when I click on preferences, I get
an exception that some function caused a protection fault - I thought we were
not supposed to get these anymore
I just had a play & have found a way round this bug that may work for you too. . .
Make a note of what model of printer the failed driver was for.
Go to Control Panel, Printers & Faxes.
Right click in the white space (i.e. not on the printers themselves, but in the area where they're listed) & select Server Properties.
Click on the Drivers tab
Click on the Name column title to sort alphabetically by name
Scroll through until you find the driver for the model mentioned (it may not have exactly the same name as the one listed, but should be fairly obvious which one you're after)
Click on the driver & click Remove
Click Yes to the prompt
Click OK to close the screen
Rerun windows update - should all be good.
Hope that's clear & brings you luck & fortune in the world (or at least stops you getting an error each time you run updates).
SOLVED:
Well a bit tired ... but of all the info above i agree and have been there with a system.
nice call on the right click the white body of window on printers but this did not fix me
However this guy wrote a good article, now this did not come fast for me to find the fix grant you this ... however with trial and error and research and reading etc I finally came to put all thought and all post and all articles together and thus it work ... with this link
Note you must be careful and read a little ... but this did the trick, after installation you will run a command ... just read a little .. will only take ten minutes of read and installation and thus you should be cozy as to know what to do ... but do it slow
This first link / solution labeled here as "A" is the main link and concept and has the link / solution labeled "B" (found below) in the main ariticle, however do note that the link labeled "B" is the solution that worked!
Solution "A"
http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
Solution "B"
If the Print Spooler service is not operational, or you want to make certain there are no printer driver remnants, either follow the instructions below or use cleanspl.exe from the Windows 2000, XP or 2003 Resource Kit (http://www.microsoft.com/downloads/d...isplayLang=en). cleanspl.exe from the Windows 2003 Resource Kit tools will work on Windows XP.
Again take the ten minutes to read ... and take all your other readings and see if this is a good fix. As for me ... it was great after much study!
After this and a restart ... I did windows update / custom and thus found all updates in custom to be 0 ... no more hp print driver update recommedation etc, infact it work so good i did not take a print screen of the error with the little yellow exlamation next to it saying hp recommends this update etc. to post here ... and I am glad as I am tired, Thus the fact is ... I am now done for the night with updates and issues.
Bookmarks