Mysterious Win10 update “Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762”

Topic

New Reply

Don’t install it if offered. If you’re using Win10, you’ll have to use wushowhide. [See the full post at: Mysterious Win10 update “Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762”] Also see the update at: http://www.infoworld.com/article/3178991/microsoft-windows/details-emerge-about-mysterious-windows-wpd-driver.html

1 user thanked author for this post.

dononline

Reply | Quote

Replies

As soon as I am through with articles I will go to my Preview Ring partition and INSTALL and let you know.

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

A manufacturer-provided driver update that finally cleared WHQL testing, perhaps?

-Noel

Reply | Quote

That was my guess too, I leaving now for there, I will update???

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

Noel,

It appears to be for ONLY MOBILE. That would explain why I am not seeing it on Preview Ring. I am going to breeze through Fast Ring and check there on my why home.

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

To wrap up my W 10 partitions investigation, I found nothing on MU/WU with WU-List, in either Fast or Preview Rings. Not even MRT, which W 8.1 has available all ready…..

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

This update is available for Windows 7, 8.1 and 10. The package contains USB driver für MediaTek Android devices and also some MTP WPD driver. It seems that those drivers are conflicting with already installed ADB-, USB- and MTP drivers.

I got reports from several users, that mobile devices are nor more recognized after this update has been installed (usb and bluetooth). It affects Android devices as well as Lumias.

I will have published a blog post an March 9, 2017 about that at Windows update: Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

7 users thanked author for this post.

Elly, SueW, ch100, woody, dononline, PhotM, lizzytish

Reply | Quote

Thanks for the heads-up, Woody. I checked all three of my WIN 10 computers and nothing here.

Reply | Quote

If you’re using Win10, you’ll have to use wushowhide.

Microsoft article How to temporarily prevent a driver update from reinstalling in Windows 10 says:

• For Ver 1511, use wushowhide
• For Ver 1607, roll back the driver through device manager

It may suggest that wushowhide can no longer be a useful tool in the latest version of Win10.

Reply | Quote

anonymous wrote:

It may suggest that wushowhide can no longer be a useful tool in the latest version of Win10.

Sure seems like they imply that, but WUShowHide is still a useful tool for listing available updates without giving the go-ahead to install them.

-Noel

Reply | Quote

That article’s ambiguous. The way I read it is that there are two different methods for uninstalling the driver (1511 vs 1607), but in both cases you need to use wushowhide.

I think that’s what they’re saying.

Reply | Quote

WuShowhide still works with drivers indefinitely in v.1607 Win 10 Pro on my Intel NUC. I have several MS Updates drivers blocked this way. I don’t see a lot of driver updates through MS Updates for my tablet, which is basically SoC.

This update would not be likely to be offered for desktop and laptop devices which have not been tethered or synced with Android devices.

-- rc primak

Reply | Quote

Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762 error was caused by my LG phone.  I went to   http://www.lg.com/us/support    clicked on “software and drivers” typed in my model # and downloaded the universal driver and install it.  Problem is gone.

2 users thanked author for this post.

rc primak, woody

Reply | Quote

Yes, the best solution seems to be for this and any other MS Updates driver issue — first get the device working again. This may require a rollback and use of wushowhide. Then, go to the real manufacturer site for your entire device (in this case, a phone) and install the latest updated driver if the device OS allows this to be done (most do).

What you have effectively done at this point is, you have updated to a newer (or equal) version number of the driver than the version number in MS Update. So, even though the download and install will go through (if not hidden by wushowhide) nothing will be disrupted, as an older driver will not overwrite a newer driver for the same hardware (the exact same hardware) in Windows.

BTW, the Creators Update promises to expand and move to a more visible position the post-install option to block all driver updates through MS Update. This will improve these incidents for many folks. Myself included. I selected preinstall to never install driver updates through MS Update on the NUC, and this setting is sometimes ignored.

-- rc primak

1 user thanked author for this post.

Elly

Reply | Quote

anonymous wrote:

If you’re using Win10, you’ll have to use wushowhide.

Microsoft article How to temporarily prevent a driver update from reinstalling in Windows 10 says:

• For Ver 1511, use wushowhide
• For Ver 1607, roll back the driver through device manager

It may suggest that wushowhide can no longer be a useful tool in the latest version of Win10.

I don’t think that should be the case.

Of course the consummate alternative is in Powershell, “Hide-WUUpdate” which is part of the “PSWindowsUpdate” Module, and should always work.

Powershell ISE Module: Installing PSWindowsUpdate, Script: Provisioning Get-Pend
https://www.askwoody.com/forums/topic/powershell-ise-module-installing-pswindowsupdate-script-provisioning-get-pend/

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote