Intel System Update failed (0x8000ffff)

Ever since Update 2004 there's a bunch of optional updates in Windows Update. Sometimes new ones are thrown in there, and occasionally they will be installed automatically. This is on default Windows installation by the way. Now I don't mind this actually, however I do not like it when something fails, like this update right here:

Intel - System - 9/19/2017 12:00:00 AM - 11.7.0.1000

Windows told me it needed a restart. So I clicked the icon at the bottom right on the taskbar, and after I checked Windows Update again once it has been rebooted it told me this:

There were some issues installing updates, but we'll try again later. If the problem persists and you want to search the Internet or contact customer support for more information, this may help: (0x8000ffff)

It told me that it couldn't install the update with this error code under 'driver updates':

0x80240035

The update has now disappeared. I tried searching for it, but there are so many of the same update labeled 'Intel - System' that I don't understand what this update tried to actually update. Why did it fail? And what did it try to update exactly?

Ok, I did some heavy search (2 hours ) and I found exactly what it belongs to.

Intel - System - 9/19/2017 12:00:00 AM - 11.7.0.1000 is the Intel Watchdog Timer Driver for Intel systems. 'Microsoft Update Catalogue' lists ALL of them per manufacturer. I went to the device manager, clicked on "view hidden items" and I found the intel Watchdog Timer Driver (WTD) under system devices. Here's the weird part though; Driver 11.7.0.1000 is already installed... I checked the resources & events tab and the device got "configured" today. But what I don't understand is that when I clicked on "try again" in Windows Update on that failed message, it shows everything as up-to-date, and the error log is completely gone, like nothing happened. I can only assume that it got installed but for some reason Windows Update thought it failed at first? and when I checked again it finally understood?

I am going to let this sit for a bit and see if something changes in the coming days before I mark this as resolved, but feel free to speculate or give me pointers as to why windows update behaved like this. I still don't know exactly what the codes indicates other than "it failed".

Hi! Thank you for the response. This make sense. Regarding why this driver was shown as available for download, maybe we should ask Microsoft. Maybe their A.I algorithm-thingy got a stroke or something, I don't know.

Plenty of online sources have observed (and Microsoft also advises) that you not install drivers recommended in the Optional Updates unless you're having a problem with the device to which the driver corresponds. This article, entitled Don’t use Windows 10’s ‘Optional Updates’ if you want a stable system from Windows Latest on September 29 is pretty illustrative.
HTH,
--Ed--

EdTittel said:

Plenty of online sources have observed (and Microsoft also advises) that you not install drivers recommended in the Optional Updates unless you're having a problem with the device to which the driver corresponds. This article, entitled Don’t use Windows 10’s ‘Optional Updates’ if you want a stable system from Windows Latest on September 29 is pretty illustrative.
HTH,
--Ed--

OldNavyGuy said:

Agree with Ed.

If you do have an issue with a driver, in addition to what the article suggested about going to your computer manufacturer's site...I would also check the hardware device vendor's site to search for updates.

Interesting then that Microsoft will download and install some of these optional drivers on a whim. This is on a completely fresh installation of Windows 10, so everything is set at the 'Microsoft default'. In my case all of the optional updates that has been downloaded automatically has been of newer versions, so I think this right here applies to me maybe:

Microsoft said that users should use the feature only when they have a specific problem. Otherwise, you should consider grabbing updates from your manufacturer’s site or wait for automatic driver updates.

In regards to this Intel system update; it hasn't popped up again so I think I can safely put it as solved. It's installed and everything is fine. I found out that the previous version was also an older driver. It got installed during the upgrade phase to 2004, and further updated through Windows Update as 11.7.0.1000.

By the way, it's scary to think that Microsoft can destroy my PC with outdated or unwanted drivers. But so far I've only been offered updates, not downgrades (knock on wood). Maybe this idea by Microsoft isn't as good as I initially thought.. I will be extra cautious, and see if I can turn off some of the auto-updates that's on by default.