Metadata staging failed event 131

Sorry it took so long to reply, but I ran into the lovely issue of opening my Mail App, and it would closed in matter of seconds. Then found other Apps not working.

I then tried to go to Hotmail through IE, Edge, and Chrome, and I couldn't get logged in.

My Devices are getting updated. So, like Rusty-45 said, it's probably just I'm not getting connected in a timely manner.

Also, this is not a server. It is a Tower Desktop. I'm running Win10 Pro updated from Win7 Ultimate. And I have VMware Workstation running on it, as I have to research issues on different OS connecting to Dell Disk Storage, and EMC.

I Work for Dell as a L3/ Senior Engineer for Disk Storage System, Equal Logic, EMC, and Brocade Fiber Channel Switches.

I have a feeling that my Win7 had too many hidden issues, and when Win10 updated it, it just kept the bad.

I'm almost to the point just to blow a new Win10 image on, and re-install all my programs. I just hate to have to go through that, again. I had to restore Win7 from backup last year, and it took like 3 weeks, 16hrs a day, to get it back.

I'm flabbergasted. That fix has always worked for me & continues to work. The problem it fixes comes & goes & has been doing so over years. It's a matter of MS's server getting slow. I'm thinking - looking at your Event Viewer - that your computer is itself a server. Maybe that puts a further stress on the situation so that neither URL will work.

But I think Rusty-45 is correct that the devices do get serviced. It's just that you must have extra junk lines in Event Viewer. That is, unless - as I saw in one thread - you have Event Viewer simply not record the event. Can you find that?

Yes, the metadata staging errors are a timing issue & nothing to get too excited about.. I stated this in my posts of May 26 & May 29. If you will check your device manager setup administration log you will probably see that each device is being properly serviced, etc. which is exactly the same info you were probably getting before the errors started. Once again remember, these actions are taking place within milliseconds of one another.

As you can see I have change it, and still getting the errors:

I found people on social TechNet with the same issues. One person has found it appears to be a timing issue to the url. Reading the posts, it looks to be, it started around May 6 2015.

If it is indeed a timing issue, I wonder if it's because the url is getting slammed by all the PCs, Servers, running MS, that it is getting over utilized. Causing the url to reject some, but allowing others to connect.

Reason I feel the issue could be a timing problem is because I'm a Senior Engineer L3, for Dell Disk Storage systems. On our mid range, to large, systems we have found issues with iSCSI timeouts with VMware, and others. Their support personal will say the Default is fine, but it is set to 5 secs. Once we change the TO settings to 60 secs, then the Disconnects stop. We still are trying to find out what Storage system is ok with a 5 sec TO value. Maybe a Direct Connect System, a.k.a. DAS. But I'm not convinced that would be enough time...

The registry fix does indeed work in Win 10. Here is what the full key looks like...

...Set like that, the Administrative error 131 goes away. The badURL is the same in Win 10 as it was in Win 8.1:  http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

I don't know whether there is something about originating from Win 7 that changes the pretty picture.