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

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.

 
Discussion Info

Last updated August 16, 2018 Views 95,233 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

My Sansa Clip+ was not recognized by Windows in either Auto or MTP mode. I'm glad I looked at my Windows Update history and then searched the latest update to find this. I tried successfully the first method, thanks!
Thanks a lot !  Explanation was very clear and easy to follow.  It has solved my problem.
Blanca

My GoPro Hero 5 is not getting detected. I have tried the workaround, and it recognizes it as MTP Device, but does not appear in MY Computer for browsing the files in it....

It seems that for mobile phones this is working, but not for my brand new camera...

Thanks M$...

Any other workaround?

I noticed that some users do not have this update specifically listed in their update history but the drivers are present on their system.  What scenario would cause that to occur a partial installation or something else?

In my scenario,

I have this update twice, one correctly installed, and then one after that one that says that is failed, very wierd...

I'd like to hope that my only sollution will be not to reinstall system... maybe any engineer in Microsoft is breaking his brain to undo this mess... Can't they release the original driver separately?

:(


Regards.

Method 1 has solved the problem. Thanks

Did you have this driver installed?  It was only available for a couple of hours, so the install rate was actually low.  Was the GoPro connected fine and then stopped being seen?

Does the GoPro work in other PCs?  I assume you have it turned on when connected and that GoPro has the sync symbol.

Charles

My GoPro Hero 5 is not getting detected. I have tried the workaround, and it recognizes it as MTP Device, but does not appear in MY Computer for browsing the files in it....

It seems that for mobile phones this is working, but not for my brand new camera...

Thanks M$...

Any other workaround?

 It was only available for a couple of hours, .


More like Two Days!  My machines kept offering it and asking for a special install as the automatic one had failed.  As it was so suspicious, given the date, I did not allow it to install.  I first noticed the request on Tuesday evening UK time, it was finally gone some time Thursday evening, after the message at the top of this thread had been posted.

Given all the discussion around the 'net I was amazed it took MS so long to respond.

--
The more people I meet, the more I like my dog.
MCC 2011, 2015, 2017

I have a Seagate Mobile Hard Disk can not be recognized by WIN 10 any more after I install this silly update...

And it can not work with the setting you post as "MTP USB Device"

Thank you Microsoft for mess up my computer again!

For me, it was "oem45.inf" that I had to remove. This update was not just available for a couple hours, it was up for at least a day or two. 

This whole ordeal would be so much easier if, oh I dunno, Microsoft just released another patch, that checked if we had that driver installed and DELETED IT THEMSELVES TO FIX THEIR MESS!!!!

I was able to fix my issue because I am aware how this works, but I really don't expect someone else with less technical know-how to know what to do or even know what to look up to fix this issue, this would result in them bringing their device(phone/tablet) and computer to a repair shop, waste a bunch of money, all to fix this issue that Microsoft caused.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.