Hello, 

none of my computers report to my WSUS Server, but show up in the Update Services Manager.

I have one Windows Server 2016 and one 2012, both wont report. 

The WSUS is using WID, not SQL.

WSUS was installed by the official Microsoft Manual.

I have tried serveral things including the following: 

On the 2012 Server:

wuauclt.exe /detectnow

 wuauclt.exe /reportnow

wuauclt.exe /resetauthorization /detectnow

On the 2016 Server:

$AutoUpdates = New-Object -ComObject "Microsoft.Update.AutoUpdate"

$AutoUpdates.DetectNow()

Tried to re-index the WSUS Database with this:  gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

Changed the Port for the Reporting Server in the GPO, which is the wsus itself, to 80 instead of 8530

Restarted all servers several times.

The Permission for the Network Service Account should be right too,unfortunalty im not able to post screenshots now.

Am i supposed to get a IIS Default site when i enter http://wsusname:8530, because right now im only getting it when i use port 80. Im not getting an error page when i try with 8530, the page is just blank.

Hi all,

We have WSUS 4 installed with sccm 1810. we enabled the new third party feature.

Here is my setup from sccm:

Company=Dell
Company=HP Business Clients
Company=Adobe Systems, Inc
Product=Office 2016
Product=Office 365 Client
Product=Windows Server 2016
Product=Office 2013
Product=Windows Server 2012
Product=Windows 10
Product=Windows 7
Product=Windows Server 2012 R2
Product=Windows Server 2008 R2
ProductFamily=Silverlight
UpdateClassification=Security Updates
UpdateClassification=Update Rollups
UpdateClassification=Upgrades
UpdateClassification=Service Packs
UpdateClassification=Feature Packs
UpdateClassification=Updates
UpdateClassification=Critical Updates

Because we also sync DELL and HP our total update number exceeds the 10000 limit (11462 to be exact). I ran a WSUS cleanup and database re-indexing and the SCCM sync showed a cleanup processing of 9926 updates. 

The problem is, I need to run the cleanup every week or so for SCCM and WSUS to run smoothly. The server restarted about a week ago for updates and the WSUS application didn't load all services (reporting services in this case. I had to restart IIS and that IS with implementing best practices on IIS for WSUS.)

 Is there a way to deal with this?

Dear all,

I would like to know if I am the only one concerned about that: 

In my update history I see: KB4493437 pending restart which is weird because I don't find that specific update in WSUS

This update name is :April 25, 2019—KB4493437 (OS Build 17134.753)

https://support.microsoft.com/en-us/help/4493437/windows-10-update-kb4493437

Thank you.

Lucas

What report can I run to show all the installed updates on a server please?

I have someone that needs to check the updates on various servers against a vulnerability scanner is report so they just need to know whats installed/KB's.

Is it possible to a) hide Active Hours from the users so they are never prompted about it; and b) disable it as a feature?  I just want Windows Updates to work they way they do with Windows 7.  The computer should reboot at a deisgnated time (in my case 1:00 AM) if needed to complete an update installation.  If 1:00 AM comes and there are no updates, then no reboot.  If the computer was off at 1:00 AM, it can just wait until the next day at 1:00 AM.

Okay, on my 5th and final server with WSUS, where I "thought" I just needed to add the Win7SP1 folders for the WSUS3Setup.cab files. Not this one. I guess there's always got to be a devil child among the problem children.

This is an SBS2011 server with WSUS. I uninstalled WSUS a few weeks ago and am now reinstalling it. On this server, and this server only, I can't reinstall. Note that I'm doing the installation from the download package, not from the Server Manager. (Same results both ways). I'm getting the following error message in the WSUSSetup.log file.

2016-06-16 20:28:00  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
2016-06-16 20:28:00  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
2016-06-16 20:28:00  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2016-06-16 20:28:04  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

Further details are provided in the WSUSSetupmsi_160616_2026.log file.

