Computer notifies Updates Needed but WSUS Server hasn't those updates

Question

Hi

I have a WSUS Server (ver. 6.3.9600.18838) on Windows Server 2012r2. This server is a replica from other centralized.

The console shows several computers reporting 6 updates as needed. The reports show these updates are not approved.

The strange thing is:

• These updates are not present in the centralized server, so, they can´t be refused nor approved.
• My server have these 6 updates without approval. I haven´t privileges to approve or refuse. The updates are no neccesary for us in this moment.
• Cleaning WSUS Server with console assistant, the updates remain despite of the first option is "Delete updates 30 days or more without approval". This updates are much older.
• In the replica server I have deleted the 6 updates with powershell, then, the updates are not present in the replica now.
• I have reseted the Windows Update Agent in one computer and deleted it in the console. After a while, the computer appears reporting exactly the same.... 6 updates are needed.

Does anyone know what may be happening ?
How could I make to clean this updates ?

Thanks in advance
Regards

Answer 1

Hi MiguelAVera-0145,

Thanks for your posting on this forum.

It is weird that the 6 updates are not present in the centralized server in a replica mode.

First, it is recommended to confirm whether the 6 updates are actual needed on the clients or not. If the clients could connect to the Internet, we could click the Check online for updates from the Microsoft Update option on the clients to install all the needed updates.
Reference picture:

We could try the below steps if you have confirm that the 6 updates are not needed.

1. Uncheck the following option as the below picture on the replica WSUS Server:
   
2. Run the WSUS Server Configuration Wizard
   

Then we could try to decline the 6 updates on the WSUS Server.

After doing the above, we could try to change back to the replica mode.

Hope the above will be helpful.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Finally the solution has been the next:

• SUSDB -> Table tbProperty -> Field PublicationState -> The value established was 0 (Published). Changed to 1 (Expired) for those 6 updates.
• Disabling "Replica mode" and refusing the updates, after, synchronizing with upstream server, the state remains to 1 (Expired).
• Enabling "Replica mode" and synchronizing again with upstream server, the state remains to 1 (Expired).
• Computer don`t notify the need of those updates.
• After the weekly cleaning, the updates are deleted and all right with the computers.

Thanks for your support Rita.

Thanks to my coworker in Seville José A. Béjar.

Answer 3

Hi Rita, thanks a lot for your answer, I applied the solutions proposed, I`ve been waiting for results.

The problematic updates are these:

First solution. Searching in Windows Update:

I applied but the 6 updates weren`t found. They're also not in Windows Update Catalog Site. On the other side, I received other updates as Update to 20H2 version, I applied it. Now, the computer still considers the updates as necessary. Then, the problem continues.

Second solution. Uncheck replica server:

If you remember I deleted with powershell the 6 updates in my replica server but they appeared again the next day, then, they were sincronized from centralized server although they are not present in that server.
After uncheck "Replica Server" I could decline the updates, then, I refresh the console and the computers were freed. Anyone showed the updates as necessary. I go back to check replica mode. These actions were made yesterday.
Today the situation is the same, the 6 updates appears as necessary in the same computers, including the computer updated to 20H2.

Answer 4

It is weird. Have you tried to delete the WSUS file on the below path:
C:\Users\Administrator\AppData\Roaming\Microsoft\MMC

Reference picture:

If not, we could try the above and then follow the Second solution. It will be helpful to reset the wsus console if we try to delete the wsus file. Hope the above will be helpful.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.