Dear folks,

we are trying to sync a Server 200*R2 WSUS 3.2 downstream server from a 2016 WSUS 10 server.

The sync went ok, but after about 24 hours only 640mb of updates were downloaded.

We have read about BITS crippling the download, and set the local GPO to disable BITS limit, as well as limit to 102400kb with no effect. We also tried to "update tbConfigurationC set BitsDownloadPriorityForeground=1".

Every time with restart, every time wihtout effect.

The download speeds are around 40kb/s or something. We neither need nor want BITS to babysit our bandwidth; the routers and shaping should worry about that.

How do we make the server download with all available bandwidth from the upstream??

Thanks!

Team,<o:p></o:p>

I have windows Server 2012 R2. I have installed WSUS (VER:6.3.9600.18838). I have applied group policy on Tested OU with WUSU Settings & client side targeting -Workstation.<o:p></o:p>

I have applied Group Policy on Windows 7,Windows 8.1 & Windows 10 machines in OU. in WSUS console,ALL COMPUTER-Workstation, I can see all Windows 7,8.1 and windows 10 Machines. but Problem is Windows 8.1 & Windows 10 machines are showing not yet reported (0%).

Its been 3 to 4 days, I have applied Update,wuauclt/Detect now,Report now on windows 8.1 and windows 10 machines. but there is no change.  Group policy is applied on all the machines in OU.

Its new windows 2012 R2 server with WSUS installed.<o:p></o:p>

Kindly advise.

I have this issue on one server but it is important server which I cannot re-install...

Windows cumulative updates for Windows Server 2016 version 1607 x64 keeps failing to install.

SSU updates are being installed successfully, but the CU updates are failing.

So the current version of Windows server 2016 is 14393.2125 which is from 3/13/2018 - this was the last successufully installed CU update.

All CU updates since that date are failed.

Usually after the CU update installation, the server restart takes very long and at the end it is rolling back and the update installation is failed.

I tried also to manually download and install the update but the same happens.

Please suggest how to troubleshoot.

WSUS on Server 2012 R2.

Was working OK yesterday, 28 June 2017.
This morning, 29th June, large number of clients (possibly all) are failing to communicate correctly, eg when attempting to do a manual "Check for Updates". Windows 7 (x86) and Server 2008r2 come up with 80244008. A windows 10 client (x64) and 2012r2 gave error 8024401f. The WSUS management console opens without any issues.

Last status report of any client into WSUS is 630am this morning, which appears to be about 10 minutes after a restart of the WSUS Server to install 2 MS Updates this morning. 4022720 (preview of monthly rollup) and 4037282 (update for Internet explorer).

I suspect one of those updates is the issue. I've checked the details of 4022720 and can't see anything obvious that would affect IIS or WSUS, nor guidance to run any post install steps. If necessary I can uninstall, but would prefer not to, as that would only delay the issue until middle of next month when the general release of what is in 4022720 is pushed out. I have, though re-run the steps from the update that came out a year ago.

Our server is configured to use port 80, so no SSL involved, but I'm wondering if something in one of the above updates has done something to affect this.  

There are a few messages in Application log and other logs that may prove useful...

EventID 3, Source: System.ServiceModel 4.0.0.0, Task Category WebHost, Level Error, user: Network Service.

I can provide other logs later (eg WSUS logs, and logs off couple of the client systems too).

Thanks in advance

Matt W.

Hi

I do have WSUS in place.
How should I configure Windows Update for Business GPO settings if I want to:

Control feature updates through GPO? I mean, I want to delay feature updates as long as I need, until enable them in WSUS.
Basically I don't want that windows picks feature update directly from Microsoft.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.

Hi all

KB3104002 lists a number of IE versions but not IE11. However kb3125869 which is the MS for this KB lists IE11 as at risk.

Microsoft offer a the KB as a stand alone install for IE11 but why isnt it listed on the windows catalogue to be inputted into WSUS?

Why offer the fix to all other versions of IE apart from IE11

System administrator

Hi guys

Is there a way to see only needed updates which are approved for install?

for example below is the normal computer view:



However the top three 2012R2 servers are infact "patched" the 14 updates needed have not yet been approved as i work one month behind.

Is there a way to not have these unapproved updated from being shown in the needed count?

We have Windows Server 2016 Standard in our environment.

We used to apply the GPO through WSUS on 2016 servers for automatic download install and reboot after the patches gets installed. But the patches don't get installed by itself and when they don't get install they don't reboot by itself.

We checked this with AD Team and they confirmed that GPO for Auto Download Install and Reboot has been implemented.

We used to go to each and every server manually and then install the patch and then reboot the server.

Even the 2016 servers created problem in downloading patches via WSUS.

Please help on this

Hello,

I am noticing that my WSUS server for some reason offering two available Win10 1809 updates to my client machines.

Windows Server 2016

Version: 10.0.14393.2007

When my client's check in and proceed to update, it also appears as if it is installing two copies.

I have a feeling that this is consuming more space on my server then needed.

