Hi All,

Question for you, if I decline an update on WSUS, which may have previously been installed - does marking it as "declined" automatically enable the "approved for removal" option, and subsequently remove it automatically from any workstations connected to it?

Thanks

James

I am installing 1803 so far I have had 18 sections (?) installed.  How man more to go?

WSUS server windows 2008 R2 STD

wsus Version: 3.2.7600.226

Windows 10 clients are not taking update from wsus server

Can some one help me?

The .net Framework updates for July broke BizTalk.  It happens.

Around July 31st Microsoft released updates to resolve this issue.  When I try to import KBs 4346877 and 4346406 into a Windows 2016 WSUS Server, I get the Error "This Update cannot be imported into Windows Server Update Services because it is not compatible with your version of WSUS." for the Windows 10, Windows Server 2016, and Windows Server 2012 R2 versions of the KBs. 

In other messages in this forum, there is a workaround by changing your protocol to 1.80 instead of the default 1.20.  If I had used the Sync function of the WSUS Server instead of manually trying to import the updates I would never had know these updates were released.

My question is "How do we determine what updates needs to be imported in the Windows 2016 Server using the alternate protocol instead of the normal sync process?"

I would like to use the WSUS Server that ships with Windows Server 2016 because it handles Windows 2016 and Windows 10 Clients better than the WSUS Server that ships with Windows Server 2012 R2.  However, if the Windows 2016 WSUS Server does not Sync all the updates and I can't even determine which updates need to be "Imported", then my server environment is missing critical security updates which I can't have. 

Server 2003 R2 Standard SP2 x64
WSUS 3.0 SP2
Kaspersky Endpoint Security 10

Recently, the synchronizastions is failed suddenly this month as it worked successfully every month before.

Image may be NSFW.
Clik here to view.

Tried Clenup Wizard and it worked successfully
Tried uninstall and reinstall it.
Internet access is normal.
Kaspersky Endpoint Security 10 is installed long time and didn't upgrade or change anything.
Have own firewall but didn't change anything recently
Run windows update manually worked.

At server application log, got these Error and warning
Error, Source: Windows Server Update    Event ID: 13042   Self-update is not working.
Warning, Source: Windows Server Update    Event ID: 13051  No client computers have ever contacted the server.
Error, Source: Windows Server Update    Event ID: 10022  The last catalog synchronization attempt was unsuccessful.

Then we tried reinstalled WSUS and clear d:\wsus <folder>. Synchronizastions are okay at initial stage but it is failed again.

Q1: What's wrong with it?  Tried the solution that found here but no luck to solve it.  Please help.
Q2: Since WUSUS is reinstalled, will clients receives new udpate only?

Hi All, 

net stop bits
net stop wuauserv
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"/v AccountDomainSid /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"/v PingID /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"/v SusClientId /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"/v SusClientIDValidation /f
rd /s/q"C:\Windows\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization/detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

Hello,

I'm having difficulty establishing a connection in the WSUS  console.  When I start WSUS, I can see my WSUS server listed, but when I select it, the connection seems to time out and I'm face with the error message: Error: Connection Error. I'm giving the option to 'reset server node'.

Event ID 7053 is shown (see below).  The services are running and I've tried deleting the MMC file as suggested.  

Anyone got any advice on this, or is there any other Logs I can look at/post in relation to this?  The server is running On 2008 R2.

Many thanks

Hi

version : WSUS 2016

DB: SQL Express 2017

we installed the WSUS 2016

But when running the report I'm getting the below error even installed the ""Microsoft Report viewer 2015  Runtime "

Please advise

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Help.Me

Hi all,

we are using a WSUS Cluster in our Company with Win10 (Build 1607-1803) clients. We are also using Office 365.

As our WSUS Admin I am facing a few problems regarding the WSUS GPO for the Clients... 

What we want to be configured in our Environment:
-NO automated Win10 Upgrade without me approving it for the clients
-No automated reboot of the clients after installing Updates

-Only check for updates from the WSUS Server
-Allow using the Microsoft Store and all its Apps in Win10
-Allow Windows Activation
-Allow downloading oder .NET Versions.

