Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, March 29, 2019 3:52 PM
Hi,
On a lot of computers when I'm using Get-windowsUpdateLog to debug my Windows 10 Features upgrade process, I have a lot of entry like :
2019/03/29 11:30:29.2618045 19856 21668 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{35508000-2073-4D76-BDDF-5004C52E2CB7}.1}
2019/03/29 11:30:29.6514007 19856 21668 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/03/29 11:30:29.6514199 19856 21668 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{3FBA4900-A6A8-44E0-A4EA-EE0BDD340C92}.1}
2019/03/29 11:30:29.6543394 19856 21668 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Dell\sysinv
2019/03/29 11:30:29.6543608 19856 21668 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/03/29 11:30:29.6543828 19856 21668 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{89FF2C00-7F9C-41DE-8ED8-C609195883AE}.1}
2019/03/29 11:30:29.6745459 19856 21668 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/03/29 11:30:29.6745682 19856 21668 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{B40F1E00-EDED-4BCC-A72A-DFC919F19DED}.1}
2019/03/29 11:30:29.6870255 19856 21668 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Dell\sysinv
2019/03/29 11:30:29.6870389 19856 21668 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/03/29 11:30:29.6870869 19856 21668 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{62491000-E111-40BA-AC2D-9C2C423A1086}.1}
How to deal with it?
regards
All replies (7)
Monday, April 1, 2019 6:08 AM
Hi,
In order to help you better, I’d like to confirm that which way did you update.
According to the information you provided, 8004100E = WBEM_E_INVALID_NAMESPACE, so it looks as if WMI is broken. I suggest you rebuild WMI by the following link:
How to repair or rebuild the WMI Repository on Windows 10
https://www.thewindowsclub.com/how-to-repair-or-rebuild-the-wmi-repository-on-windows-10
Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.
Meanwhile, you may download update manually from Microsoft Update Catalog:
http://www.catalog.update.microsoft.com/Home.aspx
Hope these can help you. If you have any questions, please feel free to contact us.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, April 1, 2019 9:35 AM
Same errors after rebuilding WMI repo.
I've just upgrade my Windows to 1809, but do you think that no access to windows update services can make this type of errors?
regards
Tuesday, April 2, 2019 8:10 AM
Do you use SCCM with Third Party Software Catalogs for Lenovo and Dell? This looks like a scanning problem with the Third-Party Software Update Catalogs that we are experiencing. It looks like its looking for specific information in WMI, but can't find that information. If you use WMI Explorer you can verify that WMI is working normal, but the keys are not present. Not sure what the solution is yet, but we are also looking in to it. If it is an SCCM Third Party software update problem perhaps this discussion must be moved to the SCCM Forums.
Kind regards,
Giovanni
Giovanni Perini
Tuesday, April 2, 2019 8:16 AM
Basically, we've just upgrade (few days ago) our SCCM to 1810, so now third party software catalogs is enable, but we don't use it yet.
Do you think that can occure this type of errors on my clients?
Tuesday, April 9, 2019 6:49 AM
Hi,
According to the current situation, I suggest you try to do a test first in case error occurs.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, May 21, 2019 11:56 AM
Hello,
I wanted to add my feedback. I'm running Windows 1803 in our environment. We're also using SCCM 1810. I've recently added SCUP integration into SCCM. I've added the Lenovo catalog into SCUP. After deploying a few Lenovo updates from SCCM our clients are now seeing the following in get-windowsupdatelog:
Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{6B28B601-FD20-48A9-B179-031F7B6A97C3}.1}
2019/05/21 07:39:11.7874690 3204 8944 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/05/21 07:39:11.7874755 3204 8944 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/05/21 07:39:11.7874792 3204 8944 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{4AB33801-1459-46B4-B914-ED8938FFA649}.1}
2019/05/21 07:39:11.8008463 3204 8944 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/05/21 07:39:11.8008528 3204 8944 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/05/21 07:39:11.8008570 3204 8944 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{CAF2FB00-79D4-4FE9-AB0D-CABBAAB60150}.1}
2019/05/21 07:39:11.9048271 3204 8944 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/05/21 07:39:11.9048369 3204 8944 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/05/21 07:39:11.9048438 3204 8944 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{ABCD7000-69EC-4064-9AEE-9CF3B4E27EBF}.1}
2019/05/21 07:39:11.9212835 3204 8944 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
2019/05/21 07:39:11.9212918 3204 8944 EEHandler *FAILED* [8004100E] Method failed [COperatorTreeNode::Evaluate:390]
2019/05/21 07:39:11.9212974 3204 8944 Agent *FAILED* [8004100E] Evaluate Installed rule, updateId = {{B7766000-EFAD-4470-AAF4-D1B5E052E223}.1}
2019/05/21 07:39:11.9810380 3204 8944 EEHandler *FAILED* [8004100E] EE: ConnectServer for namespace Root\Lenovo\drivers
I've verified WMI all is working and with no errors.
Our clients do receive Windows updates without any errors.
Dr. Chuck
Friday, July 5, 2019 11:46 AM
I am also seeing these errors in my environment. Anyone figured out whether they can be cleared? I'd expect that the Lenovo WMI namespace wouldn't exist on a non-Lenovo machine, but I'm even seeing this errors on Lenovo machines!