Windows 8 and 8.1 Forums


Continues Errors at startup "Metadata staging failed"

  1. #211


    Posts : 43
    Windows 8.1 Pro 32-bit


    Quote Originally Posted by hbordon727 View Post
    Hi guys, so i went to my local best buy and I went over to the computer department and restarted 8 different computers and they all had the 131 error and warning 200,201,202.. How is it possible that sooo many computers have this issue that has been dragging since 8.1 and still have it.. Microsoft please fix this problem asap
    I'm not surprised at all. I just upgraded from 8.1 Pro to 10 Pro (32-bit) and the upgrade reverted the registry URL to the default one that isn't working. Replaced it with the "fixed" URL and no more 131 errors, HOWEVER, I am getting the 200, 201 and 202 warnings after every boot. From what I read in some other forums, that may have something to do with the device update service trying to start before the network become active, but it is not fixed by the new metadata URL, at least in my case.

      My System SpecsSystem Spec

  2. #212


    Posts : 2
    Windows 10 Home


    Greetings from the UK!

    I just wanted to add my thanks to Saammy for the advice about changing the URL in the registry. Since upgrading from W7 to W10 a few weeks ago I've been plagued with event id 131 errors and Saammy's advice has solved this for me instantly. What does surprise me is that Saammy first posted this fix exactly 12 months ago and yet staff at Microsoft have yet to correct this problem. Worse still it now transpires that they themselves deny it even exists in Windows 10!

    Interestingly earlier today before discovering this forum and the resultant fix I used the 'Get help with this Event ID' look-up service within the event viewer console and guess what....? The Microsoft web page that opened claimed to have no information about this event error! I guess that basically means that Microsoft have yet to look into it. Surely 12 months is long enough isn't it????

    Keeps up the good work boys & girls, I'll certainly look back here if I have any further issues.

    Many thanks
      My System SpecsSystem Spec

  3. #213


    Posts : 81
    Windows 8 Home Premium 64 bit

    replacement url not working for me today


    Has anyone else faced issue with the replacement url http://dmd.metaservices.microsoft.com/dms/metadata.svc

    not functioning today or is it just me?
    Last edited by amtino; 07 Sep 2015 at 07:24.
      My System SpecsSystem Spec

  4. #214


    Posts : 2
    Windows 10 Home


    @amtino

    I'm not experiencing these issues myself fella! That said I now have a whole list of other event errors filling my logs! I wish Microsoft would make it easier to find fixes for these flippin issues, we're not all magicians!!
      My System SpecsSystem Spec

  5. #215


    Posts : 28
    Win 8.1


    Quote Originally Posted by RonnieJP View Post
    Quote Originally Posted by hbordon727 View Post
    Hi guys, so i went to my local best buy and I went over to the computer department and restarted 8 different computers and they all had the 131 error and warning 200,201,202.. How is it possible that sooo many computers have this issue that has been dragging since 8.1 and still have it.. Microsoft please fix this problem asap
    I'm not surprised at all. I just upgraded from 8.1 Pro to 10 Pro (32-bit) and the upgrade reverted the registry URL to the default one that isn't working. Replaced it with the "fixed" URL and no more 131 errors, HOWEVER, I am getting the 200, 201 and 202 warnings after every boot. From what I read in some other forums, that may have something to do with the device update service trying to start before the network become active, but it is not fixed by the new metadata URL, at least in my case.
    getting same as you @RonnieJP
    at least they're only yellow exclam warnings , not red ones
      My System SpecsSystem Spec

  6. #216


    Posts : 6
    win 10


    1) this one solution - "In reply to Marcus_83's post on September 15, 2014" ["Right click on Windows logo in the bottom left corner, then select "run" and type "regedit" (without quotes). Click "OK". Regedit will open. Now go to "Edit" (it's in the top left corner of regedit window next to "File"), click on it, and then click on "Find...". Type "DeviceMetadataServiceURL" (again without quotes) then click "Find next". Wait a few seconds and you can now see "DeviceMetadataServiceURL" in the right panel. Right click on "DeviceMetadataServiceURL" and select "Modify...". Copy and paste the new address "http://dmd.metaservices.microsoft.com/dms/metadata.svc" (always without quotes) in place of the old one. Before executing this last passage, you may want to copy the old address and save it in the notepad, in case you should experience any problems (there shouldn't be any at all) and you'd like to revert back to your previous setting. Now close the registry and you are done. Restart system. Event viewer and everything else should be finally fine. Blessings and all the best "] - is good and fixed inner ms issue that not allow redirected URLS; it fix most of issues; 2) also I had remove all inactive devices via devicemanager (view->show hidden devices); and remove all hidden/inactive devices with drivers; 3) then found that USB3.0 use ms driver; so reinstalled eaton drivers from gigabyte site, still wrong ms driver, so reinstalled in cimpatibility with win 8 and all installed fine; MS not able to retest and keep fresh DB of all drivers, etc; and sometimes older driver work more better under 8 or 10 windows; sometimes ms provide very bad and unusable drivers (for example under win10 I installed beta driver for AMD hd7870 because updated driver by ms was wrong and had terrible perfomance in apps with hardware acceleration; and it's wide ms issue, that often appears in win7 and for other VGA card AMD and NVIDIA); so my advice: - manually update drivers from offsite of MB manufacturers and from AMD/NVIDIA/intel sites; - if device old and had not driver for win 10(or 8 etc) setup it in compatibility mode...
      My System SpecsSystem Spec

  7. #217


    Posts : 81
    Windows 8 Home Premium 64 bit

    Thank you for your input


    Thank you for that, I think most of us on the forum have accepted that we have to change the url if we do not want to be flooded with event id 131 errors. Most of us have been using this since last September 2014 in fact this Microsoft Blunder celebrated its 'first birthday 'yesterday.

    I think that says it all really, I am continuing to work with the Level 3 Engineer and ill keep you all posted. In the mean time as stated by Microsoft themselves ' the url change is a 'temporary work a round' and not a solution and making changes to the registry we all do at our own risk for our own benefit. Microsoft are not happy we are doing this but it does not seem to encouraging them to get on with a real fix at present......
      My System SpecsSystem Spec

  8. #218


    Posts : 1
    Windows 10 Pro


    I'm also getting this error message with a clean install of Windows 10 Pro (not an upgrade) on my new Skylake PC. I haven't tried editing DeviceMetadataServiceURL yet, does this cause any problems other than filling my logs with errors?

    Just checked my Dell Venue Pro 8 tablet that I upgraded from Windows 8.1, and it has the same error. I thought perhaps since I login with a Microsoft ID for my tablet (but not for my desktop), and it was an upgrade from Windows 8.1 there might be a difference.
      My System SpecsSystem Spec

  9. #219


    Posts : 2
    Windows 10 Pro 64-bit


    A bit of context. I'm the QPW_Test who's post about the problem still being in the release version of Windows 10, was referenced by amtino a couple months ago.

    I'm revisiting this problem since I had some time on my hands and I thought I would look into some of the errors in my event log.
    As you can guess, the problem has not been fixed. Except for two Virtual machines XP and 8.1, all my machines are Windows 10 now.

    I jumped into the middle of this thread and started reading to the end, but of course I knew the result before starting, but the contact amtino had seemed so promising!

    Anyway I'm posting to just to put a bit of perspective on this. It is all well and good that we try to get Microsoft to clean up their act, but I have to really tell you that I have actually not found any real problem caused by these errors. As in I have certainly received driver updates.
    I suspect what happens is that it fails to connect on say the first time, but it eventually gets the connection and works OK.
    You will also note that the time that these errors are usually logged is at times like start up. Well it is certainly possible that these services are attempting to connect before the network is fully "plumbed", or other timing issues due to stopping and starting things.
    Another thing that I notice in my logs is that there seems to be a lot of errors that are logged around the time I log off/on or lock/sleep my computer.

    This really tends to make me believe that none of these problems are "real". It is more that Microsoft just isn't doing a good job on startup/shutdown sequencing.

    Also the system I'm currently on is a clean build of Windows 10 Pro 64-bit, and the Device Install Service and the Windows Time services are already setup to manual and using the local service account (I didn't change them). But it seems to me in this suggestion to change them people don't really understand that these services where never meant to be set to something like automatic and be running all the time.
    There is in fact a long line of scheduled tasks that start things, and they will start these tasks as they need them. So short of disabling them they are going to run when requested (and they shouldn't be running all the time). Manual doesn't mean "user" started.

    P.S. other "errors" like I have one for SChannel, have also remained unchanged from Windows 8/8.1 and maybe all the way back to Windows 7. Again they don't seem to actually cause any problems. There do seem to be some new ones in Windows 10 for the XBoxApp and such "apps" hanging/dying from time to time.
    Last edited by ChrisPWQ; 01 Oct 2015 at 20:24.
      My System SpecsSystem Spec

  10. #220


    Posts : 81
    Windows 8 Home Premium 64 bit


    Quote Originally Posted by TerFoldw View Post
    I'm also getting this error message with a clean install of Windows 10 Pro (not an upgrade) on my new Skylake PC. I haven't tried editing DeviceMetadataServiceURL yet, does this cause any problems other than filling my logs with errors?

    Just checked my Dell Venue Pro 8 tablet that I upgraded from Windows 8.1, and it has the same error. I thought perhaps since I login with a Microsoft ID for my tablet (but not for my desktop), and it was an upgrade from Windows 8.1 there might be a difference.

    No the errors are in no way harmful, as you say they just create a rather large error log. Modifying the url will ensure the errors cease. This is merely a timing issue at the Microsoft server end. The tasks do complete but not fast enough therefore generating the error a millisecond before the task does complete. This has happened twice in a year, Microsoft fixed it in September 2014 but now seem reluctant to do anything positive.

    You can rest in peace and leave the registry but see all the nasty errors building up in your log, if this doesn't bother you, then leave well alone. I think this is a personal preference issue at resent.
    Personally I keep a clean system and do not like to see errors unless I know I have done something wrong or tampered with something I shouldn't have .
    The fact that I know this is not system related and is a Microsoft issue really irritates me so I am using the direct url and keeping a clean log.
      My System SpecsSystem Spec

Page 22 of 27 FirstFirst ... 122021222324 ... LastLast
Continues Errors at startup "Metadata staging failed"
Related Threads
The title says it partially, but that's not the whole story: I decided to use OneDrive, and so I sent a folder from my external Toshiba drive to OneDrive. It took forever and three days to finish, and seemingly isn't finished yet. :( I now get, File Failed to Upload -- There was an error...
So I restored my system because I had no other choice from it not booting before and it was working for a day, then when I restarted it said 'installing XX / 93 updates' so I let that run, and when It finally finished, it restarted said 'configuring windows updates XX% complete...' and then it...
Specs: Acer AO756-2808 Netbook Intel Celeron CPU 877 @ 1.40Ghz Intel HD Graphics 2000 Windows 8.1 Pro 64Bit 8G Dual Ram 120SSD Updated Intel Chipset 9.4.0.1026, Intel HD Graphics 2000 9.17.10.3347, and Intel MGMTEngine 9.5.14.1724
Hello, Actually this is more than errors in the Services Console Panel. I have several errors with my fresh install of Windows 8 Pro which I have never experienced before. What also boggles me with all this is that my user account is set as Administrator as usual, but still Windows behaves as it...
When i start my computer i get that error in the bottom left,i used hijackthis and this is the report: Logfile of Trend Micro HijackThis v2.0.4 Scan saved at 10:23:07, on 27/07/2013 Platform: Unknown Windows (WinNT 6.02.1008) MSIE: Internet Explorer v10.0 (10.00.9200.16537) Boot mode: Normal...
Hi there, I am facing a problem with the backup program of Windows 8. My computer (Asus with 250SSD) disk is new and I just installed my programs. Now I want to create a System Image using Windows. The image should be around 50go. Everything works fine until I get a message error saying my...
Hey all Tearing my hair out with my 32bit W7 to W8 pro upgrade here.. :(. Setup gets to 24% and then bombs out with "Windows 8 installation has failed". The logs say.. 2012-10-27 21:01:41, Error Error while getting snapshot properties of fixed drive 2: 0x80042308...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook