Windows 10: how can Conexant - MEDIA - 7/3/2018 12:00:00 AM - 8.65.262.0 error handaling

how can i handling Conexant - MEDIA - 7/3/2018 12:00:00 AM - 8.65.262.0 this install error

:)

 

Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update

Ste84,

I'm with you. I have noted the same thing on my MDT setup with Creators Update and Fall Creators Update. Suddenly, late last week, this strange action started occurring. I allow the continuation on error for the updates, so it was not a show stopper, but with the default of 7 tries, that many reboots lengthened the time of deployment unacceptably for no decent reason.

Microsoft - Printer - 6/21/2006 12:00:00 AM - 10.0.15063.0
Error: 0x80240017

Things to note:

1. This is a NEW thing. Just started, late last week.
2. The update attempts do not appear in the update history.
3. Manually scanning for updates does not locate/attempt to install said update.
4. It affects, at least, Windows 10 Creators Update and Windows 10 Fall Creators Update (otherwise already fully patched.)

I have seen this on my virtual machine testing environment - I have NOT tested it on a physical machine yet (sounds like you are using physical machines.)

 

Error 0*80246002 installing updates on windows 10 pro version 1511

Conexant - MEDIA - 7/12/2016 12:00:00 AM - 8.66.27.55 - Error 0x80246002

 

Is this safe? Quectel Incorporated - Ports - 12/8/2017 12:00:00 AM

I rebooted today and now see Windows wants to install this update. A Google search doesn't turn up anything so I'm wondering if it's legit? "Quectel Incorporated - Ports - 12/8/2017 12:00:00 AM - 5.0.1.3"

I run Norton Security 24/7 and do various other scans with Malewarebytes and online scans with Eset and Trend Micro.

Thanks!