• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Continues Errors at startup "Metadata staging failed"


Posts
6
got it today too; try time sync and second nist server, it's bla bla error appears on refresh devices and printers; added again redirect URL to registry "DeviceMetadataServiceURL"="http://dmd.metaservices.microsoft.com/dms/metadata.svc" and it fixed for me; no 131 error now
 

My Computer

System One

  • OS
    win 10
    Computer type
    PC/Desktop

RonnieJP

Member
Member
Posts
43
I guess Microsoft is really choosing to ignore this error. Just upgraded to Threshold 2 new Build 10586 (of Windows 10) this morning. Looks like it reset the registry entry again and loads of metadata errors in event log again.
 

My Computer

System One

  • OS
    Windows 8.1 Pro 32-bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Homebuilt
    CPU
    Intel Xeon X3230
    Motherboard
    Intel D975XBX2
    Memory
    4 GB
    Graphics Card(s)
    nVidia GT-240
    Monitor(s) Displays
    Dell P2714T Touchscreen

nigel1210

New Member
Posts
1
I've just done a clean install of win 10 and i've noticed the event ID 131 in the error log.

I'm having an issue on win 10 with slow login, the dots spin about 9 or 10 times before it logs in which is really annoying.

Are other people experiencing the delayed login or is it just the error appearing?
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    PC/Desktop
    CPU
    Intel 4790K
    Motherboard
    Asus Z97 Pro Gamer
    Memory
    32GB Kingston Hyper X
    Graphics Card(s)
    Gigabyte G1 GTX 970

amtino

Member
Member
Posts
81
No delay

I personally do not have a delay with logging in but event ID 131 is still with me persistently. Very annoying.

I understand what you mean about the spinning dots, but I do not have that issue.
 

My Computer

System One

  • OS
    Windows 8 Home Premium 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    HP
    CPU
    XX
    Motherboard
    XX
    Memory
    1TB
    Graphics Card(s)
    xx
    Browser
    IE10
    Antivirus
    Norton

amtino

Member
Member
Posts
81
Still no fix

Months into this issue now and constant emails and phone calls to Microsoft - one fix in October lasted one week - no response from Microsoft since. I think we need Sammy back on the case. More members need to contact Microsoft and make a stand or this issue will remain with us.
 

My Computer

System One

  • OS
    Windows 8 Home Premium 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    HP
    CPU
    XX
    Motherboard
    XX
    Memory
    1TB
    Graphics Card(s)
    xx
    Browser
    IE10
    Antivirus
    Norton

newpath

New Member
Posts
1
You Might Kick Yourself

I registered with the Windows Eight Forums to post what I think is the definitive fix for Event ID 131. The original address in the DeviceMetadataServiceURL is:

http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

However, it should be:

http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409

Get it? clcid should be clsid.

I am using Windows 10 x64 Home and this change fixed everything for me. I should mention that after a single restart, the 131 errors were replaced with a few Warning events. Clearing the log and restarting a second time resulted in no errors or warnings. I have made this fix on three Windows 10 machines and all were fixed.

Hope this helps.
 

My Computer

System One

  • OS
    Windows 10 64-bit

Saltgrass

New Member
Pro User
Posts
1,121
Both of your links appear to be bad.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

derekimo

Moderator
Moderator
Shasta County

Posts
517
Both of your links appear to be bad.
I believe they are just pointing out the error, that link is located in the registry,

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

My Computer

