Hello.

Yesterday I moved the WSUS Content folder from an iSCSI drive to a network share, sitting on a NAS box in my homelab. I used the wsusutil movecontent command for this task.

Now, I'm getting the following error in Event Viewer.

The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

The NAS box is integrated with Active Directory and I gave Full Control permissions to the folder to the Network Service via File Explorer.

I checked for solutions online and I have tried many of them such as checking the folder in IIS virtual directory, the registry settings, etc. None of these seems to work in my case.

Unauthorized means that it might be a permissions problem but I can't seem to understand which causing this. The server is Windows Server 2016.

Can you please help me fix this? 

Hi,

I wrote a small PowerShell script which checks the registry key on remote computers and lists the status if reboot required key exists or not.

The scripts run without any error. But the results are not correct. Although some computers (for example ComputerA and ComputerE) have this key in registry the script lists all computers in OK status.

Here is the script:

$Computers = Get-Content "C:\myFolder\Computer.txt"
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" 

foreach ($Computer in $Computers) {
$Exists = Test-Path -Path "\\$Computer\$RegPath"
if ($Exists -eq $false)
{
 Write-Host -fore Green "OK on $Computer"
}
else
{
 Write-Host -fore Red "Reboot is required on $Computer"
}
}

The results:

OK on ComputerA
OK on ComputerB
OK on ComputerC
OK on ComputerD
OK on ComputerE

What is wrong in the script?

Best regards

Birdal

Hi,

Microsoft releases most of the patches on second tuesday of each month. 

We'd like to install updates on half of the servers on approx one week after that, and on second half two weeks after. 

In WSUS GPO we have a setting for monthly update with options:

Every week
First week
Second week
Third week
Fourth week

This is a bit ambiguous. What is the first week of a month?
For example, on August 2019 patch tuesday is 13th. We'd like first batch of servers start autoinstall updates on 20th and second batch on 27th. 

How should I configure GPO?

Is "first week" this month 29.7 - 4.8, or is it first full week 5.8 - 11.8 ? Or is sunday the first day of the week and the first week 28.7 - 3.8 or 4.8 - 10.8 ?

Also, on which operating systems are first - fourth week options supported?

Hello, IT expert

I have some issue with a new Wsus standalone deployment, below info:

Infraestructure:

Windows Server 2016 patch last update.

WSUS suceed latest Sync

Database is completly cleanup

Destination computers info

Windows 7 

Windows 10 LTSB 1607, 1803, 1703 etc etc.

We create our Scope GPO  Workstation-Testing, all computers in the target OU appear correctly in the computer group in Wsus.

The issue: The wsus report said that all PC has issue installing Updates, we check some PC (W10 LTSB without any update) all Stuck installing updates and then error code Error code "0x80070422

In our environment we have deployed SCCM client for other activities for support, at some point it was integrated with WSUS but due to a bad integration an error occurred in sccm and we decided to deploy it standolone WSUS.

Does having an SCCM client installed on the computers generate the issue for WSUS deploy updates?

What else could I do to solve the problem?

Hello,

1# We are having some problems with the deployment of updates:

ISSUE:  We have deployed the GPO for WSUS on Computers of the Central Office, but we have visualized that some employees move to branch offices with his c and this causes them to update from those offices, causing slowness in the networks of that office.

We havr 5mb mpls, I imagine they will understand,.

We want to know what do yoy do to solved this situation so that computera not going to update outside their local network?

Question 2 We have not yet deployed wsus in branches

What is the best way? Replica or Downstream?

Hi

A handful of machines in my network are now Win10 1903 and these machines keep reporting 'You're not up to date' when asked to check for updates. I'm aware that I need to enable the 'Windows 10, version 1903 and later' in the Products and Classifications menu in WSUS. I've also enabled the same option in the Automatic Approvals rule relevant to my workstations. I've waited 24 hours, rebooted the server, deleted the contents of SoftwareDistribution on the client machine, but I keep getting this message:



The machines appear to be checking into WSUS normally. For the client above, WSUS reports that it checked in with its status just minutes ago, and that it is missing 8 updates.

Any ideas?

Any help much appreciated.

Hello Guys,

Is any procedure  for push the updates to child domain client from forest domain wsus server.And also how to push the updates to work group clients 

Regards,

Jaswanth

Hello Support,

We are receiving Alert in Nessus Scan for Windows2016 Std R2.

i.e:-

I am unable to find this above update packages. Kindly request you provide solution on this?

Regards

TLS

I have 4 updates that showed up for Windows 7 or 8.1 upgrade to Windows 10 v1903. These updates have an Approval status of 'Not Approved'.  We do not want WSUS to push these updates out because we are manually updating computers to Windows 10.  Can these updates stay at 'Not Approved' or should I decline these updates?

Thanks for any assistance I can get on this. 

AmyOC

Hi Team,

While clicking on WSUS Synchronize getting attached error

Dear all ,

when I would like to uninstall KB4480963 I received this error "0x8000fff catastrophic failure" . Do you have any ideas ?