The Settings I've made in our WSUS Client GPO (Sorry for the wrong wording, it's in German on my System):
Activated: Deactivate automatic reboot whil user is working 7AM-7PM
Activated: Configure Automatic Update - 3. Download automatically but inform user
Activated: Intern Path to WSUS Server - Both paths pointing to our WSUS Server
Activated: Search interval - Every 3h
Activated: Do not connect to the Windows Update Internet Addresses
Activated: Do not make a planed reboot while the user is logged in
Activated: Client Targeting
Disabled: Install Updates immediately 
Rest is unconfigured.

So here is the problem I have. With the GPO settings above the users are not able to download and use apps from the Win10 App store. It shows a connection issue. Also you can't use Microsoft installation wizard e.g. for .net installation. AND I can't activate my windows! It shows me an connection error and asks me to try again later. When I disable the GPO everything works fine.

The Problem seems to be the setting in "Do not connect to the Windows Update Internet Addresses". This activated seems to block every connection to MS, even such deep system critical services like Windows activation... 
The reason I activated this is historically from Win7, where when disabled the user could click in the windows update control panel on "Check online for MS Updates". I do not want the User or Win10 itself be able to download an Win10 Upgrade WITHOUT me approving it for our Clients.

Can someone explain what I have to change for this to work the way I need it?
Thank you in advance

Regards
Mike

Hi

I install new vm win2012 r2 server with WSUS rule

and when the rule installation finish I  open the wsus and start configuration  and I get this error in the post installation "Post install is starting Fatal Error: WsusPool does not exist "

I try to remove the rule and install again and- the error still occurred

I try to change location  and give full permission -the error still occurred

I try to install all update that I found in windows update-the error still occurred

