Wsus the operation timed out error

Seyyed Soroosh Hosseinalipour 21

ITNOA

I have clean windows server 2019 core that server WSUS.

After I synchronized wsus from internet. I want to see critical update with below command

Get-WsusUpdate -Classification Critical -Approval Unapproved -Status Any

But after I write this command on powershell I see below error

The operation has timed out

The note is I change connection timeout in IIS to 600 seconds but the error does not resolved

My question is why this error occurred and how to resolve this?

I have the same question in serverfault

thanks a lot

Rita Hu -MSFT 9,641 Reputation points

2020-11-30T02:29:35.783+00:00

Hi soroshsabz,

Thanks for your posting on Q&A.

This issue often occurs when the Application Pools recycled. It is recommended to maintenance the WSUS Server as this link first if you haven't try it before. It is essential for WSUS.

If there are any updates after configure the IIS as this link, please inform me in time.

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.
Seyyed Soroosh Hosseinalipour 21 Reputation points

2020-12-04T19:45:06.66+00:00

I check it, but my problem is not resolved, I change IIS configuration as you say, but does not resolve my problem
Rita Hu -MSFT 9,641 Reputation points

2020-12-07T02:45:41.867+00:00

Perhaps we could check the Event Viewer and confirm whether there are any Event ID or error information. We could filter out the event by source - Windows Server Update Services. Here is a picture for your reference:

If there are any information, please share with us.

13 answers

Adam J. Marshall 9,511 Reputation points MVP

2020-11-30T14:42:52.803+00:00

Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

If you're not performing the maintenance, and assigning the appropriate resources to the system, then these issues will occur.

https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 9,511 Reputation points MVP

2020-12-04T20:27:24.593+00:00

If you perform the correct maintenance, WSUS will work properly for you. If you're not performing any of the maintenance, problems like what you're experiencing will happen. WSUS is not a set and forget about system. There are things you have to do to it or it will become slow, bloated, and not work properly - both at the server side and at the client side (checking for updates).
Please sign in to rate this answer.

1 person found this answer helpful.
ChopperDude 6 11 Reputation points

2022-02-22T21:42:56.417+00:00

You obviously aren't a WSUS admin. This has been an issue since day 1 with Server 2019. I've done everything listed in the How to configure WSUS and the Best Practices for WSUS that MS FINALLY updated in January, 2022.

Noting improves performance with attempting to do a server cleanup, or do anything with drivers. it usually takes me about 20 attempts just to get the unapproved drivers to show, and the only thing I am able to do with them is deny all.

I am running WSUS on two separate servers and the both have this issue. hardware doesn't seem to matter because cpu utilization never exceeds ~20% and disk might go as high as 50%.

Adam J. Marshall 9,511 Reputation points MVP

2022-02-22T22:37:46.963+00:00

You also obviously didn't look at my profile and website. WSUS Automated Maintenance (WAM) © is our software, written by me and is used around the globe to maintain hundreds of thousands of WSUS servers. That being said, my intent is not to solicit business, but to inform you of the multitudes of different areas of WSUS maintenance and optimization that need to be done on a continual basis to fix the errors that you're experiencing.

I've been personally running my WSUS server since 2014, on the same install (with Drivers enabled up until about 8 months ago now when I finally switched to Dell's Command Update for the fleet that I manage), in-place upgraded from 2012 to 2012R2 to 2019 to 2022 and it is still running perfectly.

Also, just to prove it's working:

PS C:\WINDOWS\system32> Get-WsusUpdate -Classification Critical -Approval Unapproved -Status Any Title ----- Microsoft .NET Framework 3.5 SP1 Update for Windows Vista SP1 and Windows Server 2008 x86 (KB982535) Microsoft .NET Framework 3.5 SP1 Update for Windows Vista SP1 and Windows Server 2008 for x64-based Systems (KB982535) Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows Server 2008 SP2 Update for x64-based Systems (Did a CTRL-C) PS C:\WINDOWS\system32> $(Get-WsusUpdate -Classification Critical -Approval Unapproved -Status Any).Count 777

Adam J. Marshall 9,511 Reputation points MVP

2022-02-22T22:42:26.12+00:00

Also, As for Drivers - they are the 1 downfall to WSUS - they generally don't supersede each other - you have to MANUALLY mange them. I won't lie - it's a pain. WAM can help because it can remove all the drivers and then allow only NEW ones to sync down. This alleviates a lot of the burden on the client scan.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
ChopperDude 6 11 Reputation points

2022-02-23T18:03:10.85+00:00

Well since you had to write your own software; does that mean you believe that following the Microsoft recommendations isn't really sufficient to keep WSUS working well?

I've been running WSUS since server 2008 and have never had any issues until Server 2019. I still run Server 2016 at home, on a small home-built server and I service 3 different versions of Windows with it, and have no issues, even with drivers.

Yet here at work, we run Server 2019 on a Server with 32 cores, all NVMe storage, 64gb RAM, only service Win1021H1 x64 and can't do server cleanup unless only check one box at a time, but can't run Unused Updates and Revisions or it will crash the console. And, can't do anything with Drivers, except as mentioned above.

This issue has existed since Server 2019. I've stood tried Multiple times with multiple machines, Installed Server 2019 at least five different times, even Downloaded Fresh copies of the ISO three times, just to make sure I wasn't introducing something from the DVD, all with the same terrible results.

Yet when we ran Server 2016 in the same environment , we had no issues.

I even went so far as to install 2016, configure WSUS and let it run for a month, then performed all main I/A/W MS How to configure WSUS and best practices (Pre 2022 versions) and received the same result.

So........... IMHO, it's broke.

Next I will try the evaluation version of Server 2022 and see if that works....Unfortunately I have no other option since we run on a DOD Classified Network. I've found it almost as easy to manually download the .cab from ms and push them out with a script, then query the systems to ensure they installed.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 9,511 Reputation points MVP

2022-02-23T20:48:14.21+00:00

After helping out in the community for all of these years, I've seen what "little" things need to be done, some often, some not often. Some of the items on WAM's list are what the user's and I wanted (Rename OS Descriptions, for example), rather than what Microsoft deems necessary for maintenance. We've also expanded WAM to have it's own PowerShell module that exposes our custom written Cmdlet tools to check and improve many of the IIS items Microsoft has recommend, both in that document you speak of, as well as in the multitudes of support forum posts like yours. WAM is used in many government agencies, both federal and provincial/state side, all around the world and would have a field day with your install :)

Your specs are great - except are they hardware or VM? If hardware, is it dual CPU or signle CPU with 32 cores? If VM, how many vCPU's are you exposing to the WSUS server?

https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
ChopperDude 6 11 Reputation points

2022-02-23T21:10:08.29+00:00

Hardware.

Dual CPU Xeon; dual NVMe one for OS one for WSUS db and WSUS_Storage; no other roles other than what is required by MS and for WSUS Role.

Extreme waste of Resources but that's the minimum just to get WSUS to operate at a barely tolerable level.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Wsus the operation timed out error

13 answers

Your answer