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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-06-04T12:46:38+00:00

    Have checked in registry Windows 7 and there is other DeviceMetadataServiceURL than in Windows 8.1 :  go.microsoft.com/fwlink/?LinkID=109572&clcid=0x409

    (in Window 8.1 there is 252669 ).

    Fiddler is showing that the redirect does occur (in contrast to the (Aborted) that the IE Developer Tools, Network capture sees).  So (probably) in both cases a 400 response is coming from

    http://dmd.metaservices.microsoft.com/dms/metadata.svc 

    So, again, if anyone knows what parameters that host uses they could use that as their workaround.  Evidently the Go site is figuring out where to redirect to which makes the proposed registry override unnecessary.  The problem is that either the client code is not transmitting enough or appropriately coded information with its requests (my guess) or the Go site has suddenly been made unhelpful by preventing such information to pass through it to the target host.

    FYI

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-06-04T12:19:06+00:00

     Prevent Device Metadata from Network - Binary Value does it read 0 or 1?

    Zero.  So are you going to try using 1 (to actually prevent the request?)   <eg>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-04T09:16:53+00:00

    Hi,

    Thank you very much for your information and updates.

    Today when opened my laptop /Windows 8.1/ have found again the same errors in the Event Viewer.

    Moreover - in the Control Panel when opened Devices and Printers  such errors have been repeated

    in the Event Viewer as well.

    Hope this issue wil be solved soon.

    Best regards,

    Ewa

    I am still looking at this naturally and just out of interest I have spotted some different values in the registry here on some of my machines:

    If any of you get a moment can you look at the following and tell me value Binar Value you see - ie. what is the default value 0 or 1?

    Thanks so much

    HKEY LOCAL MACHINE

    SOFTWARE

    MICROSOFT

    WINDOWS

    CURRENT VERSION

    DEVICE METADATA

    Next to last item in tree:  Prevent Device Metadata from Network - Binary Value does it read 0 or 1?  If have conflicting issues here and someone with an unamended registry can perhaps tell me the default value please?

    Cheers

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-02T18:08:59+00:00

    This will resolve your issue but modifying the registry is merely a temporary fix which hides the real issue of the malfunctioning url on the Microsoft server.  ...

    Thanks Mazda700, I undertand the issue. I'll stay tuned to this thread waiting for a real solution.

    ciao, fabio

    Was this answer helpful?

    0 comments