Continues Errors at startup "Metadata staging failed"
- Thread starter mbushnaq00
- Start date
Hi all,
I want to share what I've done that apparently has "solved" the error. I hope it could help.
1. Go to Control Panel, Administrative tools, Services
2. Go to "Device Setup Manager", open "properties"
3. Make sure "Start up type" is Manual
4. Tap the tab Log on
5. Choose "Local system account" then Ok
Now, repeat it for another service
2. Go to "Windows Time", open "properties"
3. Make sure "Start up type" is Manual
4. Tap the tab Log on
5. Choose "Local system account" then Ok
In my case it worked
I want to share what I've done that apparently has "solved" the error. I hope it could help.
1. Go to Control Panel, Administrative tools, Services
2. Go to "Device Setup Manager", open "properties"
3. Make sure "Start up type" is Manual
4. Tap the tab Log on
5. Choose "Local system account" then Ok
Now, repeat it for another service
2. Go to "Windows Time", open "properties"
3. Make sure "Start up type" is Manual
4. Tap the tab Log on
5. Choose "Local system account" then Ok
In my case it worked
Thanks for that
Hi, some of us have already done this, it is a temporary fix as you are turning off the automatic updating of hardware and devices. The idea is that those of us who have hardware and devices scheduled to update automatically and let window take care of it, it should work.
At present the url to automatically update the devices is malfunctioning and therefore producing event ID 131 ' metadata staging failed'.
Rest assured Microsoft are working on this and keeping me updated, they have not found a resolution as yet but have launched an internal investigation to try and establish what went wrong with the hardware and devices url in the registry on 6th May 2015.
As soon as I receive any more new, I will post the details.
Kind Regards
Hi, some of us have already done this, it is a temporary fix as you are turning off the automatic updating of hardware and devices. The idea is that those of us who have hardware and devices scheduled to update automatically and let window take care of it, it should work.
At present the url to automatically update the devices is malfunctioning and therefore producing event ID 131 ' metadata staging failed'.
Rest assured Microsoft are working on this and keeping me updated, they have not found a resolution as yet but have launched an internal investigation to try and establish what went wrong with the hardware and devices url in the registry on 6th May 2015.
As soon as I receive any more new, I will post the details.
Kind Regards
this error started on 6th May some people are only just seeing it. I guess it depends how often people check their event log. I wish to assure you I have made Microsoft aware of this and they are investigating the issue. I will post back with any updates I receive.
hbordon727
New Member
- Messages
- 10
Hi guys and girls.. im new on here and want to thank everyone for this forum .. I have started getting event id 131 also on boot up, noticed it started this month .. I have also noticed error 200,201,202 and 131. can someone confirm if 200,201,202 is related to 131? I don't know what else to do.. I have clean installed my windows 8.1 twice this weekend.. all drivers are up to date ... thank you=)
Hi
please do not waste your time and energy in reinstalling windows. We had this issue with this event id 131 last September and I spent hours reinstalling windows and reached a dead end. The result was that after 3 days, Microsoft repaired the malfunctioning url.
I am currently in contact with Microsoft as you will see from the forum, unfortunately it is taking somewhat longer this time for them to come up with a repair/resolution. When I here further from them, I will let you all know via the forum. Rest assured, I do know for certain they are working on it.
As for your other events you mention: 200, 201, 202 etc. I do not see these on my system, could you tell me a little bit more about that say say/are. As event id 131 is specifically related to 'metadata' which updates the hardware and devices on the operating system.
I cannot say they are/are not linked without a little more info.
Cheers
hbordon727
New Member
- Messages
- 10
thank you for the reply
hbordon727
New Member
- Messages
- 10
thank you for replying.. event 200,201, and 202 are warnings not errors.. event 201 says the following "
A connection to the Windows Metadata and Internet Services (WMIS) could not be established."
event id warning 200 says"A connection to the Windows Update service could not be established."
and event id warning 202 says "The Network List Manager reports no connectivity to the internet."
i have noticed that they are all relating to metadata ,specially warning 201 .. is it possible that error 131 url problem is triggering warning 201 etc..?
ps: for got to mention that all the warnings and error 131 are classified as Source DeviceSetupManager
A connection to the Windows Metadata and Internet Services (WMIS) could not be established."
event id warning 200 says"A connection to the Windows Update service could not be established."
and event id warning 202 says "The Network List Manager reports no connectivity to the internet."
i have noticed that they are all relating to metadata ,specially warning 201 .. is it possible that error 131 url problem is triggering warning 201 etc..?
ps: for got to mention that all the warnings and error 131 are classified as Source DeviceSetupManager
Ok I note you have done 2 fresh installs of windows this weekend. From experience, if I do a fresh install of Windows via a wireless router then like you initially I do see these events you mention in the log as warnings in particular the Windows Update cannot connect or reports no internet connectivity. However, I find once the install has completed and a full wireless connection made, these warnings do not re-occur.
If you are finding after your reinstall that the warnings are persistent, I would suggest you reset your modem/router and ensure you have a good network connection.
I have also found from experience that if I connect my PC or Laptop via Ethernet to the router before doing a fresh install I do not see the warnings at all. I am assuming this is because the Ethernet is giving the install immediate access whilst Wireless has a short time lag whilst awaiting you inputting your WEP Key etc.
These are merely my observations and personal tests but may help. You should not be seeing this warnings persistently.
Let me know how you are getting on - I did several reinstalls on several laptops last September when the 'metadata' issue occurred before and I reached a dead end, it is not a hardware issue, definitely the Microsoft Server in my opinion.
I also receive these other warnings connection to windows update and network list manager when i started getting errors with Metadata feel related to same issues. As have no issue installing update or my internet connection, those 2 besides Metadata are just warnings not errors. I have also done clean install recently.
I performed a test on one of my systems tonight with fresh install of windows 8:
Event id 131 Meta data Staging failed still prominent.
Event 200, 201 and 202 were present after the install, however, after running windows update and installing the new version of the windows update agent, the warnings were longer triggered on start-up or reboot.
Event id 131 remains on my system the main culprit at present.
Cheers
I did a quick test on this tonight before performing a fresh install of windows: On attempting to change the Windows Time to Local System Account, it merely generated an error and stated this was not possible as other services use the time provider and settings and the setting must be reverted. Sorry but it seems to generate more errors and complications and was not a resolution for me. It locked the system temporarily. Wouldn't advise anyone to go for this unless they want to perform a system restore as it will not allow you to change the setting back once 'applied'
- Messages
- 37
amtino and others -
Just fyi that I am getting the same 131 "Metadata staging failed" errors - seven at a time on each reboot of 8.1 Pro 64-bit - starting May 12, 2015.
Given that amtino has penetrated as far as level 3 and they are saying the right things, I'll wait before doing the registry switch.
Hats off to Mr. Amtino!
Just fyi that I am getting the same 131 "Metadata staging failed" errors - seven at a time on each reboot of 8.1 Pro 64-bit - starting May 12, 2015.
Given that amtino has penetrated as far as level 3 and they are saying the right things, I'll wait before doing the registry switch.
Hats off to Mr. Amtino!
Thanks for that, I will keep you posted with any progress I make. Oh and by the way, not that it makes any difference at all but I am a Mrs!
Mr or Mrs makes no difference to the speed at which Microsoft will resolve our issue.Oh yes I am sure it does, however, rest assured I have got my teeth into this and I am not letting go easily.
Still digging deep my end
I am no technology expert myself and confess I am self taught but like to try and get to the bottom of any errors that I have system wise when I know for certain I have made no changes to the system.
I spend hours reading, researching and literally getting my teeth in as I like to see s resolution when I believe there is one.
However, my first contact with Microsoft started 3 weeks ago and I have had 3 calls from them so far, they were regular but now it would seem they are busy in the background and having nothing to report.
Initially the Engineer wanted to know:
When I did I first see this error? - most certainly 6th May on my system between 9 and 9.30 am UK Time.
Had I made any system changes - No
What was I actually doing when the event first occurred - merely booting up the system.
The Engineer logged on to a screen sharing session and used something called ' problem step recorder' - I pointed out the events in the log via the mouse, I also did a refresh of the metadata so he could see the system generating the error: Control Panel, Hardware and Sound, Devices and Printers, right click on any blank space on this page and click 'refresh' this immediately generates the error because we are running the metadata task on demand.
He then tested his own system to see if the errors were generated at his end, initially he said not but then after rebooting he did indeed see the errors.
He emailed the recordings to himself together with several screen shots of the event log and said these would be sent to the relevant Department to assist them in tracking the issue.
Last Saturday I received a call saying 'this was a major concern' and did I have any other relevant information that may assist as they appreciated the insight and the research I had already done.
I explained that the temporary working scenarios were to change to forwarding url in the registry ' not ideal' tampering with registry keys is merely a mask.
The other temporary fix is to turn off this task completely: Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"
Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED.
He stated he would be reporting this back to the backend team and would keep me updated.
I am still convinced after more testing and event log reading yesterday that IE and a time issue are in some way connected here. The task does complete if you trace it back in the application log but not quite fast enough to stop the system generating the Event ID 131.
I do know what doesn't work:
System restore to a date prior to the event first being seen: negative result
Completely reinstalling the operating system from scratch - negative result
Not performing any windows updates at all - negative result
Making sure all updates are complete - negative result
Reset IE - negative result
Stop and restart the Windows Time Server - negative result.
W32tm - unregister - register - negative result
W32tm - resync - negative result
Flush the Dns Cache - negative result.
Delete all netsh profiles and start again - negative result.
I hope some of this blurb and ranting is helpful to people who are concerned about this event - ~those who do not try do not succeed~ patience is a virtue~
I am no technology expert myself and confess I am self taught but like to try and get to the bottom of any errors that I have system wise when I know for certain I have made no changes to the system.
I spend hours reading, researching and literally getting my teeth in as I like to see s resolution when I believe there is one.
However, my first contact with Microsoft started 3 weeks ago and I have had 3 calls from them so far, they were regular but now it would seem they are busy in the background and having nothing to report.
Initially the Engineer wanted to know:
When I did I first see this error? - most certainly 6th May on my system between 9 and 9.30 am UK Time.
Had I made any system changes - No
What was I actually doing when the event first occurred - merely booting up the system.
The Engineer logged on to a screen sharing session and used something called ' problem step recorder' - I pointed out the events in the log via the mouse, I also did a refresh of the metadata so he could see the system generating the error: Control Panel, Hardware and Sound, Devices and Printers, right click on any blank space on this page and click 'refresh' this immediately generates the error because we are running the metadata task on demand.
He then tested his own system to see if the errors were generated at his end, initially he said not but then after rebooting he did indeed see the errors.
He emailed the recordings to himself together with several screen shots of the event log and said these would be sent to the relevant Department to assist them in tracking the issue.
Last Saturday I received a call saying 'this was a major concern' and did I have any other relevant information that may assist as they appreciated the insight and the research I had already done.
I explained that the temporary working scenarios were to change to forwarding url in the registry ' not ideal' tampering with registry keys is merely a mask.
The other temporary fix is to turn off this task completely: Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"
Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED.
He stated he would be reporting this back to the backend team and would keep me updated.
I am still convinced after more testing and event log reading yesterday that IE and a time issue are in some way connected here. The task does complete if you trace it back in the application log but not quite fast enough to stop the system generating the Event ID 131.
I do know what doesn't work:
System restore to a date prior to the event first being seen: negative result
Completely reinstalling the operating system from scratch - negative result
Not performing any windows updates at all - negative result
Making sure all updates are complete - negative result
Reset IE - negative result
Stop and restart the Windows Time Server - negative result.
W32tm - unregister - register - negative result
W32tm - resync - negative result
Flush the Dns Cache - negative result.
Delete all netsh profiles and start again - negative result.
I hope some of this blurb and ranting is helpful to people who are concerned about this event - ~those who do not try do not succeed~ patience is a virtue~
- Messages
- 37
Did the registry change recommended here, and the error messages have stopped in both reboot and "refresh" in Devices and Printers.
I also notice that there are 10 "recommended" Windows Updates waiting for my 8.1 (which I have not run). Do we know whether any of them is related to this problem?
Thanks.
I also notice that there are 10 "recommended" Windows Updates waiting for my 8.1 (which I have not run). Do we know whether any of them is related to this problem?
Thanks.
Karen62
New Member
- Messages
- 1
- Location
- Rural England
I have this 131 error. It seems to have occurred since a system restore I did after I had WiFi adapter problems. Meanwhile I have disabled device driver updates. I had a large backlog of "recommended" updates, recently I installed a few after checking what they actually do.
