I am facing problem while I approve June 2020 monthly rollup along with remaining patches and SSU Update. I have noticed that if I approved Monthly rollup then SSU update is stopped reflecting in Windows update list. I have selected option 2 to select for download and install. As of now I am facing this problem in windows 2012 R2.

If I remove Monthly Rollup of June 2020 for windows 2012 R2, SSU update of 06-2020 KB4562253 start reporting under Windows Update and I can select it for download and install.

I have seen one forum which explain to approve this update first and then approve another updates but it wont help me because I have to finish patching in defined time line. Even I can not select day -1 as deadline, else it will start installing this KB forcefully without planned downtime / maintenance window.

Is there any fix required on windows 2012 R2?

As per log it is reflecting under total count but in GUI -> Control Panel -> Windows Update SSU is not listed in pending list.

Good Day!

We are use WSUS Role on Windows Server 2016.

Clients can't download "Feature update to Windows 10 (consumer editions), version 1803, en-us". It's stuck on 0% and  failed  after few hours with error "0x80d02002".

In WindowsUpdate.log I saw this entries:

2018/05/22 16:10:50.9524467 4496  10012 DownloadManager DO job {32BDB35B-BE74-4B32-B146-FDFDBFCF9DB4} failed, updateId = 0DF72D03-C700-4EEA-994A-9777CCDFBF90.200, hr = 0x80D02002. File URL = http://wsus.domain.com:8530/d/msdownload/update/software/secu/2018/05/windows10.0-kb4103729-x64_0cf6d3009ed0bb61fab3c4d8964cd6f209373c97.cab, local path = C:\WINDOWS\SoftwareDistribution\Download\eb380a276773ea9883b97c243ead8ed0\Windows10.0-KB4103729-X64.cab

2018/05/22 16:10:50.9529958 4496  10012 DownloadManager   Progress failure bytes total = 21692097, bytes transferred = 0

On WSUS server in "Update Files and Languages" window option "Do not store update files locally, computers install from Microsoft Update" is set.

I can't understand why clients still use local URL. And i didn't receive such errors before.
I reinstalled WSUS role (absolutely wiped db), but error still persist.

Does anybody faced with such problem?

Thanks!

Hi,

I cannot get KB4565539 to install on two servers running Windows Server 2008 R2 Service Pack 1. I can run the .msu package fine and it seems to install successfully, tells me that it needs to reboot to finish the update, but then upon reboot the package will fail (trying to apply the update before the login screen). I have the latest SSU on each server and have followed all of the steps/prerequisites in this article - https://support.microsoft.com/en-us/help/4565539/windows-7-update-kb4565539

I found this helpful, but still neither 2020-07 Rollup (KB4565524) or 2020-07 Security only (KB4565539) will install after installing KB4565354 - https://docs.microsoft.com/en-us/answers/questions/30613/microsoft-windows-server-patches-not-installing-on.html

I started a sfc scan and will run dism checks to see if anything is corrupted. I also checked out the CBS log and I see some errors but I'm not sure how to proceed. There is a lot in here, I took out what seems like it could help:

~

2020-07-16 12:06:55, Info                  CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_0.0.0.0_none_1f323f66464683e5 (7.1.7601.18742), elevation:16, lower version revision holder: 7.1.7601.18325
2020-07-16 12:06:55, Info                  CBS    Applicability(ComponentAnalyzerEvaluateSelfUpdate): Component: amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_7.1.7601.18742_none_eeadac95e75f3e9d, elevate: 16, applicable(true/false): 1
2020-07-16 12:06:55, Info                  CBS    Appl: SelfUpdate detect, component: amd64_microsoft-windows-photo-image-codec_31bf3856ad364e35_7.1.7601.18742_none_eeadac95e75f3e9d, elevation: 16, applicable: 1
2020-07-16 12:06:55, Info                  CBS    Appl: Evaluating applicability block(non detectUpdate part), disposition is: Staged, applicability: Applicable, result applicability state: Installed
2020-07-16 12:06:55, Info                  CBS    Appl: Package: Package_3_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, Update: 3035126-6_neutral_GDR, Applicable: Applicable, Dis
2020-07-16 12:06:55, Info                  CBS    External EvaluateApplicability, package: Package_3_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
2020-07-16 12:06:55, Info                  CBS    Appl: detect Parent, Package: Package_4_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, Parent: WinEmb-Media-Support~31bf3856ad364e35~amd64~~6.1.7601.17514, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2020-07-16 12:06:55, Info                  CBS    Appl: detectParent: package: Package_4_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, no parent found, go absent
2020-07-16 12:06:55, Info                  CBS    Appl: detect Parent, Package: Package_4_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, disposition state from detectParent: Absent
2020-07-16 12:06:55, Info                  CBS    Appl: Evaluating package applicability for package Package_4_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, applicable state: Absent
2020-07-16 12:06:55, Info                  CBS    EvaluateApplicability, package: Package_4_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, Package applicability: Absent.
2020-07-16 12:06:55, Info                  CBS    External EvaluateApplicability, package: Package_for_KB3035126_SP1~31bf3856ad364e35~amd64~~6.1.1.2, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
2020-07-16 12:06:55, Info                  CBS    External EvaluateApplicability, package: Package_for_KB3035126~31bf3856ad364e35~amd64~~6.1.1.2, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
2020-07-16 12:06:55, Info                  CBS    Session: 30825355_544352502 initialized by client WindowsUpdateAgent.
2020-07-16 12:07:08, Info                  CBS    Warning: Unrecognized packageExtended attribute.
2020-07-16 12:07:08, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2020-07-16 12:07:08, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2020-07-16 12:07:08, Info                  CBS    Warning: Unrecognized packageExtended attribute.