Anyone seen this issue and have a fix? Thanks

Workstation:

Hi Guys

We found lots of Event ID 364 happened on our WSUS server.

And if you look into the softwaredistribution.log ,you will see

2016-08-13 16:06:59.530 UTC Info WsusService.13 CabUtilities.CheckCertificateSignature File cert verification failed for D:\WSUS\WsusContent\E6\11AB04FDD161E6781E1E0E75CA67E55BBCBEB4E6.esd with 2148204800
2016-08-13 16:06:59.811 UTC Warning WsusService.13 ContentSyncAgent.ProcessBITSNotificationQueue Invalid file deleted: D:\WSUS\WsusContent\E6\11AB04FDD161E6781E1E0E75CA67E55BBCBEB4E6.esd

Also in Windowsupdate.log

2016-08-19 07:51:15:540  732 1aa4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2016-08-19 07:51:15:540  732 1aa4 PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016-08-19 07:51:35:837  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\wuredir.cab with dwProvFlags 0x00000080:
2016-08-19 07:51:35:837  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:837  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\TMP35B5.tmp with dwProvFlags 0x00000080:
2016-08-19 07:51:35:853  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:853  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\v6-muredir.cab with dwProvFlags 0x00000080:
2016-08-19 07:51:35:853  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:884  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\v6-muredir.cab with dwProvFlags 0x00000080:
2016-08-19 07:51:35:884  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:884  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\wuredir.cab with dwProvFlags 0x00000080:
2016-08-19 07:51:35:884  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:899  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\TMP35E4.tmp with dwProvFlags 0x00000080:
2016-08-19 07:51:35:899  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:899  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\wuredir.cab with dwProvFlags 0x00000080:
2016-08-19 07:51:35:899  732 1aa4 Misc  Microsoft signed: NA
2016-08-19 07:51:35:899  732 1aa4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\TMP35F5.tmp with dwProvFlags 0x00000080:
2016-08-19 07:51:35:899  732 1aa4 Misc  Microsoft signed: NA   :) Can anyone provide some suggestions ? Thanks

I have an existing (2012 R2) WSUS Replica server isolated from the internet. It synchronizes (through a firewall) with the internet facing parent WSUS server. There is now an architectural change and we will lose access to it's parent server. We want to configure this as a standalone with the flexibility to point to other internet facing WSUS servers in our organization.

Is this as simple as deselecting "This server is a replica of the upstream server" and pointing to the new upstream server or is there more that needs to be done?

This being a production server, I do not have the luxury of proving this.

WSUS 3.0 server reporting updates are not applicable for 2016 servers although patches have been downloaded and installed on 2016 servers.

Windows 2016 WindowsUpdate.log server log shows many of the below errors.

1600/12/31 16:00:00.0000000 336   4360   Unknown( 20): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).

Other log information is available as seen below.

2018/09/10 11:01:34.7825710 336   3776  Agent           Windows Update access disabled: No
2018/09/10 11:01:34.7884881 336   3776  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:01:34.9205997 336   4612  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/09/10 11:01:34.9206100 336   4612  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/09/10 11:01:34.9206200 336   4612  Shared          Power status changed
2018/09/10 11:01:34.9358876 336   3776  Agent           Initializing Windows Update Agent
2018/09/10 11:01:34.9373960 336   3776  DownloadManager Download manager restoring 0 downloads
2018/09/10 11:01:34.9398053 336   3776  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2018/09/10 11:01:37.4730121 336   1592  DownloadManager PurgeExpiredFiles::Found 3 expired files to delete.
2018/09/10 11:01:37.4730293 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\bd0d73364bf854970f570a2cf51388b435720e6d.
2018/09/10 11:01:37.4776616 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\48174db2b72cce60c7969dc197020c8ca58c9045.
2018/09/10 11:01:37.4831928 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\9dcadf092f9e4cca339b5f98a160086902733280.
2018/09/10 11:01:37.5496229 336   1592  DownloadManager PurgeExpiredUpdates::Found 374 non expired updates.
2018/09/10 11:01:37.6491746 336   1592  DownloadManager PurgeExpiredUpdates::Found 3 expired updates.
2018/09/10 11:01:37.7071502 336   1592  DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\Windows\SoftwareDistribution\Download\898f9fe4b16d1628e7699c9bf1d04700.
2018/09/10 11:01:37.7330569 336   1592  Shared          Effective power state: AC
2018/09/10 11:01:37.7330597 336   1592  DownloadManager Power state change detected. Source now: AC
2018/09/10 11:12:41.8143733 336   3772  Agent           Earliest future timer found:
2018/09/10 11:12:41.8143912 336   3772  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:12:42.8306986 336   4612  Agent           Earliest future timer found:
2018/09/10 11:12:42.8307130 336   4612  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:12:42.8343566 336   4612  Misc            CreateSessionStateChangeTrigger, TYPE:2, Enable:No
2018/09/10 11:12:42.8343620 336   4612  Misc            CreateSessionStateChangeTrigger, TYPE:4, Enable:No
2018/09/10 11:12:42.8776383 336   4612  Handler         CUHCbsHandler::CancelDownloadRequest called
2018/09/10 11:12:42.9330548 336   4612  Shared          * END * Service exit Exit code = 0x240001