System One

  • OS
    Win 10 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Self Built
    CPU
    Intel I5-2500K @3.3GHz
    Motherboard
    Asrock P67 Extreme4
    Memory
    16GB G.Skill Ripjaws X (4x4GB)
    Graphics Card(s)
    EVGA GeForce 750 Ti SC 2GB
    Sound Card
    ASUS Xonar DG 5.1 Channels 24-bit 96KHz PCI Interface Sound Card
    Monitor(s) Displays
    auria eq2367
    Screen Resolution
    1920 x 1080
    Hard Drives
    250GB Samsung 850 EVO SSD
    1TB WD Blue
    1TB Hitachi
    PSU
    SeaSonic X 650W 80 Plus Gold
    Case
    Corsair Obsidian 750D
    Cooling
    Corsair H60, Three 140mm case fans
    Keyboard
    Logitech Wireless Keyboard K520
    Mouse
    Logitech Wireless Mouse M310
    Internet Speed
    Wave Broadband ~ 100 dn 5 up
    Browser
    Chrome
    Antivirus
    Defender, Malwarebytes Premium
    Other Info
    Laptop specs: HP g7-1365dx /
    CPU: AMD A6-3420M APU with Radeon(tm) HD Graphics /
    RAM: Crucial 8Gb (2x4Gb) /
    SSD: Crucial M4-CT128M4SSD2 ATA Device/ FW 000F /
    GFX: AMD Radeon HD 6520G /
    OS: Windows 10 Pro x64

Saltgrass

New Member
Pro User
Posts
1,121
This has been going on for many months. It was repaired just before one update and then it started again. Since Microsoft does not seem to care I suppose I don't. It would be really unnerving if it was discovered these errors are actually causing system problems.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

gator2013

New Member
Pro User
St. Augustine

Posts
387
This is strange.

