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.

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.

Apparently the metadata staging errors are nothing to get too concerned about. You can view the device setup manager logs & see that even though the staging failed the first time it must be succeeding eventually, because the next info line after every error gives the name of the device & that it was successful. To view the logs go to event viewer, app. & services log, Microsoft, Windows, device setup manager, admin. or operational log.

Hi Rusty,

Ive checked my event viewer as you instructed above. Does the Information entry that appears straight after the error indicate that eventually it was successful. I looked for the word success or successful but it isn't stated. The following Information entry usually lists a Device that has been serviced or processed showing exactly the same time as the error..does that mean it was successful?

Thanks

Hi Rusty,

I too have checked the logs as you indicated and 'metadata staging 'is most certainly not functioning correctly on my system. 

Go to control Panel - select Hardware and Sound - select Devices and printers - now right click on a blank space anywhere on the device page and select 'refresh'  if as you say your task is eventually fulfilling itself this will not generate an error.  If, as it is on my system on other users, the metadata url is still malfunctioning you will see event is 131 'metadata staging failed' in your event log following the refresh of the hardware.

The url that is malfunctioning is a forwarding link to the Microsoft Server to update Hardware and devices data, drivers, icons etc and this link is breaking down somewhere between the users operating systems and the Microsoft Server.

Microsoft have said ' this is a major concern for them at present'  they have assured me they are still trying to locate the error and will keep me informed.

Let us know if you can refresh your hardware without errors?

Apparently the metadata staging errors are nothing to get too concerned about. You can view the device setup manager logs & see that even though the staging failed the first time it must be succeeding eventually, because the next info line after every error gives the name of the device & that it was successful. To view the logs go to event viewer, app. & services log, Microsoft, Windows, device setup manager, admin. or operational log.

Hi Rusty,

Ive checked my event viewer as you instructed above. Does the Information entry that appears straight after the error indicate that eventually it was successful. I looked for the word success or successful but it isn't stated. The following Information entry usually lists a Device that has been serviced or processed showing exactly the same time as the error..does that mean it was successful?

Thanks

Apparently the metadata staging errors are nothing to get too concerned about. You can view the device setup manager logs & see that even though the staging failed the first time it must be succeeding eventually, because the next info line after every error gives the name of the device & that it was successful. To view the logs go to event viewer, app. & services log, Microsoft, Windows, device setup manager, admin. or operational log.