~

much farther down in the CBS log:

~

2020-07-16 12:12:30, Info                  CSI    0000006a@2020/7/16:16:12:30.312 CSI perf trace:
CSIPERF:TXCOMMIT;447324
2020-07-16 12:12:30, Info                  CSI    0000006b No more queue entries, deleted pending.xml
2020-07-16 12:12:30, Info                  CBS    Startup: Primitive operations were successfully rolled back.
2020-07-16 12:12:30, Error                 CBS    Startup: Completed rollback, startupPhase: 0. [HRESULT = 0x80004005 - E_FAIL]
2020-07-16 12:12:30, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateFailed
2020-07-16 12:12:30, Info                  CBS    Doqe: Enabling Device installs
2020-07-16 12:12:30, Info                  CSI    0000006c Cancelling transactions: [1:[78]"TI4.30825355_21249816:3/Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11"[1]"]"

2020-07-16 12:12:30, Info                  CSI    0000006d Creating NT transaction (seq 2), objectname [6]"(null)"
2020-07-16 12:12:30, Info                  CSI    0000006e Created NT transaction (seq 2) result 0x00000000, handle @0x28c
2020-07-16 12:12:30, Info                  CSI    0000006f@2020/7/16:16:12:30.890 CSI perf trace:
CSIPERF:TXCOMMIT;99634
2020-07-16 12:12:30, Info                  CBS    Clearing HangDetect value
2020-07-16 12:12:30, Info                  CBS    Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
2020-07-16 12:12:30, Info                  CBS    Doqe: Unlocking driver updates, Count 1
2020-07-16 12:12:30, Info                  CBS    WER: Generating failure report for package: Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11, status: 0x80070661, failure source: AI, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2020-07-16 12:12:30, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-07-16 12:12:30, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
2020-07-16 12:12:30, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
2020-07-16 12:12:30, Info                  CBS    Failed to submit WER report. [HRESULT = 0x800700a1 - ERROR_BAD_PATHNAME]
2020-07-16 12:12:30, Info                  CBS    Failed to submit WER report. [HRESULT = 0x800700a1 - ERROR_BAD_PATHNAME]
2020-07-16 12:12:30, Info                  CBS    WER: Failed to generate failure report for package: Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11 [HRESULT = 0x800700a1 - ERROR_BAD_PATHNAME]
2020-07-16 12:12:30, Info                  CBS    Failed to submit WER report for pending package: Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11 [HRESULT = 0x800700a1 - ERROR_BAD_PATHNAME]
2020-07-16 12:12:30, Info                  CBS    SQM: Reporting package change completion for package: Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11, current: Staged, original: Staged, target: Installed, status: 0x80070661, failure source: AI, failure details: "Extended Security Updates AI installer8007066138Install (upgrade)Microsoft-Windows-SLC-Component-ExtendedSecurityUpdatesAI, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 2370, first merged sequence: 2370
2020-07-16 12:12:30, Info                  CBS    SQM: Failed to initialize Win SAT assessment. [HRESULT = 0x80040154 - Unknown Error]
2020-07-16 12:12:30, Info                  CBS    SQM: average disk throughput datapoint is invalid [HRESULT = 0x80040154 - Unknown Error]
2020-07-16 12:12:30, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_KB4565539~31bf3856ad364e35~amd64~~6.1.1.11, session id: 142862, sample type: Standard
2020-07-16 12:12:30, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard

~

Any leads would be super appreciated as we really need this patch installed, thanks.

*I am aware that 2008 R2 support ended in Jan 2020, multiple replication issues migrating to new version still working on it*

Greetings!

I have configured group policies so that after installing updates that require a reboot, the shutdown menu disables normal reboot and shutdown options. The only options left in the menu are to install updates before shutting down or restarting. These settings work correctly when monthly updates are installed. However, if you are installing a feature update (for example, Win 1909 to Win 2004), the usual options for shutdown and restarting remain in the "shutdown" menu. A lot of users do not use the option to install updates when rebooting or shutting down.

How can I disable the ability for users to restart or shut down their PC without installing an update (even if a feature update is installed)?

Hi there,

I would like to distribute the version 1903 or 1909 on a WSUS that runs on a Server 2019 standard to some clients that are still running Windows 10 1803. (both versions cannot be installed)

The update is beeing seen and offered to the clients, it gets downloaded and as soon as it is to be installed it stops immediately with the error 0x8000ffff.

Server 2019 is on 1809 (OS Build 17763.973)
Windows Update Services has version 10.0.17763.1

What i tried:

Windows Update Troubleshooter.
Read the CBS.log file (no errors found)
Uninstalling the Trend Micro Worry Free Business antivirus software
Install 1909 on a client using the Windows Update Assistant (works)
Disable computer protection
All drivers updated (these are Dell notebooks)
Resetting the wsus using wsustools

I dont know why exactly but there must be an error while downloading the update from the wsus.
Sometimes it slowly goes to about 5% and stops with error 0x80070057
and othertimes it rushes to 100% in 3 seconds and shows error 0x8007005. I also saw the error 0x80244010 a few times.

I have reviewed several online docs on delivery optimization, but could not find any information for use and configuration on disconnected networks.

My network has several remote sites, many have slow connections with low bandwidth. I have one WSUS server used to deploy updates/patches. All of the clients on my network do not have any connection to the internet. Each site connects back to Central site via VPN for access to all servers and network resources.

Question 1: Can I still take advantage of delivery optimization on my disconnected network?

Question 2: What benefits can I gain from using delivery optimization on my disconnected network?

Question 3: What are some suggested configurations and/or GPO settings for delivery optimization on disconnected networks?

Logs clearly show it is seeing updates, however it fails with only one single line every time:

Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse  

From everything I have read, this is related to the WSUS database (SUSDB). I have manually tried cleaning it using wizard (GUI, & Powershell). After hours it eventually times out. All recommendations have been to manually connect to SUSDB using one of the two methods (after verifying TCP/IP is enabled):

In SQL Mgmt Studio Express, PowerShell or sqlcmd, connect to either server \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query or \\.\pipe\MICROSOFT##WID\tsql\query, witrh the second server name the recommendation if the first doesn't wotk (first is 2008 version, second is 2012) with Windows auth.

I have my SUSDB on a separate server from SCCM which runs 2012 R2 OS. No matter what I do, I continue to get the same "Server is not found or not accessible" error.Obviously, I have to get my sync working so I can begin patching ASAP.

Any thoughts on why cannot successfully clean up WSUS to resolve this issue?

Brad Boozer Team Lead, Systems Engineering and Desktop Support Westwood Holdings Group, Inc.

Hi,

Basically, I've got so much information and at this point, I don't really know where to start with it. An important thing to note, is that these upgrades of 1607 to 1809 (deployed 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd via WSUS) have been successful on ~85% of the ~400 clients targeted. Many of the computers that were seeing the same (or similar) sequence of errors have successfully completed with no intervention. Still, some of them are still looping through these errors and restarting at inopportune times (when the user is logged in, but the machine is locked even though the "No auto-restart with logged on users for scheduled automatic updates installations" GPO is in place)

Here's what I've done to troubleshoot:

1. Server 2012 R2, WSUS 6.3.9600.18838. Confirmed that WSUS and the requisite updates for feature upgrades are installed. Well, almost. I have the .esd application/octet-stream mime type enabled, and a superseding update (KB4489881) is installed. So, this supersedes KB3095113, but does it supersede the "hotfix" version of KB3095113? All that said, feature upgrades are syncing and are successfully deploying with just these few exceptions.
   
2. Stopped Windows Update service on the client and renamed the SoftwareDistribution folder to .old., restarted WU service.
3. Disabled all non-microsoft startup services.
4. Confirmed that the WU registry settings reflect what's in the WSUS GPO.
5. Confirmed HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing is 0x00023c00
6. Disabled Symantec Endpoint Protection, tried again
7. Removed temp files

I honestly can't remember whether or not I ran the Windows Update Troubleshooter in this particular machine or not. That said, I'd really rather fix it myself so I can maybe solve the cause of problem as well as the problem itself.

I've been through several different forums where different things are suggested and I often see the "(Unable to Find Resource)" events addressed, but I haven't seen anything in forums (or in the Resolution procedures that directly addresses the errors I'm seeing. Here's an example of the string of errors shown on one machine when running the report in WSUS and clicking the "failed" link:

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/8/2019 11:08 PM:
(Unable to Find Resource:) ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 1:07 AM:
Installation successful and restart required for the following update:
Feature update to Windows 10 (business editions), version 1809, en-us x64

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 7:57 AM:
(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 8:00 AM:
Installation Failure: Windows failed to install the following update with
error 0x8024200d: Feature update to Windows 10 (business editions), version 1809, en-us x64

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 8:03 AM:
(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 8:03 AM:
Download succeeded.

[machinename.domain.local]
Feature update to Windows 10 (business editions), version 1809, en-us x64
Event reported at 4/9/2019 8:03 AM:
(Unable to Find Resource:) ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

In WindowsUpdate.log, the most common error I see is

2019/03/27 13:41:32.5086982 1416  4324  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

So, at this point I'm afraid that this is happening because the "hotfix" version of KB3095113 isn't installed. Or is it? Since I have the most current superseding update of the "Update for Windows Server 2012 R2 (KB3095113) installed? Since the upgrades are successful on the vast majority of machines, I'm second-guessing that and I don't want to have to delete/re-sync all of these updates if that's not the problem. Any help on how to resolve this and/or reconcile the fact that the update is working on the majority of machines in the environment would be greatly appreciated.

Hello.

Is there anyone out there that can help. I have been looking into this WSUS issue for months now and all I find are people repeating the same fixes that do not solve the issue.

Here is a list of things I have tried:

Checking if BITS is running (aswell as: Wuauserv / Msiserver / CryptSvc)

Renaming the softwaredistribution folder

Ran MPCMDRUN.exe /removedefinitions -All & /signatureupdate

Ran DISM.exe /online /clean-image /restorehealth

Ran Sfc /scannow

No point turning off AV as I don’t have any other AV installed

I don’t want to hide the update as that isn’t solving the issue

I have been trying my upmost to get my Environment fully patched. Most clients have installed 99% of the patches with the exception of a few Microsoft Defender updates:

For server 2012 R2 its:

KB2461484 – Version 1.319.1990.0

KB2461484 – Version 1.319.1968.0

KB2461484 – Version 1.319.1962.0

KB2461484 – Version 1.319.1955.0

KB2461484 – Version 1.319.1950.0

KB2461484 – Version 1.319.1939.0

And for Server 2016 / Win 10 its:

KB2461484 – Version 1.319.1968.0

KB2461484 – Version 1.319.1962.0

KB2461484 – Version 1.319.1955.0

KB2461484 – Version 1.319.1950.0

When I go into the client and run windows update it flashes up with the update and then says it is fully up to date and no updates are available.

(Why does it flash up and not install? Why does windows says no update needed when WSUS says updates are needed?)

After that I do a wuauclt /reportnow and wsus says 99%

Is this a windows update issue? A WSUS issue? Or an Enpoint protection issue?

Some servers are patched 100% so it tells me there is not anything wrong with WSUS or the updates and the issue must lie on the client its self

Here is what the updates look like in WSUS

Sometimes the needed number even drops to 1 and then I run a windows update again and it goes back to needing 4.

I just can’t get my head around it

I feel like the issues lies within Windows defender and it needs to be purged and then reinstalled.

It seems to me like a newer update has installed over the top of the older ones and now it is just failing to install.

For example:

KB2461484 – Version 1.319.1995.0 – Has installed

So –

KB2461484 – Version 1.319.1990.0

KB2461484 – Version 1.319.1968.0

KB2461484 – Version 1.319.1962.0

Hi everyone,

I'm very new to WSUS and SCCM. 

Currently there is an old setup using SCCM to update internal system without internet connection. A WSUS with internet access is used to download the patches and then transfer into the SCCM. I need to setup another new WSUS server to takeover the current old WSUS. Is there issue which I need to look out for? Example, do I need to remove all the content inside Wsuscontent inside the SCCM, then copy all the new WSUS server Wsuscontent over? I do know we need to export and import the metadata.

Is the Windows version between the new and old WSUS server important? The new WSUS would be using a newer version. How about WSUS version and any patches needed.

Thanks!

I have been unable to apply rollups for a few months. The latest, KB4561666, will not apply. 

cbs.log

2020-07-13 20:08:06, Info                  CBS    Startup: Initializing advanced operation queue.
2020-07-13 20:08:07, Info                  CSI    00000002 CSI Store 841863726032 (0x000000c402fd03d0) initialized
2020-07-13 20:08:07, Info                  CBS    Obtained poqexec from PoqexecCmdline: C:\Windows\System32\poqexec.exe /display_progress \SystemRoot\WinSxS\pending.xml
2020-07-13 20:08:07, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStatePrimitives, SubStage: 0
2020-07-13 20:08:07, Info                  CBS    Setting ExecuteState key to: CbsExecuteStatePrimitives
2020-07-13 20:08:07, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStatePrimitives, SubStage: 2
2020-07-13 20:08:07, Info                  CBS    Startup: Processing non-critical driver operations queue, Count 6.
2020-07-13 20:08:07, Info                  CBS    Doqe: Resetting result: 0x00000000, for Inf: ntprint.inf
2020-07-13 20:08:07, Info                  CBS    Doqe: Locking driver updates, Count 8
2020-07-13 20:08:07, Info                  CSI    00000003 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:4400799d8359d60101000000e002ec02} pathid: {l:16 b:4400799d8359d60102000000e002ec02} path: [l:172{86}]"\SystemRoot\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19678_none_4e174d17c34cb3ea" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000004 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:3527809d8359d60103000000e002ec02} pathid: {l:16 b:3527809d8359d60104000000e002ec02} path: [l:180{90}]"\SystemRoot\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.18790_none_2bb006008eb5c61f" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000005 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:8c89829d8359d60105000000e002ec02} pathid: {l:16 b:8c89829d8359d60106000000e002ec02} path: [l:176{88}]"\SystemRoot\WinSxS\x86_ntprint.inf_31bf3856ad364e35_6.3.9600.18790_none_cf916a7cd65854e9" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000006 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:e3eb849d8359d60107000000e002ec02} pathid: {l:16 b:e3eb849d8359d60108000000e002ec02} path: [l:172{86}]"\SystemRoot\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.19724_none_4e495d71c327c000" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000007 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:3e4e879d8359d60109000000e002ec02} pathid: {l:16 b:3e4e879d8359d6010a000000e002ec02} path: [l:182{91}]"\SystemRoot\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.19728_none_43d27c99a7a30b45" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000008 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:3e4e879d8359d6010b000000e002ec02} pathid: {l:16 b:3e4e879d8359d6010c000000e002ec02} path: [l:178{89}]"\SystemRoot\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.19728_none_e7b3e115ef459a0f" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    00000009 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:bcb0899d8359d6010d000000e002ec02} pathid: {l:16 b:bcb0899d8359d6010e000000e002ec02} path: [l:180{90}]"\SystemRoot\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.19728_none_2c03a0fc8e75e6e1" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CSI    0000000a Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:bcb0899d8359d6010f000000e002ec02} pathid: {l:16 b:bcb0899d8359d60110000000e002ec02} path: [l:176{88}]"\SystemRoot\WinSxS\x86_ntprint.inf_31bf3856ad364e35_6.3.9600.19728_none_cfe50578d61875ab" pid: 2e0 starttime: 132391660857983175 (0x01d659839caa00c7)
2020-07-13 20:08:07, Info                  CBS    Doqe:   q-install: Inf: prnms003.inf, Ranking: 2, Device-Install: 0, Key: 35, Identity: prnms003.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.19728, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2020-07-13 20:08:07, Info                  CBS    Doqe:   q-install: Inf: prnms003.inf, Ranking: 2, Device-Install: 0, Key: 36, Identity: prnms003.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.19728, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS
2020-07-13 20:08:07, Info                  CBS    Doqe:   q-install: Inf: ntprint.inf, Ranking: 2, Device-Install: 0, Key: 37, Identity: ntprint.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.19728, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2020-07-13 20:08:07, Info                  CBS    Doqe:   q-install: Inf: ntprint.inf, Ranking: 2, Device-Install: 0, Key: 38, Identity: ntprint.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.19728, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS
2020-07-13 20:08:07, Info                  CBS    Perf: Doqe: Install started.
2020-07-13 20:08:07, Info                  CBS    Doqe: [Forward] Installing driver updates, Count 4
2020-07-13 20:08:07, Info                  CBS            INSTALL index: 4, phase: 1, result 0, inf: prnms003.inf
2020-07-13 20:08:07, Info                  CBS            INSTALL index: 5, phase: 1, result 0, inf: prnms003.inf
2020-07-13 20:08:07, Info                  CBS            INSTALL index: 6, phase: 1, result 3, inf: ntprint.inf
2020-07-13 20:08:07, Info                  CBS    Doqe: Recording result: 0x80070003, for Inf: ntprint.inf
2020-07-13 20:08:07, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2020-07-13 20:08:07, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2020-07-13 20:08:07, Info                  CBS    Perf: Doqe: Install ended.
2020-07-13 20:08:07, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2020-07-13 20:08:07, Error                 CBS    Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2020-07-13 20:08:07, Info                  CBS    Startup: Rolling back KTM, because drivers failed.

