need help..

Our upstream server is on server 2012r2 platform  and downstream server is on server 2008r2.. but here the problem is after few min synchronization goes idle and Last synchronization shows failed and update needing files shows Zero.. even on the upstream server if i check Installed /not applicable shows zero update with particular server, do we have any diagnose tool .. looking for the help badly.. (ports are checked as well pinging with upstream server, WSUS configuration wizard successfully run and no issue) 

Hi,

We having an issue with one of our Windows 10 clients.

When try yo update this machine get this error:

Feature update to Windows 10, version 1909 - Error 0xc1900130

When go to the Windows updates see this message:

Your version of Windows has reached the end of support. We recommend that you update to the latest version of Windows 10 to receive the latest security features and enhancements.

I did check the version of the Windows 10 and is at 1803 and I can see that updates to the 1903 and 1909 has been failed.

Should we download and install the 1903 manually?

Shahin

I recently started running WSUS in our environment.

The servers(mostly Server 2012 R2), have been somewhat lax as far as being

kept updated.

I just did a synch, and received many hundreds of Security Updates, and a goodly pile of Critical Updates.

Surely, I won;t need to install every one of these.

Is there some means of filtering out updates that perhaps, have been superceded by a rollup, etc, so my list of

required updates can be more...manageable?

Many thanks,

Rich

Hi,

At one of our sites we have a 2012 R2 WSUS server with around 60 clients connecting to it.  All clients are Windows 10, of a variety of builds.  There is no common build that this problem is affecting.  This has been working fine since we set it up a few years ago.  However, over the space of about a month, 75% of the clients have stopped checking in with WSUS, with the Last Status and Last Contact dates not updating. The other 25% continue to work fine.

Of all the clients i've checked so far, the Last Checked date shown in Windows Update Settings on the client itself matches the date I'm seeing in WSUS, so i don't actually think it's a problem with the WSUS server itself.  Also, if I click the Check Now button then the client immediately connects to WSUS and downloads the required updates and the date value gets updated in WSUS, so the problem seems to be that the clients are just not checking.

All clients use the same GPO Policy, so it can't be a problem with that.  I can't see any issues in Event Viewer, but the check isn't even running so I guess if nothing is happening there won't be a matching event anyway!.  I could manually connect or visit them all and push the check now button, but i've got no confidence that won't just be a one-off that doesn't fix the actual problem and i'll end up having to do the same thing next month.

Does anybody have any suggestions on what be the problem and how to fix it (ideally not by suggesting buying applications to manage this)?

Thanks

Hi,

We are new to WSUS and has set up a number of Testing Servers for WSUS.

From WSUS Console, we find that there are 2 updates have been downloaded for a Server (ServerA) for a number of days BUT not installed.   

In Group Policy, we have set up 

1) Auto-download and Schedule to Install

2) Scheduled Install Day - Every Day

3) Scheduled Install Time - 6:00

When we RDP to ServerA, In the notification area, there is a message "You need some updates. Select this message to install".  When we go to Settings > Windows Update, we find that it notifies us "Updates are Available" and "Install Now".

When I press "Install Now", it is stuck at "Preparing Updates to Install - 0%".  The update is "2020-03 Cumulative Update for Windows Server 2016 for x64-based Systems KB4540670"

Just would like to know is there any way to find out why the Updates are not installed ?  Is there anything wrong ?

Your advice is sought.

Hello I work in place with a secure network no connection to outside. I have a WSUS server ready but I can't connect it to MICROSOFT servers , I wanted to know if there is a way to get updates from another active WSUS server
Manually without connecting their together

thank you 

Mr Nobody.

Hello,

I have a report from WSUS:

Computer Name	Needed	Installed Failed	No Status
vrprdssvr1	17	8507       14			0
fpgisiweb	25	8497	   13			3
vmpwmtmp	21	8505	   12			0
vopairmagnetapp	17	8509	   12			0
sopentsql1	50	8475	   10			3
sopbldbkmobile3	93	8380	    6			59

When I go to the server itself and launch the Windows Updates "Check Updates" nothing is showing they are green Up-to-date.

Even if I try to launch Check Updates from Microsoft online I get few patches but nothing above 5 so far!!!

Why this discrepancy?

an example 

The report is showing needed 568

the windows updates from Microsoft is proposing 2 importants and 6 optionals!!! ==> 8 versus 568!!!

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

dears,

as you know most of the clients now are working from home while connecting through vpn.

my wsus is configured to push updates to the pcs through gpos.

my question is will this still work if vpn is connected?

regards

Hello,

I have a report from WSUS:

