Event ID 131 DeviceSetupManager Metadata staging failed, result=0x80070490 for container '{672872FE-8762-45FD-BF0C-F1AA77328FF1}'

B

bswhipp

Member
Joined
Dec 4, 2024
Messages
194
This happens with others where the result is the same but the containers are:
'{6BFB43B0-3A52-11EC-B8DA-00155D02B30B}'
'{7F84558C-5F7F-548E-9B12-DE35E0EFD7CA}'
'{90193291-A262-475F-9E39-8C79F25B7C9E}'
'{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'

This ONLY happens when remoting into the server.
 
Solution
Hi bswhipp,
That's a solid observation. Local printer redirection can indeed cause these kinds of errors. When you remote into the server, it's common for Windows to attempt automatic printer installation for locally redirected devices. If the server is unable to locate the necessary metadata or driver information for these printers, you can see the DeviceSetupManager logging an error with result 0x80070490 (Element not found).
Here are a couple of things you might consider:
  • Update Printer Drivers:
     – Ensure that both the client and server have the latest drivers installed for your local printers. This can sometimes resolve mismatches causing the error.
  • Disable Printer Redirection:
     – If remote printing isn’t...
Hi bswhipp,
The error you're seeing—DeviceSetupManager Metadata staging failed with result 0x80070490 (which essentially means "Element not found")—often indicates that the system is trying to stage metadata for a device container that it can’t locate. Given that this only occurs when remoting into the server, here are a few insights and suggestions:
  • Nature of the Error:
      0x80070490 corresponds to an “Element not found” error. Essentially, the DeviceSetupManager is attempting to stage metadata for specific device containers (indicated by the GUIDs) and is failing to find them. This may be related to virtual or transient devices that don’t exist or aren’t fully populated during an RDP session.
  • Why Only When Remoting?
      Remote Desktop sessions can change the hardware context by not enumerating all physical devices or by loading virtual drivers (for display, audio, etc.). In these scenarios, some device containers might not be present, leading to this error. If you’re not experiencing any functional issues during remote sessions, it’s possible these messages are benign.
  • What to Check or Do:
      
  
  • Verify that your Windows Server is fully updated, as some of these issues can be addressed in subsequent patches.
      
  • Confirm that Device Manager does not display any devices flagged with errors or missing drivers.
      
  • Consider running system integrity checks with commands like:
       sfc /scannow
       DISM /Online /Cleanup-Image /RestoreHealth
       These can help ensure that no system files are corrupted.
      
  • If concerned, check the operating system documentation or Microsoft’s support forums to see if this is a recognized issue in the version of Windows Server you’re running.
      
  • Impact Considerations:
      If you’re not observing any adverse effects (other than the logged event every few minutes during an RDP session), it might simply be a benign warning indicative of a slight mismatch in device enumeration in remote sessions.
Ultimately, if the error doesn’t seem to impact performance or functionality, it may be safe to monitor it without immediate action. However, if you start noticing related issues with device functionality or performance degradation, further investigation into installed drivers and remote session settings may be warranted.
Let me know if you have any more questions or need further troubleshooting steps!
ChatGPT
 
I think it has to do with local printers to the device remoting into the server where the server is trying to install those printers and it does not find the information it needs to install the devices.
 
Hi bswhipp,
That's a solid observation. Local printer redirection can indeed cause these kinds of errors. When you remote into the server, it's common for Windows to attempt automatic printer installation for locally redirected devices. If the server is unable to locate the necessary metadata or driver information for these printers, you can see the DeviceSetupManager logging an error with result 0x80070490 (Element not found).
Here are a couple of things you might consider:
  • Update Printer Drivers:
     – Ensure that both the client and server have the latest drivers installed for your local printers. This can sometimes resolve mismatches causing the error.
  • Disable Printer Redirection:
     – If remote printing isn’t needed, you can disable printer redirection on the RDP connection. This can usually be done in the Remote Desktop Client options under the Local Resources tab (uncheck “Printers”). Also, check any Group Policy settings related to Remote Desktop Services for printer redirection.
  • Assess the Necessity:
     – If the error is benign (not affecting the usability of the RDP session or performance), it might simply be a case of Windows attempting to install non-critical components. Sometimes, these warnings can be safely ignored unless they lead to further issues.
So yes, if the server is trying to install local printers during remoting and can’t find the correct installation details, that would definitely trigger these events. Monitoring the system and updating drivers/configuration as necessary should help mitigate it.
Let me know if you need any further assistance or details on how to adjust these settings!
 
Solution
You must log in or register to reply here.