setupapi.dev.log

>>>  [Setup Import Driver Package - C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint.inf]>>>  Section start 2020/07/13 20:08:32.140
      cmd: C:\Windows\System32\spoolsv.exe
     inf: Provider: Microsoft
     inf: Class GUID: {4D36E979-E325-11CE-BFC1-08002BE10318}
     inf: Driver Version: 06/21/2006,6.3.9600.17415
     pol: {Driver package policy check} 20:08:32.328
     pol: {Driver package policy check - exit(0x00000000)} 20:08:32.328
     sto: {Stage Driver Package: C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint.inf} 20:08:32.343
     inf:      {Query Configurability: C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint.inf} 20:08:32.343
     inf:           Driver package 'tsprint.inf' is configurable.
     inf:      {Query Configurability: exit(0x00000000)} 20:08:32.343
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint.inf' to 'C:\Windows\System32\DriverStore\Temp\{4550f12c-0e6b-044c-9d3f-8c29b21ea080}\tsprint.inf'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint-PipelineConfig.xml' to 'C:\Windows\System32\DriverStore\Temp\{4550f12c-0e6b-044c-9d3f-8c29b21ea080}\tsprint-PipelineConfig.xml'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\tsprint-datafile.dat' to 'C:\Windows\System32\DriverStore\Temp\{4550f12c-0e6b-044c-9d3f-8c29b21ea080}\tsprint-datafile.dat'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{E5059964-01C3-457E-9A4A-890C83197DE1}\amd64\tsprint.dll' to 'C:\Windows\System32\DriverStore\Temp\{4550f12c-0e6b-044c-9d3f-8c29b21ea080}\amd64\tsprint.dll'.
     sto:      {DRIVERSTORE IMPORT VALIDATE} 20:08:32.359
