question

Rumpi-7730 avatar image
0 Votes"
Rumpi-7730 asked ·

Windows 10 20H2 not synching with WSUS

Hello,

we are facing Problems with new win10 20H2 clients on our WSUS Server (Windows Server 2019) . They are showing up in the WSUS console but then keep saying "you're up to date".

Recording to the WindowsUpdate.log there is a problem with an query from the MSFT_VSInstance. It fails with the errorcode 80041010. A research didnt get me much further.

 2021.03.02 10:42:30.2605500 7572  4160  EEHandler       *FAILED* [80041010]   EE: ExecQuery for query select * FROM MSFT_VSInstance where ((Version LIKE 15.9.28307.[123456789][0123456789][0123456789][0123456789]" AND Version < "15.9.28307.1401") OR (Version LIKE "15.9.28307.[123456789][0123456789][0123456789]" AND Version <= "15.9.28307.960") OR (Version LIKE "15.9.28307.[123456789][0123456789]" AND Version <= "15.9.28307.53")) AND Version > "15.9.0" AND ChannelId LIKE "VisualStudio.15.Release""

I have no clue.

Can anyone help?

Rumpi

windows-10-generalwindows-server-update-services
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi

Stop "windows update" service, empty "SoftwareDistribution" folder under windows and try to check update again.

0 Votes 0 ·
AJTek-Adam-J-Marshall avatar image
0 Votes"
AJTek-Adam-J-Marshall answered ·

Are the clients actually reporting to the WSUS Server?
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

Run through the guidance on that page from top to bottom.

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

They are reporting, yes. Strangely enough, a clean installation of a windows 10 1909 Ent is working fine in our WSUS environment.

I allready run through the steps you mentioned in your guidance. Unfortunately the client is still reporting that it is up to date.

0 Votes 0 ·
RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered ·

Hello Rumpi,

Thanks for your posting on this forum.

Did you find any other error informations on the windowsUpdate.log? The fragmentary errors are difficult for me to analyze.

In addition, please help to confirm whether the Windows 10 20H2 clients have installed the latest SSUs and CUs. The latest SSU is KB4598481 and the latest CU is kb4601319.

Thanks for your time.

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.

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for your advice. After the installation of the latest SSU und CU we are still facing the problem.

I cannot find any problem in the update log. Nevertheless I attached it. Maybe somebody can figure out what is going wrong.73702-windowsupdate.log


0 Votes 0 ·
windowsupdate.log (1.5 MiB)
RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered ·

Hello Rumpi,

Thanks for your reply.

According to the log you provided, it seems that the client did not scan for updates from the WSUS Server at all. So I recommended to follow the below steps to see whether this issue will be resolved or not:

  1. Apply the follow policies on the client first:
    Do not allow update deferral policies to cause scans against Windows Update
    Download Mode(Path: Configuration\Policies\Administrative Templates\Windows Components\Delivery Optimization):
    Reference picture:
    73704-11.png


  2. Disable the following policy if you have enabled:
    Do not connect to any Windows Update Internet locations

  3. Refresh the policy on the clients and then check for updates manually. Please consider sharing the windowsupdate.log if the above isn't helpful.

Thanks for your support and appreciate your time.

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.


11.png (34.8 KiB)
· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you very much. But unfortunately that didnt help either. No new errors in the log file.

I dont get why a clean installation of a windows 10 1909 Ent is working fine in our WSUS environment. That doesnt make any sense.


73762-windowsupdate.log


0 Votes 0 ·
windowsupdate.log (1.5 MiB)
RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered ·

Hello Rumpi,

It did help. The clients scanned for updates from the WSUS Server now but the error still existed. Reference picture:
74100-15.png

I suspect that the error occurred due to the corrupted system files. Please try to follow the below commands to repair the missing or corrupted system files first:

 DISM.exe /Online /Cleanup-image /Restorehealth 
 sfc /scannow 

Reference link: https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

Then we could reset the Windows Update Component. Open the PowerShell ISE as an administrator and run the following script:
74098-reset-the-windows-update.txt

Reference picture:
74211-16.png

Then we could try to check for updates on the clients manually. In addition, we could also check online for updates from the Microsoft Update.

Please feedback to me if there are any updates of this thread. Thanks for your cooperation.

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.


15.png (67.3 KiB)
16.png (473.1 KiB)
·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.