Computer Name	Needed	Installed Failed	No Status
vrprdssvr1	17	8507       14			0
fpgisiweb	25	8497	   13			3
vmpwmtmp	21	8505	   12			0
vopairmagnetapp	17	8509	   12			0
sopentsql1	50	8475	   10			3
sopbldbkmobile3	93	8380	    6			59

When I go to the server itself and launch the Windows Updates "Check Updates" nothing is showing they are green Up-to-date.

Even if I try to launch Check Updates from Microsoft online I get few patches but nothing above 5 so far!!!

Why this discrepancy?

an example 

The report is showing needed 568

the windows updates from Microsoft is proposing 2 importants and 6 optionals!!! ==> 8 versus 568!!!

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Hi, I have installed test WSUS server in on premises environment.(windows server 2019)

Trying to get AD group policies working. It looks like computers status is showing approval- Install, Status- Downloaded or Pending reboot.

If I click on Status it may show additional information:

(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature Update to Windows 10 Version 1909 x64-based systems 2019-11 via Enablement Package

(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: 2020-01 Update for Windows 10 Version 1903 for x64-based Systems (KB4497165)

(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: 2020-03 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4541335)

My first question will be: what I am missing and why my PCs are not getting restarted,

second: Does message "Unable to Find Resource" means that it was not downloaded correctly?

Hi to all

Which is the best troubleshooting for this message?

Warm regards MeVs

I need your assistance.

I installed and configured WSUS on brand new Windows Server 2016. All clients are reporting to the WSUS and they show the number of patches that are missing. All of the are approved for installation. But when I detect from client side, clients show that they don't need any updates. Please assist.

Hi there.  I've done a fair amount of research and attempted multiple suggestions from other threads about this issue but nothing has worked so I'm hoping someone can provide me with some information about the Database Error message I'm getting when running Server Cleanup Wizard in WSUS version 6.3.9600.18838.  I can run all the options except the first one and get this error when running it.  Help would really be appreciated.  Thanks.

FIRST ERROR in EVENT LOG    

The WSUS administration console was unable to connect to the WSUS Server Database.

Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.

System.Data.SqlClient.SqlException -- Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

SECOND ERROR in EVENT LOG

The description for Event ID 0 from source WSusCertServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

We've had similar issues as other post on the forum.  We've tried the wsusutil reset command with no success.

Following is information from Event Log:

Reason: The operation timed out
Content file download failed.

Source File: /Content/23/14D19C27B28CC3990260D7191F6E0FF6C7483623.txt
Destination File: D:\WSUS\WsusContent\23\14D19C27B28CC3990260D7191F6E0FF6C7483623.txt

Synchronizations complete successfully, but not all folders listed in the upstream WSUS server's content folder are copying to the downstream server content directory.   I'm new to troubleshooting WSUS servers communications and have used all the tools I have in my toolbox.  Thanks.

Following is BITS information:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\windows\system32>bitsadmin /list /allusers /verbose

BITSADMIN version 3.0
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

GUID: {2540BD6B-785D-4E29-B330-36DAC2B71A33} DISPLAY: '56c376e1-f528-498d-8dfe-0c5b5c35c47f'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:04:37 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/27/3F3333142DF227191986F94D84D48BCD5CD08627.txt -> D:\WSUS\WsusContent\27\3F3333142DF227191986F94D84D48BCD5CD08627.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/27/3F3333142DF227191986F94D84D48BCD5CD08627.txt -> D:\WSUS\WsusContent\27\3F3333142DF227191986F94D84D48BCD5CD08627.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {93C23E04-1608-477E-ADA9-CE894F6F8CEF} DISPLAY: 'af44bc2f-7f56-4947-b225-49ce5f3460d1'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:04:41 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/C0/57D5966AFCD65B90EE02C43E102064CB4D3D18C0.txt -> D:\WSUS\WsusContent\C0\57D5966AFCD65B90EE02C43E102064CB4D3D18C0.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/C0/57D5966AFCD65B90EE02C43E102064CB4D3D18C0.txt -> D:\WSUS\WsusContent\C0\57D5966AFCD65B90EE02C43E102064CB4D3D18C0.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {D18E4AFF-4625-456D-AE6C-9B034856EB6D} DISPLAY: 'bc78112e-478f-48d6-887f-4b4ad3852c1c'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:04:46 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/BB/3C6441D1B8316EC74D5C33C6670F7DEC0523E5BB.txt -> D:\WSUS\WsusContent\BB\3C6441D1B8316EC74D5C33C6670F7DEC0523E5BB.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/BB/3C6441D1B8316EC74D5C33C6670F7DEC0523E5BB.txt -> D:\WSUS\WsusContent\BB\3C6441D1B8316EC74D5C33C6670F7DEC0523E5BB.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {15D4A40A-BFB1-4747-A4BE-2F1ADC7EAA39} DISPLAY: '46988441-4393-4fda-a15e-5ec5f3e1d144'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:04:51 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/5E/3DB9FA0FDD93A65E1E173D46371ACB9BAD142C5E.txt -> D:\WSUS\WsusContent\5E\3DB9FA0FDD93A65E1E173D46371ACB9BAD142C5E.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/5E/3DB9FA0FDD93A65E1E173D46371ACB9BAD142C5E.txt -> D:\WSUS\WsusContent\5E\3DB9FA0FDD93A65E1E173D46371ACB9BAD142C5E.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {4A2D8EC7-F779-4360-97C1-A0795F41011E} DISPLAY: '633202de-210f-41a3-81e3-76789f935203'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:04:56 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/EF/533B47AE27BB4C29B9AE18F7B80F0566B198A6EF.txt -> D:\WSUS\WsusContent\EF\533B47AE27BB4C29B9AE18F7B80F0566B198A6EF.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/EF/533B47AE27BB4C29B9AE18F7B80F0566B198A6EF.txt -> D:\WSUS\WsusContent\EF\533B47AE27BB4C29B9AE18F7B80F0566B198A6EF.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {3FCF6CEE-A2A6-4B80-9C3B-A50ECD01A541} DISPLAY: '2247c661-b95d-4ca9-b3a9-8537c331c9ed'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:05:01 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/14/4B7834A808728207C47A4383441043120B763014.txt -> D:\WSUS\WsusContent\14\4B7834A808728207C47A4383441043120B763014.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/14/4B7834A808728207C47A4383441043120B763014.txt -> D:\WSUS\WsusContent\14\4B7834A808728207C47A4383441043120B763014.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {9E5C9B6A-A7BA-45F5-A624-77660CB116AE} DISPLAY: 'f446c165-69d2-4953-94c5-b38ffb04ab98'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:05:06 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/6F/4869F73A61B98411C94708AC1665C972F8F2686F.txt -> D:\WSUS\WsusContent\6F\4869F73A61B98411C94708AC1665C972F8F2686F.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/6F/4869F73A61B98411C94708AC1665C972F8F2686F.txt -> D:\WSUS\WsusContent\6F\4869F73A61B98411C94708AC1665C972F8F2686F.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {39D2EA83-7F0F-4BEB-9845-6D1AE5A7F186} DISPLAY: '0e8a0f3b-9d85-4989-883c-d80b937507c6'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:05:11 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/B6/2794D84D91CE5E74E562CA72869085992BA231B6.txt -> D:\WSUS\WsusContent\B6\2794D84D91CE5E74E562CA72869085992BA231B6.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/B6/2794D84D91CE5E74E562CA72869085992BA231B6.txt -> D:\WSUS\WsusContent\B6\2794D84D91CE5E74E562CA72869085992BA231B6.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {0296E3A3-1FEC-4B75-908F-BF079F5EAEA8} DISPLAY: '0098dc1e-62f7-4c65-998e-e4380b3c6778'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:05:15 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/47/4A52F1D594B493AD6EFF53A5797C8309E3FB5A47.txt -> D:\WSUS\WsusContent\47\4A52F1D594B493AD6EFF53A5797C8309E3FB5A47.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/47/4A52F1D594B493AD6EFF53A5797C8309E3FB5A47.txt -> D:\WSUS\WsusContent\47\4A52F1D594B493AD6EFF53A5797C8309E3FB5A47.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

GUID: {390F23B3-B957-4FA5-8AB6-6B8F51F89CB1} DISPLAY: '6d7ece3e-c29d-4665-8f31-fa52645857de'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\NETWORK SERVICE
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 4/13/2020 12:34:17 PM MODIFICATION TIME: 4/13/2020 1:05:20 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 86400 ERROR COUNT: 4
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://xxx-01:8530/Content/09/3863AEDA3405D044FA31F031A9CD41B1001E9809.txt -> D:\WSUS\WsusContent\09\3863AEDA3405D044FA31F031A9CD41B1001E9809.txt
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION: SUSFile
JOB FILES:
        0 / UNKNOWN WORKING http://xxx-01:8530/Content/09/3863AEDA3405D044FA31F031A9CD41B1001E9809.txt -> D:\WSUS\WsusContent\09\3863AEDA3405D044FA31F031A9CD41B1001E9809.txt
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :false
         Enable serving to peers         :false

CUSTOM HEADERS: NULL

Listed 10 job(s).

C:\windows\system32>

Discovered early today that my C:\ space on my WSUS server had gone down to 1G. Opportunities for clearing space in folders other than C:\wsus were minimal and almost nothing. I a) did read that one could move their WSUS content to a different place on their server with a WSUSUTIL command, and b) saw that I had an available D:\ on the same server that was essentially empty. Server is a physical rack server running Windows Server 2012 Standard, x64, Processor Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz, 2200 Mhz, 6 Core(s), 12 Logical Processor(s), 12.0G RAM, with an approx. 1T C:\ (full!) and 1T D:\ (empty). So I stopped the WSUS, W3, and WID services, ran "wsusutil.exe postinstall CONTENT_DIR=D:\WSUS", giving me a "Post install is starting", a nice clean log with no errors that I can see, and a "Post install has successfully completed". The plan was to leave the WID on C:\ and have the content on D:\.

