Hey Microsoft, could you please stop breaking my PC? The latest WPD driver update released on March 8, 2017 is just the latest in a long string of bad updates. If Windows 10 is going to force these updates on my system, the least Microsoft could do is test them properly first.
Don’t get us wrong: automatic updates are very important for security reasons, and we believe they are a good thing. The problem is that Microsoft isn’t just releasing security updates. They’re making major changes to Windows, and not testing the updates properly. They need to do better.
Microsoft Just Released a Bad Driver Update, and I Have to Fix It
The latest and most obnoxious update—at least for me, personally—was the “Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762” update released on March 8, 2017.
Microsoft removed this update from Windows Update, but not until after my and other PCs installed it. As a Microsoft representative explained in a discussion post on Microsoft’s community forums:
“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”
That’s right: Microsoft released a bad driver update that broke the MTP drivers in Windows. MTP is used to access files on connected Android phones and tablets, media players, Windows phones, and some other types of portable devices.
This update seems broken for everyone, so how did it get onto Windows Update in the first place? Driver updates are supposed to be tested through the Windows Hardware Quality Labs before they’re allowed onto Windows Update. Apparently that isn’t happening properly.
Microsoft caught the problem, so that should be the end of the story, right? Nope. Microsoft isn’t going to release an automatic fix through Windows Update to correct the problem. It’s my job to fix what Microsoft broke on my PC, and it’s your job to fix it on your PC if Windows 10 automatically installed the same update for you.
As this is a driver update, there’s no way to “uninstall” it like you would a normal update. Instead, Microsoft recommends you use a system restore point, something that won’t be possible on many PCs, as Windows 10 seems to sometimes ship with System Restore disabled. If you can’t do that, Microsoft invites you to follow a 13-step process involving the Device Manager and several commands run in an Administrator Command Prompt window.
That’s absurd. Worse yet,…