with this log , I can`t figure way its happened and how to fix it

2017-01-12 16:35:54  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spDeleteComputer'. The module will still be created; however, it cannot run successfully until the object exists.
2017-01-12 16:35:54  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2017-01-12 16:35:54  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.

2017-01-12 16:39:26  Configuring website on port 8530
2017-01-12 16:39:46  System.InvalidOperationException: WsusPool does not exist
   at Microsoft.UpdateServices.Administration.UseCustomWebSite.GetWsusPool()
   at Microsoft.UpdateServices.Administration.UseCustomWebSite.InstallAndConfigure(IisConfiguration& iisConfiguration, Int32 newPortNumber)
   at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

I would like to install WSUS on a Windows 2016 domain controller.  I have read an article recommending not to do that on Windows 2008 or 2012 domain controller,

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff646928(v=ws.10)

Does this apply to 2016 as well?  My particular DC is actually a BDC and serves no other roles.  If I decide to go ahead and install it anyway, what would be the impact?

Thanks,

Hi there,

I'm trying to reinstall WSUS on my SCCM server (2012 R2) as a SQL db instead of WID. I inherited it this way. No matter what I try, the post-install tasks bomb out with this error:

2018-08-08 12:08:16  Postinstall started
2018-08-08 12:08:16  Detected role services: Api, Database, UI, Services
2018-08-08 12:08:16  Start: LoadSettingsFromParameters
2018-08-08 12:08:16  Content local is: True
2018-08-08 12:08:16  Content directory is: D:\Windows Server Update Service
2018-08-08 12:08:16  SQL instname is: GAMBIT
2018-08-08 12:08:16  End: LoadSettingsFromParameters
2018-08-08 12:08:16  Start: Run
2018-08-08 12:08:16  Fetching WsusAdministratorsSid from registry store
2018-08-08 12:08:16  Value is S-1-5-21-1355483703-2602408213-1168805140-1004
2018-08-08 12:08:16  Fetching WsusReportersSid from registry store
2018-08-08 12:08:16  Value is S-1-5-21-1355483703-2602408213-1168805140-1005
2018-08-08 12:09:15  Configuring content directory...
2018-08-08 12:09:15  Configuring groups...
2018-08-08 12:09:15  Starting group configuration for WSUS Administrators...
2018-08-08 12:09:15  Found group in regsitry, attempting to use it...
2018-08-08 12:09:18  Writing group to registry...
2018-08-08 12:09:18  Finished group creation
2018-08-08 12:09:18  Starting group configuration for WSUS Reporters...
2018-08-08 12:09:18  Found group in regsitry, attempting to use it...
2018-08-08 12:09:18  Writing group to registry...
2018-08-08 12:09:18  Finished group creation
2018-08-08 12:09:18  Configuring permissions...
2018-08-08 12:09:18  Fetching content directory...
2018-08-08 12:09:18  Fetching ContentDir from registry store
2018-08-08 12:09:18  Value is D:\Windows Server Update Service
2018-08-08 12:09:18  Fetching group SIDs...
2018-08-08 12:09:18  Fetching WsusAdministratorsSid from registry store
2018-08-08 12:09:18  Value is S-1-5-21-1355483703-2602408213-1168805140-1004
2018-08-08 12:09:18  Fetching WsusReportersSid from registry store
2018-08-08 12:09:18  Value is S-1-5-21-1355483703-2602408213-1168805140-1005
2018-08-08 12:09:18  Creating group principals...
2018-08-08 12:09:18  Granting directory permissions...
2018-08-08 12:09:18  Granting permissions on content directory...
2018-08-08 12:09:18  Granting registry permissions...
2018-08-08 12:09:18  Granting registry permissions...
2018-08-08 12:09:18  Granting registry permissions...
2018-08-08 12:09:18  Configuring shares...
2018-08-08 12:09:18  Configuring network shares...
2018-08-08 12:09:18  Fetching content directory...
2018-08-08 12:09:18  Fetching ContentDir from registry store
2018-08-08 12:09:18  Value is D:\Windows Server Update Service
2018-08-08 12:09:18  Fetching WSUS admin SID...
2018-08-08 12:09:18  Fetching WsusAdministratorsSid from registry store
2018-08-08 12:09:18  Value is S-1-5-21-1355483703-2602408213-1168805140-1004
2018-08-08 12:09:18  Content directory is local, creating content shares...
2018-08-08 12:09:18  Creating share "UpdateServicesPackages" with path "D:\Windows Server Update Service\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2018-08-08 12:09:18  Creating share...
2018-08-08 12:09:18  Share successfully created
2018-08-08 12:09:18  Creating share "WsusContent" with path "D:\Windows Server Update Service\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2018-08-08 12:09:18  Creating share...
2018-08-08 12:09:18  Share successfully created
2018-08-08 12:09:19  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2018-08-08 12:09:19  Creating share...
2018-08-08 12:09:19  Share successfully created
2018-08-08 12:09:19  Finished creating content shares
2018-08-08 12:09:19  Stopping service WSUSService
2018-08-08 12:09:19  Stopping service W3SVC
2018-08-08 12:10:49  Configuring database...
2018-08-08 12:10:49  Configuring the database...
2018-08-08 12:10:49  Establishing DB connection...
2018-08-08 12:10:49  Checking to see if database exists...
2018-08-08 12:10:49  Database does not exist
2018-08-08 12:10:49  Loading install type query...
2018-08-08 12:10:49  DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (9600)
DECLARE @scriptMinorVersion     int = (18694)
DECLARE @databaseMajorVersion   int 
DECLARE @databaseMinorVersion   int 
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return 
    END 
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END

2018-08-08 12:10:49  Install type is: Fresh
2018-08-08 12:10:49  Creating database...
2018-08-08 12:10:50  Msg 5105, Level 16, State 2, Server GAMBIT,  Line 2
A file activation error occurred. The physical file name 'D\:Database\SUSDB.mdf' may be incorrect. Diagnose and correct additional errors, and retry the operation.Msg 1802, Level 16, State 1, Server GAMBIT,  Line 2
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2018-08-08 12:10:50  Re-Establishing Connection to execute Multi User Query ...
2018-08-08 12:10:50  Ensuring SUSDB is set to Multi-User Mode ...
2018-08-08 12:10:50  Microsoft.UpdateServices.Administration.CommandException: Database creation failed
   at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDatabase()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal)
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

I've uninstalled WSUS (including WID), made sure the WSUScontent folder and SUSDB/SUSDB.log are detached and gone, deleted the IIS site. Pretty much everything at these two Answers:

https://social.technet.microsoft.com/Forums/ie/en-US/c7a6f2d6-2e4d-437b-a104-03328c146d4a/wsus-post-deployment-tasks-configuration-failed?forum=winserverwsus

https://social.technet.microsoft.com/Forums/office/en-US/74c48550-52f6-4160-b8a6-67fc4e6eab79/wsus-post-install-fails-quotfatal-error-the-system-cannot-find-the-path-specifiedquot?forum=winserverwsus

This is my first time configuring WSUS/SCCM. Help?

I have a Windows Server 2016 with WSUS installed on it. I am having a lot of issues. I am wondering if there is this many issues or one big patch I need. 

Event Log:

7032, 12072, 12052, 12042, 12032, 12022, 12002, 10032, and 13042

I have the database on the system drive. I have uninstalled and reinstall the Roll. 

I have clients I have physically verified are 100% up to date but no matter what command I use I can not get them to report. They see the update server and they browse the IIS folder they just do not report status. All PCs are 99% except 5 which are 5% and 3 of those are current just reporting. I have approved all updates possible. I have done the WSUS cleanup, 

The server will stay up for about 2 hours then just crash. I have to run IISReset to get it back. 

What am I missing here?

We've been running WSUS on Windows Sever 2012 R2 for a while now and I haven't approved ANY "Upgrades" to Windows 10.  Despite that, I have a Windows 10 Enterprise system running build 1709 that has decided to force an upgrade to 1803.  If you look at this system in WSUS there is no record of the 1803 upgrade even applying to this system.

Thus far I haven't been using the defer option at all, I just simply don't approve "upgrades" in WSUS until we are ready.  This seems to have worked great except with this one 1709 system.  Any idea what is going on here?

Hi all- After updating Windows 10 clients to 1803, KB4338819 is showing in my WSUS console as needed. If you check from a client PC, it reports it is up to date. If I install the update manually on a workstation, it reports in to our SUS server and then that PC is 100%. Any ideas here? The update is approved for install on both my staging/test group and production group.

Thanks!

I want to get updates from only wsus.

But when i watch windows update log, 
there are lot of log like below.

2018/01/15 09:04:36.1520630 7364  6424  SLS             [0]1CC4.1918::01/15/2018-09:04:36.152 [sls]Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.15063.0/0?CH=796&L=ja-JP&P=&PT=0x30&WUA=10.0.15063.726&MK=Dell+Inc.&MD=XPS+13+9350

My computer downloaded from windows update.

My wsus register settings are below.

Is there any mistake?

Please help me and sorry about terrible english.

Image may be NSFW.
Clik here to view.

Hello Friends,

We have WSUS version 6.3.9600.18694 installed and we have client computers with Windows 10 & Windows 7

We have set  the GPO as auto download and schedule to install for client machine on every week.

But our problem is that our windows 10 machines are not getting any notification for install updates or restart.

Seeking your help in this.

Regards,

Sapan Shah

Hi ,

We're trying to reinstall our WSUS server on server 2012 and pointing the Content Folder on a shared drive.

However the WSUS was not able to download updates.

There are error generated whenever we tried to run "Synchronize now" on the WSUS console.

Error ID: 364 

Is it possible on this WSUS version to use a shared folder for WSUS content?

Thanks and God bless!

Regards,
Stephen

Having some issues installing 1803 on Win 10 machines via a 2012 WSUS Server.

We have 2012R2 and 2016 WSUS Servers which seem to be fine and all clients are updating via these, but a few sites have a 2012 WSUS Server and all appear to fail with 0x8000FFFF.

I've confirmed the KB is installed that allows 2012 to cater for Win 10 feature upgrades, ran the <g class="gr_ gr_17 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="17" id="17">postinstall</g> /servicing (and restarted WSUS), and added the .esd MIME type to IIS.

Pointing a machine on this site to update via one of our 2016 servers allows the update to be installed as expected, so this only appears to be an issue with 2012.

Any ideas?

On a Server 2008 R2 SP1 with WSUS 3.0 SP2, after disabling TLS 1.0, the synchronizations fail with Microsoft Update Servers. The error message is long, but basically says: “The client and server cannot communicate, because they do not possess a common algorithm”. Event Viewer shows Event ID 10022 for WSUS and Event ID 36871 for Schannel (both vague).

TLS 1.1 and 1.2 are enabled in the registry. I have tried various .net updates/solutions. I tried to install KB3154518 - Support for TLS System Default Versions included in the .NET Framework 3.5.1 on Windows 7 SP1 and Server 2008 R2 SP1 but that update says it is not applicable to the OS (and not even sure if it affects .net 2). I did add the registry keys associated with KB3154518 and I added the registry keys for SchUseStrongCrypto.

I can check for updates via Windows Updates through the Control Panel, and that works. If I approve an update that had been previously synced the download does complete. Workstation clients work as expected (HTTP port 80). The only problem is synchronizations with Microsoft Update servers within WSUS console. WSUS build is 3.2.7600.283.

Is it possible, and if so, what steps are required to have WSUS 3.0 SP2 work properly with TLS 1.0 disabled on a 2008 R2 server?