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
    2014-09-14T16:46:53+00:00

    I was thinking that folder and file was probably created by the Logitech  wireless keyboard/mouse usb transceiver - when I first plugged it in  to initially auto-download its little program and to do its routine checks for updates.    I had just never noticed it before maybe.

    Those two events are same exact two it had, no others ... but it quit after I deleted the LocaleMetaData folders.   Even at boot,  the event errors didn't show up after I had initially thought I had fixed it... until you asked me to manually run the task .. .then they showed up for first time in a while,, and show up at every restart.

     I made a custom view for event 131 for that picture I uploaded of the event viewer..    They showed up on the 12th,, just like you said.   Had never seen those errors numbers before then.

    fwiw  - I just now made a recimg    CustomRefreshImage.wim and Refreshed windows,  and they are not showing up again right now on restarts.    Some things the recimg will quickly fix for me ,, some things every now and then though, will carry over.

    ... next time maintenance runs, they might start showing up again at login ??   But I'm hoping not before you figure out the fix :)  hah

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-14T14:58:49+00:00

    The LocaleMetaData seem to be the folders for saved Event Viewer entries (http://forums.holdemmanager.com/general-support/395021-localemetadata-folder-desktop.html, http://technet.microsoft.com/en-us/library/cc749339.aspx). It is possible that they were created when some program or any user on your laptop that might have had saved contents of Event Viewer (and if OneDrive is set to be your default save location, it might have been placed there).

    When you would go to Event Viewer -> Applications and Services Logs ->Microsoft -> Windows -> DeviceSetupManager -> Admin, do you have more device GUIDs with errors on September 12 but now you only have two (00000000-0000-0000-FFFF-FFFFFFFFFFFF, 8D44F423-E670-11E3-8250-806E6F6E6963)? Or did you always have errors regarding those two?

    In my case the GUIDs are always the same (7 in total).

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-14T13:07:46+00:00

    Thanks.

    Its the Logitech wireless mouse/keyboard   usb wireless transceiver/adapter,   plus a whole list off almost everything for the fffff error    I searched the registry.

    I stopped the constant running of the error messages by deleting folders,  which had a slight trick to be able to do it.   OneDrive originally alerted me it couldn't sync the folder.  I wondered whom added the folder for something to do with tcpip.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-14T12:49:24+00:00

    Thank you. I believe you are also affected (though you do have less errors).

    The "00000000-0000-0000-FFFF-FFFFFFFFFFFF" is probably the ID of your laptop (as a whole computer). I have the same error, too.

    The "8D44F423-E670-11E3-8250-806E6F6E6963" is probably one of your devices. You can go to Event Viewer -> Applications and Services Logs ->Microsoft -> Windows -> DeviceSetupManager -> Admin and check an Information entry that appears right after an Error entry for a given device GUID. This should provide the device name.

    Was this answer helpful?

    0 comments