Hello,  i have a WSUS upstream and downstream environment. The client machine are appearing in the upstream successfully.

I am testing client machine on 2012 R2, but when i approve a update with a deadline, the updates is not downloading and installing automatically. I have approve the updates as i can see it via the client machine when i run Check For Updates, but i thought i don't need to do this. for the WSUS registry, i have the following settings on the client side

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]

"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000000
"UseWUServer"=dword:00000001

1- Download critical and security update, approve them then send to them to the computers on the networks 

2- For every other updates, I want my client to open his windows update client, the client will connect to our server to check if there are updates needed. At that time, the downloads and installation will start. Please help

I think that if the updates are approved, they will be sent straight to our clients, i don't want that I want my client  to ask for updates. 

Please help. I want to follow the approve update procedure with deadline set against the approval updates

I have a fully updated WSUS server running on 2012 R2 which correctly shows Windows 10 clients when logged onto the WSUS box itself.

From Windows 8/8.1 the Windows 10 clients show as Windows Vista and I cannot find a Windows Update that seems to address this on Windows 8, only the update for Windows Server 2010 R2.

Any suggestions please?

In the console of WSUS into a Windows server 2008 R2, i have any clients in different version XP, 7, 8 and now 8.1 but for this client version 8.1 WSUS report a wrong version Windows 6.3 like first with Windows 8 --> 6.2

Microsoft resolved the problem for wrong version in WSUS console for Windows 8 and 2012 server, but the problem appear again with 8.1 and 2012 R2.

I'm afroid because this issue is know since Windows 8.1 preview exist...

I think there is a bug that not resolved by Microsoft because i have installed the last KB for WSUS : Version
3.2.7600.262

Also i googlelised this problem during 1 hour but i find nothing on this issue ?!  If in a Deutsch forum but anyone find an answer...

Thanks for your help.

I'm facing severe performance issues on the WSUS server after deploying KB3159706 AND following all the steps in https://support.microsoft.com/en-us/kb/3159706 except for the web.config part as we do not use HTTPS.

The Windows Internal Database and IIS Worker Process are taking up almost 100% of CPU all the time and around 70% of RAM.

This server has always been very stable with less than 70% RAM and idle CPU most of the time.

