Continues Errors at startup "Metadata staging failed"

[ChrisPWQ]

The tasks do complete but not fast enough therefore generating the error a millisecond before the task does complete. This has happened twice in a year, Microsoft fixed it in September 2014 but now seem reluctant to do anything positive.

I really wonder sometimes about how people view solving problems like this. Why Microsoft didn't just bump up the timeout by a little bit is beyond me.

 

[maxoptimus]

The tasks do complete but not fast enough therefore generating the error a millisecond before the task does complete. This has happened twice in a year, Microsoft fixed it in September 2014 but now seem reluctant to do anything positive.

I really wonder sometimes about how people view solving problems like this. Why Microsoft didn't just bump up the timeout by a little bit is beyond me.

about timing it can be your ISP provider issues (i.e. bad internet connection on your side)
but it's event ids 121 123 etc
we discused 131 issue, somewhere on ms answers dicribed: it's appears when msserver redirect to other ms server url but it's blocked by ms in windows design;
I have changed url and do reinstall of few old drivers in compadibility mode and cleanup hidden unused items from device manager and none of 131 few months... (see my prev post...)

 

[hbordon727]

Hi everyone! I have managed to get rid of error 131 and the 200,201,202,203 warnings in Windows 10 without using the url change trick that everyone keeps talking about!! I have 2 computers at home which are now fixed! All I did was go into the time and date settings and changed the Internet time server from the default windows to the second one available called nist. Something (sorry I can't remember the exact name) anyways please try for your selfs and report back... =)

 

[hbordon727]

If anyone needs better instructions please let me know =)

 

[hbordon727]

I also went into control panel and hardware to try to reproduce error 131 and all is good!

 

[Saltgrass]

I will keep an eye on mine before making your change. I have not had the error since 10/2...

 

[amtino]

I will keep an eye on mine before making your change. I have not had the error since 10/2...

I have changed the time server and all is well. So now we have a further resolution - Thank you hborden727 for sharing this with us.
Did you have any particular updates or changes on 10/2 when yours went away?

 

[jds63]

I have not done anything and my metadata failed in Event Viewer seems to have gone away now with Windows 10.

 

[amtino]

I have not done anything and my metadata failed in Event Viewer seems to have gone away now with Windows 10.

Thanks for keeping us updated:

I have been running on the nist.gov time server for 24 hours with no errors - tonight I reverted back to the original url and windows time server and again, no errors.

It would appear the issue 'may have' been fixed. I will keep an eye on it for the net few days. I am guessing this is very recent as I have been checking the url at least once a week and last week it was still producing event ID 131.

Fingers crossed .......

 

[hbordon727]

Hi guys and girls! So I did some more research on this error 131.. If i go back to the original windows time server the error is back... So the trick is to stay on the more reliable nist. Time server... Think about this for a second, every single pc sold comes with Windows. Time server as default so the server is going to be slower to react! So nist is the answer! You guys can and should switch back to the default url just in case you don't create an unknown issue further down the line and use the more reliable atomic nist server from the government =) ps:Amtino you are truly amazing, I have been watching you on here for a while and you are truly smart and amazing!

 

[amtino]

Hi guys and girls! So I did some more research on this error 131.. If i go back to the original windows time server the error is back... So the trick is to stay on the more reliable nist. Time server... Think about this for a second, every single pc sold comes with Windows. Time server as default so the server is going to be slower to react! So nist is the answer! You guys can and should switch back to the default url just in case you don't create an unknown issue further down the line and use the more reliable atomic nist server from the government =) ps:Amtino you are truly amazing, I have been watching you on here for a while and you are truly smart and amazing!

Thank you so much for your kind comments, it is appreciated.

I am testing at present as follows:

reverted back to Windows Time Server
reverted back to the correct url in the registry

I have no errors at present and if I refresh the Hardware and Devices Page - no errors.

My OS is Windows 8 - IE10

I will keep the page updated with any findings.

As you know 'anything can happen'

 

[jds63]

I have not done anything and my metadata failed in Event Viewer seems to have gone away now with Windows 10.

Thanks for keeping us updated:

I have been running on the nist.gov time server for 24 hours with no errors - tonight I reverted back to the original url and windows time server and again, no errors.

It would appear the issue 'may have' been fixed. I will keep an eye on it for the net few days. I am guessing this is very recent as I have been checking the url at least once a week and last week it was still producing event ID 131.

Fingers crossed .......

Your welcome, i checked again today still no ID 131. Now if i can figure some of others i get,some are warnings, few errors, too long to list or know what they mean, but i do believe it has nothing to do with this thread.

 

[amtino]

Just to let you all know as promised - I have finally, after many months, received confirmation from Microsoft that all issues with the timeserver and Event ID 131 have now been resolved:

I have reverted back to the correct url in the registry:

I have tested this on 2 systems for 5 days:
I have used both the windows and nist time servers as some members felt the nist.gov time server was a resolution.


I have been unable to reproduce the Metadata Staging error with either server.

I have refreshed the hardware and devices page manually several times and booted and rebooted the systems several times per day.

I am happy at my end that the issue is resolved for now.

I am sorry it took so long.


I have received comments via another forum that it is not fixed for Windows 10 users, sorry but I do not know why this should be the case.

 

[RonnieJP]

Just to let you all know as promised - I have finally, after many months, received confirmation from Microsoft that all issues with the timeserver and Event ID 131 have now been resolved
I have received comments via another forum that it is not fixed for Windows 10 users, sorry but I do not know why this should be the case.

Sorry I shortened your quoted post Amtino, but I just wanted to ask your opinion. I had this issue on Windows 8.1 and replaced the original registry URL with the "corrected" one. When I upgraded to Windows 10, it changed the registry URL back to the original and I got the 131 errors. So I changed the URL and it's been working fine and I never looked back. so I haven't taken the time to go back to the original URL to test it. Do you think there's any harm in using the "new" URL going forward?

 

[amtino]

Just to let you all know as promised - I have finally, after many months, received confirmation from Microsoft that all issues with the timeserver and Event ID 131 have now been resolved
I have received comments via another forum that it is not fixed for Windows 10 users, sorry but I do not know why this should be the case.

Sorry I shortened your quoted post Amtino, but I just wanted to ask your opinion. I had this issue on Windows 8.1 and replaced the original registry URL with the "corrected" one. When I upgraded to Windows 10, it changed the registry URL back to the original and I got the 131 errors. So I changed the URL and it's been working fine and I never looked back. so I haven't taken the time to go back to the original URL to test it. Do you think there's any harm in using the "new" URL going forward?

No not at all - all that happens here is that you are using the direct url to connect to the Microsoft Server as apposed to using the original url which is a forwarding link connecting to the same server.

Both 'should' work. Our issue was the original forwarding url was failing. As of today it is working.

You should not see Error 131 with either url.

 

[gator2013]

Just to let you all know as promised - I have finally, after many months, received confirmation from Microsoft that all issues with the timeserver and Event ID 131 have now been resolved:

I have reverted back to the correct url in the registry:

I have tested this on 2 systems for 5 days:
I have used both the windows and nist time servers as some members felt the nist.gov time server was a resolution.


I have been unable to reproduce the Metadata Staging error with either server.

I have refreshed the hardware and devices page manually several times and booted and rebooted the systems several times per day.

I am happy at my end that the issue is resolved for now.

I am sorry it took so long.


I have received comments via another forum that it is not fixed for Windows 10 users, sorry but I do not know why this should be the case.

Thanks for the update.

I have reverted to the original MS metadata link on 2 PC's and everything is working as it should. I appreciate your follow-through.

I wonder how long this will last

 

[amtino]

Not long!!!!!

The Metadata error returned on all 3 of my systems at 1am this morning during scheduled maintenance.

I cannot get the forwarding url to work either at present but will keep you posted.

Total mess.......

PS..... just got the forwarding url to work. I don't think I am ever going to change it back to the original registry key again, it is too unreliable.

 

[gator2013]

The Metadata error returned on all 3 of my systems at 1am this morning during scheduled maintenance.

I cannot get the forwarding url to work either at present but will keep you posted.

Total mess.......

PS..... just got the forwarding url to work. I don't think I am ever going to change it back to the original registry key again, it is too unreliable.

Same here. Just a few hours ago a restart on one of my PC's took a little longer than normal and looking at the Event Log the errors had returned. I have successfully returned to the alternate address (Sammy's original fix). I have lost all trust in MS in regards to their methods for advancing their business plan.

 

[maxoptimus]

can't see 131 but have few 123 timeout during 30 sec for some usb, etc devices.... (time sync still off, original URL)

 

[amtino]

Alternative url now working

Yes I now have Sammys alternate URL Working but not the original.

I tried a few times refreshing 'hardware and devices' before I could convince myself this error had come back so quickly. Less than one month.

According to Microsoft they fixed it on 2nd October following my 6 month consultation with them, disgusting.

Clever how they fixed a timing issue just before 'daylight saving' and then after 'daylight saving' it goes back again.

Perhaps they didn't want their own systems going wrong.

I for one will not put the correct url back again. I feel I have learnt my lesson now.

Apple Mac here I come.