MSI (s) (8C:E0) [20:27:39:394]: Product: Windows Server Update Services 3.0 SP2 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action PERF_COUNTER_INST, location: C:\Program Files\Update Services\Setup\HideConsoleApp.exe, command: C:\Windows\Microsoft.NET\Framework64\v4.6.1055\InstallUtil.exe /LogFile="C:\Users\Administrator\AppData\Local\Temp\WSUSCa_160616_2025.log" /ShowCallStack /WsusInstall /CategoryMessageFile="C:\Program Files\Update Services\Common\EventCategories.dll " "C:\Program Files\Update Services\Setup\bin\Microsoft.UpdateServices.Setup.CustomActions.dll "

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action PERF_COUNTER_INST, location: C:\Program Files\Update Services\Setup\HideConsoleApp.exe, command: C:\Windows\Microsoft.NET\Framework64\v4.6.1055\InstallUtil.exe /LogFile="C:\Users\Administrator\AppData\Local\Temp\WSUSCa_160616_2025.log" /ShowCallStack /WsusInstall /CategoryMessageFile="C:\Program Files\Update Services\Common\EventCategories.dll" "C:\Program Files\Update Services\Setup\bin\Microsoft.UpdateServices.Setup.CustomActions.dll "
MSI (s) (8C:E0) [20:27:41:377]: User policy value 'DisableRollback' is 0
MSI (s) (8C:E0) [20:27:41:377]: Machine policy value 'DisableRollback' is 0
Action ended 20:27:41: InstallFinalize. Return value 3.

I don't know how to deal with this, since after the error a rollback occurs, and the referenced files and folders are removed. Any takers on this? If you need the entire log, let me know. It's a biggie and I'll have to break it up into 2-3 posts. I'm stumped.

 -Carl

On a Windows Server 2008 R2 SP1, I am unable to install KB4493472, which always fails with

Installation Failure: Windows failed to install the following update with error 0x8024200d: 2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472).

What I have already tried:

1. Running sfc /scannow, which gives a clean result
2. Running the System Update Readiness tool (found at KB947821 on support.microsoft.com), which also shows no errors
3. Removal of the %WinDir%\SoftwareDistribution folder
4. Installing the update manually with downloads from catalog.update.microsoft.com
   

None of the above have made any difference;  this update still fails to install.  The relevant section of WindowsUpdate.log contains:

...

2019-04-11    09:01:19:524     936    d8c    AU    All updates already downloaded, setting percent complete to 100
2019-04-11    09:01:19:648    3812    97c    Handler    WARNING: CBS called ResolveSource
2019-04-11    09:01:20:538     936    a10    AU    All updates already downloaded, setting percent complete to 100
2019-04-11    09:01:20:772    3812    97c    Handler    FATAL: CBS called Error with 0x800f081f,
2019-04-11    09:01:20:772     936    cfc    AU    >>##  RESUMED  ## AU: Installing update [UpdateId = {C8630C56-66BA-4F5F-8564-30D73F25BEB8}]
2019-04-11    09:01:20:772     936    cfc    AU      # WARNING: Install failed, error = 0x8024200D / 0x8024200D
2019-04-11    09:01:20:772    3812    ec8    Handler    FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8024200d
2019-04-11    09:01:20:772    3812    ec8    Handler    :::::::::
2019-04-11    09:01:20:772    3812    ec8    Handler    ::  END  ::  Handler: CBS Install
2019-04-11    09:01:20:772    3812    ec8    Handler    :::::::::::::
2019-04-11    09:01:20:787     936    4e0    DnldMgr    Install failed because the update {87A05CC7-9216-4F54-8A7C-B732888AA710} was not complete; mark update as not downloaded.
2019-04-11    09:01:20:787     936    4e0    Agent    LogHistory called. idUpdate={C8630C56-66BA-4F5F-8564-30D73F25BEB8}.201, resultMapped=8024200D, resultUnMapped=8024200D
2019-04-11    09:01:20:787     936    4e0    Agent    *********
2019-04-11    09:01:20:787     936    cfc    AU    Install call completed.
2019-04-11    09:01:20:787     936    4e0    Agent    **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
...

And an excerpt of CBS.log (that seems to apply) contains:

...

