Metadata staging failed event 131

Ive been getting the schannel 36888 error for about as long as you. Mine is always the SChannel 10 error. Like you the Metadata one seems to have cleared up for me too. Ive seen that fix you mention for the schannel error before but im just a bit reluctant to use it. Ive always hoped that Microsoft would sort it out eventually..but it looks like theyre not going to do that

Microsoft Windows 8  - no metadata errors logged in event viewer since October 6th.  OS was not used for a week so unsure exactly when it cleared.

Thanks amtino - you are a dedicated and determined person.

No event ID 131 metadata errors since October 4th.  I use time.windows.com.

It would appear amtinos considerable time and effort spent getting Microsoft to trace this issue has worked for some of us.   I use Windows 8.

Amtino thank you for investing such time and determination with this - I see from many forums the time you have spent trying to solve this issue.

I upgraded? to Win 10 2 months ago & have had only the occasional metadata staging error come up since then. I checked your suggestion & found that my computer was already set on the nist.gov. time. This is by no means a recommendation for Win 10, I have several new errors that are coming up now some of them daily. There is absolutely nothing new & improved that I have found on win 10, all they did was change things around, in other words cosmetic changes only, & now I have several new error messages constantly popping up.

Hi

My OS is still Windows 8  (I totally refused Windows 10 when I was offered it early as a resolution to the Metadata Staging error).  when I was in regular with contact with Microsoft requesting the fix for event ID 131 they tried their best to get me to take the trial issue promising it would fix the issue and I was not convinced).

However, on my system I have tested now for a week on the Windows-time.com and also Nist.Gov.Time

I do not have any metadata errors as yet and I am assured my Microsoft that it is fixed.

I have tried refreshing the hardware and devices page many times to try and produce the error but it remains clear.

I am sorry this is not working in windows 10. 

It appeared to correct itself on my system on 2nd October. - The only other thing I did do was Power Cycle my Router but I doubt that had anything to do with the timing issue we were facing with event ID 131.

Has anyone else seen this error go away or is it just me?

Hi Rusty.

Out of curiosity is one of the regular errors you are getting on Windows 10 the schannel 36888 error. Ive been getting this for months on both Windows 8 and Windows 8.1 when I updated ages ago.. It seems to be a common one that Ive never been able to fix. I get more than 10 of those every day without fail as soon as I go on the internet

Hi

I have been getting the SChannel errors since July 2014 - No updates have ever cured this issue.

The metadata error has now been fixed and I have also changed my time server as mentioned above.

I did get them everyday - mainly SChannel 10 - which is a bad handshake!  according to Microsoft.

I also occasionly saw SChannel error 40 - not sure what this one is.

They all log under 36888.

Now that the metadata event has finally gone and the event viewer is virtually clean I have given up on the SChannel error and turned logging off for the event:

Regedit:

HKEY - Local Machine

SYSTEM

Current Control Set

Control

Security Providers - long way down the list

SCHANNEL

click on Event logging and modify the 1 to 0

No more 'visible' SChannel errors

Hope this helps