Resolving an Empty Patching Tab on a LabTech Agent

An empty LabTech patching tab on an agent indicates that the Windows Update agent on the local machine is unable to provide LabTech with patch information. The UPDATES - Empty Patch Window internal monitor should detect this issue on an agent and run the autofix script Monitor Empty Patch Window, in an attempt to resolve the issue. If the autofix script is unable to fix the issue, a ticket will be created and manual troubleshooting steps will be needed.

In this case, the Windows Update agent on the local machine or a local network (firewall) is preventing the machine from accessing Microsoft's Windows Update site. If all agents for a client are unable to send patch information to LabTech verify all agents have access to the following sites and make any necessary firewall adjustments to allow these below sites:

  • http://*.update.microsoft.com
  • https://*.update.microsoft.com
  • http://download.windowsupdate.com

If an individual agent has an empty patching tab, it indicates an issue with the Windows Update agent on the local machine. To attempt to resolve the issue, run the Microsoft Fix-It Tool for Windows Update on the agent which can be downloaded at the below link:

http://support.microsoft.com/mats/windows_update/

If the Fix-It Tool is unable to resolve the problem, run through the advanced Windows Update Troubleshooting steps below:

  1. Open a Windows Command Prompt window by selecting Start > Run. Enter ‘CMD' and press [Enter].
  2. Stop the BITS service and the Windows Update service by entering the below commands, each followed by pressing [Enter].
    net stop bits
    net stop wuauserv
  3. Delete the qmgr*.dat files by entering the below command and pressing [Enter].
    Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
  4. Rename the following folders to *.BAK:
    • %systemroot%\SoftwareDistribution\DataStore
    • %systemroot%\SoftwareDistribution\Download
    • %systemroot%\system32\catroot2

    To do this, type the below commands, each followed by pressing [Enter]. You may need to stop the cryptsvc service before renaming catroot2.

    • Ren %systemroot%\SoftwareDistribution\DataStore *.bak
    • Ren %systemroot%\SoftwareDistribution\Download *.bak
    • Ren %systemroot%\system32\catroot2 *.bak
  5. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, type the below two commands, each followed by pressing [Enter].
    • sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
    • sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
  6. Type the below command and press [Enter].
    cd /d %windir%\system32
  7. Re-register the BITS files and the Windows Update files. To do this, type the following commands at a command prompt, each followed by pressing [Enter].
    • regsvr32.exe atl.dll
    • regsvr32.exe slbcsp.dll
    • regsvr32.exe urlmon.dll
    • regsvr32.exe cryptdlg.dll
    • regsvr32.exe mshtml.dll
    • regsvr32.exe oleaut32.dll
    • regsvr32.exe shdocvw.dll
    • regsvr32.exe ole32.dll
    • regsvr32.exe browseui.dll
    • regsvr32.exe shell32.dll
    • regsvr32.exe jscript.dll
    • regsvr32.exe initpki.dll
    • regsvr32.exe vbscript.dll
    • regsvr32.exe wuapi.dll
    • regsvr32.exe scrrun.dll
    • regsvr32.exe wuaueng.dll
    • regsvr32.exe msxml.dll
    • regsvr32.exe wuaueng1.dll
    • regsvr32.exe msxml3.dll
    • regsvr32.exe wucltui.dll
    • regsvr32.exe msxml6.dll
    • regsvr32.exe wups.dll
    • regsvr32.exe actxprxy.dll
    • regsvr32.exe wups2.dll
    • regsvr32.exe softpub.dll
    • regsvr32.exe wuweb.dll
    • regsvr32.exe wintrust.dll
    • regsvr32.exe qmgr.dll
    • regsvr32.exe dssenh.dll
    • regsvr32.exe qmgrprxy.dll
    • regsvr32.exe rsaenh.dll
    • regsvr32.exe wucltux.dll
    • regsvr32.exe gpkcsp.dll
    • regsvr32.exe muweb.dll
    • regsvr32.exe sccbase.dll
    • regsvr32.exe wuwebv.dll
  8. Reset Winsock by typing the below command and pressing [Enter].
    • netsh winsock reset
  9. If you are running Windows XP or Windows Server 2003, you will have to set the proxy settings. To do this, type the below command at a command prompt and press [Enter].
    • proxycfg.exe -d
  10. Restart the BITS service and the Windows Update service. To do this, type the following commands at a command prompt, each followed by pressing [Enter].
    • net start bits
    • net start wuauserv
  11. If you are running Windows Vista or Windows Server 2008, clear the BITS queue. To do this, type the following command at a command prompt and press [Enter].
    • bitsadmin.exe /reset /allusers
  12. Install the latest Windows Update Agent. For more information, click the following article Microsoft Knowledge Base article.

    949104 - How to obtain the latest version of the Windows Update Agent to help manage updates on a computer

  13. Restart the machine.

Following these above steps will allow you to resolve your patching issue. If issues continue to persist, it would be best to involve LabTech Support to determine the root cause.