Windows Server 2012 R2 vulnerable to M101-M106 Printer 'rename'.

This is simply to give information to anyone wondering about the problem.

Specifically, since November 29th or so, people have started noticing their Windows 10 and 11 systems having spontaneous installs of HP Smart, as well as all of their printers being relabeled to M101-M106.  Double clicking on a printer shows an error, but right clicking will allow normal use of the printer.  

Most of the responses from Microsoft, that I can find at this point, are of the finger-pointing at HP Smart.   Others are suspecting a metadata service change.    Neither really explains why non-updated (during this time period) older servers such as 2012 R2 are receiving the problems, as they don't have access to the Microsoft Store, nor to HP Smart.   Nor should they have updated printer drivers.  

That's the entirety of the post.  It's not here to try to find a solution, it's to make sure that someone else looking doesn't feel alone.

Here's an initial thread. 

https://answers.microsoft.com/en-us/windows/forum/all/why-all-my-printer-model-converted-to-hp-laserjet/1b39d3c1-199e-4a5f-987f-729401d7e8f5

https://www.bleepingcomputer.com/news/microsoft/microsoft-confirms-windows-bug-renames-printers-to-hp-laserjet-m101-m106/

https://www.bleepingcomputer.com/news/microsoft/microsoft-confirms-windows-bug-renames-printers-to-hp-laserjet-m101-m106/

I posted there first - down at the bottom of the comments.

Please note that the article has Microsoft claiming that if machines don't have access to the store, they won't have the problem.   This is incorrect, leading to this post.