This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 95%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
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.
I check it, but my problem is not resolved, I change IIS configuration as you say, but does not resolve my problem
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 73%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC6%3C/text%3E%3C/svg%3E)
Checking your website; I'm not sure WAM would work for us.
I have an upstream server that I do not have access to, except for synchronization of course.
WAM would work perfectly fine on yours. Actually updated the Licensing Explained page regarding this today to make it more clear.
The main goal of running WAM on all WSUS servers is so that every server gets the maintenance that is recommended by Microsoft. WAM will work on every WSUS server you can throw it on - but with varying degrees of total improvement (dependant on how the WSUS Server is configured - if replica, less efficient as replica's can't decline updates as they come from the upstream. If autonomous or single - 100% efficiency of that specific server). I have no hesitation that it would fix your issues - but that being said...
Are you using the WID or an actual SQL server installation (if so, what version? Standard/Enterprise or Express?)
With those specs, you should have WSUS working like a purring kitten.
Not wanting to STIG another application, we use WID, and RUN Server Standard.
Completing the STIG for SQL is a total nightmare, and often takes multiple attempts to make it stick AND be able to connect anything to is, plus, we would have to place it on a separate machine, because of STIG requirements...the list goes on and on.
Understandably - WID can handle thousands of clients (when sized appropriately) so there really is no 'need' to run full SQL unless you have other requirements (HA, shared storage, etc). If you have questions regarding WAM or what not, contact us through our website and we'll be happy to answer the questions for you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 28.000000000000004%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
I have to say I also have this issue. I have 2 servers running 2016 & 2019 Standard. One is a physical server with 2016(this is the original WSUS server for the org) and was working very well on 2012 R2 and once upgraded to 2016 WSUS kept on with these Time out errors in the MMC. I built a VM with 4 Cores and 32GB AM and clean build and also get the same errors, in fact much more frequently that it is not even usable. I would gladly pay for a remote support session at this point because I have followed all recommendations and even used WAM and it still didnt fix the issue at all.
I think its a limitation of MMC and the app pools