Problem with windows server 2012 R2 and 2016 getting updates from WSUS.

Today is the day after patch Tuesday and our WSUS console shows many updates for both 2012 R2 and 2016 server.   Once on either server there are no updates from WSUS.   Both 2012 R2 and 2016 show 0 updates.   Then we can choose check online for windows updates and there are many updates.    so it seems like there is a disconnect happening for 2012 r2 and 2016 server.   we are not halving this problem with windows 7 and windows 10

Jeff Tresnak

Hi together,

we want to upgrade Windows 7 Prof (SP1) to Windows 10 using WSUS.

How to proceed?

The "Upgrade from Win 7 to Win 10, Version 1803, de-de x64" (KB 3012973) should be the right paket.

Software\Policies\Microsoft\Windows\WindowsUpdate\DisableOSUpgrade is set to 0

SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\AllowOSUpgrade is set to 1.

Should this be possible in general?

I am not sure because Windowsw 7 is on actual patch level...

Neither WSUS means that there is a pending installation nor is there any available update on the client.

Thanks for help

Gernot

Greetings/Grüße Gernot

 Current my CAS and Primary on WSUS 3.0 SP2 , once i rebuild secondary with 2016 OS with WSUS 10.0 does this communicate with my primary WSUS 3.0 ?  

nash525

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.

Hi,

is it a perhaps a bug in Windows Server 2019?!

We have Group Policy for Windows Updates and use in our infrastracture WSUS. According to Group Policy, the updates will be downloaded to the system, and then an administrator will install the downloaded updates.

We tested Windows Updates onsome  Windows Server 2019 machines.

If the click "Check for updates", then the updates will be downloaded and automatically installed!!! That is fatal!

If I check "View configured update policy", then our policy are listed for the updates. It seems all are correct.

Image may be NSFW.
Clik here to view.

What is the issue here? A bug?

Best regards

Birdal

I am trying to connect to WSUS server remotely from my web application built in ASP.NET Core 2.0. I am using the Microsoft.UpdateServices.Administration.dll to achieve this. I was able to establish successful connection to the server when I built a C# console application and used the same dll file in assembly reference. 

Below is the sample code from the console app which worked:

using System;
using System.Reflection;
using Microsoft.UpdateServices.Administration;

namespace WsusRemoteConnectivityConsoleApp
{
  class Program
  {
      static void Main(string[] args)
      {
         IUpdateServer remoteServer = 
         AdminProxy.GetUpdateServer("WsusServer1",false,8530);
         Console.WriteLine(remoteServer.Name);
      }
  }
}

The expected output as well as the actual output in the console app is "WsusServer1".

But using the same line of code in the web app, I am not able to connect to the WSUS server. I receive exception saying that "The requested security protocol is not supported" in this lineIUpdateServer remoteServer = AdminProxy.GetUpdateServer("WsusServer1",false,8530);

Any help is appreciated. Thanks.

Hi,

I am trying to find the date/time when update(s) were install on certain PCs. 

I approved 4 updates on April/10 targeting a certain group in WSUS.

The GPO for that group is set as follows which means the install will trigger on April/12 Friday at 8:00pm approx?

Image may be NSFW.
Clik here to view.

What I have noticed that some of the PC's in this WSUS group have 2 updates already installed and other two show the status Downloaded.  I am thinking the status should be Downloaded for ALL 4 updates and the install should trigger based on the GPO on April/12 around 8:00pm.

 See below..

Image may be NSFW.
Clik here to view.

I am trying to find the date/time when these 2 updates were installed?

Thank you

hello,

I am having issues with WSUS on Windows 2019 and Win 10 Clients so I setup a very clean lab in Azure.

I setup a 2019 DC, 2019 WSUS box and a Windows 10 client in azure.

I installed wsus got it setup and syncing, AD setup and a GPO that turns on Automatic updates and points the update service to the wsus box.

the win 10 client fails to connect back to wsus with the following error... what am I missing?

WS failing to talk to it... diag tools reports.. GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

