Users are still having trouble managing their printers and other hardware despite Microsoft’s claims that Windows Metadata connection issues have been fixed.
A Windows computer’s operating system connects to the Windows Metadata and Internet Services  ( WMIS ) website when new hardware is added in order to download metadata packages related to that hardware.  ,
A description of the WMIS website reads,” When the operating system detects a new device, it queries an online service called the , Windows Metadata, and Internet Services&ndrpp, ( WMIS ) for the device’s metadata package.”
The Device Metadata Retrieval Client ( DMRC ), which runs on the local computer, downloads and installs any available device metadata packages from WMIS.
The model name, description, OEM provider, various properties and actions, and the device’s associated hardware categories are all included in these metadata packages.
The Devices and Printers settings page is one of the Window dialogs that uses this information after that.
Services for Windows Metadata are not available.
The Metadata service at http ://go.microsoft.com/fwlink/? LinkID=252669&,clcid=0x409, which reroutes tohttp ://dmd .metaservices .mvc, has been inaccessible to Windows since November.
An error message stating “502 Bad Gateway” appears when a browser is used to access the URL, indicating that something is wrong.
This led to repeated Event ID 131 errors for” DeviceSetupManager” appearing in the Windows Event Viewer logs with a description of” Metadata staging failed, result=0x80070490,” as reported by BornCity  in December.
An administrator handling these errors informed BleepingComputer that their organization is having issues due to their inability to connect to the Windows Metadata services.
When fixing printer issues or adding and deleting print queues, these issues can cause 4 to 5 minute delays, which frequently result in the filing of support tickets.
This can quickly cause IT staff issues in a large organization with thousands of Windows devices.
However, Microsoft’s release of the cumulative updates for Windows 10KB5034763 and nbbsp, Windows 11, and Windows 11 MB5034765 this week, as part of their February 2024 Patch Tuesday and NBSP, with what they claim to be a fix for the Windows Metadata connection issues, gave Windows administrators short-lived happiness.
Both of these updates claim to fix issues with Windows Metadata servers, and they also add that HTTPS will be used to connect, increasing their security.
Both support bulletins state that” this update addresses a problem that affects the download of device metadata.”
” Downloads over HTTPS from Windows Metadata and Internet Services ( WMIS ) are now safer.”
Following the installation of the updates, BleepingComputer can verify that the new URL, https ://devicemetadataservice .trafficmanager.net/dms/metaldata .svc? LinkID=2257403&,clcid=0x409, is using HTTPs and redirects to it.
However, Microsoft has n’t connected devicemetadataservice to an IP address. traffic supervisor. connection attempts are unsuccessful due to a network in DNS.
BleepingComputer is the source.
The Event Log now displays repeated Event ID 201 connection errors with the message” A connection to the Windows Metadata and Internet Services ( WMIS ) could not be established,” according to BleepingComputer.
After installing the update, other Windows administrators claim to have encountered similar Event ID 201 errors in Event Viewer.
According to a post on the , Microsoft forums,” Same here- no 131’s anymore but **** of 201.”
It is unclear why Microsoft initially disabled the Metadata servers and why they are n’t being restored to normal.
Microsoft was contacted by BleepingComputer yesterday regarding this problem, but we have not heard back from them.