Metadata staging failed event 131

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

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.

A new resolution to the issue without changing the url in the registry or touching anything we shouldn't really:

Click on time and date at bottom right of screen.

select Internet time

change the server in the drop down list from windows time to nist.gov.   Update the time.

Your system should now be error free:  I have tested this by refreshing all hardware devices etc.  all OK.

The nist.gov time server is obviously correct to the millisecond and the window time server is not!

AM

amtino        replied on        

For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.

I was searching for information about it, and ran across this thread.

For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.

I was searching for information about it, and ran across this thread.

I just knew this would happen.  I worked closely with Microsoft Level 3 support for six weeks from May onwards trying to get them to fix this issue.  They assured me they were acknowledging this as a serious issue.  After six weeks they recommended I wait for Windows 10 and all would be well.

I refused the upgrade, I knew it would not resolve, all versions of Windows connect to the Microsoft server and they did acknowledge it was a server issue.

I am going to get back to them know and suggest that once again they look for a fix.

Cheers

My latest contact with Microsoft was to address  issues some users have seen with the automatic maintenance that should automatically run on all systems at 3am  and a lot of us see the message ' the operator or Administrator prevented the task from running and a code' I cannot quote the exact message without trawling through my screen.

However, that is  by the by, what I was trying to tell Microsoft was that the error code generated at 3am seemed to also have effects on producing the event id 131 - I genuinely feel there is a connection.

The response I got was that maintenance tasks will not run on battery power, if I leave my laptop on battery power overnight, maintenance tasks will fail.  I have tested this by leaving 2 Laptops connected to the A C power overnight and guess what - the maintenance tasks still do not run and event id 131 appears in the log on opening up next morning.

I was offered a free upgrade to Windows 10 to 'resolve all my concerns and issues'  I am not interested.  I am interested to know that 2 users have already informed me Windows 10 has the same server issues.

Perhaps..... when windows 10 goes live and all the users see the event log looking like a war zone, Microsoft will finally get lots more complaints and get down to resolving this issue on their server.  I am not giving up on this one, like you say, this is not hardware/user related it is clearly am issue with Microsoft Servers.