Microsoft windows devicesetupmanager admin код 131

Log name: Microsoft-Windows-DeviceSetupManager/Admin
Source: DeviceSetupManager
Event ID: 131
Level: Error
User: SYSTEM

Metadata staging failed, result=0x80070490 for container ‘{00000000-0000-0000-FFFF-FFFFFFFFFFFF}’

Открыл редактор реестра под админом:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata\DeviceMetadataServiceURL
Было значение
http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409
Поменял на
http://dmd.metaservices.microsoft.com/dms/metadata.svc

Детали здесь.

  • Об авторе
  • Недавние публикации

DenTNT

Источник

Discus and support Event Error 131-DeviceSetupManager-Metadata staging failed in Windows 10 BSOD Crashes and Debugging to solve the problem; I have recently been besieged with numerous ‘Event Viewer Errors 131- Metadata staging failed.’ These errors just appeared for the first time three…
Discussion in ‘Windows 10 BSOD Crashes and Debugging’ started by Andy Asmussen, Sep 16, 2019.

  1. 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

    :)

  2. 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?

  3. 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,

  4. Event Error 131-DeviceSetupManager-Metadata staging failed

    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.

    Event Error 131-DeviceSetupManager-Metadata staging failed [​IMG]

    administrative_events.zip

Thema:

Event Error 131-DeviceSetupManager-Metadata staging failed

  1. Event Error 131-DeviceSetupManager-Metadata staging failed — Similar Threads — Event Error 131

  2. Event Error 131 causing crashing. and freezing on my pc.

    in Windows 10 Software and Apps

    Event Error 131 causing crashing. and freezing on my pc.: this error is the only one inside my event log before and after crashing. I have tried changing the url to no avail. please help meMetadata staging failed, result=0x80004005 for container ‘{F74A0DD6-F469-50F2-B874-C3E8F3856C72}’- <Event…

  3. DeviceSetupManager Errors (Event IDs 131, 200, 201 & 202)

    in Windows 10 Support

    DeviceSetupManager Errors (Event IDs 131, 200, 201 & 202): Hello, Googling this issue seemed a lot more common a few years back, including on this forum. I am getting the same errors and warnings every time I boot my PC, and whenever I click on ‘ Control Panel > Hardware and Sound > Devices and Printers’. Error 131 says: «Metadata…

  4. DeviceSetupManager Error ID 131. Constant freezing and restart of PC.

    in Windows 10 BSOD Crashes and Debugging

    DeviceSetupManager Error ID 131. Constant freezing and restart of PC.: Hi, i’m having problems with windows 10 lately.

    I’m experiencing constant freezing and the only way to get back to «normal» for few time due the constantly problem is restarting the PC directly from the case.

    Event viewer show me this error ID 131: DeviceSetupManager….

  5. Who do we contact to fix these «Metadata Staging Failed» errors?

    in Windows 10 BSOD Crashes and Debugging

    Who do we contact to fix these «Metadata Staging Failed» errors?: I’ve been getting these Event ID 131 errors in the Event Viewer for ages, now:

    Metadata staging failed, result=0x8007000D for container ‘{00000000-0000-0000-FFFF-FFFFFFFFFFFF}’

    They’ve survived at least two Fresh Start re-installs of Windows 10 across both Intel and AMD…

  6. Metadata staging failed, result=0x8007000D

    in Windows 10 Drivers and Hardware

    Metadata staging failed, result=0x8007000D: Hi,

    I have having issue with my Bluetooth headphone. My headphone is shown as paired but sound doesn.t play.

    Reconnecting fixes it for a few minutes.

    I digged into Event Viewer tool and found the following every-time this happened.

    Metadata staging failed,…

  7. Event ID 131 Metadata errors happening lately.

    in Windows 10 Support

    Event ID 131 Metadata errors happening lately.: So I’m getting these the past couple of days recently.

    Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container ‘0x8007000D’

    Metadata staging failed, result={9C52FEAA-DABE-5636-BEC0-AFDCA171FDBD} for container ‘0x80070057’

    Thing is that I don’t…

  8. Metadata staging failed

    in Windows 10 Drivers and Hardware

    Metadata staging failed: These errors have started building up with every reboot.. What’s going on? Never seen them in W764? But now after upgrading to W10 64..

    Metadata staging failed, result={CA0E9E80-3E97-FCAC-730A-8CB080FA2581} for container ‘0x80070490’

    A connection to the Windows Metadata…

  9. Event Viewer Errors 131+122 DeviceSetupManager

    in Windows 10 Performance & Maintenance

    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…

  10. Metadata staging failed — Event ID 131

    in Windows 10 Support

    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…