!!!  sig:           Driver package does not contain a catalog file, and Code Integrity is enforced.
!!!  sig:           Driver package failed signature validation. Error = 0xE000022F
     sto:      {DRIVERSTORE IMPORT VALIDATE: exit(0xe000022f)} 20:08:32.390
!!!  sig:      Driver package failed signature verification. Error = 0xE000022F
!!!  sto:      Failed to import driver package into Driver Store. Error = 0xE000022F
     sto: {Stage Driver Package: exit(0xe000022f)} 20:08:32.390<<<  Section end 2020/07/13 20:08:32.390<<<  [Exit status: FAILURE(0xe000022f)]


[Boot Session: 2020/07/13 20:09:32.584]

>>>  [Setup Import Driver Package - C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint.inf]>>>  Section start 2020/07/13 20:10:07.917
      cmd: C:\Windows\System32\spoolsv.exe
     inf: Provider: Microsoft
     inf: Class GUID: {4D36E979-E325-11CE-BFC1-08002BE10318}
     inf: Driver Version: 06/21/2006,6.3.9600.17415
     pol: {Driver package policy check} 20:10:08.105
     pol: {Driver package policy check - exit(0x00000000)} 20:10:08.105
     sto: {Stage Driver Package: C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint.inf} 20:10:08.121
     inf:      {Query Configurability: C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint.inf} 20:10:08.136
     inf:           Driver package 'tsprint.inf' is configurable.
     inf:      {Query Configurability: exit(0x00000000)} 20:10:08.136
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint.inf' to 'C:\Windows\System32\DriverStore\Temp\{33a54c21-3608-fe43-b603-be9f34e89dda}\tsprint.inf'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint-PipelineConfig.xml' to 'C:\Windows\System32\DriverStore\Temp\{33a54c21-3608-fe43-b603-be9f34e89dda}\tsprint-PipelineConfig.xml'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\tsprint-datafile.dat' to 'C:\Windows\System32\DriverStore\Temp\{33a54c21-3608-fe43-b603-be9f34e89dda}\tsprint-datafile.dat'.
     flq:      Copying 'C:\Windows\system32\spool\DRIVERS\x64\{09278BEB-F80D-4C5E-8CB3-45E756F96FDD}\amd64\tsprint.dll' to 'C:\Windows\System32\DriverStore\Temp\{33a54c21-3608-fe43-b603-be9f34e89dda}\amd64\tsprint.dll'.
     sto:      {DRIVERSTORE IMPORT VALIDATE} 20:10:08.167
