Continues Errors at startup "Metadata staging failed"

[amtino]

Issue upgraded to level 3 engineers

I spoke yesterday with a Microsoft engineer at Technical Level 3 - he agreed this was a genuine issue, he has copies of all the threads and he has asked that he be given at least 3 days to try and locate the server error to ensure it is repaired. We just have to wait once again.

Unfortunately he was unable to generate the error on his own PC but he admitted it depends on the server you are connected to via Microsoft.

 

[gator2013]

I spoke yesterday with a Microsoft engineer at Technical Level 3 - he agreed this was a genuine issue, he has copies of all the threads and he has asked that he be given at least 3 days to try and locate the server error to ensure it is repaired. We just have to wait once again.

Unfortunately he was unable to generate the error on his own PC but he admitted it depends on the server you are connected to via Microsoft.

Many Thanks Hope MS resolves the issue.

 

[amtino]

Thank you - just to keep you up to date

I had a call back from Microsoft this morning saying that they had carried out extensive checks and were unable to generate this error on any of their machines. However, the Level 3 engineer remotely accessed my laptop and made several screen shots, did several tests and recorded them using some clever recorder, emailed everything to himself. I showed him how to generate the error by booting up the machine and also by refreshing the hardware and devices page.

The outcome was that he finally produced the error on his own PC. He has gone back to study his reports and screenshots and promised to get back to me soon. I think I am on the right road now.

Lets sit back and wait. Will keep you up to date.

 

[gator2013]

Thanks for the update.

Certainly seems you are on the right track. I think the last time this occurred it was clear that it was a very obscure problem. It will be very interesting to see how this goes.

 

[jds63]

I had a call back from Microsoft this morning saying that they had carried out extensive checks and were unable to generate this error on any of their machines. However, the Level 3 engineer remotely accessed my laptop and made several screen shots, did several tests and recorded them using some clever recorder, emailed everything to himself. I showed him how to generate the error by booting up the machine and also by refreshing the hardware and devices page.

The outcome was that he finally produced the error on his own PC. He has gone back to study his reports and screenshots and promised to get back to me soon. I think I am on the right road now.

Lets sit back and wait. Will keep you up to date.

Thanks again Amtino, good follow up with them. Been following this thread since i saw my error with metadata. So far has caused me no BSOD or anything else, thankful for that for now.

 

[Phone Man]

Why is this thread marked "solved" when it is still broke???

Jim

 

[jds63]

Why is this thread marked "solved" when it is still broke???

Jim

Assume because of the workarounds used in previous parts of this thread if read back more. Just a band-aid on it for now.

 

[gator2013]

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

 

[jds63]

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

I knew that !!

 

[Saltgrass]

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

 

[gator2013]

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.

 

[Saltgrass]

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.

View attachment 61705

 

[gator2013]

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

View attachment 61706

 

[jds63]

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.

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

 

[WillyK]

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

 

[Marcus]

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?

 

[WillyK]

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.

 

[amtino]

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

 

[amtino]

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.

 

[amtino]

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.