ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Windows Updates all fail with 'Not Applicable'

book

Article ID: 161907

calendar_today

Updated On:

Products

Patch Management Solution for Windows

Issue/Introduction

Client is Microsoft Windows 7 Enterprise x64; found all Software Updates target and fail to install.
 
Confirmed the Windows Modules Installer (Manual) and Windows Update Services (Automatic) are Started per TECH41678.

Exit Code: -2145124329 (Not Applicable)
Exit Code: 2359302 (HEX=240006: Already Installed)
Exit Code 1783 (The stub received bad data [not able to install])

Cause

  1. Found most environments have issues with a stale Windows System Assessment Scan package sending back inaccurately causing the wrongful targeting.
  2. Found some environments experienced possible problems with a stale Service Pack install on the Operating System level.
  3. Found some environments experienced corruption during initial installation of the software during image deployment.
  4. Found one instance where the Client had never installed any Software Updates and the Windows Installer Tool was failing with Error: 80073712
  5. Found some return Exit Code -2145124329, 2359302 or 1783: This is typically indicative of an issue related to the Windows servicing store, or software corruption, which can prevent the successful installation of OS patches, Service Packs, and additional software.
  6. Found some instances caused by the entire image being corrupt.


 

Resolution

Work through the following options to resolve this issue:

  1. Clear the Assessment Package on the SMP/Site Server:
    • RDP to the SMP.
       
    • Review the Console > Reports > SSE Reports > Server > Task (Custom imported Report Pack from KM: HOWTO52986):
      • Ensure there are no listed items in the Currently Running Tasks Report
      • Work through the attached document (Quick - Truncate Task Tables & Cleanup Orphaned...) if there are a multitude and if they date more than a few days ago
         
    • Drill down to the C:\Program Files\Altiris\Patch
      Management\Packages\WindowsVulnerabilityScan:
      • Delete the contents of this folder (AeXPatchAssessment.exe, catalog.xml, hf.xml, servicepacks.xml and STPatchAssessmentSrv.exe files).
         
    • Go to the Console > Manage > Jobs and Tasks > System Jobs & Tasks >
      Software > Patch Management > Import Patch Data for Windows:
      • Disable the Incremental, Delete previously, Automatically revise, Enable distribution and Disable superseded settings; run the PMImport when you are able as that will rebuild the Vulnerability files.

         
  2. Repair the Software or Service Packs on the affected Client:
    • Control Panel > Programs and Features
    • Highlight the affected software > right-click > repair
      • Note: May also try right-click > uninstall, and rerun the installer executable
         
  3. Uninstall / Reinstall the affected Software or Service Packs on the Client:
    • Control Panel > Programs and Features
    • Highlight the affected software > right-click > uninstall
      • Note: Reinstall through the supported vendor methods as the initial install/registration may have caused the corruption
  4. Work through the process from Microsoft to resolve the Error 80073712 preventing the updates from installing:
  5. Typically this issue can be resolved by running the Windows System Update Readiness Tool on the machine experiencing this issue.
    • Tool is utilized on the following OS types:
      • Windows Vista
      • Windows 7 32-bit
      • Windows 7 64-bit
      • Windows Server 2008
      • Windows Server 2008 R2
    • Note: Review the process for Repairing Errors in the CheckSUR.log 
    • Advisory: This tool will sometimes show no errors yet all updates continue to fail; review step #5 below in this instance once confirming that the update is, in fact, vulnerable by checking the Assessment Scan results against the targeting rules set by the vendor.
    • Diagnostic and repair functionality in the System Update Readiness Tool is built into the Operating System within Windows 8 and Windows Server 2012 machines:
      • Utilize the DISM CMDs from the same readiness tool as this is all encompassed on the same article in this segment above.
         
  6. Work through the process to Repair Windows Image:
    • Or recreate/reimage the client, as an OS level problem was discovered.