2019-04-11 09:01:18, Info                  CBS    Exec: Staging Package: Package_1638_for_KB4493472~31bf3856ad364e35~amd64~~6.1.1.8, Update: 4493472-4632_neutral_LDR, PinDeployment: amd64_e4822cf0ae2405da024528817dbaa38d_31bf3856ad364e35_7.6.7601.24085_none_fcacf8b0c370094d
2019-04-11 09:01:18, Info                  CBS    Exec: Staging Package: Package_1674_for_KB4493472~31bf3856ad364e35~amd64~~6.1.1.8, Update: 4493472-4702_neutral_LDR
2019-04-11 09:01:18, Info                  CBS    Exec: Staging Package: Package_1674_for_KB4493472~31bf3856ad364e35~amd64~~6.1.1.8, Update: 4493472-4702_neutral_LDR, PinDeployment: amd64_de052ec1b8076fd60bfd864a5134f012_31bf3856ad364e35_7.6.7601.24085_none_8959acdf028cdf1a
2019-04-11 09:01:19, Info                  CBS    Calling client to resolve source, cannot find file 'usbccgp.sys' at path: \\?\C:\Windows\SoftwareDistribution\Download\6ea408e302996a5e7f006433d356c2a3\amd64_usb.inf_31bf3856ad364e35_6.1.7601.24138_none_29961caa3e3c75d8\usbccgp.sys
2019-04-11 09:01:19, Error                 CBS    Exec: Failed to pre-stage package: Package_1674_for_KB4493472~31bf3856ad364e35~amd64~~6.1.1.8, file: usbccgp.sys, source: \\?\C:\Windows\SoftwareDistribution\Download\6ea408e302996a5e7f006433d356c2a3\amd64_usb.inf_31bf3856ad364e35_6.1.7601.24138_none_29961caa3e3c75d8\usbccgp.sys, sandbox: (null) [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Info                  CBS    Failed to gather all required files. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Info                  CBS    Failed to gather all missing files for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Info                  CSI    00000014@2019/4/11:15:01:19.648 CSI Transaction @0xbc27e0 destroyed
2019-04-11 09:01:19, Error                 CBS    Failed to pre- stage package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Info                  CBS    Perf: Stage chain complete.
2019-04-11 09:01:19, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-04-11 09:01:19, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8, status: 0x800f081f, failure source: Stage, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2019-04-11 09:01:19, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-04-11 09:01:19, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
2019-04-11 09:01:19, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
2019-04-11 09:01:20, Info                  CBS    Reboot mark refs: 0

...

I have a ZIP file containing WindowsUpdate.log, CBS.log, and CheckSUR.log, if this would be useful.

Good Day!

We are use WSUS Role on Windows Server 2016.

Clients can't download "Feature update to Windows 10 (consumer editions), version 1803, en-us". It's stuck on 0% and  failed  after few hours with error "0x80d02002".

In WindowsUpdate.log I saw this entries:

2018/05/22 16:10:50.9524467 4496  10012 DownloadManager DO job {32BDB35B-BE74-4B32-B146-FDFDBFCF9DB4} failed, updateId = 0DF72D03-C700-4EEA-994A-9777CCDFBF90.200, hr = 0x80D02002. File URL = http://wsus.domain.com:8530/d/msdownload/update/software/secu/2018/05/windows10.0-kb4103729-x64_0cf6d3009ed0bb61fab3c4d8964cd6f209373c97.cab, local path = C:\WINDOWS\SoftwareDistribution\Download\eb380a276773ea9883b97c243ead8ed0\Windows10.0-KB4103729-X64.cab

2018/05/22 16:10:50.9529958 4496  10012 DownloadManager   Progress failure bytes total = 21692097, bytes transferred = 0

On WSUS server in "Update Files and Languages" window option "Do not store update files locally, computers install from Microsoft Update" is set.

I can't understand why clients still use local URL. And i didn't receive such errors before.
I reinstalled WSUS role (absolutely wiped db), but error still persist.

Does anybody faced with such problem?

Thanks!

hello I tried to re-install WSUS 

i faced an issue when i started to post-install 

this the log

2019-04-30 12:10:45  Postinstall started
2019-04-30 12:10:45  Detected role services: UI, WidDatabase, Services
2019-04-30 12:10:45  Start: LoadSettingsFromXml
2019-04-30 12:10:45  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2019-04-30 12:10:45  System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception. ---> System.IO.InvalidDataException: Invalid installation directory
   at Microsoft.UpdateServices.Internal.SetupInfo.GetInstallDirectory()
   at Microsoft.UpdateServices.Internal.UtilConstants..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
   at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception.

Hi all,

I have a Windows Server 2012 R2 VM running WSUS; having added a couple of Windows 2016 servers to my network I wanted to know if it's possible to patch them using this WSUS server or do I need to look at SCCM now as an alternative?

Thanks in advance.

Kath

I'm in the process of upgrading roughly 50 workstations from Win7 to Win10. We currently use a WSUS server to handle updates. Is WSUS necessary for Win10 machines? Does the peer-to-peer updates handle what WSUS did in previous versions of Windows or do I still WSUS? 

Currently WSUS is currently on a Windows Server 2008 R2 server running version 3.2. As it currently stands, when I upgrade the workstations I'm denying the current policies (in GPO) set up in WSUS (because they don't apply as they're for Win7). 

Not sure how to handle updates. Any suggestions are greatly appreciated!

Hi, All 

I'm facing an issue with WSUS, Sync failed with error unable to resolve upstream server 

but it's not syncing from upstream server it's doing from Microsoft Updates

Hi guys - All of my Windows 10 1709 clients (fully updated) have stopped reporting their status to WSUS running on 2012 R2.

It appears that this started happening for me on the 3rd January.  All other client OS's and Server OS's are reporting status without issue.

Steps I've attempted so far.

1. Ran Windows Update troubleshooter (The machines can all receive updates from Microsoft update servers)

2. wuauclt /reportnow (No change)

3. Telnet to ports 8530 and 8531 are successful from all Windows 10 clients.

4. Server cleanup performed on WSUS (no change)

5. Forward and reverse DNS lookups are all fine from the Windows 10 clients to the WSUS server.

Here's the logs from the clients.

2018/01/10 16:59:16.5569761 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
2018/01/10 16:59:16.5569774 3624  5620  WebServices     WS error: The operation timed out
2018/01/10 16:59:16.5569815 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
2018/01/10 16:59:16.5569844 3624  5620  WebServices     WS Error code: Server
2018/01/10 16:59:16.5570045 3624  5620  WebServices     WS error: <detail/>
2018/01/10 16:59:16.5575165 3624  5620  IdleTimer       WU operation (CLegacyEventUploader::HandleEvents, operation # 1071) stopped; does use network; is at background priority
2018/01/10 17:06:11.8244134 3624  5620  Misc            Got WSUS Client/Server URL: http://andromeda.apollo.local:8530/ClientWebService/client.asmx""
2018/01/10 17:06:11.8415981 3624  5620  ProtocolTalker  OK to reuse existing configuration
2018/01/10 17:06:11.8416035 3624  5620  ProtocolTalker  Existing cookie is valid, just use it
2018/01/10 17:06:11.8416055 3624  5620  ProtocolTalker  PTInfo: Server requested registration
2018/01/10 17:06:11.8966714 3624  5620  Misc            Got WSUS Reporting URL: http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx""
2018/01/10 17:06:11.8966841 3624  5620  IdleTimer       WU operation (CLegacyEventUploader::HandleEvents) started; operation # 1072; does use network; is at background priority
2018/01/10 17:06:11.8969229 3624  5620  WebServices     Auto proxy settings for this web service call.
2018/01/10 17:06:38.8547668 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547688 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547705 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547721 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547738 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547750 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547799 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547820 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547836 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547853 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547865 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547882 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547898 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547914 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547931 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547947 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547964 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547980 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8547997 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8548013 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8548034 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8548050 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:38.8548079 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
2018/01/10 17:06:38.8548091 3624  5620  WebServices     WS error: The operation timed out
2018/01/10 17:06:38.8548132 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
2018/01/10 17:06:38.8548161 3624  5620  WebServices     WS Error code: Server
2018/01/10 17:06:38.8548379 3624  5620  WebServices     WS error: <detail/>
2018/01/10 17:06:40.8551609 3624  5620  WebServices     Auto proxy settings for this web service call.
2018/01/10 17:06:40.8846397 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846418 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846430 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846447 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846459 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846476 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846517 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846537 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846632 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846648 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846665 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846681 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846693 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846710 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846726 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846743 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846759 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846776 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846792 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846808 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846829 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846845 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:40.8846874 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
2018/01/10 17:06:40.8846886 3624  5620  WebServices     WS error: The operation timed out
2018/01/10 17:06:40.8846932 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
2018/01/10 17:06:40.8846960 3624  5620  WebServices     WS Error code: Server
2018/01/10 17:06:40.8847166 3624  5620  WebServices     WS error: <detail/>
2018/01/10 17:06:42.8850605 3624  5620  WebServices     Auto proxy settings for this web service call.
2018/01/10 17:06:42.9168866 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168887 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168903 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168916 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168932 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168945 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9168986 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169006 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169101 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169117 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169134 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169150 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169162 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169179 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169195 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169212 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169228 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169245 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169261 3624  5620  WebServices     WS error: The body of the received message contained a fault.
2018/01/10 17:06:42.9169277 3624  5620  WebServices     WS error: The body of the received message contained a fault.

If I navigate to the reporting services URL from any Windows 10 client I get 

Server Error in '/ReportingWebService' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<!-- Web.Config Configuration File --><configuration><system.web><customErrors mode="Off"/></system.web></configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<!-- Web.Config Configuration File --><configuration><system.web><customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/></system.web></configuration>

This issue appears to be related to an update that has applied recently, presumably for Windows 10 1709.

Any ideas?

Many thanks

Hi,

  In My environment some of the Windows 10 and Windows 8.1 clients not reporting to the WSUS server. But its contacting ,I already done the basic troubleshooting as per below . pls help to resolve this issue.

Note :- Today i have taken new Windows 10 laptop and added the same in domain . Based on the GPO settings its contacting to the WSUS server . But not reporting ( If any Windows 7 added newly with the same GPO settings its contacting and reporting ) 

Kindly refer the Windows update log also 

wuauclt.exe /detectnow

wuauclt.exe /reportnow

wuauclt.exe /resetauthorization /detectnow

Stopping wuauserv, deleting C:\Windows\SoftwareDistribution\DataStore\ and Download, Starting wuauserv and wuauclt.exe /detectnow

Deleting the clients from WSUS console.

http://wsus:8530/selfupdate/iuident.cab

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f--> Client ID Successfully Reconfigured automatically.

Server cleanup completed .

server Rebooted.

WSUS Data store having 100 GB free space. 

Able to telnet from the client.

Regards,

V.P.Neelakandan

Hi,

I found the issued. Windows 10 clients not reporting to WSUS Windows Server 2016 but windows 7 run normally.

Please advise me to check and solve the problem.

Thank you

i am having issues with getting updates from my wsus server.

I have specified the FQDN in GPO and 8530. all firewall is off and all my device gets this same error code.

please advise what is it i am doing wrong?

In our enviroment we are rolling out Windows 10 Pro and I'm configuring WSUS to update those Windows 10 clients.

In the products categorie there are a lot Windows 10 options but what is the difference?
- Windows 10 and later drivers
- Windows 10 and later upgrade & Servicing drivers
- Windows 10 Feature On Demand
- Windows 10 GDR-DU
- Windows 10 Language Interface Packs
- Windows 10 Language Packs
- Windows 10 LTSB
- Windows 10

Also in the Classifications you can choose between "Update Rollups", "Updates" and "Upgrades". What is the difference and what I need to take?

Thanks in advance.

For years, I've had WSUS running on 2012R2 server. All was well for Windows 7 updates. Once we began migrating to Win 10, WSUS would show status of "Not yet reporting" for all Windows 10 machines.

I did some research and figured I would spin up a new WSUS running on Win 2019 server to try and resolve.

Same issues. Windows 7 reports as normal and all Win 10 workstations report asNot yet reporting on this brand new WSUS server.

The 2019 WSUS is still running as a downstream server to the 2012R2.

What can be done to properly report the Win 10 machines?

Hi,

I try many times the PowerShell command "Invoke-WsusServerCleanup -CleanupUnneededContentFiles" but it stop after some minutes

Invoke-WsusServerCleanup : The operation has timed out
In Line:1 car:1
+ Invoke-WsusServerCleanup -CleanupUnneededContentFiles
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Updat...rCleanupCommand:InvokeWsusServerCleanupCommand) [I
   WsusServerCleanup], WebException
    + FullyQualifiedErrorId : ServerIsInvalid,Microsoft.UpdateServices.Commands.InvokeWsusServerCleanupCommand

Any ideas?

Regards