For you information when I would like install any security monthly rollup I receive this error "

Server 2012 R2 Std .

I try applied this tasks below but nothing result :

1.net stop wuauserv 
2.net stop cryptsvc
3.REN %systemroot%\SoftwareDistribution SoftwareDistribution.bak (dossier des updates)
4.REN %systemroot%\system32\catroot2 catroot2.bak
5.net start wuauserv
6.net start cryptsvc
7.SFC /Scannow
8.DISM /Online /Cleanup-Image /ScanHealth
9.DISM /Online /Cleanup-Image /CheckHealth
10.DISM.exe /Online /Cleanup-image /Restorehealth
11.DISM /online /remove-package:"C:\Temp\Updates\kb....\kb...-x64.cab"
12.DISM /online /add-package /packagepath:"C:\Temp\Updates\kb....\KB...-x64.cab"
13.Script https://gallery.technet.microsoft.com/scriptcenter/reset-Windows-update-agent-d824badc
14.https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78

Thanks in advance .

Dear all ,

when I would like to uninstall KB4480963 I received this error "0x8000fff 2147549183 catastrophic failure" . Do you have any ideas ?

For you information when I would like install any security monthly rollup I receive this error "

Server 2012 R2 Std .

I try applied this tasks below but nothing result :

1.net stop wuauserv 
2.net stop cryptsvc
3.REN %systemroot%\SoftwareDistribution SoftwareDistribution.bak 
4.REN %systemroot%\system32\catroot2 catroot2.bak
5.net start wuauserv
6.net start cryptsvc
7.SFC /Scannow
8.DISM /Online /Cleanup-Image /ScanHealth
9.DISM /Online /Cleanup-Image /CheckHealth
10.DISM.exe /Online /Cleanup-image /Restorehealth
11.DISM /online /remove-package:"C:\Temp\Updates\kb....\kb...-x64.cab"
12.DISM /online /add-package /packagepath:"C:\Temp\Updates\kb....\KB...-x64.cab"
13.Script https://gallery.technet.microsoft.com/scriptcenter/reset-Windows-update-agent-d824badc
14.https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78

Thanks in advance .

As the title suggests I am struggling to get our servers downloading LP's, both server 1607 (2016) and 1809 (2019).

I uderstand that LPs are available through WSUS for build 1607 and these have been downloaded and Approved for a group in WSUS where both 1607 and 1809 servers live. On the 1607 when i click on Reagoion and Language i see it serachng WU but then nothing, 'A language pack isn't available'.

For the 1809 server the LPs are no lonnger available and i have been advised to Enable the setting 'Specify settings for optional component installation and component repair' and select 'Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)'. Again like the 1607 build it cannot find the labguage pack.

The only way to get this working acropss both servers is to disable WSUS on the server by editing the regvalue UseWUServer. This then trundles off to the Internet and downlodeds the LP!

Is there anyway to get both types of server to doanload the LPs without having to mess around on each server?

Regards

Hi,

do you use/know any enterprise tool for patch management based on WSUS?

What we want:

The tool should 

- check up-to-date state of Windows servers related to Windows Updates which are published by internal WSUS servers (OS from Windows 2008 to Windows 2019),

- solve issue if any Windows update check/download/tec. issue exists,

- report state of each machines visual (statistically) and as text/csv logs (installed/needed updates, severity of updates, reboot time of machines, etc...)  updates on each machine

- and some more...

Any suggestions?

Best regards

Birdal

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 all,

My server 2008R2 SP1 unable to install KB4490628. Wheni tired to install KB4490628 the installation screen always show installed however when i restart the server and check the installation log in windowsupdate.log and windows update history it show failed. I have tired use sfc /scannow, disable anti-virus, disable network and rename softwaredistribution folder but it still failure. Please help.

Dear community,

in our company we are using WSUS servers to distribute updates within our network.

We have one master WSUS server the rest WSUS servers are synced as replica to it.

Both master server and replica servers are running Windows Server 2016 with latest (09-2019) patches. Update service is on version 10.0.14393.2007.

When we are creating a report we have noticed that some servers connected to replica WSUS servers to download updates stops reporting their status.

These servers are also running Windows Server 2016 with latest patches.

When we hit check for updates it says that no needed updates were detected which is correct but status report remains old on WSUS server.

We have tried all basic troubleshooting steps like clean distribution folder, sfc scannow, reboot the server even reinstall WSUS replica server but none of it helped.

Could you please advise us where can be the problem here?

Thank you in advance!

Hi,

I'm pushing out the Windows 10 1903 upgrade to our systems using WSUS (with GPO), which mostly seems to work.  However, some systems fail to install the upgrade - some for known reasons such as incompatible software, whereas others just randomly seem to fail.

If I visit a failed computer, more often than not, there is a 'Fix Issues' button or 'Try Again' button or 'Install Now' button and if i click them the computer then successfully updates with no further work required.

How can I get the computers to try again without requiring me to physically them to click these buttons or having to instruct users to do that?  I don't really want to deadline the upgrade as I'm delivering it in batches.

Thanks