Microsoft claims to have fastened Home windows Metadata connection points which proceed to plague prospects, inflicting issues for customers attempting to handle their printers and different {hardware}.
When new {hardware} is added to a Home windows pc, the working system connects to a Microsoft-operated web site known as the Windows Metadata and Internet Services (WMIS) to obtain metadata packages related to the actual {hardware}.
“When the working system detects a brand new system, it queries a web based service known as the Windows Metadata and Internet Services (WMIS) for a metadata package deal for the system,” reads an outline of the WMIS website.
“If a tool metadata package deal is on the market, the System Metadata Retrieval Shopper (DMRC) that runs on the native pc downloads the package deal from WMIS and installs the package deal on the native pc.”
These metadata packages include details about the {hardware}, reminiscent of its mannequin identify, description, OEM supplier, numerous properties and actions, and the system’s related {hardware} classes.
This data is then utilized in numerous Window dialogs, such because the Units and Printers settings web page.
Home windows Metadata providers unavailable
Nonetheless, since November, Home windows has been unable to hook up with the Metadata service positioned at http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409, which redirects to http://dmd.metaservices.microsoft.com/metadata.svc.
When visiting the URL from a browser, the positioning exhibits an error stating “502 Unhealthy Gateway,” indicating one thing is mistaken with the positioning.
As reported by BornCity in December, this induced occasional Occasion ID 201 connection error occasions and repeated Occasion ID 131 errors for ‘DeviceSetupManager’ to seem within the Home windows Occasion Viewer logs, with an outline of “Metadata staging failed, end result=0x80070490”.
![Repeated 131 errors in Windows event logs](https://www.bleepstatic.com/images/news/Microsoft/w/wmis-errors/before-patch-events.jpg)
BleepingComputer was informed by an admin coping with these errors that the shortcoming to hook up with the Home windows Metadata providers is inflicting issues of their group.
These issues embrace 4-5 minute delays when troubleshooting printer issues or including and deleting print queues, normally resulting in help tickets being filed in regards to the points.
For a big group with 1000’s of Home windows units, this could rapidly grow to be an issue for IT employees.
Nonetheless, Home windows admins had short-lived happiness this week, as Microsoft launched the Windows 10 KB5034763 and Windows 11 KB5034765 cumulative updates as a part of the February 2024 Patch Tuesday with what they declare is a repair for the Window Metadata connection points.
These updates each state that they resolve the issues connecting to the Home windows Metadata servers, and as an added bonus, the connection will likely be over HTTPS, making them safer.
“This replace addresses a difficulty that impacts the obtain of system metadata,” reads each help bulletins.
“Downloads from the Home windows Metadata and Web Providers (WMIS) over HTTPS are actually safer.”
After putting in the updates, BleepingComputer can affirm that the brand new Metadata server URL, https://go.microsoft.com/fwlink/?LinkID=2257403&clcid=0x409, is utilizing HTTPs and redirects to the brand new URL https://devicemetadataservice.trafficmanager.internet/dms/metadata.svc?LinkID=2257403&clcid=0x409, which additionally makes use of HTTPs.
Nonetheless, Microsoft has failed to associate an IP address to devicemetadataservice.trafficmanager.internet in DNS, inflicting connection makes an attempt to fail.
![Connection errors to new WMIS server](https://www.bleepstatic.com/images/news/Microsoft/w/wmis-errors/connection-error.jpg)
Supply: BleepingComputer
BleepingComputer is now informed that that is inflicting the Occasion Log to point out repeated Occasion ID 201 connection errors, stating, “A connection to the Home windows Metadata and Web Providers (WMIS) couldn’t be established.”
Different Home windows admins report seeing comparable Occasion ID 201 errors in Occasion Viewer after putting in the replace.
“Similar right here – no 131’s anymore however **** of 201’s,” reads a put up on the Microsoft forums.
It’s unclear why Microsoft disabled the Metadata servers within the first place and why they aren’t bringing them again on-line as anticipated.
BleepingComputer contacted Microsoft about this challenge yesterday however has not acquired a response to our e mail.