Windows 10: Event Error 131-DeviceSetupManager-Metadata staging failed

I have recently been besieged with numerous 'Event Viewer Errors 131- Metadata staging failed.' These errors just appeared for the first time three days ago, and have logged over 100 same events since.


Following an earlier thread, for this same complaint ( https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/devicemetadataserviceurl-event-131/411a471f-8963-4015-ad7a-2cce49fdb2b6) the 'DeviceMetaDataServiceURL' , http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409, was found to be incorrect. Web search of this link proved to show an invalid and security threat location. Changing the URL location to http://dmd.metaservices. microsoft.com/dms/metadata.svc, was given as the solution, and evidently had given some users good results. It has not worked for me, and a Web search of the new URL, http://dmd.metaservices.microsoft.com/dms/metadata.svc leads to a '404 Not Found' response, and suggestion to clear the DNS cache. Cache was cleared, but URL still led to "404 Not Found' result. What is the correct 'DeviceMetdataServiceURL'?


While it has been proposed that this is more of a nuisance error, than a major problem, and all other programs and computer functions are working well, the amount of Event Errors 131, is frustrating and bothersome. I have run the SFC checker, DISM /Online /Cleanup-Image /RestoreHealth through the Administration PowerShell, all to no avail. Also a 'Clean Boot' was systematically followed, with no problems noted.


My current version of Windows 10, is Version 1903, (OS Build 18362.356), with the latest Cumulative Update (KB 4515384), and .NET Framework Update (KB 4514359), being recently installed, along with Store Updates for numerous Apps. I mention these updates as that is the only recent change made to the OS, prior to the appearance of a multitude of DeviceSetupManager - Metadata Setup failures.


Any help or suggestions regarding this issue, would be appreciated ... sans doing a 'Clean Install' or a 'Repair Upgrade from Windows 10 ISO file', as my ISP connection is very..very slow .. and this issue is not terminal .. at least not yet.. A copy of one event error below, with all other 131 Errors similar less specified container:


Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 9/15/2019 9:52:37 AM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: DESKTOP-RDH6O3N
Description:
Metadata staging failed, result=0x800704C7 for container '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}" />
<EventID>131</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-09-15T16:52:37.635620300Z" />
<EventRecordID>372</EventRecordID>
<Correlation />
<Execution ProcessID="11760" ThreadID="13348" />
<Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
<Computer>DESKTOP-RDH6O3N</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Prop_ContainerId">{00000000-0000-0000-FFFF-FFFFFFFFFFFF}</Data>
<Data Name="HRESULT">2147943623</Data>
</EventData>
</Event>

Thanks,

Andy Asmussen

:)

 

A series of DeviceSetupManager warnings in Windows 10 event logs

I have been "cleaning up" Windows 10, and I'm noticing a series of warnings in the Event Viewer every time I start Windows. And they are in the following order.

It seems that Event 202 repeats every other instance until I finally get the error: Event 131. What would I have to do to fix these problems, so they stop showing up every time in Event Viewer?

 

Metadata staging failed - Event ID 131


Good morning,

Ever since I upgraded my computer to Windows 10 (Home) 64-bit a few months ago from Win 8.1 I have discovered the following Event ID 131 error in Event Viewer, sometimes as many as five times in a row, after restarting or upon booting up:

Metadata staging failed, result=0x80070490 for container '{1959BB49-AC94-11E5-AE34-3010B356F6E6}'

After googling for a few hours I did find a forum (TechNet) where this error was attributed to 'timing' and that Microsoft was aware of it.

A couple workarounds were given until Microsoft comes up with the fix. One workaround given was changing the time from 'Windows-time' to 'time-nist.gov'. However, even though it worked for some folks, it didn't stop the error in my Event Viewer.

I am just wondering if anyone on this forum has experienced the same Event Viewer error and maybe found a way to stop it from occurring.

Thanks and regards,

 

Event Viewer Errors 131+122 DeviceSetupManager


HI.

I'm getting swamped with event id 122 and 131.

My gpedit.msc policy of "Prevent installation of devices not described by other policy settings" is set to "not configured"
and "Turn off Windows Updated device driver searching" is set to Disabled.

Under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata]
I have "DeviceMetadataServiceURL"="http://dmd.metaservices.microsoft.com/dms/metadata.svc"

So all should be correct, right?


I have no idea why I'm getting this.

attached Event Viewer message log in zip file.






administrative_events.zip