Multiple errors in Event Viewer: EventID 131 from DeviceSetupManager since September 12, 2014

Anonymous
2014-09-14T08:35:45+00:00

Hello,

Since September 12, 2014 I receive multple errors in Event Viewer from DeviceSetupManager.

Sample error looks like this:

Metadata staging failed, result={E9031C57-C25D-8227-E390-3662BD05D0CB} for container '0x80070490'

This error occurs when the Metadata Refresh in \Microsoft\Windows\Device Setup scheduled task is run or when accessing Control Panel -> Devices and Printers when Device Installation Settings are set to "Recommended" or are set to "Automatically get the device app and info provided by your device manufacturer".

What I believe happens is Windows attempts to contact a Microsoft web server to obtain additional information about a device (custom icon for example) and this process had started to fail for me since September 12, 2014. More details on it can be found on this page.

Looking at the Debug logs of Microsoft-Windows-DeviceSetupManager I can see the following error:

Job (13) has completed for device container '{3c7878f1-bc70-523d-b17c-7aaf5253f81a}', status=Hard Error

Looking at the network traffic, I can see communication using HTTP protocol with Microsoft server which returns HTTP 301 (page has been moved).

SFC /scannow returns no errors. All the latest Windows Updates are installed. I've already tried to remove %PROGRAMDATA%\Microsoft\Windows\DeviceMetadataCache folder to no avail.

Does anybody else see this error message and what can I do to fix the problem?

Windows for home | Previous Windows versions | Performance and system failures

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.

0 comments
Answer accepted by question author
Anonymous
2014-09-19T22:34:49+00:00

I just checked ... seems the original url works fine now.     Thanks Emkay1001 !

Was this answer helpful?

0 comments

139 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-06-27T13:54:59+00:00

    I started getting those 131 events again.

    Network Location Awareness  service was default AutoStart .. changed to delayed.  

    Seems to have stopped it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-06-27T06:59:50+00:00

    I seem to get these event 131 error logs for multiple devices (keyboard, XPS Document Writer, external HDD, USB flash) and it all started on May the 11th.

    So is this not a fault at my end?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-10T21:59:04+00:00

    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?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-06T23:09:18+00:00

    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.

    Was this answer helpful?

    0 comments