Windows Update prompts for installing an update that has already been installed on the user machine.

-


Causes:--

Normally windows update center will download available updates and have them installed and maintain a record for the same so that the same update is not repeated again, however if there is some issue with the Windows Update Center itself, it would either fail to download the updates or would fail to maintain a record of the installed updates.

Generally on a user’s computer, the Windows Update center is being disabled. Due to lack of permissions to download files from the internet, it’s the SCCM Windows Update service that executes and installs these updates on the machines and if for any reason a user’s computer is having any issue with corrupted files or any other, these updates status may not be reaching to SCCM Compliance and as a result shows up as a required update in the machine. Even if the update is installed, the SCCM Compliance wouldn’t have a record for its installation which is why it would constantly popup and repeat the same update as a required update yet to be installed.

Due to corrupted or wrong registry entries.

The corrupted component based servicing (CBS) manifest.

Missing system files, broken system files etc.


 Resolution:--

With Windows System File Checker command.

The command is sfc /scannow.
It will inspect all of the important Windows files on your computer, including Windows DLL files. If System File Checker finds an issue with any of these protected files, it will replace it.
How to Use sfc /scannow
Open Command Prompt as an administrator, often referred to as an "elevated" Command Prompt.

Important: For the sfc /scannow command to work properly, it must be executed from an elevated Command Prompt window in Windows 8, Windows 7 and Windows Vista. This is not required in previous versions of Windows.

Once Command Prompt is open, type the following command "sfc /scannow" and press Enter.

System File Checker will now verify the integrity of every protected operating system file on the computer.
Note: System File Checker may or may not prompt to restart but even if it doesn't, machine should be restarted anyway.
 
Repeat whatever process caused the original problem to see if sfc /scannow corrected the issue.

Manual cleanup process to reset ‘things’.

1)      Stop the Windows update service:
         a. Start menu--> Type Services.msc in the Start Search.
         b. Open the page and look for Windows Update services
         c. right click on it and select stop.

2)      Go to C:\Windows\ and delete the Software Distribution folder.
         Note: Here C drive is the one that you have logged into.

3)      Go back to Services.msc and Start the Windows Update.

4)      Download the updates getting failed from the Microsoft site and save it on the desktop.

5)      Once downloaded Run it as Administrator.

      6)      Once installed, restart the machine.

Comments

Post a Comment

Popular posts from this blog

SCCM: Determining installed applications last use time_ SQL Query.

-
ConfigMgr will definitely be able to let SCCM admins know what are installed in the environment regardless if it is a server or workstation. SCCM by default comes with a set of reports that SCCM admins can utilize to gather information. The one that I am going to mention today is , "Computers that has a metered program but have not run the program since a specific date". What is so special about this report you may think, I had the same thinking as you but it is pretty interesting to know how is this data derived. The data set for this is based on Software Inventory and this means gathering file types that are on machines. The last used time is gathered asp art of software metering. This report will provide the information based on the files inventoried and their respective last used date. Nothing unique right? Here comes the interesting part, picture the scenario as below. All of us will know that in order for Microsoft Office to be used, it has to be inst...
Read more

Unable to read existing WUA Group Policy object. Error = 0x80004005.

-
Image
Wanted to share.. It will be helpful to achieve maximum rate of patching compliance. As we often face issues to troubleshoot the systems with  "Enforcement Status Unknown" state. Issue Some of the servers / workstations are appearing as “ Enforcement Status Unknown ” in Patching Deployment Report. Logs mentioned below. Unable to find or read WUA Managed server policy. Unable to read existing WUA Group Policy object. Error = 0x80004005. Failed to Add Update Source for WUAgent of type (2) and id ({6219E813-D37D-4D15-ADA7-3E4DADF55C9E}). Error = 0x80004005. Resolution Issue appears to be with corrupt policy info locally on the machine.  Please go to c:\windows\system32\grouppolicy\machine and delete the registry.pol  file.  Run GPUpdate /force command after that .
Read more

Configmgr OnSearchComplete – Failed to end search job Error 0x80244022 WUAHandler.log

-
WSUS POOL in IIS getting stopped frequently, causing scan  failures from client end     So why does the WSUS App pool crash and how to fix it? The WSUS App pool “private memory limit” setting is by default configured to 1.7 GB, the pool crashed because it couldn’t keep up. In order to fix that, people increase the memory on the Software Update Point and also configure the WSUS App pool memory limit with 8-12 GB. After that App pool should be started and let the clients flood the network for a couple of hours and everything was back to normal. So why couldn’t the WSUS App pool keep up? This is due to the larger number of updates in the catalog which continues to grow over time.  After the Patch Tuesday sync from Microsoft, clients started scanning successfully at first, but the Update catalog reached a size that increased the load on the Software Update Point. Due to the default memory limit of the app pool the server ran out of memory caus...
Read more