{"id":2452,"date":"2017-03-09T00:11:00","date_gmt":"2017-03-08T23:11:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2452"},"modified":"2024-10-05T23:22:25","modified_gmt":"2024-10-05T21:22:25","slug":"windows-update-microsoft-wpd-2222016-120000-am-5-2-5326-4762","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/03\/09\/windows-update-microsoft-wpd-2222016-120000-am-5-2-5326-4762\/","title":{"rendered":"Windows update: Microsoft – WPD – 2\/22\/2016 12:00:00 AM – 5.2.5326.4762"},"content":{"rendered":"

[German<\/a>]Microsoft has released on March 8, 2017 another mysterious update 'Microsoft – WPD – 2\/22\/2016 12:00:00 AM – 5.2.5326.4762' for\u00a0 Windows 7, 8,1, 10. Some users are reporting issues with mobile devices after installing this update. Here are a few details.<\/p>\n

<\/p>\n

\"\"I received yester evening an e-mail from a blog reader informing me about this new update (I haven't received it yet on my machine). The date for this update is February 22, 2016. Searching the web gave me some hits, but without further details.<\/p>\n

The abbreviation WPD stands for Microsoft Windows Portable Devices. WPD drivers enables the communication with connected mobile devices and storage media (see also<\/a>). WPD driver should exchange Windows Media Device Manager (WMDM) and Windows Image Acquisition (WIA) drivers for mobile devices and scanners.<\/p>\n

Currently I haven't found details about that update on Microsoft's web pages. At TenForums is a longer discussion<\/a> about this package. Weighting the experiences with previous INTEL driver updates, my recommendation is, to block installation of this package. In Windows 10 use the instructions given within my blog post How to block Windows 10 updates<\/a>.<\/p>\n

Addendum: More details about this update<\/h3>\n

I was able to download and inspect this update form Microsoft Update Catalog. The description from the Update Catalog doesn't contain too much details:<\/p>\n

<\/p>\n

The 8,5 MB CAB file contains driver for Windows USB support for MediaTek Android devices.<\/p>\n

<\/p>\n

The .inf files shipped within the CAB file specifies that this update supports the following drivers:<\/p>\n

Android ADB Interface
\nAndroid Composite ADB Interface
\nAndroid Bootloader Interface
\nAndroid USB Driver<\/p>\n

Here are some details from the .inf file:<\/p>\n

;
\n; Android WinUsb driver installation.
\n;
\n[Version]
\nSignature\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"$Windows NT$\"
\nClass\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = AndroidUsbDeviceClass
\nClassGuid\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = {3F966BD9-FA04-4ec5-991C-D326973B5128}
\nProvider\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = %ProviderName%
\nDriverVer\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = 07\/28\/2016,11.0.0000.00000
\nCatalogFile = androidwinusb.cat
\n<\/em>\u2026
\n<\/em>ProviderName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"MediaTek\"
\nSingleAdbInterface\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"Android ADB Interface\"
\nCompositeAdbInterface\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"Android Composite ADB Interface\"
\nSingleBootLoaderInterface\u00a0\u00a0 = \"Android Bootloader Interface\"
\nWinUSB_SvcDesc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"Android USB Driver\"
\nDISK_NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"Android WinUsb installation disk\"
\nClassName\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = \"Android Phone\"<\/em><\/p>\n

Other .inf files contains information about MTP protocol support via WPT driver. But I was wondering why the package also contains outdates USB2Ser drivers (and the inf files contains comments from 2011). Also an RNDIS-over-USB host driver for Intenet Sharing device comes with an .inf file dated at 2011.<\/p>\n

The driver may causes conflicts with mobile device recognition<\/h3>\n

At tenforum a user reported<\/a>, that after installing this update Windows 10 wasn't able to connect to his smartphone. Other users are confirming this issue \u2013 some also for Lumia phones. I got also a similar comment from a Lumia user within my German blog<\/a>. In case your phone is no longer detected, try (see<\/a>):<\/p>\n

1. Open Device Manager (devmgmt.msc).
\n2. Right click on your phone listed in Device Manager, and click on Update driver<\/em>.
\n3. Click on Browse my computer for driver software<\/em> in wizard.
\n4. Click on Let me pick from a list of available drivers on my computer<\/em>
\n5. Check the Show compatible hardware<\/em> check box, then select MTP USB Device<\/em>, and click on Next<\/em>.<\/p>\n

If that doesn't help, try to reboot Windows and test, whether the phone is accessible via MTP from Windows.<\/p>\n

Update error 0x800f0217 and other issues I came across<\/h3>\n

Within this Microsoft Answers forum<\/a> thread some user reported update error 0x800f0217 \u2013 but I have seen similar reports. The users should be glad that the installation fails and should use the instructions given within my blog post How to block Windows 10 updates<\/a> to hide the update.<\/p>\n

There is also another Microsoft Answers forum thread<\/a> (on page 5) from user verdy.p claiming more strange things:<\/p>\n

I got the issue too with this broken MTP driver update and my Android phone will no longer connect to the PC.<\/p>\n

Going to the device manager, showing hidden devices,\u00a0 making sure the phone is not plugged on USB, and removing the \"ghost\/gray\" driver, then plugging the driver again, Windows Update will search and find a matching drier for my LG phone, will try to install it, but will fail also while adding MTP support to the device.<\/p>\n

Also I've just noted that my PC has 3 hidden network interfaces, which are not listed in the PowerShell cmdlet \"Get-NetAdapter\", but are using names like \"Ethernet\", \"Ethernet *1\", and \"Ethernet debug\", but my real interface is now \"Ethernet #3\".<\/p>\n

It's impossible to remove these adapters, or rename them, they are active but have no active IPv4\/IPv6 routing or addresses. They look like backdoors ! Note that none of them was associated to a VM I know (but they could be associated with a hidden VM started in Hyper-V and probably hosting most of the code of the \"CIA Vault 7\" backdoor).<\/p>\n

I've found also weird user SUID in the registry, with some hidden files locked permanently, not listed in any directory with a visible name. Trying to erase the disk clusters (booting from a safe DVD image without mounting the system disk) where they are located to make them inoperant does not work: they are still there, and the content of these clusters are restored as soon as I reboot Windows, even though I checked that they were cleared by rebooting several times from the safe DVD.<\/p><\/blockquote>\n

A possible workaround could be to use system restore to wind back to a restore point before the update has been installed and block the update (see How to block Windows 10 updates<\/a>). But I fear, in Windows 10 system restore won't work due to my article Windows 10 Update KB3213986 kills system restore<\/a>. But we have to wait and see, if that's true.<\/p>\n

Addendum #1:<\/strong> There is now also an article at InfoWorld about that update \u2013 but without too much details till yet \u2013 (side note: I'm in touch with the article author, see also the discussion at askwoody.com<\/a>).<\/p>\n

Addendum #2: <\/strong>Some users are asking, why the driver don't get offered on their system. The reason seems simple: Windows Update pulls the driver only, after a mobile devices are connected to the Windows machine. The driver hasn't been offered on my Windows 7 SP1 production machine during writing the initial version of my German blog post. Later on I've had connected a Nexus 4 smartphone to this machine via USB cable – and suddenly the driver popped up in Windows Update as an optional update.<\/p>\n

I got also a comment<\/a> from a German user, claiming that the driver update has been offered as an important update in Windows 8.1. There is a pitfall in Windows 7\/Windows 8.1 update settings. If the option Give me recommended updates the same was I receiving important updates<\/em> (see screenshot here<\/a>) is checked, the update will be flagged as important.<\/p>\n

Addendum #3:<\/strong>\u00a0Microsoft has published now a short statement within Microsoft Answers forum about that issue. Microsoft recommends the workout I've published above.\u00a0But they described also a way to remove the faulty driver from driver cache (preventing a re-install).\u00a0I've covered this topic within my blog post\u00a0Microsoft's Fix for the 'Microsoft \u2013 WPD \u2013 2\/22\/2016 12:00:00 AM \u2013 5.2.5326.4762' driver issue<\/a>.<\/p>\n

Similar articles:<\/strong>
\nWindows: optional update 'Intel \u2013 System \u2013 8\/19\/2016'<\/a>
\nHow to block Windows 10 updates<\/a>
\nIntel Bluetooth driver released via Windows Update (02\/15\/2017)?<\/a>
\nWindows 7\/8.1: Optional INTEL System driver updates<\/a>
\nWindows: optional update 'Intel \u2013 System \u2013 6\/28\/2016'<\/a><\/p>\n

Windows 10 Update KB3213986 kills system restore<\/a>
\nWindows System Restore fails with error 0xC000000D<\/a>
\nWindows 10 Version 1607: System restore error 0x80070091 [Fix]<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Microsoft has released on March 8, 2017 another mysterious update 'Microsoft – WPD – 2\/22\/2016 12:00:00 AM – 5.2.5326.4762' for\u00a0 Windows 7, 8,1, 10. Some users are reporting issues with mobile devices after installing this update. Here are a few … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[],"class_list":["post-2452","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2452","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=2452"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2452\/revisions"}],"predecessor-version":[{"id":36046,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2452\/revisions\/36046"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}