I have been involved with this from the very beginning as you can see from earlier posts. I have been running with the original replacement link provided by saammy (http://dmd.metaservices.microsoft.com/dms/metadata.svc) with no errors or problems. I have been running with this link in place for so long and have not thought about it until the last several posts. Just now I decided to check the registry and to my surprise, a new link was in place which I did not install. Microsoft â This must have been modified through an update or something but I have no idea as to when but I have not experienced any errors from it.

I am going to experiment with the various links to see what works and what doesn't and will get back.

The weird part is my other PC, which I don't use every day but has all the same updates as my desktop, still has the replacement from saammy. Go Figure
 
Last edited:

My Computer

System One

  • OS
    windows 8.1 64, LT -Windows 10 Home 64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    HP 500-075 Desktop + HP 15-f018dx Laptop
    CPU
    Intel Core i5 3470 Ivy Bridge 3.2 GHz Quad Core/ LT - i3-4030U 1.9 GHz
    Motherboard
    Foxcon Joshua-H61-uATX
    Memory
    8 GB/ LT - 6GB
    Graphics Card(s)
    Intel Graphics Media Accelerator HD (DX10.1)
    Sound Card
    Integrated IDT 92HD73E
    Hard Drives
    1T HDD, 16G Sandisk Cache Drive, 2T Seagate 3.0 External
    Keyboard
    Wireless
    Mouse
    Wireless
    Browser
    IE11
    Antivirus
    Norton 360
    Other Info
    CyberPower UPS, Macrium Backup, Revo Pro, Malwarebytes Premium

Saltgrass

New Member
Pro User
Posts
1,121
It looks like the last error I had for that event happened at 6:30 pm on 1/26..... Maybe I haven't done whatever is causing the errors, but it stopped before and started back up.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

thexman

New Member
Posts
1
I registered with the Windows Eight Forums to post what I think is the definitive fix for Event ID 131. The original address in the DeviceMetadataServiceURL is:

http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

However, it should be:

http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409

Get it? clcid should be clsid.

I am using Windows 10 x64 Home and this change fixed everything for me. I should mention that after a single restart, the 131 errors were replaced with a few Warning events. Clearing the log and restarting a second time resulted in no errors or warnings. I have made this fix on three Windows 10 machines and all were fixed.

Hope this helps.
I also just registered to answer. Tried the original URL => "clcid=" and afterwards "clsid=" and only the second worked. Moreover, the .srv ending URL did not solve the problem for me. I got other Staging (Connection) Warnings instead. So the clsid= did it for me. Errors and Warning are gone no sideeffects noticed. My PC is on Win 10 Pro...thx!!
 

My Computer

System One

  • OS
    U 14.04 lts, Win 7,8,10

OdinSon

New Member
Alabama

Posts
21
I made an interesting discovery. Apparently microsoft has changed something on the domain. Maybe someone of you can order what to do.

I have checked the path in the registry and this is the result.
The path is for Metdaten: go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

View attachment 50810

I have the solution for the problem.
Searches on regedit for the following entry: DeviceMetadataServiceURL
There you change the URL in the following: http://dmd.metaservices.microsoft.com/dms/metadata.svc
after you have closed the editor is saved the change.
Now the problem is solved and it will also re-loaded device information.
Hats off to you friend thanks so much fresh installed last night nothing but globs or errors redid reg key and new link and followed Shawns tut on the app/store/sync updates not seeing nothing worth worrying about on reboots in event viewer now.

Thanks to you both for the hard work I been using Shawns methods since Win7 came out, I can tell you spent much time and has helped many, and many Thanks from me! :cool:
 

My Computer

System One

  • OS
    Windows 8.1 Pro 64bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Thor V2 / EVGA / Intel
    CPU
    Intel Skylake i6700k Unlocked 4.2ghz 1151 socket - OC'd 4.6 | 58C Max on air
    Motherboard
    EVGA Z170 FTW
    Memory
    16GB=2x8GB Gskill Ripjaws V DDR4 3200mhz memory
    Graphics Card(s)
    EVGA GeForce GTX 960 FTW GAMING ACX 2.0+ with Backplate
    Sound Card
    Realtek HD Audio
    Monitor(s) Displays
    27" ViewSonic 144HZ Gaming Monitor - 24" ASUS 60HZ 1080p hdmi
    Screen Resolution
    1920x1080
    Hard Drives
    120gb Kingston V300 now = 550+Mbps in ATTO
    2 - 1TB WD Blacks with dual processor
    1 - 5TB WD Black with dual processor
    PSU
    EVGA SuperNova G2 750W PSU
    Case
    Rosewill Thor V2 Case Full Tower Black
    Cooling
    (Case 3x230mm - 2x140mm) (CPU Cooler Master Hyper 212X 2x120mm fans)
    Keyboard
    G.SKILL RIPJAWS KM780 MX Mechanical Gaming Keyboard Cherry MX Brown with Gaming Keycaps
    Mouse
    Razer Abyssus 3500dpi
    Internet Speed
    100mbps up/down
    Browser
    Firefox
    Antivirus
    Malewarebytes Corporate | Avast | Win Defender
    Other Info
    * [Controller] Logitech F310 Gamepad
    * [Joystick] Logitech Attack 3

gil80

New Member
Posts
3
Hi all... I know this is a Win8 forum but I'm experiencing it on my Win10 and can't find a solution anywhere.
This thread seems the most serious one around this event 121 issue and this issue seems to be alive to this day.
I've tried all the suggestions in this thread but I'm still getting this issue.
I currently use this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409

Did anyone resolve this?
 

My Computer

System One

  • OS
    Win8.1 Pro

gator2013

New Member
Pro User
St. Augustine

Posts
387
Hi all... I know this is a Win8 forum but I'm experiencing it on my Win10 and can't find a solution anywhere.
This thread seems the most serious one around this event 121 issue and this issue seems to be alive to this day.
I've tried all the suggestions in this thread but I'm still getting this issue.
I currently use this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409

Did anyone resolve this?
I don't believe this issue is any closer to being resolved than it was when it returned. The only link I have had success with is the original link provided by Saammy http://dmd.metaservices.microsoft.com/dms/metadata.svc . I have been using this link without errors since September 2014 all other suggestions result in errors. I have no idea what is going on with this and I have basically given up hope that it will be resolved.
 

My Computer

System One

  • OS
    windows 8.1 64, LT -Windows 10 Home 64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    HP 500-075 Desktop + HP 15-f018dx Laptop
    CPU
    Intel Core i5 3470 Ivy Bridge 3.2 GHz Quad Core/ LT - i3-4030U 1.9 GHz
    Motherboard
    Foxcon Joshua-H61-uATX
    Memory
    8 GB/ LT - 6GB
    Graphics Card(s)
    Intel Graphics Media Accelerator HD (DX10.1)
    Sound Card
    Integrated IDT 92HD73E
    Hard Drives
    1T HDD, 16G Sandisk Cache Drive, 2T Seagate 3.0 External
    Keyboard
    Wireless
    Mouse
    Wireless
    Browser
    IE11
    Antivirus
    Norton 360
    Other Info
    CyberPower UPS, Macrium Backup, Revo Pro, Malwarebytes Premium

amtino

Member
Member
Posts
81
No Luck

As most of you will know, I invested several months working closely with Microsoft to get this issue fixed. It was indeed fixed in October 2015 a week before daylight saving kicked in. Following daylight saving, the error returned. I have had no response at all from Microsoft until yesterday when I was told 'support for windows eight ended 12th January' So it would appear that is it!

In the meantime, like many others I have found the one and only resolve is the alternative URL provided by saammy back in 2014.

If anyone finds any other resolve, do keep us posted.

Thanks to all who have contributed thus far.
 

My Computer

System One

  • OS
    Windows 8 Home Premium 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    HP
    CPU
    XX
    Motherboard
    XX
    Memory
    1TB
    Graphics Card(s)
    xx
    Browser
    IE10
    Antivirus
    Norton

amtino

Member
Member
Posts
81
It would appear, once again, following daylight saving, this error has magically gone away! I do not have it at present yet Microsoft told me the back end team were still working on the issue. In March we had a fix and then following daylight saving the metadata error returned.

I am not confident enough to go back to the original url on a permanent basis but at present, during testing, the error 131 metadata staging failed, is not showing up.

Anyone else tested this recently?
 

My Computer

System One

  • OS
    Windows 8 Home Premium 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    HP
    CPU
    XX
    Motherboard
    XX
    Memory
    1TB
    Graphics Card(s)
    xx
    Browser
    IE10
    Antivirus
    Norton

scitch

New Member
Posts
1
clcid means country language code list. 409 is the us language code so url should be true. clsid is a classidentifier a name for an object. completely wrong use.
http://dmd.metaservices.microsoft.com/dms/metadata.svc works for me.

Hi all... I know this is a Win8 forum but I'm experiencing it on my Win10 and can't find a solution anywhere.
This thread seems the most serious one around this event 121 issue and this issue seems to be alive to this day.
I've tried all the suggestions in this thread but I'm still getting this issue.
I currently use this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409

Did anyone resolve this?
 

My Computer

System One

  • OS
    Windows 10 pro

amtino

Member
Member
Posts
81
Url not redirecting

I have spent over a year dealing directly with Microsoft on this issue as you will see from the forum notes. They still have not come up with a repair for this issue. However, stopping the url from trying to forward and redirect will solve your issue for you. Change the registry to: http://dmd.metaservices.microsoft.com/dms/metadata.svc. This will connect directly to refresh your Hardware without error logging. If you need any further assistance to change the url, please post back.
 

My Computer

System One

  • OS
    Windows 8 Home Premium 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    HP
    CPU
    XX
    Motherboard
    XX
    Memory
    1TB
    Graphics Card(s)
    xx
    Browser
    IE10
    Antivirus
    Norton

JohnBurns

New Member
Pro User
Oklahoma City, OK

Posts
415
I have read thru this entire thread and have yet to find an answer to the 200,201,202 warnings. It's now December,2016 and I would hope Microsoft has some sort of fix , but not yet. Guess warnings are not harming anything and MS likes to keep us users feeling insecure and dependent on MS by having warnings in our event viewers! Oh, well...................doesn't matter, I guess.
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    HP Pavillion p6230f
    CPU
    HP AMD Phenom II X4 810
    Motherboard
    FOXCONN ALOE
    Memory
    8 GBytes
    Graphics Card(s)
    ATI/AMD Radeon HD 42
    Sound Card
    ATI/AMD SB600 - High
    Monitor(s) Displays
    Dell SE198WFP
    Screen Resolution
    1440 x 900
    Hard Drives
    Seagate ST3750528AS
    Browser
    IE 11
    Antivirus
    Windows Defender

Users Who Are Viewing This Thread (Users: 0, Guests: 2)