Metadata staging failed event 131

Im having exactly the same issue on my PC with the metadata staging failed device manager errors and this was a clean installation. Other issues I was having also were Schannel Event ID 36888 TLS Protocol Errors repeated on a daily basis. I did several reinstalls but it made no difference. As soon as I went on the internet these errors appeared in batches of three...usually between 6 and 12 of them every day!!

Thankfully now though the Schannel errors have now stopped.

I don't know what is going on at Microsoft nowadays but with Windows 8/8.1 there is constantly problems in Event Viewer.

At one time I always downloaded all Windows Updates with extremely rarely any problems but Im scared to install the Optional Updates now.

Yes, I agree with you here, I have been seeing the SChannel errors on and off for a few months and certainly could not tie it down to any errors at my end, I assumed once again it was a Microsoft issue and as I did not want to constantly look at all these TLS errors, I turned off event logging for them.  If you want to know how to do this for future reference, just reply and I will send you the guide.

I like you rarely perform any windows updates now,  they simply wreck my system and I did decided from a personal point of view that a previous IE Cumulative Security Update was responsible for generating the SChannel errors, but over a period of time, further updates would appear to have cleared this issue.

IE being the only updates I did do stopped last month when the update locked everyone out of IE Gallery and refused to allow users to change search providers amongst other issues.  No more updates for me at present. 

As for the metadata error, I have 5 systems, one of which is a clean install and rest assured they are all suffering with the event id 131 illness at present.  I am in constant contact with Microsoft regarding this issue, and I am assured they are working on it.

I will keep you all posted on my progress. 

Thanks Mazda for your feedback. I too decided that the Schannel errors were linked to the Internet Security Update. Thankfully subsequent updates seem to have sorted it.

As for the TLS errors I don't want to turn off event logging as it only masks the problem really..though I can definitely understand why you've done it yourself. I researched the problem on the net and saw someone else has done the same thing.

As for the Windows Updates becoming very unreliable..the known problem with KB3022345 is the most annoying one of late. I stopped installing optional updates as that Update was causing corruption errors in SFC scans. Then Microsoft made it an important update so it was downloaded automatically (I thought Microsoft must have sorted the problem out with KB3022345). ..the problem is now back on my system. But what are you supposed to do when Microsoft changes it to an important update..so frustrating. Windows Updates has caused me loads of problems..this never used to happen. I used to think it was very reliable.

Thanks for your response, it is always helpful to know other users are suffering the same stress and Microsoft issues and it is not me loosing my marbles!

However, if you can remember or you can still see it in your event log, I would be very interested to know when the SChannel TLS errors stopped appearing, I thought mine had gone but faced them again yesterday but I have not done any IE Cumulative updates for a few months.  I just wondered if you had an idea of the date or month and I would give the IE Update a try for that month see if it clears my SChannel errors.  If you do not have this info in memory or to hand in the log do not worry but it may assist me in getting to the bottom of the TLS 40 issue even I cannot yet fix the metadata.

Cheers

Mine was a clean Windows8/8.1 Installation done on the 10/5/2015 and the most Schannel errors Ive had in any day has been two, most days just one, and none at all for the last two days if that helps you at all. Ive installed all the IE security updates. The only Windows Updates I haven't installed on my system at the moment are 10 Optional Updates.

One  Im having particular trouble with at the moment on a daily basis is a critical error, Driver  Frameworks User mode Event ID 10110 and 10115. Its related to the Windows Location Provider. That ones got me stumped because I don't seem to be having any issues..my computer is working fine.

Event ID 10110 and 10115 I have done a little research some of it may be helpful, I am not an expert but do like to try feasible options.