2019/04/12 20:37:45.6345097 3808  7648  Misc            Got WSUS Client/Server URL:http://win2k19wsus/ClientWebService/client.asmx""
2019/04/12 20:37:45.6399281 3808  7648  Driver          Skipping printer driver 3 due to incomplete info or mismatched environment - HWID[(null)] Provider[Microsoft] MfgName[Microsoft] Name[Remote Desktop Easy Print] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
2019/04/12 20:37:45.6399336 3808  7648  Driver          Skipping printer driver 6 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
2019/04/12 20:37:46.1130568 3808  7648  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =http://win2k19wsus/ClientWebService/client.asmx
2019/04/12 20:37:46.1132251 3808  7648  ProtocolTalker  PT: Calling GetConfig on server
2019/04/12 20:37:46.1132330 3808  7648  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 50; does use network; is at background priority
2019/04/12 20:37:46.1132580 3808  7648  WebServices     Auto proxy settings for this web service call.
2019/04/12 20:37:47.7064490 3808  7648  WebServices     WS error: There was an error communicating with the endpoint at 'http://win2k19wsus/ClientWebService/client.asmx'.
2019/04/12 20:37:47.7064512 3808  7648  WebServices     WS error: The server returned HTTP status code '404 (0x194)' with text 'Not Found'.
2019/04/12 20:37:47.7064526 3808  7648  WebServices     WS error: The requested resource was not found.
2019/04/12 20:37:47.7064555 3808  7648  WebServices     *FAILED* [80244019] Web service call
2019/04/12 20:37:47.7064565 3808  7648  WebServices     Current service auth scheme=0.
2019/04/12 20:37:47.7068531 3808  7648  WebServices     Current Proxy auth scheme=0.
2019/04/12 20:37:47.7068661 3808  7648  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 50) stopped; does use network; is at background priority
2019/04/12 20:37:47.7068729 3808  7648  ProtocolTalker  *FAILED* [80244019] GetConfig_WithRecovery failed
2019/04/12 20:37:47.7068749 3808  7648  ProtocolTalker  *FAILED* [80244019] RefreshConfig failed
2019/04/12 20:37:47.7068772 3808  7648  ProtocolTalker  *FAILED* [80244019] RefreshPTState failed
2019/04/12 20:37:47.7068808 3808  7648  ProtocolTalker  SyncUpdates round trips: 0
2019/04/12 20:37:47.7068822 3808  7648  ProtocolTalker  *FAILED* [80244019] Sync of Updates
2019/04/12 20:37:47.7068918 3808  7648  ProtocolTalker  *FAILED* [80244019] SyncServerUpdatesInternal failed
2019/04/12 20:37:47.7266841 3808  7648  Agent           *FAILED* [80244019] Synchronize
2019/04/12 20:37:47.8072050 3808  7648  Agent           * END * Finding updates CallerId = UpdateOrchestrator, Id = 9, Exit code = 0x80244019 (cV = Q8VCXHsTGk+2k/2h.1.1.0.0.2)
2019/04/12 20:37:47.8083798 3808  7648  IdleTimer       WU operation (CSearchCall::Init ID 9, operation # 49) stopped; does use network; is not at background priority
2019/04/12 20:37:47.8203778 4948  7136  ComApi          *RESUMED*   Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = Q8VCXHsTGk+2k/2h.1.1.0.0)
2019/04/12 20:37:47.8213255 4948  7136  ComApi          Exit code = 0x00000000, Result code = 0x80244019 (cV = Q8VCXHsTGk+2k/2h.1.1.0.0)

Although I have a GPO set with Auto Updating set to 4- Auto download and schedule the install, the 2016 servers are not auto installing these update or if they do install, they are not rebooting, so I am force to logon and kick off the install.

The WSUS Server is a Windows 2012 R2 Server and all other clients seem in install and reboot per the GPO.

Please advise,

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?

I realize thet my question can sound strange as is not strictly related to WSUS.

My question is related to Microsoft updates instead.

A customer implemented a custom solution to manage updates by creating a background process that executes updates, either for their custom applications and for Windows updates.