Looked in file system and the new D:\WSUS was still essentially empty. Re-started my services and still nothing happening. Now a) manually-started synchronizations fail, and b) my workstation (as a good test - unfortunately other users may well be getting the same) is now stalled at 0% when I clicked the Download button for today's available updates.

Server may have still worked before I started this, but was full to the point of being choked. *Actually*, I had already gone into my server before and UN-checked some classifications like Drivers to save space. I had also run a clean-up script on my server a few times already that would a) do a "wee bit" of good and b) take my server out of service for a week. (Which is why I don't run it too often, but console wizard always timed out and won't work at all.) SO, if I could re-load into new area (instead of dragging all the old junk over from the old area) I'd be happy. THANKS in advance for ideas!

On one of our Windows Server 2012 R2 standard virtual servers we are getting a failure when installing the following update:  "2020-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4541509)"  

The update will install, but when the server restarts we get the following error message when the server comes back up:  

"We couldn't complete the updates; Undoing changes; Don't turn off your computer"

The general error message in the event log was:

"Event 20, WindowsUpdateClient-  Installation Failure:  Windows failed to install the following update with error 0x800F0922:  2020-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4541309)."

The detailed error message in the event log was:

"errorCode- 0x800f0922

updateTitle- 2020-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4541509"

updateGuid- {20C43E88-7DCE-4FFE-90F2-66F5047EC347}

