Windows Update driver for Samsung ML-2010 is faulty

Windows update is trying to install a printer driver for my Samsung ML 2010
but it fails and returns a 800F0233 error. The file direct from Samsung does
the same. According to Microsoft's site at:

https://www.microsoft.com/whdc/drive...pkgerrors.mspx

that error code is the fault of Samsung. Does Microsoft not test the drivers
it makes available through Windows Update?

No the vendor tests the drivers and tells MS that everything works fine.

I forwarded this information to someone who can connect with the Windows
Update team so they can determine what to do with the driver.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"JCK" <JCK@discussions.microsoft.com> wrote in message
news:6C77BFD2-9279-4D42-87E1-7D25B04FD306@microsoft.com...
> Windows update is trying to install a printer driver for my Samsung ML
> 2010
> but it fails and returns a 800F0233 error. The file direct from Samsung
> does
> the same. According to Microsoft's site at:
>
> https://www.microsoft.com/whdc/drive...pkgerrors.mspx
>
> that error code is the fault of Samsung. Does Microsoft not test the
> drivers
> it makes available through Windows Update?

Thanks for the info. It tried again today and this time it worked.

Glad it worked. The Windows Update group analyzed the VISTA WU print
drivers failure rate and seemed concerned that the number of failures is
higher than other device drivers available. Maybe they'll start removing
the failing ones. Or just keep trying until it works as in your case.

What's the better solution?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"JCK" <JCK@discussions.microsoft.com> wrote in message
news:A2061359-7632-456F-9CD1-D68F2F8F2308@microsoft.com...
> Thanks for the info. It tried again today and this time it worked.