I noticed also this warning in the even log (#12 - Unable to find schema for config section 'system.xaml.hosting/httpHandlers'. This section will be ignored.)

Please advise

Hello,

I am attempting to install WSUS on a Windows Server 2012 R2 Standard box.  I'm a little worried as when I was installing WSUS through server manager it didn't seem to indicate a way to install updates offline.  The server I am configuring is to be completely offline and manages a small portion of offline PCs w/ AD.  Configuring such a server without Internet access has been challenging to say the least.

Is it even possible, with this version of WSUS, to upload Microsoft updates manually to then have WSUS disperse out the PCs in the offline AD environment?  It's looking like it may not be possible and I may have to try going with a 3rd party vendor such as BigFix.  Thank you for your help.

We are running a few hundred PC's on our Network, we are distributing a new set of windows 7 PC's some of which do not look as though they are getting updated.

The WSUS Update service recognizes the PC's as Not yet Reported, they are imaged without sysprep but some of the machines are updating just fine.

I have tried everything I could find on the internet and checked every setting I could but I am new to WSUS.

Here is some of the Windowsupdate.log

2016-07-14                    09:58:09:199                1220           998              AU                 #############

2016-07-14                    09:58:09:199                1220           998              AU                 ## START ##  AU: Search for updates

2016-07-14                    09:58:09:199                1220           998              AU                 #########

2016-07-14                    09:58:09:199                1220           998              AU                 <<## SUBMITTED ## AU: Search for updates [CallId = {7A0F6DC4-E5A1-4186-A7E2-C5BD61173FD2}]

2016-07-14                    09:58:09:199                1220           c50               Agent           *************

2016-07-14                    09:58:09:199                1220           c50               Agent           ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

2016-07-14                    09:58:09:199                1220           c50               Agent           *********

2016-07-14                    09:58:09:199                1220           c50               Agent             * Online = Yes; Ignore download priority = No

2016-07-14                    09:58:09:199                1220           c50               Agent             * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"

2016-07-14                    09:58:09:199                1220           c50               Agent             * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

2016-07-14                    09:58:09:199                1220           c50               Agent             * Search Scope = {Machine}

2016-07-14                    09:58:09:215                1220           c50               Setup           Checking for agent SelfUpdate

2016-07-14                    09:58:09:230                1220           c50               Setup           Client version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161

2016-07-14                    09:58:11:882                1220           c50               Misc             Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:

2016-07-14                    09:58:16:562                1220           c50               Misc             Microsoft signed: NA

2016-07-14                    09:58:16:578                1220           c50               Misc             WARNING: Cab does not contain correct inner CAB file.

2016-07-14                    09:58:16:578                1220           c50               Misc             Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:

2016-07-14                    09:58:16:578                1220           c50               Misc             Microsoft signed: NA

2016-07-14                    09:58:16:578                1220           c50               Setup           Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.

2016-07-14                    09:58:16:578                1220           c50               Setup           Skipping SelfUpdate check based on the /SKIP directive in wuident

2016-07-14                    09:58:16:578                1220           c50               Setup           SelfUpdate check completed.  SelfUpdate is NOT required.

2016-07-14                    09:58:17:327                1220           c50               PT                  +++++++++++  PT: Synchronizing server updates  +++++++++++

2016-07-14                    09:58:17:327                1220           c50               PT                    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://our_Server/ClientWebService/client.asmx

2016-07-14                    09:58:17:420                1220           c50               PT                  WARNING: Cached cookie has expired or new PID is available

2016-07-14                    09:58:17:420                1220           c50               PT                  Initializing simple targeting cookie, clientId = e468e36a-5502-4434-b6fa-fbbe41e2efea, target group = User Computers, DNS name = devonj1.celgar.com

2016-07-14                    09:58:17:420                1220           c50               PT                    Server URL = http://our_Server/SimpleAuthWebService/SimpleAuth.asmx

2016-07-14                    09:59:19:170                1220           c50               Misc             WARNING: Send failed with hr = 80072ee2.

2016-07-14                    09:59:19:170                1220           c50               Misc             WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>

2016-07-14                    09:59:19:170                1220           c50               Misc             FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2

2016-07-14                    09:59:19:170                1220           c50               PT                    + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0

2016-07-14                    09:59:19:170                1220           c50               PT                    + Caller provided credentials = No

2016-07-14                    09:59:19:170                1220           c50               PT                    + Impersonate flags = 0

2016-07-14                    09:59:19:170                1220           c50               PT                    + Possible authorization schemes used =

2016-07-14                    09:59:19:170                1220           c50               PT                  WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200

2016-07-14                    09:59:19:170                1220           c50               PT                  WARNING: PTError: 0x80072ee2

2016-07-14                    09:59:19:170                1220           c50               PT                  WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2

2016-07-14                    09:59:19:170                1220           c50               PT                  WARNING: Sync of Updates: 0x80072ee2

2016-07-14                    09:59:19:170                1220           c50               PT                  WARNING: SyncServerUpdatesInternal failed: 0x80072ee2

2016-07-14                    09:59:19:170                1220           c50               Agent             * WARNING: Failed to synchronize, error = 0x80072EE2

2016-07-14                    09:59:19:170                1220           c50               Agent             * WARNING: Exit code = 0x80072EE2

2016-07-14                    09:59:19:170                1220           c50               Agent           *********

2016-07-14                    09:59:19:170                1220           c50               Agent           **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

2016-07-14                    09:59:19:170                1220           c50               Agent           *************

2016-07-14                    09:59:19:170                1220           c50               Agent           WARNING: WU client failed Searching for update with error 0x80072ee2

2016-07-14                    09:59:19:170                1220           15d8           AU                 >>##  RESUMED  ## AU: Search for updates [CallId = {7A0F6DC4-E5A1-4186-A7E2-C5BD61173FD2}]

2016-07-14                    09:59:19:170                1220           15d8           AU                   # WARNING: Search callback failed, result = 0x80072EE2

2016-07-14                    09:59:19:170                1220           15d8           AU                   # WARNING: Failed to find updates with error code 80072EE2

2016-07-14                    09:59:19:170                1220           15d8           AU                 #########

2016-07-14                    09:59:19:170                1220           15d8           AU                 ##  END  ##  AU: Search for updates [CallId = {7A0F6DC4-E5A1-4186-A7E2-C5BD61173FD2}]

2016-07-14                    09:59:19:170                1220           15d8           AU                 #############

2016-07-14                    09:59:19:170                1220           15d8           AU                 Need to show Unable to Detect notification

2016-07-14                    09:59:19:170                1220           15d8           AU                 Successfully wrote event for AU health state:1

2016-07-14                    09:59:19:170                1220           15d8           AU                 AU setting next detection timeout to 2016-07-14 21:59:19

2016-07-14                    09:59:19:170                1220           15d8           AU                 Setting AU scheduled install time to 2016-07-15 11:00:00

2016-07-14                    09:59:19:170                1220           15d8           AU                 Successfully wrote event for AU health state:1

2016-07-14                    09:59:19:170                1220           15d8           AU                 Successfully wrote event for AU health state:1

2016-07-14                    09:59:24:178                1220           c50               Report        REPORT EVENT: {68869BA1-E888-4BC0-8AB7-7271469FB81D}   2016-07-14 09:59:19:170-0700           1                    148              101              {00000000-0000-0000-0000-000000000000}              0                    80072ee2                       AutomaticUpdates     Failure                       Software Synchronization            Windows Update Client failed to detect with error 0x80072ee2.

2016-07-14                    09:59:24:178                1220           c50               Report        CWERReporter::HandleEvents - WER report upload completed with status 0x8

2016-07-14                    09:59:24:178                1220           c50               Report        WER Report sent: 7.6.7601.19161 0x80072ee2(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0

2016-07-14                    10:10:03:341                1220           c50               PT                  WARNING: Cached cookie has expired or new PID is available

2016-07-14                    10:10:03:341                1220           c50               PT                  Initializing simple targeting cookie, clientId = e468e36a-5502-4434-b6fa-fbbe41e2efea, target group = User Computers, DNS name = devonj1.celgar.com

2016-07-14                    10:10:03:341                1220           c50               PT                    Server URL = http://our_Server/SimpleAuthWebService/SimpleAuth.asmx

2016-07-14                    10:10:05:728                1220           c50               Report        Uploading 1 events using cached cookie, reporting URL = http://our_Server/ReportingWebService/ReportingWebService.asmx

2016-07-14                    10:10:05:728                1220           c50               Report        Reporter successfully uploaded 1 events.

Any Help would be great, thanks

Hi,

While addressing July 2016  monthly patching, I found sometyhing wrong with KB3170377. This was part of MS16-092

I checked in SCCM for this,  and it shows Superseded already?
Did Microsoft pulled this patch out or replaced with something else? screenshot link below:

https://s31.postimg.org/yqisilp23/KB3170377.jpg

Thanks,

Hi

In SBS 2011 domain I have pcs with varying levels of updates applied. Screen below. What do I need to do to get them all to 100%?

Thanks

Regards

Hi

SBS 2011 std.

In SBS Console its says 'Warning' under Update Status. Under computer properties->Updates it shows several updates that are 'Not installed' or 'Downloaded'.

How can I get rid of warnings for Update Status and get all OK?

Thanks

Regards

Attempting to install WSUS 3.0 SP2 on a Windows Server 2003 Enterprise system. I'm asking the setup to create a new database on one of our existing SQL Server 2005 systems. When the setup gets to the "configuring database" step it stops and throws "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." The two logs it suggests I look at are below. I'm not seeing any errors that mean anything to me.

Any direction you can give will be greatly appreciated.

WSUSSetup.log:

2009-12-04 15:26:21  Success   MWUSSetup          Validating pre-requisites...
2009-12-04 15:26:22  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2009-12-04 15:26:28  Success   MWUSSetup          No SQL instances found
2009-12-04 15:26:42  Success   MWUSSetup          Initializing installation details
2009-12-04 15:26:42  Success   MWUSSetup          Installing ASP.Net
2009-12-04 15:27:24  Success   MWUSSetup          ASP.Net is installed successfully
2009-12-04 15:27:24  Success   MWUSSetup          Installing WSUS...
2009-12-04 15:27:28  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
2009-12-04 15:27:28  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
2009-12-04 15:27:29  Success   CustomActions.Dll  .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
2009-12-04 15:27:33  Success   CustomActions.Dll  Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
2009-12-04 15:27:33  Success   CustomActions.Dll  Creating WSUS Reporters user group
2009-12-04 15:27:33  Success   CustomActions.Dll  WSUS Reporters user group already exists
2009-12-04 15:27:33  Success   CustomActions.Dll  Successfully created WSUS Reporters user group
2009-12-04 15:27:33  Success   CustomActions.Dll  Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
2009-12-04 15:27:33  Success   CustomActions.Dll  Creating WSUS Administrators user group
2009-12-04 15:27:33  Success   CustomActions.Dll  WSUS Administrators user group already exists
2009-12-04 15:27:33  Success   CustomActions.Dll  Successfully created WSUS Administrators user group
2009-12-04 15:27:33  Success   CustomActions.Dll  Successfully created WSUS user groups
2009-12-04 15:27:33  Success   CustomActions.Dll  Succesfully set binary SID property
2009-12-04 15:27:33  Success   CustomActions.Dll  Succesfully set binary SID property
2009-12-04 15:27:33  Success   CustomActions.Dll  Successfully set binary SID properties
2009-12-04 15:28:50  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
2009-12-04 15:28:50  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
2009-12-04 15:28:50  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
 

Snippet from bottom of WSUSSetupmsi_091204_1527.log:

Property(S): PIDRET = 0
Property(S): WUSADMIN_DESCRIPTION = WSUS Administrators can administer the Windows Server Update Services server.
Property(S): WSUS_REPORTERS_DESCRIPTIONS = WSUS Administrators who can only run reports on the Windows Server Update Services server.
Property(S): CUSTOM_WEBSITE = WSUS Administration
Property(S): PACKAGES_SHARE_DESCRIPTION = A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system.
Property(S): CONTENT_SHARE_DESCRIPTION = A network share to be used by Local Publishing to place published content on this WSUS system.
Property(S): WSUSTEMP_SHARE_DESCRIPTION = A network share used by Local Publishing from a Remote WSUS Console Instance.
Property(S): ALLCOMP_TG_NAME = All Computers
Property(S): ALLCOMP_TG_DESC = This target group provides default settings for all computer clients.
Property(S): UNASSIGN_TG_NAME = Unassigned Computers
Property(S): UNASSIGN_TG_DESC = Computers that are not members of a specific target group.
Property(S): DSS_TG_NAME = Downstream Servers
Property(S): DSS_TG_DESC = Downstream WSUS servers that are allowed to sync updates from this server.
Property(S): WSUS_REPORTERS_FULL = OURSERVERTPA\WSUS Reporters
Property(S): WUS_ADMINISTRATORS_FULL = OURSERVERTPA\WSUS Administrators
Property(S): LANGUAGE_ID = 1033
Property(S): COMPLETE_SQLINSTANCE = DELLSQL
Property(S): FRONTEND_MACHINE_NAME = OURDOMAIN\OURSERVERTPA$
Property(S): LARGEST_NTFS_DRIVE = C:\
Property(S): ROOTDRIVE = c:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): NetFxPath = C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Property(S): SOURCEDIR = c:\e3a290230374d0a80dc466e2\SUS\
Property(S): SourcedirProduct = {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
Property(S): WS_ACCOUNT_SID = 0105000000000005150000006A69AD55083B9BDD8399EF5CAF290000
Property(S): WUS_ADMINISTRATORS_SID = 0105000000000005150000002AE7CD661E90CABDBFC37FA2F7030000
Property(S): ProductToBeRegistered = 1
MSI (s) (58:7C) [15:28:49:860]: Note: 1: 1708
MSI (s) (58:7C) [15:28:49:860]: Product: Windows Server Update Services 3.0 SP2 -- Installation failed.

MSI (s) (58:7C) [15:28:49:875]: Cleaning up uninstalled install packages, if any exist
MSI (s) (58:7C) [15:28:49:875]: MainEngineThread is returning 1603
MSI (s) (58:78) [15:28:49:985]: Destroying RemoteAPI object.
MSI (s) (58:90) [15:28:49:985]: Custom Action Manager thread ending.
=== Logging stopped: 12/4/2009  15:28:49 ===
MSI (c) (30:54) [15:28:50:016]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (30:54) [15:28:50:016]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/4/2009  15:28:50 ===

Hi! I hope someone can throw me idea about my problem, so...

We have server 2012 R2 with WSUS - version 6.3.9600.17477. 

Clients windows 10 Pro. 

SCCM 2012 R2 - bits is not configured in default client policy.

GPO configured and policy applied successfully. Registry on clients says:

Problem Updates are not throttling and go in full speed. It's not on all clients, but quite lots of them. WSUS not running in foreground mode. 

I something misconfigured? 

Thanks,

Ronald

Hi There,

WSUS seems to have failed on my Server 2012 R2 server and I can't remove it. Any manual removal technique that I can use?  See the below image.

I have two offline WSUS 3.0 which both are failing to download patch since June 20th.  I have tried everything I can find from the web and still getting the "fail download some update" error.

I export the package from the edge WSUS and import to my offline one without and issue.

The event id in the application log is 10032.

Please help......

Hello, 

I am trying to import SQL Server Cumulative Updates into WSUS on Windows Server 2012 R2. In WSUS, I have all of the SQL products selected, as well as all of the classifications (feature packs, updates, service packs, etc.) selected.

When I try to import the Cumulative Updates (Like KB3144517) into WSUS, the "Import" button is greyed out and I get the error "This update cannot be imported into Windows Server Update Services, because it does not have the required applicability information."

Is there anything I may have misconfigured on my end, or a solution to fix this problem?

Thank you

Symptom: WSUS Clients detect updates but will not download them after moving content folder to network share.  Error in EventViewer and WindowsUpdate.log is WSUS Content folder not found.

Assuming a working WSUS setup using local WsusContent before beginning these steps.

I wanted to share my WSUS conversion solution switching from local storage to a network share to prove it is it possible. I also moved my SUSDB database to a SQL Cluster, but that should not be required to move the Content folder.

• First, copy the WsusContent folder to your network share MANUALLY.
• for me it wasd:\WsusContent to \\backup\Windows_Updates\WsusContent
  

• Run WSUS Postinstall again. My example is:
  

go to directory where wsusutil is:  cd "\Program Files\Update Services\Tools"

Run command: 

wsusutil postinstall content_dir=\\backup\Windows_Updates  sql_instance_name=sql\db  (this is my SQL cluster)

At this point WSUS clients can check for and discover updates but not download them. The next steps fix downloading of updates.

• Next edit the registry: HKLM\System\CurrentControlSet\Services\LanmanServer\Shares\WsusContent ChangeWsusContent REG_MULTI_SZ from D:\WsusContent to \\Backup\Windows_Updates\WsusContent  

•  In the same place, ChangeUpdateServicesPackages to new location as well. Mine was \\Backup\Windows_Updates\UpdateServicesPackages

• The postinstall not only missed the registry changes above, it also messes up the IIS Content virtual directory.  To fix, open IIS Manager, expand Sites, find site with Content folder. Right-click Content, Manage virtual directory, Advanced Settings and change Physical Path to \\backup\windows_updates\wsusContent\ – The leading backslashes were missing on mine.

• In this same spot, also set permissions to the network share to use proper credentials, I used domain admin.  Right click Content -> Manage Virtual Directory -> Advanced Settings…   Physical Path Credentials, click “…” on right side.  Select specific user, click Set… add something you know will work on the network share.

• Reboot WSUS server and updates should start downloading to clients.

I have a computer that was added to the domain a couple of months ago, but no matter what I do it will not show up in the WSUS.  I have tried so many things that were recommended both on this and other websites that I have lost count.  Does anyone have a sure fire way to force a pc to show up on the WSUS?

The computer is covered by a GPO that should have it checking the WSUS at least daily (at 3:00am), but it does not.  Out of 115 computers, this is the only one with a problem.  I have tried forcing it to report, resetting it, etc.

Please help!  Thank you in advance for your assistance.

Rebecca Palmer