To manage software updates using SCCM/Configmgr, software update scan (with help of windows update agent) is mandatory without which,client cannot download the update catalog (metadata) from WSUS and perform the scan for letting the server know what is required and what is not required using the state messages. Wii ghost squad review. When i was looking at the software update scan reports few days ago,identified some of the clients (Windows servers) could not able perform software update scan. So i decided to take look at the one of the client logs and troubleshoot further. After logging into the server,looked at wuahandler.log,scanagent.log and windowsupdate.log as these logs will help you help to troubleshoot software update scan issues at the initial stage. Below is windows update log. WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250 COMAPI FATAL: Unable to connect to the service (hr=80080005) COMAPI WARNING: Unable to establish connection to the service. (hr=80080005) After seeing this error,i tried to stop windows update service but windows update service stuck at “stopping” status (hung) and never finish.

I have issues where the configuration manager CAS server is showing the clients as 'Pending System Restart'. When you look at the client it's referring to, it shows the status as having been sent. Jul 24, 2015  KB installation stuck in 'Pending Verification' and 'Waiting to Install' System Center 2012 Configuration Manager. Configuration Manager 2012 - Security, Updates and Compliance https. For few cases i did reinstall the SCCM client.

So i have to kill the service to stop using taskkill command. Open cmd as an administrator • Run: taskkill /f /fi “services eq wuauserv” After the windows update service start, tried initiating the software update scan to see if that makes any any difference but again issue repeat (same error code in windows update log,software update scan never move forward using wuahandler.log ) I even tried installing the updates manually to see if that goes through but that also failed. After doing the basic troubleshooting as said above,the issue is not with SCCM client or windows update agent rather it is more of windows issue likely to be caused due to a missing/corrupt class in root microsoft windows servermanager How do you know the issue is related to missing/corrupt wmi class? For this,you need to create dump to analyse what is going on and here is what found in the dump log.