Among the operating systems affected is Windows 10, Windows 8.1 and Windows 7.
Listed only as "Microsoft - WPD - 2/22/2016 12:00:00 AM - 5.2.5326.4762" users are now searching for answers as to how to correct the problem. BetaNews quotes a Microsoft forum post user saying it "is the driver for Windows 10 Mobile devices" and Windows blogger G?nther Born claims it is an Android driver.
Microsoft Australia has not commented on the issue.
For Windows 7 and Windows 8.1 users the faulty driver was optional, however Windows 10 owners were not given any choice as the Win 10 operating system, installs all driver updates automatically and without warning.
Windows 7 and Windows 8.1 users who did accidentally install the problematic driver can simply roll back their systems to a previous restore point, but Windows 10 does not create restore points automatically and the feature must be manually enabled.
A Microsoft Answers Forum posted the following comment:
"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."