Continues Errors at startup "Metadata staging failed"

[doan]

I've been lurking in this thread, I just joined so I can participate,

I have ONE system that is doing this. 8.1 enterprise fully updated. Mine started with the symptom that disk management would take forever (20-30 seconds) to load. Also other programs or functions such as TreeSize that are looking for all the storage devices would hang or respond slowly. The fix I read in this thread of turning off driver updates helped a lot, but it was still slow compared to other machines.

Then while rebooting, I saw the old PATA controller stating that it found no drives (because there are no PATA devices). So I rebooted again and turned off the PATA and floppy controllers. This makes sense since I had updated the bios prior to this issue. All the delays want away after that.

Turning windows driver updates back on slows it down a little. For now i'm leaving it off. When updates are on I still get the 131 error whenever devices are refreshed.

I hope this helps someone....

 

[amtino]

Mine also shows 0 and DeviceMetaDataServiceURL http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Thanks very much - I now have all of them reading 0 - not that is has resolved anything but at least I know they are correct.

 

[gator2013]

Mine also shows 0 and DeviceMetaDataServiceURL http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Thanks very much - I now have all of them reading 0 - not that is has resolved anything but at least I know they are correct.

I am still following this thread daily. Been running both my machines with the substitute link for weeks now with no errors and no obvious or strange behavior of any kind. I cannot find a way to generate the errors with the substitute link even by refreshing the Device/Printer page. Every couple days or so I revert back to the stock link with no joy. Don't know what implications there might be staying with the substitute link if any. I am planning on upgrading one of my machines to W10 as soon as it's available while leaving my desktop with W8.1 so I can see what effects all this might have with the upgrade.

BTW, That value is 0 on both my machines with the substitute link installed

Thanks for all your efforts.

 

[jds63]

Mine also shows 0 and DeviceMetaDataServiceURL http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Thanks very much - I now have all of them reading 0 - not that is has resolved anything but at least I know they are correct.

Most welcome, wishing for a resolve, thank Amtino !

 

[amtino]

Still hoping for a fix

I have not heard from Microsoft today but hope to hear something next week.

I have experimented like other users, using the substitute url, turning off hardware and device updates.

The substitute url is the only temporary fix that will leave the event log 'tidy'.

Turning off the update feature and stopping the task from running does not work for me.

I also tried changing the options and selecting ' never use windows update'. This filled the event log with large numbers of warnings instead: Windows update is blocked by policy - The Network List Manager reports no connectivity. A connections to Windows Update could not be established.


None of these are ideal but are workarounds for now.

I am currently looking into the relationship between Windows Update Agent, Device Set-up Manager and also Bonjour.

I note in Services that Bonjour specifically is used by Task Scheduler and also for updating Devices. Metadata also uses the Windows Update Agent.

Could this be a windows Update Agent generated error? or could Bonjour be involved somewhere? The plot thickens a little but I think it is worth looking at.

I do recall (but it is no longer visible in my log) shortly after daylight saving at the end of March I had this odd event in the log from Bonjour to the effect that it had rolled back some so many millions ticks? Can anyone else recall seeing an error of this nature shortly after daylight saving. There may or may not be a link. We do know it is some kind of timing issue.

 

[jds63]

Your digging deep Amtino ! For one if i am correct not a great loss until corrected to loose ability to update other devices by disabling hardware and device updates as seemed be best solution for now if people want to rid the errors in Event Viewer. I feel i update my own devices through manufacturer's websites and even use Intel update utility which they rarely have updates lately. Again i am not positive what other updates i may not be able to get on my own by needing Windows update to do it for me in meantime.

Just a thought, because these erros are not causing any system problems or BSOD. I do admire your dedication and yes this needs to be fixed, even soon looking at upgrade to Windows 10 which i feel may still have this issue, who knows. Thank you !!

 

[amtino]

No News yet

I have no news of a fix yet, do not know if anyone else has had a response. I have noticed that the planned maintenance at 3am does not appear to be functioning either. Has anyone else noticed this?

