A
Andy Asmussen
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 ( DeviceMetadataServiceURL Event 131) 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
Continue reading...
Following an earlier thread, for this same complaint ( DeviceMetadataServiceURL Event 131) 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
Continue reading...