updateRevisionNumber- 200

serviceGuid- {9482F4B4-E343-43B6-B170-9A65BC822C77}"

This issue occurs on our production Citrix server, so I cannot just delete the VM, and create a new one.  (Eventually we will do this when we upgrade to Server 2016, but for now I need to resolve this issue)

I have done the following troubleshooting steps on a clone of this server:

STEP #1:  Performed the following commands in elevated command prompt:  (FAILED)

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\\Windows\\SoftwareDistribution SoftwareDistribution.old

ren C:\\Windows\\System32\\catroot2 Catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

STEP #2:  Performed the following:  (FAILED)

DISM /Online /Cleanup-Image /RestoreHealth

STEP #3:  Performed the following:  (FAILED)

Installed the update through elevated PowerShell

STEP #4:  Performed the following:  (FAILED)

Uninstalled all non Microsoft programs, and uninstalled all Microsoft updates going back to mid 2019.  Then I rebooted, and re-installed all the updates up to the one that was failing.

STEP #5:  Performed the following:  (FAILED)

Ran the System File Checker, and deleted the Windows update catalog folder; allowed Windows update to recreate that folder.  

Has anyone else had this problem? 

(Please only introduce new ideas, not the generic answers you commonly see on the technical forums where you can tell the person did not actually read the entire post they are replying to)  

Hello,

My WSUS server is pulling down monthly cumulative updates for 1709, 1803 & 1809, but not for 1903. We have a few laptops in our enterprise that are running 1903 which need monthly updates. In the Products and Classification settings under Windows I have Microsoft Edge and Windows 10 checked. is there something else I need to do to pull down updates for 1903?

Hank Vare

Hello,

I need to open WSUS to the Internet via SSL connection.

My questions:
1) Can I expose WSUS to the Internet.?
2) How to solve security.? Only internal Certification authority .? Each computer will have a client certification.
3) How to authorize computers from internet .? Through client certification?

Thx Michal.

Hi

I have few client computer in WSUS, few of the client computer is having problem in reporting status to WSUS.

Below is error on WSUS

"This computer has not reported status in 100 days."

Expecting a suitable answer.

Thanks in advance.