Search. Scheduled Tasks
Scroll down to active tasks - Scheduled Maintenance

For the 3am scheduled maintenance - I see ' The Operator or Administrator has refused the request'

Anyone else seeing this?

 

[jds63]

Wish i can say yes, but i never contacted MS. I do have this message in Task Scheduler

At 2 am every day 6/10/2015, next one on 6/11/2015. The Operator or Administator has refused the request (0x800710e0)

As for Metadata failed, i receive about 2 a day.

 

[hbordon727]

****crossing my fingers**** that windows 10 will not have this issue... event 131 error plus warning 200,201,202 (all metadata related) are driving me nuts... my computer used to boot up wih no errors or warnings before this thing... microsoft please fix it... if i knew right now that windows 10 didnt have this problem then i wouldnt care that much because windows 10 is right around the corner.. (offcourse we will instead be battling other new errors lol) ... never ending

 

[Sayjimwoo]

Just to add to the thread. After formatting W8.1 I am also receiving errors 131, 200, 201, 202. I rid myself of the 131 error by using the temp url in regedit suggested earlier in the thread (until Microsoft find a fix).
For the 200, 201 and 202 errors, I removed them by going into Services and changing the "Windows Driver Foundation" service to Automatic.
Rebooted several times to test and I am completely error free

 

[jds63]

Just a band-aid for now. If keep system and hardware drivers up to date from your manufacturer site you should be o.k. for now.

 

[Sayjimwoo]

Just a band-aid for now. If keep system and hardware drivers up to date from your manufacturer site you should be o.k. for now.

I never let windows install drivers anyway, I find they just cause problems. I always install them myself

 

[jds63]

Just a band-aid for now. If keep system and hardware drivers up to date from your manufacturer site you should be o.k. for now.

I never let windows install drivers anyway, I find they just cause problems. I always install them myself

True, comes to certain one for system sometimes hard to find and know have correct ones, example... Intel updates if not on manufacturer sites. Like my Intel management engine interface driver not on manufacturer site, but from windows update was genuine and worked with no issues.

 

[Sayjimwoo]

Just a band-aid for now. If keep system and hardware drivers up to date from your manufacturer site you should be o.k. for now.

I never let windows install drivers anyway, I find they just cause problems. I always install them myself

True, comes to certain one for system sometimes hard to find and know have correct ones, example... Intel updates if not on manufacturer sites. Like my Intel management engine interface driver not on manufacturer site, but from windows update was genuine and worked with no issues.

Yeah Windows always installs the MEI drivers for me even though I have an alternative one from the manufacturers website. The one Windows installs seems okay though and I have not had any issues. I normally have to install my own MEI drivers darn quick before windows does.

I install my Razer Synapse drivers myself but after the initial reboot shortly after formatting, Windows insists on installing it's own Razer drivers again so I have to manually quit it.
Sometimes the Nvidia drivers are older versions, it also installs ALL the Nvidia software (I prefer to choose my own and untick the 3D stuff and Geforce experience)