!!!  sig:           Driver package does not contain a catalog file, and Code Integrity is enforced.
!!!  sig:           Driver package failed signature validation. Error = 0xE000022F
     sto:      {DRIVERSTORE IMPORT VALIDATE: exit(0xe000022f)} 20:10:08.199
!!!  sig:      Driver package failed signature verification. Error = 0xE000022F
!!!  sto:      Failed to import driver package into Driver Store. Error = 0xE000022F
     sto: {Stage Driver Package: exit(0xe000022f)} 20:10:08.199<<<  Section end 2020/07/13 20:10:08.214<<<  [Exit status: FAILURE(0xe000022f)]

Is this a signing issue? A missing file issue?

I am having issues with WSUS server on 2019. I setup server and then ran the initial update sync. I then setup GPO's to assigned computers to the different groups. next I plan to add one down stream server. 

It started where I occasionally got this connection error and I would have to restart it. Has gotten alot worse and the restart are not always help or they happen within 2-3 minutes of opening WSUS console Especially if I got to the sync section. 

Here is what I have done to address the situation so far. 

1. I have run the MS WSUS clean up Powershell WSUS-Clean found  I could not get it to run which i think is because the WSUS is not running due to the errors. 

2. I ran the MS WSUS Clean up Updates Powershell found here:  Sometimes that fixes issues along with a restart sometime the server will not come back up. 

