Continues Errors at startup "Metadata staging failed"
- Thread starter mbushnaq00
- Start date
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.
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.
Last edited:
- Messages
- 11
Thanks, this seems to be the right solution. I am now getting the following information event:
Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 9/15/2014 12:31:17 AM
Event ID: 100
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: ASUS
Description:
DSM service start, mode is Normal, last session (or boot) was 18 seconds ago
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{FCBB06BB-6A2A-46E3-ABAA-246CB4E508B2}" />
<EventID>100</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-09-14T20:31:17.386095200Z" />
<EventRecordID>5057</EventRecordID>
<Correlation />
<Execution ProcessID="368" ThreadID="3924" />
<Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
<Computer>ASUS</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Prop_CoreServiceMode">0</Data>
<Data Name="Prop_Event_Window_Seconds">18</Data>
</EventData>
</Event>
Thank you very much! I have one more question. If I leave everything as is, will I experience any problems or negative consequences (particularly while updating my system), apart from the obvious red marks and error messages in event viewer? Can anyone please answer this? Thanks
Thank you, fantastic job! Sounds like the perfect solution. I'm a bit afraid to touch the registry, but I will try it out nonetheless
Did it and worked like a charm, thank you again
Last edited:
How did you discover the new URL/path ? & its ok for the win8.1 hardware metadata ?
Last edited:
I have read the following document and then understood the workings of the STAGE DEVICE.
https://edulibs.org/get_paper.php?id=8646177
Now that I've tested everything in detail, I can say that for me everything works. I can install new hardware and drivers are located and installed via Windows Update. The information is being loaded.
Maybe this is just a temporary problem which Micrsosoft as drives with the reserves, but I just did not want to wait for a patch.
giusan70
New Member
- Messages
- 3
thanks it works perfect for me. 8forums the best
- Messages
- 374
- Location
- St. Augustine
I agree 100%.
I have this exact same issue and it started 2 days after all the 9/9 updates so I am not totally convinced it is directly related to the updates installed on 9/9/14. Possibly some other background update. I do think it is entirely possible that something has changed on the Microsoft end though because obviously there is some sort of communication issue with Metadata collection.
If MS changed a URL I am surprised it has not affected more users. This is the first 8.1 error issue I have had with this PC since purchase last December. Nothing has changed on my PC NOTHING! File Checker shows no issues and Component Store is clean.
I am scheduled for a call from Tier 2 MS Support on Tuesday to examine the issue but I don't have much confidence in those folks. If simply changing the URL in the Registry will fix the problem, I can do that but I would like to have more information. I don't want to make any changes that might backfire with a future update. I have Restore Points, Custom Refresh Images and Macrium Images on an external drive to fall back on but I still want more of an explanation.
I hope to hear from more users.
Thanks
I can understand that so many users have a few concerns. But one thing is clear. I myself am owner of a computer company and have a partnership with Microsoft. Even the most know nothing in the 2nd level support of a change in the URL. But I got a call and there I was told that this is probably a problem in the internal forwarding. Microsoft developed their base further and also get more information from the hardware manufacturers, therefore it was necessary to make some changes. Either this is corrected on the part of Microsoft, or there is a patch soon, because there are many thousands of clients affected. Just because most people do not look in their event viewer, does not mean they are not a victim of this error.
- Messages
- 374
- Location
- St. Augustine
Thanks for your comments.
In the fix you describe is it simply substituting this address http://dmd.metaservices.microsoft.com/dms/metadata.svc in place of the existing address? go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409
Thanks
Yes...
Hey Saammy, I think I made an interesting/strange discovery. If you backup the original registry key and, after having applied the url change and restarted as you wisely suggested, put the old key back in place, and restart system again, then there will be no errors in the event viewer as well. That is, the old previously not working url will now work just as fine. Do you or anyone else have any idea as to why this strange phenomenon happens?
Looks like I was wrong. After more testing and the useful mikiep suggestion, I can confirm the old url does not work under any circumstances
Last edited:
I take it back. After doing as you suggested, with the old url in place the error is still there. Only the new url really works. Thank you
Presuming that error reports are being submitted to Microsoft, then the error will eventually be addressed if it is indeed a Microsoft problem.
Device Manager errors aren't all catastrophic/fatal, and there's quite a few that I just ignore when working on systems.
If you spend all your time working on these errors, then you'll never have time to use your system.
The question I ask myself is "Is this error actually causing a problem for me on the system?"
If not, then I leave it be. If it is (or if it's possible) then I do some more research.
Device Manager errors aren't all catastrophic/fatal, and there's quite a few that I just ignore when working on systems.
If you spend all your time working on these errors, then you'll never have time to use your system.
The question I ask myself is "Is this error actually causing a problem for me on the system?"
If not, then I leave it be. If it is (or if it's possible) then I do some more research.
- Messages
- 27
You're right John,
But still, for some that don't really understand, it's like you you get a check engine warning light in your car. It might be a loose gas cap or the engine is actually dying
If you don't understand the warning system it's a bit irritating. Then what is the purpose of that warning system if you can't understand it.
FWIW - I ignore my check engine light also! :0)
Seriously tho', there are reporting mechanisms for different levels of understanding.
For example, the Action Center would correspond roughly to the check engine light - while the Event Viewer would roughly correspond to the error codes generated when the tech connects a computer code checker to the diagnostic port on the car. The codes tell you things, but you have to have a different skill set to interpret the results.
This isn't to discourage people from using it, rather it's to show that it's more difficult to interpret - and that it'll take some work to figure out why this error is being generated. The Event Viewer is one of the tools that confounded me early in my career - and it took a lot of work for me to start to understand it.
This topic was an excellent example of the community working together to figure out what's wrong with a common problem and to take steps to fix it. I was really impressed by the hard work and cooperation that this topic shows!
Seriously tho', there are reporting mechanisms for different levels of understanding.
For example, the Action Center would correspond roughly to the check engine light - while the Event Viewer would roughly correspond to the error codes generated when the tech connects a computer code checker to the diagnostic port on the car. The codes tell you things, but you have to have a different skill set to interpret the results.
This isn't to discourage people from using it, rather it's to show that it's more difficult to interpret - and that it'll take some work to figure out why this error is being generated. The Event Viewer is one of the tools that confounded me early in my career - and it took a lot of work for me to start to understand it.
This topic was an excellent example of the community working together to figure out what's wrong with a common problem and to take steps to fix it. I was really impressed by the hard work and cooperation that this topic shows!
Thank you for your compliment to this community. Although I am relatively new to this forum, but also long been active in the IT environment.
We all know that there is no perfect system and we need to work together when it comes to problems. Whether Microsoft, Apple, or the normal user. We're all in the same boat. The technological age.
We are all different people and have our own views and opinions, but the fact that we can collectively advise to mutually complement each other, bringing us further.
We all know that there is no perfect system and we need to work together when it comes to problems. Whether Microsoft, Apple, or the normal user. We're all in the same boat. The technological age.
We are all different people and have our own views and opinions, but the fact that we can collectively advise to mutually complement each other, bringing us further.
