Continues Errors at startup "Metadata staging failed"
- Thread starter mbushnaq00
- Start date
I am experiencing this issue on a brand new Dell laptop and it's actually causing quite a problem for me. It litteraly broke the "project" function in Windows ( Devices > Project ). Can't believe it's taking so long to fix.
And oh yeah, getting the same error as everyone else here...
Metadata staging failed, result={66C542FE-13A5-11E5-824F-FD9DFFCAE6FC} for container '0x80070490'
Sorry to hear Amtino, since Windows 10 about to come out it is probably not there biggest concern. Not sure if you were taking free upgrade to see if it goes away there. Thanks for your efforts.
I'm on Win10's latest insider build10240
Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'
seems to come and go - depends on the weather at startup maybe
Wish I knew what that container '0x80070490' actually is or refers to.
Every now and then I do see a warning about MS hidden device driver, Teredo Tunneling Adapter failed to load.
Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'
seems to come and go - depends on the weather at startup maybe
Wish I knew what that container '0x80070490' actually is or refers to.
Every now and then I do see a warning about MS hidden device driver, Teredo Tunneling Adapter failed to load.
I'm on Win10's latest insider build10240
Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'
seems to come and go - depends on the weather at startup maybe
Wish I knew what that container '0x80070490' actually is or refers to.
Every now and then I do see a warning about MS hidden device driver, Teredo Tunneling Adapter failed to load.
Well tells us not solved there either, not sure myself about these error codes, someone more technical knowledge then i. Take it to Ten Forums, been open.
I had a couple of African Greys. One was bald... he or she was a good guy. The other was just piercing growl overly noisy when strangers around. Traded him for a yellow nape in pin feathers that learned way too much and talked way too much. Once I came home to a frantic 81 year old neighbor... telling me my baby daughter been screaming and crying all day and no one home.. She didn't believe me it was just the parrot.. she had to walk through and search my house. Of course the parrot was quiet as a mouse while she was there except telling her bye bye.
Yeah, Greys are known to pick there feathers, along with Cockatoo. Greys are best talkers and seem be most intelligent. Mine is 18 years old drives me nuts at times, but great companion to me. Some are aggressive to strangers, mine growls when afraid or being on defense, also raising feathers up. Amazon Yellow Nape another great parrot too.
- Messages
- 114
- Location
- New Jersey
Upgraded to Windows 10 from 8.1 and got the error. Changed the URL in the Registry but I still get the error. I haven't seen it at Windows startup. it showed up once after Windows was running for awhile. I'll keep an eye on it.
I am interested to see that despite all my communication with Microsoft and their promises that issue would be resolved in Windows 10 and wait for my upgrade, it has not gone away.
All versions of windows use the same server, Microsoft acknowledged in May that it was a server issue. I refused the upgrade. I had a good idea it would not go away.
From the Microsoft Forum
AM
amtino replied on August 7, 2015
In reply to QPW_Test's post on August 7, 2015
For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.
I was searching for information about it, and ran across this thread.
I refused the upgrade, I knew it would not resolve, all versions of Windows connect to the Microsoft server and they did acknowledge it was a server issue.
I am going to get back to them know and suggest that once again they look for a fix.
Cheers
I will let you all know if Microsoft respond to me. Communication was going well in May and June and then at the end of June - 'Whilst we acknowledge this is a serious issue and has been investigated by our Back End Team, we recommend you wait for windows 10'
AH Ah - I will now start chewing away at them once again.
All versions of windows use the same server, Microsoft acknowledged in May that it was a server issue. I refused the upgrade. I had a good idea it would not go away.
From the Microsoft Forum
AM
amtino replied on August 7, 2015
For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.
I was searching for information about it, and ran across this thread.
For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.
I was searching for information about it, and ran across this thread.
I just knew this would happen. I worked closely with Microsoft Level 3 support for six weeks from May onwards trying to get them to fix this issue. They assured me they were acknowledging this as a serious issue. After six weeks they recommended I wait for Windows 10 and all would be well.I was searching for information about it, and ran across this thread.
I refused the upgrade, I knew it would not resolve, all versions of Windows connect to the Microsoft server and they did acknowledge it was a server issue.
I am going to get back to them know and suggest that once again they look for a fix.
Cheers
I will let you all know if Microsoft respond to me. Communication was going well in May and June and then at the end of June - 'Whilst we acknowledge this is a serious issue and has been investigated by our Back End Team, we recommend you wait for windows 10'
AH Ah - I will now start chewing away at them once again.
- Messages
- 114
- Location
- New Jersey
I no longer get the error message on Windows 10 Final. I have the default URL http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409. If I recall correctly when I first installed Windows 10 I still got the error. Somewhere down the line I stopped getting them.
- Messages
- 108
I still get the errors using Windows 8.1 Pro; haven't checked the logs on a Windows 10 Home laptop.
The URL redirection is outside our machines, however, thus nothing we do fixes the problem; as with others I've simply changed the registry data to point at the redirected URL to cause this problem to go away - since the problem has consistently been one of redirecting the same URL to the same other URL (for more than a year?) I fully expect this "fix" to hang around for some time working fine.
W.r.t. the intermittent nature of the problem it certainly looks to THIS experienced software developer that it is one of timing and/or one of misconfiguration of a particular server being used by Microsoft. BTW, I'm located in Virginia but, for whatever reason, my desktop connects to a Microsoft server in Singapore for unknown reasons (perhaps load balancing - not necessarily related to this problem). It is unlikely, for example, that the Microsoft engineers who attempted to duplicate the error tried a route that transits Singapore - a long way away both distance and internet-transit-time from Virginia...
Anyway, I'm expecting the intermediate processing of redirecting a URL to another URL that is now being bypassed to "fix" this particular error we're seeing.
Hello everybody,
excuse my long absence, but it has done a lot in my life. Above all, I am for the second time became a father.
By chance, I saw that there seems to be problems again. This is not personally noticed me, because I have not put my proposed link from my post in the original condition.
If the problem still current?
If so, I'll forward it to my contact at Microsoft.
Greetings
excuse my long absence, but it has done a lot in my life. Above all, I am for the second time became a father.
By chance, I saw that there seems to be problems again. This is not personally noticed me, because I have not put my proposed link from my post in the original condition.
If the problem still current?
If so, I'll forward it to my contact at Microsoft.
Greetings
- Messages
- 114
- Location
- New Jersey
No problems on Windows 10 Pro x64. Have the original URL in the Registry.
Congrats on being a father for the second time. I have two sons myself, all grown up.
Congrats on being a father for the second time. I have two sons myself, all grown up.
thanks for your congratulations.
Glad to hear that there are no problems at the moment.
Hi Sammy good to have you back, I need your help. Yes we do have the old issue of url not working on the metadata just as we did in September. You raised this with your contact and had it resolved.
We have had this issue on Windows 8 and 8.1 since 16th May and I have been speaking directly with a level 3 engineer who confirmed this was a major issue with the metadata url not forwarding correctly. They also promised me it would be rectified and kept in touch for several weeks but have now gone off the radar without a fix.
The issue is identical to the issue last September, I am therefore using the old temporary fix you kindly gave us in September:
http:// dmd.metaservices.microsoft.com/dms/metadata.svc. and for now that works.
If you still have your contact and think you can get a result, I and many more forum members would very much appreciate your assistance.
Congratulations by the way.
Kind Regards
Saga continues.....been almost a year now. Thank you all for your efforts on this matter as i have been following this thread for probably 6 months or more. On Windows 10 and as said here still i see same issue, 4 errors today other day was 9 errors on metadata.
I sure would like to see a resolve to this one - Sammy maybe our man here, after all he did get this issue fixed last September.
I have spent numerous hours trying to find a resolve and also spent a lot of time with the Microsoft Engineer - They have all the details, screen shots, video recording s of my PC showing the error, when it occurs, how and why etc. They did acknowledge this was probably a url forwarding issue or a time issue on the server, they also said 'it is a major concern' I was promised a fix and then my engineer went off the radar.
Perhaps if Sammy can use his contact, we might just see a fix in the near future.
Thanks to all - we will get there in the end.