3. I notice that there is a large amount of MEM usage for SQL Server Windows NT - Windows Internal Database around 4k. 

4. I due to the high CPU usage I followed the instructions in the following articular to change application pool memory. I set it to 0. 

I also have deleted the appdata file for WSUS several times. 

This seems to have fixed some of the issues. 

However when ever I go into sync now it will run the history the progress bar on the bottom right gets to 85 percent and then the error comes back. Also the memory is high again for the SQL Server Window NT and the IIS Worker Process is at 2.8 GB of memory. I also notice that if I restart the computer after this happens the WSUS Application Pool in IIS is stopped. 

Please let me know if you guys have any ideas?

Hi,

Please support, Iam trying to import updates I have folder updates and copy to wsuscontent folder in WSUS server.

when I inter comment line wsusulit.exe import export.xml.gz export.log 

It is showing error:

fatal error: the gzip stream can not contain more than 4GB data.

Thank You for support.

Hey everyone.. I have been having some issues on windows 8.1 under a specific hardware platform ..  We are using a WSUS server. I know the reg keys are working, as other win 8.1 OS's under a diff HW platform are reporting in just fine. 

I have tried --

Renaming/deleting the sw dist folder, reimporting all reg keys including SUSID's.  Also have just completed a reimage of the entire computer.  The same error of 80244007 within the actual WSUS server Gui.  Deleting the PC from the Server and resetauthorizations.

