Messed up metadata could be to blame for Microsoft's Windows printer woes
- Reference: 1702046047
- News link: https://www.theregister.co.uk/2023/12/08/messed_up_metadata_to_blame/
- Source link:
Our reader notes that the issue appeared to start with the update, which is when we first caught wind that [1]not all was right . This caused printers to identify themselves as HP. Once that happened, the HP Smart apps package was triggered because Windows detected HP products on the system.
Microsoft confirms Smart App issue renaming everyone's printers to HP [2]READ MORE
The reader went on to note that support personnel were initially quite happy for the afflicted users to believe it was all an HP issue "until we pointed out none of our kit has the HP app as it's blocked."
Oops.
Our reader told us, "They've pulled the SSU KBs and also seem to have switched off the metadata service dmd.metaservices.microsoft.com, which jazzes up printer icons and info."
[3]
dmd.metaservices.microsoft.com is [4]an enterprise connection endpoint used to retrieve device metadata. If one blocks traffic from it, metadata won't be updated. Like, say, renaming printers to HP Laserjets and changing the icons.
[5]
[6]
We put the suggestions to Microsoft, but the company has yet to respond.
However, as of last night, Microsoft had updated the [7]known issue regarding the problem to include the text: "Our investigations indicate that this issue is not caused by an HP update."
[8]
So the fault presumably lies somewhere within Microsoft, but, as the company says: "We are investigating this issue and will provide an update when more information is available."
[9]HP printer software turns up uninvited on Windows systems
[10]Microsoft confirms Smart App issue renaming everyone's printers to HP
[11]HP TV ads claim its printers are 'made to be less hated'
[12]USB Cart of Death: The wheeled scourge that drove Windows devs to despair
Hopefully, Microsoft will get a move on. As well as exonerating HP from blame, Microsoft warned techies dealing with the problem that while standard operations should work as expected, this issue "might affect associations with other manufacturer-supplied printer apps to extend basic printer capabilities." It added: "If this is the case, some or all of those extended functions might not work."
And not just those. Our reader noted that while most users were unlikely to be hit by the problems, "secure print and scanning is borked for many."
We asked Microsoft's Copilot – because that is where all the investment seems to be going instead of, you know, testing stuff – when printing would get fixed. It directed us to a March 2021 update and the automated printer troubleshooter. It ended with a perky "I hope this helps!"
No. It really didn't. ®
Get our [13]Tech Resources
[1] https://www.theregister.com/2023/12/05/hp_smartapp_microsoft_issue/
[2] https://www.theregister.com/2023/12/05/hp_smartapp_microsoft_issue/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZXNLvbQvEtNZ7GcdZQR3qgAAAAA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://learn.microsoft.com/en-us/windows/privacy/manage-windows-1903-endpoints
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZXNLvbQvEtNZ7GcdZQR3qgAAAAA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZXNLvbQvEtNZ7GcdZQR3qgAAAAA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-23H2#3218msgdesc
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZXNLvbQvEtNZ7GcdZQR3qgAAAAA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://www.theregister.com/2023/11/30/windows_hp_software_uninvited/
[10] https://www.theregister.com/2023/12/05/hp_smartapp_microsoft_issue/
[11] https://www.theregister.com/2023/12/07/hp_made_to_be_less_hated/
[12] https://www.theregister.com/2023/11/25/windows_usb_cart_of_death/
[13] https://whitepapers.theregister.com/
Yet again
an excellent reason why enforced automatic 'update' is a lousy idea. It's impossible to have trust in a system that's constantly being tinkered with in unknown ways, quite apart from the frequency of blunders by this particular tinkerer.
Re: Yet again
This isn't confined to Windows.
We use rabbitmq which uses erlang on Ubuntu server.
Last year, and update managed to install the entire fucking X server as part of an erlang "update". Just a regular update, not an upgrade.
I only realised when the CM console suddenly went all GUI.
This is a production system - a hell of a unwind.
'It ended with a perky "I hope this helps!"'
Is that the way you like it, Mr Beeblebrox?
Stop collecting
Stop collecting data Microsoft!! Problem solved. Maybe try reading and implementing from your Feedback Hub, that would give you clues as to customers needs. If you even care.
I wonder how much HP paid them for this? Disabling all your competitors' products must have cost a pretty penny... /s
"We asked Microsoft's Copilot "
At least it didn't send you a poop emoji.