Share via

Device Setup Manager Metadata staging failed Event ID 131

Anonymous
2023-12-08T03:12:46+00:00

I did KB 890830, KB5032339, KB5032189 and KB4023057 today and on reboot after updating I started getting many of the event id 131 Device Setup Manager Metadata staging failed.  I would get the code 131 when plugging in my backup USB external.  Even when using USB thumb drive- this never happen prior to today's update.  Also, lots of the Event ID on boot. Never had these prior to the update. I am on WIndows 10 PRo, 22H2, OS Build 19045.3693, Dell OPtiplex 64 bit, 12GB memory and 500GB disk.

I got to looking at the registry for devicemedadataserviceURL.  I went to that URL (go.microsoft.com/fwlink/?linkid=252669&clcid=0x409) and got redirected  as site not available to  dmd.metaservices.microsoft.com where I pressed continue and got a 505 Bad Gateway error.

And then just for the heck of it I did a DISM with /checkhealth and all was good, did DISM with /scanhealth and it said all was fine.  Even did sfc /scannow and chkdsk, all was well. NO system files missing or disk problems.

Then I did some thinking (which can be dangerous)  Booting or adding external drives got many of the 131 errors.  However when I disconnect from the internet and boot system or add external drives-  I GOT NO ERRORS Event code131. 

Between all this, I believe our friends at Microsoft have a bad pointer. in the registry entry devicemedadataserviceURL. 

I did an image of system prior to updating, thought about restore and still considering.  All is working fine, I tried all devices and all are working.  I shouldn't look at that event log!  I just today after the mentioned above updates started getting these errors. 

I should add going to control Panel, search for Device Installation, select change device installation setting to NO- does fix the error.  Tested, reboot or adding external drive no longer gets the 131 error.  Now is this a good idea, I don't know, I am not that up on computers anymore.  I retired in 2003 after 38 years as system software tech on mainframes.  Was certified also for Microsoft, but a lot changed since then and I really don't attempt to keep up.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

115 answers

Sort by: Most helpful
  1. Anonymous
    2023-12-17T13:26:32+00:00

    This is the problem:

    This reg key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata\DeviceMetaDataServiceURL

    Points to this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409Which then redirects to this URL: https://devicemetadataservice.trafficmanager.net/dms/metadata.svc

    The 2nd URL is broken and this has happened many times before, going all the way back to Windows 7 in 2015.

    Microsoft needs to fix this. It has been noticed in Germany that it started happening after installation of the 2023-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5032288) and the 2023-11 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5032189). Don't know about Windows 8.1. Windows 7 systems are EOL and get no patches without an extended license.

    In addition to that regedit change mentioned in one of the other replies, the Metadata Staging (used for many things, not just print queues) can also be disabled by going into Windows Settings, then select System, then select About (lower left-Windows 10), then Advanced System Settings (on the right-side), then select the Hardware tab, then click the Device Installation Settings button. In the popup box that appears, you can change it from YES (recommended) to NO (your device might not work as expected). In a Windows Server OS, it is a slightly different process to get to Advanced System Settings.

    Now I don't know about you but, for me, I would prefer that Microsoft gets off its behind and fixes the URL, once again... Then I can expect my device to work "as expected"). Capiche?!?

    Changing the regkey or changing the system setting are both quick fixes and they are NOT acceptable options to me...

    300+ people found this answer helpful.
    0 comments No comments
  2. lmacri 2,500 Reputation points
    2023-12-23T14:19:43+00:00

    Hi Tufrustrated:

    See the workaround suggested by DiverJer in the original post of this thread, which I've modified for clarity and posted below. I have also seen this workaround suggested in threads in various Windows 10 forums.

    1. Open your Advanced System Settings by going to Settings | System | About and select the Advanced System Settings link (under Related Settings). You can also open a Run dialog box and enter sysdm.cpl or simply search for "Advanced System Settings" from the search box on your taskbar.
    2. Choose the Hardware tab and click the Device Installation Settings button.
    3. For the question "Do you want to automatically download manufacturers' apps and custom icons available for your devices?" select "No (your device might not work as expected)" and then click Save Changes.

    Image

    However, see the 05-Dec-2023 post by Microsoft Agent Hahn - MSFT in Don T5's Getting multiple Event ID error 131 Device Set-up Manager which warns that:

    "... Disabling the Device Installation Settings is indeed a workaround, but keep in mind that it also prevents automatic driver installations and updates*. While this may stop the specific errors you were encountering, it's not a long-term solution, especially if you want to ensure that your system is up-to-date with the latest drivers for optimal performance and security.*"

    These DeviceSetupManager Event ID 131 errors in my Event Viewer are annoying but they don't seem to be causing any obvious problems on my Win 10 laptop (e.g., like high CPU activity) and they aren't serious enough to be logged in my Reliability Monitor, so I've decided to leave my Device Installation Settings as "Yes (recommended)" and wait to see if Microsoft eventually fixes the problem.

    Also note that Don T5 has filed a bug report at https://aka.ms/AAo1su9 about these DeviceSetupManager Event ID 131 errors via the Microsoft’s Feedback Hub app. If you have the Feedback Hub app on your system (my Win 10 laptop shipped from the factory with this app preinstalled) then be sure to go to that bug report and give it an Upvote. The more votes this bug report gets the more attention it will get from the Microsoft software developers.


    Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.0 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.6.294-1.0.2201 * Macrium Reflect Free v8.0.7783

    90+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-12-18T20:55:17+00:00

    Absolutely. Broken redirect. You’d think it’d be https too.

    How can they not know their link is broken? Unless — and I’m just spitballing here — they don’t have PCs and use Apple exclusively.

    50+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-12-13T21:13:34+00:00

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DeviceSetupManager/Admin

    "Enabled"=dword:00000000

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata

    "PreventDeviceMetadataFromNetwork"=dword:00000001

    50+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-12-29T11:58:19+00:00

    Don’t go messing around in the registry when you can use the Settings App.

    YOU CANNOT FIX THIS PROBLEM! It is Microsoft’s responsibility.

    You can only stop the errors until MS fixes it by the hardware setting.

    40+ people found this answer helpful.
    0 comments No comments