Anyway, enough was enough so I disabled all windows permissions, although there are a couple of things that do get overridden - I always turn off Restore and it randomly enables itself about 4-5 times till it eventually stays off. Secondly, I am not part of a homegroup nor do I share files on a network etc and I ensure it is all disabled, eventually, the file sharing turns itself on, I first notice because I have event viewer errors of printer drivers failing to install (due to my wife's wireless printer trying to install onto my pc). I then have to turn fill sharing off AGAIN.

Why windows gives you these options but overrides them as soon as your back is turned I do not know.
Sorry for going slightly off topic

 

[jds63]

I never let windows install drivers anyway, I find they just cause problems. I always install them myself

True, comes to certain one for system sometimes hard to find and know have correct ones, example... Intel updates if not on manufacturer sites. Like my Intel management engine interface driver not on manufacturer site, but from windows update was genuine and worked with no issues.

Yeah Windows always installs the MEI drivers for me even though I have an alternative one from the manufacturers website. The one Windows installs seems okay though and I have not had any issues. I normally have to install my own MEI drivers darn quick before windows does.

I install my Razer Synapse drivers myself but after the initial reboot shortly after formatting, Windows insists on installing it's own Razer drivers again so I have to manually quit it.
Sometimes the Nvidia drivers are older versions, it also installs ALL the Nvidia software (I prefer to choose my own and untick the 3D stuff and Geforce experience)

Anyway, enough was enough so I disabled all windows permissions, although there are a couple of things that do get overridden - I always turn off Restore and it randomly enables itself about 4-5 times till it eventually stays off. Secondly, I am not part of a homegroup nor do I share files on a network etc and I ensure it is all disabled, eventually, the file sharing turns itself on, I first notice because I have event viewer errors of printer drivers failing to install (due to my wife's wireless printer trying to install onto my pc). I then have to turn fill sharing off AGAIN.

Why windows gives you these options but overrides them as soon as your back is turned I do not know.
Sorry for going slightly off topic

No, quite o.k., all has to do with same ideas of metadata reasoning. Not a great idea turn off system restore unless using a program to make backup images of the drives. Intel MEI on my manufacturer's site still tends be older then one windows put in and is Signed driver from windows update. Well, printers, mouse and others are examples of ones can do yourself and are better off as i do the same with those too. Of course is main reasons for service failing in question, to update other drivers.

 

[amtino]

Still no fix

Hi
I have been away for 2 weeks and I had hoped to see a fix on my return. I will contact Microsoft for an update as soon as I can.

Thank you

 

[jds63]

Thanks Amtino, true have not seen any replies here in weeks. I only have been getting 1 Metadata failed lately, but receive this one a few times, believe it is related in someway.

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 6/29/2015 4:58:04 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User:
Computer:
Description:
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-06-29T20:58:04.395500300Z" />
<EventRecordID>3631</EventRecordID>
<Correlation />
<Execution ProcessID="820" ThreadID="4512" />
<Channel>System</Channel>
<Computer>DS</Computer>
<Security UserID="S-1-5-21-529135684-1407376196-145692821-1001" />
</System>
<EventData>
<Data Name="param1">{1B1F472E-3221-4826-97DB-2C2324D389AE}</Data>
</EventData>
</Event>

 

[gator2013]

Hi
I have been away for 2 weeks and I had hoped to see a fix on my return. I will contact Microsoft for an update as soon as I can.

Thank you

I continue to use the alternate link on 2 systems without any errors. I have not forgotten about it but I don't really think about very much. Personally, with W-10 coming out very soon I don't think MS is going to fix this and it is not impossible that this is all related in some way to the release of W-10. It has been well established that updates of all types are going to be delivered differently with W-10 which makes me tend to believe that this might all be irrelevant once you move to w-10. I will be shocked and disappointed if I find this bug still exists after the transition to W-10.

 

[amtino]

Hi
I have been away for 2 weeks and I had hoped to see a fix on my return. I will contact Microsoft for an update as soon as I can.

Thank you

I continue to use the alternate link on 2 systems without any errors. I have not forgotten about it but I don't really think about very much. Personally, with W-10 coming out very soon I don't think MS is going to fix this and it is not impossible that this is all related in some way to the release of W-10. It has been well established that updates of all types are going to be delivered differently with W-10 which makes me tend to believe that this might all be irrelevant once you move to w-10. I will be shocked and disappointed if I find this bug still exists after the transition to W-10.

I hate to burst anyones bubble, but I have had confirmation from Microsoft and other users that windows 10 uses the same servers and same forwarding url and the beta version is currently facing the same issues we are: Link from my other forum: I am still trying to liaise with Microsoft for a fix - I shall persist

Multiple errors in Event Viewer: EventID 131 from - Microsoft Community

 

[jds63]

Lots to read, thanks for update ! Kind of figured this would be still an issue in Win 10, we will wait and see,TY

Just received this optional update other day wondered if i needed it because stating for corporate use, just strikes me as seems similar to issues here in someways https://support.microsoft.com/en-us/kb/3065988