Typically this event is recorded together with event id 10111 from the same source. Event id 10111 provides information about the actual device that caused this problem.                      

       It's a user-mode driver error,  that unfortunately appears often in Vista and Windows 7 as well.  Some say  update the driver,  problem solved, if you know what driver is causing the issue, do you see any yellow exclamation signs in Device manager? This may sound stupid but have you checked to ensure that the Windows Location Platform was actually activated when you did the reinstall.  This tick box can be checked or unchecked on set-up so easily. You can check it is indeed on and you can also disable it and restart it to see if it makes a difference:       Control Panel> Programmes> Programmes and Features> Turn Windows Features on or off> scroll down the list ensure you have a tick in Windows Location Platform.  If not add one and check your results.  If indeed it is already ticked, untick  thus disabling the Location Platform temporarily.  Reboot the system, check the log, go back and reinstate the tick to turn the Location platform back on.  May or may not be helpful but worth a try and doesn't do any system damage. 

Hi Mazda..thanks for your feedback.

There are no yellow exclamations or sign of any problems at all in Device Manager. I checked Windows Location Provider and it was activated. I tried your suggestion to uncheck the box, reboot and then recheck it again but the errors are still there. Im hoping its something that will be corrected in a future Windows Updates as it doesn't seem to be causing any issues on my PC

     Let me make myself perfectly clear, I am only a casual user of computers & the internet & certainly no expert at diagnosing error messages. My previous response about not being overly concerned about this error message or most error messages is based on past experience. Usually patience & research pays off without going bananas & making radical changes to your system. Also the info in the Device setup manager admin. log shows that each device has been serviced, processed a task, wrote 34 properties, & gives the active worktime. This is exactly the same info this log is showing before the error messages began occurring on May 6th. This is what leads me to believe the required tasks are being performed even though metadata staging failure is occurring first. Remember, these actions all occur within milliseconds of one another.  My one concern is that the debug log never shows metadata staging jobs as complete & gives the status often as "hard error."

Hopefully, the problem is actually a MS url problem & will be resolved soon. Keep us informed.

I am still in contact with Microsoft and hope to have a fix for this malfunctioning url soon.  I cannot trace why it is not forwarding a the correct speed.  As you say it appears the metadata is refreshing but not at the speed required to stop the system generating the initial Event ID 13 'metadata staging failed'

Perhaps the task is not being given the correct, or is sitting in a queue.

I am still digging and the hole is getting bigger but no resolve in sight yet.

Im having exactly the same issue on my PC with the metadata staging failed device manager errors and this was a clean installation. Other issues I was having also were Schannel Event ID 36888 TLS Protocol Errors repeated on a daily basis. I did several reinstalls but it made no difference. As soon as I went on the internet these errors appeared in batches of three...usually between 6 and 12 of them every day!!

Thankfully now though the Schannel errors have now stopped.

I don't know what is going on at Microsoft nowadays but with Windows 8/8.1 there is constantly problems in Event Viewer.

At one time I always downloaded all Windows Updates with extremely rarely any problems but Im scared to install the Optional Updates now.

Yes, I agree with you here, I have been seeing the SChannel errors on and off for a few months and certainly could not tie it down to any errors at my end, I assumed once again it was a Microsoft issue and as I did not want to constantly look at all these TLS errors, I turned off event logging for them.  If you want to know how to do this for future reference, just reply and I will send you the guide.

I like you rarely perform any windows updates now,  they simply wreck my system and I did decided from a personal point of view that a previous IE Cumulative Security Update was responsible for generating the SChannel errors, but over a period of time, further updates would appear to have cleared this issue.

IE being the only updates I did do stopped last month when the update locked everyone out of IE Gallery and refused to allow users to change search providers amongst other issues.  No more updates for me at present. 

As for the metadata error, I have 5 systems, one of which is a clean install and rest assured they are all suffering with the event id 131 illness at present.  I am in constant contact with Microsoft regarding this issue, and I am assured they are working on it.

I will keep you all posted on my progress. 

Thanks Mazda for your feedback. I too decided that the Schannel errors were linked to the Internet Security Update. Thankfully subsequent updates seem to have sorted it.

