This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
my computer runs fine but i keep getting this error and i have no idea how to fix. i never had this error until i turn on my machine today. i have not installed anything new programs nor uninstalled anything and i only see that my comp installed updates to the windows defender and that's pretty much it
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I can reliably produce Event ID 131 when attempting to establish a Miracast session with my Surface Pro 3 and a Microsoft Wireless Display Adapter. The connection fails. The SP3 is fully updated. The MWDA has the latest firmware update.
Strangely enough, it only happens when the MWDA is connected to an native HD device. When it is connected to a low-res projector (1280x1024), it connects fine. My Lumia 830 connects to the MWDA with no problems regardless of what it is connected to.
Thanks for the heads up on how to trace a device by using a GUID. Have you heard anything new about the metadata error situation? I had hopes MS was actually fixing it because for the past two days I have had errors for one device only, but then I refreshed the Printers folder & three more errors showed up for three other devices , so I guess they are still not making any headway.
No news yet, last I heard, Microsoft were stil trying to establish the route course. Ithink we have a long wait ahead.
Thanks for the heads up on how to trace a device by using a GUID. Have you heard anything new about the metadata error situation? I had hopes MS was actually fixing it because for the past two days I have had errors for one device only, but then I refreshed the Printers folder & three more errors showed up for three other devices , so I guess they are still not making any headway.
I have found automatic maintenance to be totally unreliable. It will say that it has run & the time it ran, but when I check Maintenance Configurator or Regular Maintenance, more often than not Regular Maintenance has not run & I have to run it manually. This has been going on for several months now. Like I said previously, this is how I know for certain that Regular Maintenance is the trigger for these Metadata
staging errors. MS just sent 13 important or recommended updates yesterday, but still no fix for this problem.
Can you tell me is there a simple way to trace an app or device from a known GUID? An answer from anyone on this would be appreciated.
Hi, thanks for confirming you also see issues with the Microsoft Maintenance.
With reference to tracing a device or app - copy the GUID without { } just the numbers and letters, open registry editor, on the menu bar click edit, click find, paste or type your GUID and this should locate what you are looking for or give you some clues. If not get back to me, there are other ways but not quite as quick.
I have found automatic maintenance to be totally unreliable. It will say that it has run & the time it ran, but when I check Maintenance Configurator or Regular Maintenance, more often than not Regular Maintenance has not run & I have to run it manually. This has been going on for several months now. Like I said previously, this is how I know for certain that Regular Maintenance is the trigger for these Metadata
staging errors. MS just sent 13 important or recommended updates yesterday, but still no fix for this problem.
Can you tell me is there a simple way to trace an app or device from a known GUID? An answer from anyone on this would be appreciated.
