Discussion
  • Important thread
24424 views

After installing a driver update “Microsoft – WPD – 2/22/2016 12:00:00 AM - 5.2.5326.4762” you lose access to your connected phone or portable device

Jestoni Mac started on

Updated with a solution (3/22/17)

Please verify this is your experience before working through the solution below.

An incorrect device driver was released for Windows 10, on March 8, 2017, that affected a small group of users with connected phones or portable devices.  After installation, these devices are not detected properly by Windows 10, but are affected in no other way. 

We removed the driver from Windows Update the same day, but if the driver had already installed, you may still be having this issue.

You can check if you installed it by looking in your Windows 10 update history.

From Start, choose Settings, then Update and Security, Windows Update, and then select Update History.

This driver will be listed as Microsoft – WPD – 2/22/2016 12:00:00 AM - 5.2.5326.4762. If it is in the list, try the methods below to remove the driver and fix the issue.

To resolve this problem,
Microsoft has developed a driver troubleshooter that can be downloaded and run on Windows 7, Windows 8/8.1 and Windows 10 PCs experiencing this issue.

Solution:
    1. Download the Windows troubleshooter here and click Run to launch.
    2. Click Next to step through the troubleshooter.  It will ask to “Find a fix or workaround for new issue 108018”.  Click Next again.
    3. The troubleshooter will detect problems and if all goes well, you should see a screen informing you that it fixed “Emerging issue 108018".


     4. Click Close to exit the troubleshooter.

Previous manual steps to remove the problem driver:

Method 1: Use a System Restore Point

  1. Press Windows Key + R to bring up Run.
  2. In Run, type rstrui and then press OK.
  3. If a system restore point is available, it will show in System Restore.  Follow the steps to restore your system to a point prior to the March 8 install of this driver.

Method 2: Roll back the device driver and remove from system

Part 1: Roll back the driver (When finished, you must complete Part 2 or the incorrect driver will reinstall)

  1. Press Windows Key + X and then choose Device Manager in the menu.
  2. Look for the device with a yellow and red mark next to it.  It should be your phone or other connected device.
  3. Press-and-hold or right-click on the device and choose Update Driver Software.
  4. You may need to reboot and reconnect the device. If so, follow these steps again to get back to the driver update.
  5. Select Browse my computer for driver software.
  6. Choose Let me pick from a list of available drivers on my computer.
  7. Check Show compatible hardware, select MTP USB Device, and then choose Next.
  8. Finish the install and reboot your PC. Verify that the mobile device is detected.

Part 2: Prevent the driver from reinstalling

  1. Press Windows Key + X, and in the menu click on Command Prompt (Admin), and then choose Yes on the prompt.
  2. Type pnputil.exe -e and hit Enter.  This will list installed device drivers.
  3. Scroll through the list looking for the description that matches the one in the below example (except for the .inf file’s published name).  Make a note of the .inf file name associated.  It should be something like oem##.inf with a one or two digit number after the oem in the name, and have the Driver date and version as shown in the following example:

Example:
Published name :            oem42.inf

Driver package provider :   Microsoft

Class :                     Portable Devices

Driver date and version :   02/22/2016 5.2.5326.4762

Signer name :               Microsoft Windows Hardware Compatibility Publisher

     4. Now type pnputil.exe -d oem##.inf where the ## is the number in the file name noted below.  Example: oem62.inf.

     5. Hit Enter and the incorrect driver is now deleted from your system.  When you disconnect and reconnect your device, it should not   reinstall the incorrect driver.

Regards.

148 people have recommended this discussion

Abuse history


progress