As for the TLS errors I don't want to turn off event logging as it only masks the problem really..though I can definitely understand why you've done it yourself. I researched the problem on the net and saw someone else has done the same thing.

As for the Windows Updates becoming very unreliable..the known problem with KB3022345 is the most annoying one of late. I stopped installing optional updates as that Update was causing corruption errors in SFC scans. Then Microsoft made it an important update so it was downloaded automatically (I thought Microsoft must have sorted the problem out with KB3022345). ..the problem is now back on my system. But what are you supposed to do when Microsoft changes it to an important update..so frustrating. Windows Updates has caused me loads of problems..this never used to happen. I used to think it was very reliable.

Thanks for your response, it is always helpful to know other users are suffering the same stress and Microsoft issues and it is not me loosing my marbles!

However, if you can remember or you can still see it in your event log, I would be very interested to know when the SChannel TLS errors stopped appearing, I thought mine had gone but faced them again yesterday but I have not done any IE Cumulative updates for a few months.  I just wondered if you had an idea of the date or month and I would give the IE Update a try for that month see if it clears my SChannel errors.  If you do not have this info in memory or to hand in the log do not worry but it may assist me in getting to the bottom of the TLS 40 issue even I cannot yet fix the metadata.

Cheers

Mine was a clean Windows8/8.1 Installation done on the 10/5/2015 and the most Schannel errors Ive had in any day has been two, most days just one, and none at all for the last two days if that helps you at all. Ive installed all the IE security updates. The only Windows Updates I haven't installed on my system at the moment are 10 Optional Updates.

One  Im having particular trouble with at the moment on a daily basis is a critical error, Driver  Frameworks User mode Event ID 10110 and 10115. Its related to the Windows Location Provider. That ones got me stumped because I don't seem to be having any issues..my computer is working fine.

Event ID 10110 and 10115 I have done a little research some of it may be helpful, I am not an expert but do like to try feasible options.

Typically this event is recorded together with event id 10111 from the same source. Event id 10111 provides information about the actual device that caused this problem.                      

       It's a user-mode driver error,  that unfortunately appears often in Vista and Windows 7 as well.  Some say  update the driver,  problem solved, if you know what driver is causing the issue, do you see any yellow exclamation signs in Device manager? This may sound stupid but have you checked to ensure that the Windows Location Platform was actually activated when you did the reinstall.  This tick box can be checked or unchecked on set-up so easily. You can check it is indeed on and you can also disable it and restart it to see if it makes a difference:       Control Panel> Programmes> Programmes and Features> Turn Windows Features on or off> scroll down the list ensure you have a tick in Windows Location Platform.  If not add one and check your results.  If indeed it is already ticked, untick  thus disabling the Location Platform temporarily.  Reboot the system, check the log, go back and reinstate the tick to turn the Location platform back on.  May or may not be helpful but worth a try and doesn't do any system damage.

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~

     Let me make myself perfectly clear, I am only a casual user of computers & the internet & certainly no expert at diagnosing error messages. My previous response about not being overly concerned about this error message or most error messages is based on past experience. Usually patience & research pays off without going bananas & making radical changes to your system. Also the info in the Device setup manager admin. log shows that each device has been serviced, processed a task, wrote 34 properties, & gives the active worktime. This is exactly the same info this log is showing before the error messages began occurring on May 6th. This is what leads me to believe the required tasks are being performed even though metadata staging failure is occurring first. Remember, these actions all occur within milliseconds of one another.  My one concern is that the debug log never shows metadata staging jobs as complete & gives the status often as "hard error."

Hopefully, the problem is actually a MS url problem & will be resolved soon. Keep us informed.

Hi Rusty..as you can tell Im no expert either. Im hoping someone at Microsoft can clarify this for us and that Microsoft sorts this issue out with an update. Its always a bit concerning when you get regular repeated daily error messages like this one