When checking the windowsupdate.log file I saw this before I reimaged the computer.. Serialization Failure.  Character value 28 is invalid. 

I have checked the HLKM/hardware/system/bios reg key and there aren't any different characters than a pc that is working correctly. 

2018-10-31 11:25:25:096  968 a9c Misc ===========  Logging initialized (build: 7.9.9600.17930, tz: -0400)  ===========
2018-10-31 11:25:25:096  968 a9c Misc   = Process: C:\windows\system32\svchost.exe
2018-10-31 11:25:25:096  968 a9c Misc   = Module: c:\windows\system32\wuaueng.dll
2018-10-31 11:25:25:096  968 a9c Service *************
2018-10-31 11:25:25:096  968 a9c Service ** START **  Service: Service startup
2018-10-31 11:25:25:096  968 a9c Service *********
2018-10-31 11:25:25:112  968 a9c IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
2018-10-31 11:25:25:112  968 a9c Agent   * WU client version 7.9.9600.17930
2018-10-31 11:25:25:112  968 a9c Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2018-10-31 11:25:25:112  968 a9c Agent   * Base directory: C:\windows\SoftwareDistribution
2018-10-31 11:25:25:112  968 a9c Agent   * Access type: No proxy
2018-10-31 11:25:25:112  968 a9c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2018-10-31 11:25:25:112  968 a9c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018-10-31 11:25:25:112  968 a9c Agent   * Network state: Connected
2018-10-31 11:25:25:112  968 a9c Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2018-10-31 11:25:25:112  968 a9c Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018-10-31 11:25:25:143  968 a9c Agent ***********  Agent: Initializing global settings cache  ***********
2018-10-31 11:25:25:143  968 a9c Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2018-10-31 11:25:25:143  968 a9c Agent   * WSUS server: http://vmmscswusp01.XX.XX:8530/
2018-10-31 11:25:25:143  968 a9c Agent   * WSUS status server: http://vmmscswusp01.XX.XX:8530/
2018-10-31 11:25:25:143  968 a9c Agent   * Target group: PM Prod Workstations
2018-10-31 11:25:25:143  968 a9c Agent   * Windows Update access disabled: No
2018-10-31 11:25:25:143  968 a9c WuTask WuTaskManager delay initialize completed successfully..
2018-10-31 11:25:25:143  968 a9c AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2018-10-31 16:20:27, not idle-only, not network-only
2018-10-31 11:25:25:143  968 a9c AU     Timer: 143FB093-8AA1-4DBC-A582-8806F8F4C1F7, Expires 2018-11-02 15:24:36, not idle-only, not network-only
2018-10-31 11:25:25:143  968 a9c AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2018-11-01 15:24:23, not idle-only, not network-only
2018-10-31 11:25:25:143  968 a9c AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-11-01 15:24:23, not idle-only, not network-only
2018-10-31 11:25:25:159  968 a9c Report CWERReporter::Init succeeded
2018-10-31 11:25:25:159  968 a9c Agent ***********  Agent: Initializing Windows Update Agent  ***********
2018-10-31 11:25:25:174  968 a9c DnldMgr Download manager restoring 0 downloads
2018-10-31 11:25:25:205  968 a9c Agent   * WARNING: Failed to mark wuauserv as triggered by group policy change, hr = 0x80070005
2018-10-31 11:25:25:205  968 a9c AU ###########  AU: Initializing Automatic Updates  ###########
2018-10-31 11:25:25:205  968 a9c AU AIR Mode is disabled
2018-10-31 11:25:25:205  968 a9c AU   # Policy Driven Provider:  http://vmmscswusp01.XX.XX:8530/
2018-10-31 11:25:25:205  968 a9c AU   # Detection frequency: 1
2018-10-31 11:25:25:205  968 a9c AU   # Target group: PM Prod Workstations
2018-10-31 11:25:25:205  968 a9c AU   # Approval type: Scheduled (Policy)
2018-10-31 11:25:25:205  968 a9c AU   # Auto-install minor updates: No (Policy)
2018-10-31 11:25:25:205  968 a9c AU   # Will interact with non-admins (Non-admins are elevated (Policy))
2018-10-31 11:25:28:143  968 a9c AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x800704C6
2018-10-31 11:25:28:190  968 a9c AU AU finished delayed initialization
2018-10-31 11:25:28:190  968 a9c AU Currently AUX is enabled - so not show any WU Upgrade notifications.
2018-10-31 11:25:28:268  968 a9c AU Adding timer:
2018-10-31 11:25:28:268  968 a9c AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2018-10-31 16:20:27, not idle-only, not network-only
2018-10-31 11:25:28:268  968 a9c AU Currently AUX is enabled - so not show any WU Upgrade notifications.
2018-10-31 11:25:28:706  968 1034 DnldMgr Asking handlers to reconcile their sandboxes
2018-10-31 11:33:31:051  968 1034 EP Got WSUS Client/Server URL: "http://vmmscswusp01.XX.XX:8530/ClientWebService/client.asmx"
2018-10-31 11:33:31:066  968 1034 IdleTmr WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery) started; operation # 10; does use network; is at background priority
2018-10-31 11:33:31:066  968 1034 WS WARNING: Nws Failure: errorCode=0x803d0000
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing an element with WS_WRITE_OPTION '1', name 'RegisterComputer' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing a field with WS_TYPE '26 (0x1A)', WS_FIELD_MAPPING '2', name 'computerInfo' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing a field with WS_TYPE '17 (0x11)', WS_FIELD_MAPPING '2', name 'ComputerModel' and namespace 'http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: The character value 28 (0x1C) is not valid.
2018-10-31 11:33:31:066  968 1034 WS WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439
2018-10-31 11:33:31:066  968 1034 WS WARNING: Web service call failed with hr = 80240439.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Current service auth scheme='None'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2018-10-31 11:33:31:066  968 1034 WS FATAL: OnCallFailure failed with hr=0X80240439
2018-10-31 11:33:31:066  968 1034 IdleTmr WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery, operation # 10) stopped; does use network; is at background priority
2018-10-31 11:33:31:066  968 1034 EP Got WSUS Client/Server URL: "http://vmmscswusp01.XX.XX:8530/ClientWebService/client.asmx"
2018-10-31 11:33:31:066  968 1034 PT WARNING: PTError: 0x80240439
2018-10-31 11:33:31:066  968 1034 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80240439, Not Fatal
2018-10-31 11:33:31:066  968 1034 EP Got WSUS Reporting URL: "http://vmmscswusp01.XX.XX:8530/ReportingWebService/ReportingWebService.asmx"
2018-10-31 11:33:31:066  968 1034 Report OpenReportingWebServiceConnection, reporting URL = http://vmmscswusp01.XX.XX:8530/ReportingWebService/ReportingWebService.asmx
2018-10-31 11:33:31:066  968 1034 IdleTmr WU operation (CLegacyEventUploader::HandleEvents) started; operation # 11; does use network; is at background priority
2018-10-31 11:33:31:066  968 1034 Report Uploading 2 events using cached cookie.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Nws Failure: errorCode=0x803d0000
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing an element with WS_WRITE_OPTION '1', name 'ReportEventBatch' and namespace 'http://www.microsoft.com/SoftwareDistribution'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing a field with WS_TYPE '26 (0x1A)', WS_FIELD_MAPPING '3', name 'eventBatch' and namespace 'http://www.microsoft.com/SoftwareDistribution'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing a field with WS_TYPE '26 (0x1A)', WS_FIELD_MAPPING '2', name 'ExtendedData' and namespace 'http://www.microsoft.com/SoftwareDistribution'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Serialization failure occurred when writing a field with WS_TYPE '17 (0x11)', WS_FIELD_MAPPING '2', name 'ComputerModel' and namespace 'http://www.microsoft.com/SoftwareDistribution'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: The character value 28 (0x1C) is not valid.
2018-10-31 11:33:31:066  968 1034 WS WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439
2018-10-31 11:33:31:066  968 1034 WS WARNING: Web service call failed with hr = 80240439.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Current service auth scheme='None'.
2018-10-31 11:33:31:066  968 1034 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2018-10-31 11:33:31:066  968 1034 WS FATAL: OnCallFailure failed with hr=0X80240439
2018-10-31 11:33:31:066  968 1034 Report WARNING: Failed to upload events to the server with hr = 80240439.
2018-10-31 11:33:31:066  968 1034 Report WARNING: Reporter failed to upload events with hr = 80240439.
2018-10-31 11:33:31:066  968 1034 IdleTmr WU operation (CLegacyEventUploader::HandleEvents, operation # 11) stopped; does use network; is at background priority

Edited to remove the domain name.

I have even deleted the PC out of the wsus server.. the PC will connect to the server and display the dns name, but no other info comes across.... and I cant obtain any updates from the server, to the PC.