When they attempt to execute a Microsoft Windows update the update fails and in the logs they see the following eror:

WARNING: AU found no suitable session to launch client in

If they exectute the same update in the same server manually everything works fine and the log reports a line like:

Launched new AU client for directive 'Reboot Pending', session id = 0x2

The background process is executed as Administrator so I don't think there is any authorization issue.

So the question is: how can they confngure theyr background process in order to make AU available to the update they want to run?

Or, how can they confngure their service in order to launch the Windows Update in a way compatible to the execution in a background context?

Regards

Mario

I am looking to see what other WSUS admin's are doing in regards to being able to deploy BIOS updates and the latest driver updates to their machines (Intel, Display, RST ...)

WSUS does not seem to be able to accomplish this goal.

Thanks

Hi,

I'm struggling to figure out why my wsus clients aren't reporting in on a regular basis. They seem to only report in if I execute a manual check for updates on the device itself. I have the following GPO set, I'm not sure what else I'm missing.

Computer Configuration/Policies/Administrative Templates/Windows Components/Windows updates/Policy

- Automatic Updates detection frequency --> 22hours

- Configure Automatic Updates --> 3 - Auto download and notify for install

- Specify intranet Microsoft update service location

   - Set the intranet update service for detecting updates (http://[internalwsus]:8530)

   - Set the intranet statistics server (http://[internalwsus]:8530)

I know my intranet settings are valid since the servers to register initially but for whatever reason none of them check within the 22 hour interval. I've left some devices go for several days with no update so I don't think it's a matter of me not letting WSUS do it's thing....

Client: Windows 2016

WSUS Server: Windows 2016

Any advice would be appreciated!

please find the error code which have been coming frequently...if any one have resolution please help me out.

Hello,

When you install the update from Windows update KB4489878 fails and installs it. (Windows server 2008 R2)

The error is:

2019-04-02 10:20:05:242  860 1a10 DnldMgr Asking handler to generate non-range requests.
2019-04-02 10:20:05:242  860 1a10 Handler Generating request for CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E in sandbox C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc
2019-04-02 10:20:05:242  860 1a10 Handler Selecting self-contained because update does not have express payload.
2019-04-02 10:20:05:242  860 1a10 Handler Selected payload type is ptSelfContained
2019-04-02 10:20:05:242  860 1a10 Handler Detected download state is dsStart
2019-04-02 10:20:05:242  860 1a10 Handler Adding Windows6.1-KB4489878-x64.cab (entire file) to request list.
2019-04-02 10:20:05:242  860 1a10 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019-04-02 10:20:06:272  860 1a10 Misc Validating signature for C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc\Windows6.1-KB4489878-x64.cab with dwProvFlags 0x00000080:
2019-04-02 10:20:07:723  860 1a10 Misc  Microsoft signed: Yes
2019-04-02 10:20:07:723  860 1a10 DnldMgr Asking handler to generate non-range requests.
2019-04-02 10:20:07:723  860 1a10 Handler Generating request for CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E in sandbox C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc
2019-04-02 10:20:07:723  860 1a10 Handler Selecting self-contained because update does not have express payload.
2019-04-02 10:20:07:723  860 1a10 Handler Selected payload type is ptSelfContained
2019-04-02 10:20:07:723  860 1a10 Handler Detected download state is dsHavePackage
2019-04-02 10:20:07:723  860 1a10 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019-04-02 10:20:07:723  860 265c AU Launched new AU client for directive 'Download Approval', session id = 0x2
2019-04-02 10:20:07:738 5040 3014 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:07:738 5040 3014 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:07:738 5040 3014 AUClnt Launched Client UI process
2019-04-02 10:20:07:754 5040 3014 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:07:754 5040 3014 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:07:754 5040 3014 Misc   = Module: C:\Windows\system32\wucltux.dll
2019-04-02 10:20:07:754 5040 3014 CltUI AU client got new directive = 'Download Approval', serviceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, return = 0
2019-04-02 10:20:07:816 11848 27a0 COMAPI -------------
2019-04-02 10:20:07:816 11848 27a0 COMAPI -- START --  COMAPI: Install [ClientId = wusa]
2019-04-02 10:20:07:816 11848 27a0 COMAPI ---------
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Allow source prompts: Yes; Forced: No; Force quiet: No
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Updates in request: 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - ServiceID = {6A498F13-AD63-44DA-A31F-39ADA0DDC6AF} Third party service
2019-04-02 10:20:07:816  860 1da4 Agent *************
2019-04-02 10:20:07:816  860 1da4 Agent ** START **  Agent: Installing updates [CallerId = wusa]
2019-04-02 10:20:07:816  860 1da4 Agent *********
2019-04-02 10:20:07:816  860 1da4 Agent   * Updates to install = 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Updates to install = 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI <<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]
2019-04-02 10:20:07:816  860 1da4 Agent   *   Title = Security Update for Windows (KB4489878)
2019-04-02 10:20:07:816  860 1da4 Agent   *   UpdateId = {00B91A79-94CE-4E82-BA5F-5E8CE88C0F64}.501
2019-04-02 10:20:07:816  860 1da4 Agent   *     Bundles 1 updates:
2019-04-02 10:20:07:816  860 1da4 Agent   *       {1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E}.501
2019-04-02 10:20:08:362  860 1da4 Agent WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point
2019-04-02 10:20:08:362  860 1da4 Agent WARNING: LoadLibrary failed for srclient.dll with hr:8007007e
2019-04-02 10:20:08:362  860 1da4 Handler Attempting to create remote handler process as MADAP8017\Administrator in session 3
2019-04-02 10:20:08:378  860 1da4 DnldMgr Preparing update for install, updateId = {1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E}.501.
2019-04-02 10:20:08:393 10192 2618 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:08:393 10192 2618 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:08:393 10192 2618 Misc   = Module: C:\Windows\system32\wuaueng.dll
2019-04-02 10:20:08:393 10192 2618 Handler :::::::::::::
2019-04-02 10:20:08:393 10192 2618 Handler :: START ::  Handler: CBS Install
2019-04-02 10:20:08:393 10192 2618 Handler :::::::::
2019-04-02 10:20:08:409 10192 2618 Handler Starting install of CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E
2019-04-02 10:20:08:799 10192 2618 Handler CBS package identity: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24385.1.9
2019-04-02 10:20:08:815 10192 2618 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\Windows6.1-KB4489878-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\inst
2019-04-02 10:20:13:370  860 195c Report REPORT EVENT: {66649B29-CBDF-4DAA-B3EE-6F969812A173} 2019-04-02 10:20:08:362+0100 1 181 101 {00B91A79-94CE-4E82-BA5F-5E8CE88C0F64} 501 0 wusa Success Content Install Installation Started: Windows successfully started the following update: Security Update for Windows (KB4489878)
2019-04-02 10:20:33:619  860 2bbc AU Getting featured update notifications.  fIncludeDismissed = true
2019-04-02 10:20:33:619  860 2bbc AU No featured updates available.
2019-04-02 10:23:17:309 10192 2790 Handler FATAL: CBS called Error with 0x80070002,
2019-04-02 10:23:21:365 10192 2618 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070002

I wanted to try out a test 2019 WSUS server. Everything seemed to go smoothly, however when I go look at All Computers, I get a system node crash.

I looked at the possibility of it being the same as the bad BIOS name, but I do not seem to see any errors.

The error is as follows:

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\.


System.InvalidCastException -- Unable to cast object of type 'System.Guid' to type 'System.String'.

Source
Microsoft.UpdateServices.BaseApi

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchComputers(String computerTargetScopeXml)
   at Microsoft.UpdateServices.Internal.BaseApi.ComputerTarget.SearchComputerTargets(ComputerTargetScope searchScope, UpdateServer updateServer)
   at Microsoft.UpdateServices.UI.AdminApiAccess.ComputerTargetManager.GetComputerTargets(ComputerTargetScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkComputerPropertiesCache.GetAndCacheComputers(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()

Has anyone come across this error before?

Thanks.