Users found this page by searching for:

  1. metadata staging failed result=0x8007000d for container {00000000-0000-0000-ffff-ffffffffffff}

    ,

  2. devicesetupmanager 131

    ,

  3. Metadata staging failed result=0x8007000D

    ,

  4. event id 131 devicesetupmanager,
  5. metadata staging failed,
  6. metadata staging failed windows 10,
  7. metadata staging failed result=0x800704c7 for container {00000000-0000-0000-ffff-ffffffffffff},
  8. device setup manager error 131,
  9. device setup manager 131,
  10. error 10/29/2019 9:35:21 pm devicesetupmanager 131 none,
  11. windows 10 event 131 devicesetupmanager failed,
  12. devicesetupmanager event id 131 RDS 2016,
  13. Description:Metadata staging failed result=0x80070490 for container {7ECAC27A-A91D-DC6E-A22B-B104BA0CCB8F},
  14. {fcbb06bb-6a2a-46e3-abaa-246cb4e508b2} 131,
  15. Metadata staging failed result=0x8007EE4F for container {


Windows 10 Forums

Источник
  • Remove From My Forums

  • Question

  • На серверах Windows Server 2016 в журнале событий ошибка:

    Источник: DeviceSetupManager

    ID: 131

    Сбой промежуточного сохранения метаданных, результат=0x80070057 для контейнера «{83FDFEE6-0CC5-663E-4FB0-48707EF272CF}»

    Не могу понять, что это за ошибка.

Answers

  • Привет,

    Посмотрите тему с решениями внизу:

    Metadata staging failed, result=0x80070057 for container 

    Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется «как есть» без каких-либо гарантий. Не забывайте помечать сообщения как ответы и полезные,
    если они Вам помогли.

    • Marked as answer by

      Friday, November 29, 2019 8:37 AM

Источник

  • Forums

  • Microsoft Windows Boards

  • Windows 10

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Event Error 131-DeviceSetupManager-Metadata staging failed


  • Thread starter

    Andy Asmussen


  • Start date

  • #1

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…

  • Forums

  • Microsoft Windows Boards

  • Windows 10

  • This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
Источник
  • Remove From My Forums

  • Question

  • Serious broken url on windows operating system

    Today at 9:11
    AM

    Fault occurrene  commenced 9.30 am uk time 6th May

    Event ID 131:  this event is occurring on hundreds of windows operating systems at my place of work and throughout the community.  Metadata staging is failing because the Microsoft link in the registry is malfunctioning.

    The Microsoft url has somehow become corrupt on your server and no one can connect to that url it is dead and needs an urgent prolevel repair.

    this error is generated by the registry key: HKEY-Local-Machine/Software/Microsoft/Windows/Current Version/Device Metadata:

    In this registry is the url required to connect to Windows Metadata

     This link should forward to: 
    http://dmd.metaservices.microsoft.com/dms/metadata.svc.  It is not forwarding therefore all windows operating systems are being flooded with event id 131  meta data staging failed, because the link is malfunctioning the hardware and devices update
    is generating the errors.  Needs fixing,  please point us all in the right direction to get Microsoft to fix this please

     please advise me this issue will be sent to the relevant department.  There are many users on community sites wondering why there systems are suddenly being flooded with metadata errors.

Answers

    • Edited by

      Tuesday, May 12, 2015 9:13 AM

    • Proposed as answer by
      Yolanda Zhu
      Tuesday, May 19, 2015 7:58 AM
    • Marked as answer by
      Deason Wu
      Thursday, May 21, 2015 7:51 AM
Источник

  • Microsoft windows desktop runtime что это и можно ли удалить
  • Microsoft windows client language pack
  • Microsoft windows desktop runtime что это за программа и нужна ли она
  • Microsoft windows client cbs что это
  • Microsoft windows clean up utility