An attempt was made to use the Microsoft's public symbol server with no success.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/microsoft-public-symbols

This is consistent throughout the Windows 2016 platform. Windows 2008 ad 2012 systems report correctly.

Hi All,

I have taken over the responsibility of our WSUS server 2012 r2.

My issues is that WSUS server is not updating client with Win10 1607 \1709  build to build 1803

These are the setting which were already configured so far.

1. In IIS manager the MIME is set too - Filename - .esd & MIMe Type to - application/octet-stream

2. GPM set so that user receive updates at schedule time.

Following setting now  Enabled 

Configure Automatic Updates 

Specify intranet  Microsoft update service location

Allow non-administrators to receive update notification

Allow Automatic updates immediate installation

No auto-restart with logged on user for schedule automatic updates installation

I would appreciate any input or suggestion on how I can make sure that ALL updates are pushed out accordingly.

Thank you.

Hitesh Mistry

I have WSUS (version 6.3.9600.18694) running on Windows
 Server 2012. Everything seems to be working fine except the Server Cleanup Wizard. Whenever I try to run it, it immediately fails giving me the "Reset Server Node" message. The event that shows up in the Application log is the following:

(Event ID: 7053)
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.  Note:  I tried this and there was no change

System.ComponentModel.Win32Exception -- The service cannot be started, either because it is disabled or because it has no enabled devices associated with it

Source
System.Windows.Forms

Stack Trace:
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)

Any help in solving this problem would be greatly appreciated!

Thanks,

Reez

Once in a while when I launch the WSUS console and it error out. When checking the Event logs, I see a warning and multiple errors. I'm not sure where to begging my search as how to resolve the issue.

But, a simple reboot seem to fix the issue. Any one seen or experience this issue?

Hello,

I've got a script which replicates a report in WSUS itself and it's working perfectly fine; however I'd like an additional one which runs the report but only on a specific Group/Groups

Below is the script

[void][reflection.assembly]::LoadWithPartialName(“Microsoft.UpdateServices.Administration”)
$wsus =[Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer(“server”,$false, '8530')

$computerscope = New-Object Microsoft.UpdateServices.Administration.ComputerTargetScope
$updatescope = New-Object Microsoft.UpdateServices.Administration.UpdateScope

$workstationsGroup = $wsus.GetComputerTargetGroups()
$computerscope.IncludeSubgroups = $true
$computerscope.IncludeDownstreamComputerTargets = $true

$updatescope.ApprovedStates = [Microsoft.UpdateServices.Administration.ApprovedStates]::LatestRevisionApproved
$updatescope.ExcludeOptionalUpdates = $true
$updatescope.UpdateSources = [Microsoft.UpdateServices.Administration.UpdateSources]::MicrosoftUpdate

$d = Get-Date -format yyyy_MM_dd

$wsus.GetSummariesPerComputerTarget($updatescope,$computerscope) |
    Select-Object @{L='Computer'; E={($wsus.GetComputerTarget([guid]$_.ComputerTargetId)).FullDomainName}},
        @{L=’NeededCount’;E={($_.DownloadedCount +   $_.NotInstalledCount)}},DownloadedCount,NotInstalledCount,FailedCount,InstalledCount,NotApplicableCount | where {$_.NeededCount -gt 0} |
        Export-Csv -NoClobber -NoTypeInformation -Path S:\WSUS_Scheduled_Tasks\Needed_Updates\Report_$($d).csv

I read online and it says I need to put a where pipe on line 7, so I put this

$workstationsGroup = $wsus.GetComputerTargetGroups() | where {$_.Name -eq "ServerGroup"}

The report runs but it's still searching the entire WSUS and not just computers in that group.

Do I need to put the where statement somewhere else in the script?

Hello,

I think there might be an issue with downstream servers in server wsus 2019.

First I did update my main WSUS to 2019. All Downstream were 2016. After that I was not able to view the complete computer list on the main server. As soon as you choose the “All Computers” or a computer group that is from a downstream server the console crashes. When you delete the downstream server from the “Downstream Servers” section I am able to browse the list again.

After that I decided to reinstall all WSUS Servers with server 2019 even including the main one. And I did again get the error.

Tried it via Powershell gives me the following error.

$wsusserver = "localhost"
[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
$wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer($wsusserver,$False)
$computerScope = New-object Microsoft.UpdateServices.Administration.ComputerTargetScope
$computerScope.IncludeDownstreamComputerTargets = $true
$wsus.GetComputerTargets($computerScope)

Exception calling "GetComputerTargets" with "1" argument(s):"Unable to cast object of type 'System.Guid' to type 'System.String'."

At line:1 char:1

If I choose to not include Downstream Computer Targets it works.