ReasonDescriptionThe update is supersededAs updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you may encounter this error message. Search for the update on the Windows Update catalog: Windows Update Catalog Click on the Package Details tab to view the list of updates that are superseded The update is already installedIf the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter…

We need to run SFC /SCANNOW and a full DISM /Online /Cleanup-Image /RestoreHealth Patches: While installing this patches may face issue,KB3197873; KB4012213; KB4019213; KB4022726 2. error = 0x800B0100msiexec /unregister and msiexec /register regsvr32 wuapi.dll Run CheckSUR tool and restartnet stop cryptsvc rename %systemroot%\system32\catroot2 catroot2old net start cryptsvc

Symptom: You use Microsoft Windows Server Update Services (WSUS) to deploy software updates to computers that are in your organization. When a WSUS client computer scans for updates on the WSUS server, the following error message is logged in the WindowsUpdate.log file on the client computer: WS error: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.InstalledNonLeafUpdateIDs</Message><ID>GUID</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates”</Method></detail>” *FAILED* [80244007] SyncUpdates_WithRecovery failed Additionally, the following exception is logged in the SoftwareDistribution.log file on the WSUS server: ThrowException: actor = http://WSUSServerName:8530/ClientWebService/client.asmx, ID=GUID, ErrorCode=InvalidParameters, Message=parameters.InstalledNonLeafUpdateIDs, Client=Client_ID Cause This issue occurs when the number of updates to be synchronized exceeds the maximum number of installed prerequisites that a WSUS client can pass to SyncUpdates. Resolution To fix the issue, follow these steps…

Import-Module BITSTransfer get-help *bits* Get-BitsTransfer -AllUsers Get-BitsTransfer -AllUsers | select * Get-BitsTransfer -AllUsers | select -ExpandProperty FileList We can use PowerShell to help streamline this process so we don’t have to output to a log file and search for our 0 BytesTransferred. Get-BitsTransfer -AllUsers | foreach {get-bitstransfer -jobid $_.jobid | select -ExpandProperty FileList | where {$_.BytesTransferred -eq 0} | select -first 1}

BITSAdmin is a command-line tool that you can use to create download or upload jobs and monitor their progress. For example, to list all BITS jobs, you can issue the command bitsadmin /list /verbose. Here’s a screenshot of sample output for that command. No BITS queue job: For More link

Here we are talking about the method of unsticking stuck Windows Updates. We have seen this several times with customers and on our own machines where Windows Updates are stuck downloading, installing, or failing to install for a variety of reasons. We found one way that fixes them all, without having too many steps, and can be done by any administrator… So what do you need to do? Simple: Stop the BITS and the Windows Update Services Delete or rename the SoftwareDistribution folder NOTE: If deleting, it would be a good idea to copy or backup this folder first Start the BITS and Windows Update Services. NOTE: You should now…

net stop wuauserv reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f net start wuauserv wuauclt.exe /resetauthorization /detectnow wuauclt /report Gpupdate /force pause