Windows 8 and 8.1 Forums


Continues Errors at startup "Metadata staging failed"

  1. #111


    St. Augustine
    Posts : 388
    windows 8.1 64, LT -Windows 10 Home 64


    Quote Originally Posted by Saltgrass View Post
    Could this simply be Microsoft making changes to the update process while preparing for the release of Windows 10? Both my 8.1 and 10 installs are seeing the same errors.

    I think some of the recent Windows 8.1 optional updates are related to that event or at least are meant to align Windows 8 with Windows 10. But I certainly could be wrong...
    I guess anything is possible but remember, this occurred last Sept. as well and MS acknowledged to Saammy that it was the result of an internal error and was repaired within a few days. As for updates? A couple days after I noticed this I re-imaged my primary PC to a point before any April updates (Macrium) and the metadata error occurred immediately. Trying to be objective, I guess it could be some sort of firewall or permissions issue but considering that there was no such issue the first time, I don't think this is the case. I hope there will be a solution as I think this type of device updating is important especially with W-10 on the way.

      My System SpecsSystem Spec

  2. #112


    Posts : 1,121
    Windows 8.1 x64


    The fact it occurred last September could still seem to be involved with the Insider program and changes being tested for that program. I think it was started a couple of months earlier but I don't remember exactly.

    I set my advanced properties to not download device drivers and got no Metadata errors in Windows 10. I reset it back to default and checked for updates again and got 10 Metadata errors.

    It may not be relevant to Windows 8, but Microsoft is modifying update servers in Windows 10 and has the options shown in the attachment. Such changes could very possibly be also effecting Windows 8. Maybe we will find out in a couple of months or hopefully before.

    Attachment 61705
      My System SpecsSystem Spec

  3. #113


    St. Augustine
    Posts : 388
    windows 8.1 64, LT -Windows 10 Home 64


    Yes, I agree 100%

    It is certainly possible that there is a connection with MS changing how updated device info will be downloaded.

    Saammy thought it was some sort of a forwarding link problem and when you look at the stock URL
    go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 I think it is clear there is some forwarding going on.

    But in the meantime what happens to all those systems getting errors? Will it all be resolved automatically in the background? I guess that's the million $ ?.

    Your screenshot of W-10 is quite a bit different than W-8/8.1

    Attachment 61706
      My System SpecsSystem Spec

  4. #114


    N.Y.
    Posts : 2,214
    Windows 10 Pro 64bit


    Quote Originally Posted by Saltgrass View Post
    The fact it occurred last September could still seem to be involved with the Insider program and changes being tested for that program. I think it was started a couple of months earlier but I don't remember exactly.

    I set my advanced properties to not download device drivers and got no Metadata errors in Windows 10. I reset it back to default and checked for updates again and got 10 Metadata errors.

    It may not be relevant to Windows 8, but Microsoft is modifying update servers in Windows 10 and has the options shown in the attachment. Such changes could very possibly be also effecting Windows 8. Maybe we will find out in a couple of months or hopefully before.

    Attachment 61705
    Well that is one of the fixes here if read back and even one Brink suggested i try in Windows 8.1, i get all your other points about server and Windows 10, thanks for informative thoughts on how this could of occurred..
      My System SpecsSystem Spec

  5. #115


    Posts : 2
    Windows 8.1


    Hi guys,

    Something else is seriously wrong here and NOT the registry value for:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata

    If you take the original registry value:
    "http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409"

    and enter it directly in your net browser, it simply resolves to:
    "http://dmd.metaservices.microsoft.com/dms/metadata.svc"

    So by hard coding this result into your Registry you may temporarily solve the particular metadata issue here (as long as the resulting address stays valid), but it doesn’t really solve the actual problem, i.e. that Windows is unable to launch the original URL in the Registry and/or resolve it (or maybe it can but then it cannot use it?).

    The unknown root cause and actual problem may affect any other similar redirection initiated in the Registry, even though it may not be visible to the common user. The workaround only fixes the particular single problem of the Event 10010 and … that’s all.

    Another story is that the “Event Log Online Help” link in the Event Viewer still doesn’t work (possibly related to the same problem?) but here something else is going on. The official Microsoft URL: “go.microsoft.com/fwlink/events.asp” is INVALID, hence no Event can ever get any help by using this link (btw this problem is just the same regardless the OS since it is caused by the URL which is used in all Microsoft OS).

    So what’s wrong here and why Windows is unable to launch "go.microsoft.com/fwlink..." based URLs from the Registry (or maybe any URLs at all...)?
      My System SpecsSystem Spec

  6. #116


    Posts : 13
    Windows 8.1 x64


    I'm using the "original" Microsoft URL, and at start up I get three occurrences of this error at the moment. Anyone else is experiencing the problem right now? Is this URL still not working on your systems?
      My System SpecsSystem Spec

  7. #117


    Posts : 2
    Windows 8.1


    Quote Originally Posted by Marcus View Post
    I'm using the "original" Microsoft URL, and at start up I get three occurrences of this error at the moment. Anyone else is experiencing the problem right now? Is this URL still not working on your systems?
    I've currently hard coded the specific metadata URL into the Registry (I guess, like everybody else), just to get rid of these event log errors, so I really don't know but I doubt it's been a change (have no time to test this right now). At the same time I find it very strange that “go.microsoft.com/fwlink/events.asp” returns a 404 server error... I suspect some connection here.
      My System SpecsSystem Spec

  8. #118


    Posts : 81
    Windows 8 Home Premium 64 bit

    Yes this is still occurring


    Just to confirm I still have the error if I use the correct forwarding url, changing the url does remove the error from the event log, but it is merely a temporary fix.

    You may note from my previous posts that I am in the process of dealing directly with a level 3 support engineer regarding this issue. He has taken various screenshots from my system together with some recordings for analysis. He has confirmed this is an issue for Microsoft to solve and he is proceeding with the necessary investigations. I have 2 updates so far, so I know they are working on the issue. When I receive a further update I will let you all know.

    Kind Regards
      My System SpecsSystem Spec

  9. #119


    Posts : 81
    Windows 8 Home Premium 64 bit


    Quote Originally Posted by WillyK View Post
    Hi guys,

    Something else is seriously wrong here and NOT the registry value for:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata

    If you take the original registry value:
    "http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409"

    and enter it directly in your net browser, it simply resolves to:
    "http://dmd.metaservices.microsoft.com/dms/metadata.svc"

    So by hard coding this result into your Registry you may temporarily solve the particular metadata issue here (as long as the resulting address stays valid), but it doesn’t really solve the actual problem, i.e. that Windows is unable to launch the original URL in the Registry and/or resolve it (or maybe it can but then it cannot use it?).

    The unknown root cause and actual problem may affect any other similar redirection initiated in the Registry, even though it may not be visible to the common user. The workaround only fixes the particular single problem of the Event 10010 and … that’s all.

    Another story is that the “Event Log Online Help” link in the Event Viewer still doesn’t work (possibly related to the same problem?) but here something else is going on. The official Microsoft URL: “go.microsoft.com/fwlink/events.asp” is INVALID, hence no Event can ever get any help by using this link (btw this problem is just the same regardless the OS since it is caused by the URL which is used in all Microsoft OS).

    So what’s wrong here and why Windows is unable to launch "go.microsoft.com/fwlink..." based URLs from the Registry (or maybe any URLs at all...)?

    Hi there.

    I tried this originally and if I take the original url and paste it into my browser unfortunately it does resolve directly to metadata services as it should, it malfunctions with Http error 404 - bad request.

    You will note from my other posts I am currently dealing with a level 3 engineer at Microsoft regarding this issue. He has screenshots and recordings from my PC to use for analysis and has confirmed there is an issue with the forwarding links in the registry but at present it does not know the root cause. He has launched an internal investigation into the issue and has promised to keep me updated. Any updates I receive I will post for you all to read. I aim to see this one through if I can.
      My System SpecsSystem Spec

  10. #120


    Posts : 81
    Windows 8 Home Premium 64 bit


    Quote Originally Posted by gator2013 View Post
    Quote Originally Posted by Phone Man View Post
    Why is this thread marked "solved" when it is still broke???

    Jim
    In a PM several days ago I asked Brink if he could remove the Solved checkmark on this thread. His answer was, the thread starter is the only one that can do that. I will try sending the thread starter a PM and ask if he can/will mark as unsolved.

    Update:

    PM Sent
    Yes it was marked as resolved last September when we faced the issue. As a recurring issue we have all latched onto a previously resolved issue.
      My System SpecsSystem Spec

Page 12 of 27 FirstFirst ... 2101112131422 ... 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