Remember the problem users were experiencing in December with appearing out of nowhere? Well, it seems to be happening again.
In December there were complaints about a spate of drivers with names like these:
INTEL – System – 1/4/2013 12:00:00 AM – 0.0.0.1
Intel – System – 3/13/2016 12:00:00 AM – 22.214.171.1240
explained the sudden appearance of very old drivers, but that may or may not be what’s causing this latest problem.
that their Windows systems are this driver:
Microsoft - WPD - 2/22/2016 12:00:00 AM - 5.2.5326.4762
Amiel Spencer on the says the installation triggers an Error 0x800f0217.
In case you missed the memo, the has a description of WPD drivers:
Microsoft Windows Portable Devices (WPD) enables a computer to communicate with attached media and storage devices. This system supersedes both Windows Media Device Manager (WMDM) and Windows Image Acquisition (WIA) by providing a flexible, robust way for a computer to communicate with music players, storage devices, mobile phones, and many other types of connected devices.
Microsoft provides several drivers for standard protocols and devices, including Picture Transfer Protocol (PTP), Media Transfer Protocol (MTP) devices, and Mass Storage Class (MSC) devices.
It’s looking like déjà vu all over again. For reasons unknown, Microsoft has suddenly released a new driver that may or may not be beneficial for your computer.
Until we get additional information or a report about beneficial side effects from installing this driver, I strongly suggest you avoid it. If you’ve already installed the driver, follow the instructions on AskWoody.com to . If you haven’t installed it and are using Windows 10, consider hauling out to make sure you don’t get stuck.
This would be a great use for the “” option in the Win10 Settings app and in Group Policy, but I’m not convinced that either setting will prevent this particular driver from being installed.
Thanks to AElMassry for the heads-up.
Discussion continues on the