Hi to all

Which is the best troubleshooting for this message?

Warm regards MeVs

I have 3 servers total, one is updating correctly, but the other 2 have never updated.  Decided to see how updates were being installed (automatically) and they have NEVER updated.

I tried the instructions of stopping the update service and deleting windows\software-distribution but that didin't work.

Any ideas?  The working server is an exact copy of one that is not updating.  It's funny because I installed Windows 2012 R2 and all the software needed on the one that doesn't update, then cloned it, then activated them with their licenses and the second one is updating fine.  The 3rd server was an update from 2008 R2 to 2012 R2 and everything went well and all the software worked fine, but it has never updated either.

Hello,

i have some problem to update Windows Server 2008R2

In WindowUpdate Log , i have this error

2019-11-19	19:50:25:448	 956	4adb8	Agent	** START **  Agent: Installing updates [CallerId = wusa]
2019-11-19	19:50:25:448	 956	4adb8	Agent	*********
2019-11-19	19:50:25:448	 956	4adb8	Agent	  * Updates to install = 1
2019-11-19	19:50:25:453	 956	4adb8	Agent	  *   Title = Update for Windows (KB4019990)
2019-11-19	19:50:25:453	 956	4adb8	Agent	  *   UpdateId = {5930D161-54D9-4205-BACD-13F48051D0C2}.501
2019-11-19	19:50:25:453	 956	4adb8	Agent	  *     Bundles 1 updates:
2019-11-19	19:50:25:453	 956	4adb8	Agent	  *       {82E2053F-6560-4DBF-BF95-625C4D0137AC}.501
2019-11-19	19:50:25:457	 956	4adb8	Agent	WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point
2019-11-19	19:50:25:458	 956	4adb8	Agent	WARNING: LoadLibrary failed for srclient.dll with hr:8007007e
2019-11-19	19:50:25:520	 956	4adb8	DnldMgr	Preparing update for install, updateId = {82E2053F-6560-4DBF-BF95-625C4D0137AC}.501.
2019-11-19	19:50:25:523	302484	4aea4	Misc	===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-11-19	19:50:25:523	302484	4aea4	Misc	  = Process: C:\Windows\system32\wuauclt.exe
2019-11-19	19:50:25:523	302484	4aea4	Misc	  = Module: C:\Windows\system32\wuaueng.dll
2019-11-19	19:50:25:521	302484	4aea4	Handler	:::::::::::::
2019-11-19	19:50:25:523	302484	4aea4	Handler	:: START ::  Handler: CBS Install
2019-11-19	19:50:25:523	302484	4aea4	Handler	:::::::::
2019-11-19	19:50:25:526	302484	4aea4	Handler	Starting install of CBS update 82E2053F-6560-4DBF-BF95-625C4D0137AC
2019-11-19	19:50:25:528	302484	4aea4	Handler	CBS package identity: Package_for_KB4019990~31bf3856ad364e35~amd64~~6.1.1.2
2019-11-19	19:50:25:532	302484	4aea4	Handler	Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\94802b1b3adeeb4feecfe2afe338b652\Windows6.1-KB4019990-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\94802b1b3adeeb4feecfe2afe338b652\inst
2019-11-19	19:50:26:923	302484	4ae78	Handler	FATAL: CBS called Error with 0x80073712, 
2019-11-19	19:50:26:936	302484	4aea4	Handler	FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80073712
2019-11-19	19:50:26:937	302484	4aea4	Handler	:::::::::
2019-11-19	19:50:26:937	302484	4aea4	Handler	::  END  ::  Handler: CBS Install
2019-11-19	19:50:26:937	302484	4aea4	Handler	:::::::::::::
2019-11-19	19:50:26:938	 956	4adb8	Agent	LogHistory called. idUpdate={5930D161-54D9-4205-BACD-13F48051D0C2}.501, resultMapped=80073712, resultUnMapped=80073712
2019-11-19	19:50:26:947	 956	4adb8	Agent	*********
2019-11-19	19:50:26:947	 956	4adb8	Agent	**  END  **  Agent: Installing updates [CallerId = wusa]
2019-11-19	19:50:26:947	 956	4adb8	Agent	*************
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	>>--  RESUMED  -- COMAPI: Install [ClientId = wusa]
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	  - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	  - Reboot required = No
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	  - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	---------
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	--  END  --  COMAPI: Install [ClientId = wusa]
2019-11-19	19:50:26:947	306816	4afa8	COMAPI	-------------
2019-11-19	19:50:26:953	306816	4ae88	COMAPI	-----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
2019-11-19	19:50:26:953	306816	4ae88	COMAPI	  - ServiceId = {2e9ff964-9980-4007-a6f3-c075169ec9a4}
2019-11-19	19:50:26:976	306816	4ae88	COMAPI	IUpdateService removing volatile scan package service, serviceID = {2E9FF964-9980-4007-A6F3-C075169EC9A4}
2019-11-19	19:50:26:977	 956	49c28	Agent	WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
2019-11-19	19:50:26:977	306816	4ae88	COMAPI	WARNING: ISusInternal::RemoveService failed, hr=80248014
2019-11-19	19:50:26:990	 956	4a4e0	AU	###########  AU: Uninitializing Automatic Updates  ###########
2019-11-19	19:50:26:993	 956	4a4e0	Report	REPORT EVENT: {D5512F90-3F7F-4E5C-82A9-380DC46498BF}	2019-11-19 19:50:25:459+0100	1	181	101	{5930D161-54D9-4205-BACD-13F48051D0C2}	501	0	wusa	Success	Content Install	Installation Started: Windows successfully started the following update: Update for Windows (KB4019990)
2019-11-19	19:50:26:993	 956	4a4e0	Report	REPORT EVENT: {147D623B-EF1B-42EE-93B2-BC48CD8951B1}	2019-11-19 19:50:26:938+0100	1	182	101	{5930D161-54D9-4205-BACD-13F48051D0C2}	501	80073712	wusa	Failure	Content Install	Installation Failure: Windows failed to install the following update with error 0x80073712: Update for Windows (KB4019990).
2019-11-19	19:50:27:001	 956	4a4e0	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
2019-11-19	19:50:27:002	 956	4a4e0	Report	WER Report sent: 7.6.7601.24085 0x80073712(0x80073712) 930D161-54D9-4205-BACD-13F48051D0C2 Install 501 0 wusa {2E9FF964-9980-4007-A6F3-C075169EC9A4} 0
2019-11-19	19:50:27:109	 956	4a4e0	Service	*********
2019-11-19	19:50:27:109	 956	4a4e0	Service	**  END  **  Service: Service exit [Exit code = 0x240001]
2019-11-19	19:50:27:109	 956	4a4e0	Service	*************
2019-11-19	19:51:46:137	303024	4a4bc	Misc	===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========

In CBS.log, when i try to install KB update

I have This One

2019-11-19 19:50:21, Error                 CSI    0004a893 (F) Could not find pending.xml identifier in registry.
[gle=0x80004005]
2019-11-19 19:50:21, Error                 CSI    0004a894@2019/11/19:18:50:21.742 (F) d:\win7sp1_gdr\base\wcp\componentstore\com\store.cpp(360): Store corruption detected in function `anonymous-namespace'::QueryPendingXmlIdentifier expression: 0RegistryCorruption on resource [50]"\Registry\Machine\COMPONENTS\\PendingXmlIdentifier"[gle=0x80004005]
2019-11-19 19:50:22, Error                 CSI    0004a895 (F) HRESULT_FROM_WIN32(14098) #488447659# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80073712]
2019-11-19 19:50:22, Error                 CSI    0004a896 (F) HRESULT_FROM_WIN32(14098) #488447657# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_Analyze(Flags = 1, riid = {f4d9decb-0250-4ad4-9500-85c7f2f281ec}, ppUnk = NULL, disp = 0)[gle=0x80073712]
2019-11-19 19:50:22, Info                  CBS    Failed to get transaction analysis. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to get inventory. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CSI    0004a897@2019/11/19:18:50:22.107 CSI Transaction @0x32c6b0 destroyed
2019-11-19 19:50:22, Info                  CBS    Failed to get inventory [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    ComponentAnalyzerEvaluateSelfUpdate call failed. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate self update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate non detect parent update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate non parent [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    failed to evaluate single applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to get applicability on updates [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Error                 CBS    Failed to call external evaluate applicability on package: Package_44_for_KB4015546~31bf3856ad364e35~amd64~~6.1.1.3, Update: 4015546-51_neutral_LDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate external applicability for package update: 4015546-848_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB4015546_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 4015546-848_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Failed to evaluate external applicability for package update: 4015546-1275_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB4015546~31bf3856ad364e35~amd64~~6.1.1.3, Update: 4015546-1275_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2019-11-19 19:50:22, Info                  CBS    Session: 30777098_845700349 initialized by client WindowsUpdateAgent.
2019-11-19 19:50:22, Info                  CBS    Appl: detect Parent, Package: Package_for_KB4015546~31bf3856ad364e35~amd64~~6.1.1.3, Parent: Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~ar-SA~6.1.7601.17514, Disposition = Detect, VersionComp: EQ, ServiceComp: GE, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2019-11-19 19:50:22, Info                  CBS    Appl: detectParent: package: Package_for_KB4015546~31bf3856ad364e35~amd64~~6.1.1.3, no parent found, go absent

After some check on registry 

I Don't have registry key in HKLM\Components\ like PendingXmlIdentifier or NextQueueEntryIndex or AdvancedInstallersNeedResolving

But in HKLM\SoftWare\Microsoft\Windows\CurrentVersion\SidebySide\CorruptionFlags\

I have 2 KEY Reg_SZ "CorruptPendingXML" value "01d15e17d13be65b" and "CorruptPendingXmlIdentifier" value "01d5a0216993f9e8"

And 2 key REG_DWORD Flags => 6144

LastCorruption => 13

I would like to know if it's my problem and what it means if possible.

Thank You

Hello,

We set up a new WSUS server on Windows Server 2016. We want to update\patch our corporate PCs that are on Windows 7 and Windows 10 1809. We DO NOT want to upgrade to new versions of Windows 10 via WSUS and we DO NOT want to update the WIndows 7 PCs to Windows 10. We are doing that trough SCCM or clean install. What option do I choose just to get updates/security update/critical updates... JUST for Windows 10 1809 and Windows 7 and not upgrades to newer versions? 

At the moment we only have one PC on this new infrastructure for testing purposes. It has Windows 10 1809 and Office 2016 and before joining it to our WSUS server it had all the latest updates from Microsoft downloaded from the Internet and installed. On the WSUS server from Products we selected Windows 10, Windows 7, Office 2016 (and 2013 for other PCs that will be added later) and from Classifications we selected Critical Updates, Definition Updates, Feature Packs, Security Updates, Update Rollups and Updates.
I also created an automatic approval rule for the group that the test PC is a member of for Critical Updates, Security Updates and Update Rollups. When I ran the rule I got over 5000 updates that were approved and over 400GB to download form Microsoft to the WSUS server. We got updates for Office 2013 and other older versions of Windows 10. Why is this happening? Isn't the automatic approval rule supposed to approve only the updates that are needed by the PC?

Please help because 400GB of data for just one PC seems too much to me.

Hi,

In our Monthly patching we have troubling to install Security Monthly Quality Rollup patches on Windows server 2012 R2.

Some severs getting keep failed to install ecurity Monthly Quality Rollup patches.

For Example last month patches KB4520005 failed like we have last  4 months patches.

Error code which we getting is 0X800F0831 in SCCM console.

we have installed latest servicing patches to this machines and all back troubleshooting link system file corruption, Rename software distribution folder, manual installation everything got unsuccessful.

Thanks,

Mohanbabu

Hello and sorry for my english,

In my WSUS i selected win 10, version 1903. In classification i have "upgrades, updates...
And all of this is accepted by default for my PC group in WSUS. 

Update on my computers works well with WSUS. Computers already in win 1903 receive updates.

but computers in windows 10 version 1809 or 1803 don't upgrade to win version 1903.

I don't understand why they don't upgrade to 1903. In this computers, in windows update, if i click for search update, they find nothing, they don't find the upgrade 1903.

thanks for help

Good Day,

Is there a way to setup WSUS to download Monthly Rollup KBs ONLY for Windows 7, Windows Server 2008, 2012 and 2016?

I want to login to WSUS and only see these KBs visible for me to approve and deploy to computers on our network.

Thanks much.

I'm running WSUS (standalone) on Server 2019.  All of our pilot machines on Windows 10 1909 are reporting to WSUS with build numbers of 18362 (1903) instead of 18363 (1909).

I understand that 1903/1909 share the same baseline and that the difference between them is basically a feature enablement package, but the different build numbers still need to be properly reported in WSUS. Otherwise, a whole bunch of reporting that I do just goes out the window.

Hello Support,

We are receiving Alert in Nessus Scan for Windows2016 Std R2.

i.e:-

I am unable to find this above the update packages. Kindly request you to provide a solution on this?

Regards

TLS

Hello

I've been at war with WSUS, getting it to install on a 2012 R2 member server in a 2008 domain.

The first stage of the role installation was fine, but the post installation tasks failed. First of all the security on the ..\webservices folders was not set correctly but I found a solution to that where iCACLS was used to grant permissions. Next, the NT SERVICE\MSSQL$MICROSOFT##WID account could not be used to start the WID service because it did not have the Log on as a service right.

It's this last bit that I'm having continuing problems with. I ended up using services.msc to change the WID logon to use the local system account which worked fine and the post installation tasks completed successfully. 

>>Note that WSUS is now up and running - updates are being downloaded and clients are reporting to the server.<<

However, when using Group Policy to grant the NT SERVICE\MSSQL$MICROSOFT##WID account the log on as a service right in User Rights Assignment I am unable to get the account recognised. I have tried using the full form NT SERVICE\MSSQL$MICROSOFT##WID and just the account itself and then using Check names to validate it, but it fails to validate.

I left the account name in the Log on as a service settings and rebooted the WSUS server in the hope that the service would be properly installed and registered on the system. Since then,as mentioned above, I abandoned the use of the account to start WID and chose the option to use the Local system account because NT SERVICE\MSSQL$MICROSOFT##WID has never been recognised. I also saw many SceCli 1202 events in the Application event logs stating an account cannot be resolved to a SID. Running the Find command against winlogon.log, MSSQL$MICROSOFT##WID is the culprit. I have now removed the account from the Group Policy setting.

My question is: can I leave the system account 'in charge' of WID? It seems clear that NT SERVICE\MSSQL$MICROSOFT##WID does not exist and is not affecting the performance of the WSUS installation.

Many thanks

Mark

Hey! So I'm upgrading a clients system to Windows 10. I want as little UWP app bloat as possible, so I'm using a PS script to remove all but the none essentials. 

My question is, where does the UWP apps get their updates from? The Windows Store app or WSUS? I want to remove the Windows Store app if possible. But I also want the apps I leave to be updated.

Thankful for any input on this!

The message "The service master key could not be force regenerated as requested by the -F startup option. The error number is 33094." appears in the Application log on the Windows 2012 R2 server that runs WSUS on our network.

For example:

9:40:59pm The service master key could not be force regenerated as requested by the -F startup option. The error number is 33094.
9:41:00pm The Windows Internal Database service entered the running state.

Nothing bad seems to happen as a result of this message popping up in the event logs, but I'd like to get to the bottom of it anyway.

I've Googled for a solution, but so far I haven't found one.

Matty Brown&lt;br/&gt; Computer Programmer (VBA 7.0/MS Access 2010, VB.Net 2005, ColdFusion 8)

Hi, 

Trying to deploy v1903 update to v1809 workstations.
Approved the update as I usually do, but WSUS reports 16 of those updates as "failed".

When checking the status on the workstation, it does not mention update even being tried to install (nothing about v1903 in update history). 

So which has correct information ; WSUS console or workstation's update history?

Hi

All my windows 10 in domain are 1903 version

In wsus console i have selected option (products an classification) "windows10" but there is another option "windows 10, 1903 and later"

Should i uncheck "windows 10" and check "windows 10,1903 and later"

Whats the diffrence? Please help

thx

Hi,
I noticed that my computers who have upgrade to windows 10 1909 have not the correct number version in wsus report.
They appears like 10.0.18362.xxx instead of 18363.xxx  (https://docs.microsoft.com/fr-fr/windows/release-information/)

Is it normal ?

Regards

Hi, 

I've approved v1903 update to be installed on rest of our workstations, since pilot went well.
However,  computers are struggling to download updates from WSUS server. 

It takes hours to download even the smaller updates. WSUS server is showing network traffic of 50kbps, which mostly is due my RDP connection to it. The speed randomly spikes to 50-100Mbps, but falls back to near zero in couple of seconds.

Currently there are 8 clients trying to download updates  (I'm told that single wsus server should be able to server this many clients). 

The server is virtual 2012r2 with latest patches installed. 2vCPU, 8Gb Ram, OS and Database disks are on SSD-disks. 
CPU Usage is less than 5% and memory usage 25%. The server has 10Gb nic connected to our lan. Clients has 1Gb network connection. 

I have rebooted the server couple of time, with no luck. 

After reboot, I'll get following errors in application log:

The Reporting Web Service is not working.

The API Remoting Web Service is not working.

The Server Synchronization Web Service is not working.

The Client Web Service is not working.

The SimpleAuth Web Service is not working.

The DSS Authentication Web Service is not working.

Exactly after 50minutes of previous error messages I get status messages on the eventlog:

Self-update is working.

The Reporting Web Service is working correctly.

The Server Synchronization Web Service is working correctly.

The Client Web Service is working correctly.

The SimpleAuth Web Service is working correctly.

The DSS Authentication Web Service is working correctly.

The WSUS content directory is accessible.

And exactly 10minutes after those informational messages, I get the same error messages again.

Any idea how to start troubleshooting this?

Apart from ms-updates, there has not been changes lately on the server. Problem may or may not relate wider approvement of win10 v1903 update.

Hello,

I have several servers

Operating System: Windows Server 2016

WSUS Server: Windows Server 2012

which are failing during the launch of "Check for updates"

The process has been tried several time and alwys the same error in return.

Some other fixes have been tried:

sfc /scannow
---------------------------------------------------------------
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Reboot

same error afterwards...

also

Press Windows key + R, type "services.msc" (without quotes) in start run box and press Enter. 
b. Locate Windows Update service.
c. Right click on the Windows Update service and select Properties.
d. In Start-up type, select Enable.
e. Click Start under Service status.
f. Click OK.
g. Repeat the steps c to f for the following services also:
Background Intelligent Transfer Service & Cryptographic Service.

No luck either...

I am providing also the ReportingEvents.log from the SoftwareDistribution folder...

{8C52BA2A-F087-47BF-9F19-29DEFBFFEB57}	2019-11-25 06:26:30:628-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{EC9723E1-26D1-4926-8F06-A3A74DDD80AC}	2019-11-25 06:32:46:670-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	<<PROCESS>>: CompatTelRunner.exe	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{65AC11E2-A706-4B72-AEC0-E1E8951EA011}	2019-11-25 06:34:28:955-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	<<PROCESS>>: CompatTelRunner.exe	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{01FFC349-F3EF-4B99-9388-27DE58B47CD0}	2019-11-25 06:45:27:969-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{769AD491-D914-41BE-AF69-21511ADB9365}	2019-11-25 06:45:32:359-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{0B8DF465-E8EA-4A15-9365-E2D31FDCC843}	2019-11-25 06:46:11:343-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{86B94752-AA43-4A11-B57F-C0B583E6D80E}	2019-11-25 06:52:30:612-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{AC0E2638-E6F9-493D-874B-50F267F01D96}	2019-11-25 07:03:33:633-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{F7970FD0-CFA8-44E5-9D7E-5CC2E7CDD84B}	2019-11-25 07:06:26:711-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{DB7CF3B2-D758-43FD-855E-C3D674B850C8}	2019-11-25 07:46:50:208-0800	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Device Driver Retrieval Client	Success	Software Synchronization	Windows Update Client successfully detected 3 updates.
{EF19D8A6-6C43-4B38-84FA-A6D6E78F33A0}	2019-11-25 07:47:21:338-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	UpdateOrchestrator	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.
{02F6707B-3688-4145-9ADC-6FDE60203FEA}	2019-11-25 08:01:57:200-0800	1	148 [AGENT_DETECTION_FAILED]	101	{00000000-0000-0000-0000-000000000000}	0	80244022	TrustedInstaller FOD	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244022.

Any idea?

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Hello,

We have about 50 Win 7 pro OEM workstations I'd like to upgrade to Win 10 pro via WSUS.  I am able to upgrade between versions of Win 10 without issues (1703 to 1903) for instance, but not Win 7 to Win 10 using OEM licensing...  On the console if I run a status report, it will say "Install, Not applicable".  If I change the product key on one of these OEM machines to a Win 7 VL key, then the console reads "Install, Not installed"...  I am then able to upgrade the machine via WSUS... 

These are HP OEM licenses with COA keys installed.  If I use a USB stick and install it manually, they'll all work.  I am running Server 2012 r2 (6.3.9600.18838) fully patched version.  I'm at a loss, anyone know why they won't upgrade via WSUS???

Thanks in advance...  Ken

Hello,

 I'm working on using WSUS to manage updates for our 2003 servers (as they're unsupported on our version of SCCM). I have around 300 Windows 2003 servers. They cannot all have the same update approved at the same time and nor can they be rebooted at the same time.

I was thinking of deploying say 5 different computer groups in WSUS and using GPOs to state which day of the week the updates will be deployed. I'm slightly lost on the best way to manage the computers and updates?

If I have 5 different computer groups in WSUS (let's say from least critical,1, to most important,5), will I need 5 different GPOs to deploy the updates? 

advice appreciated.

Thanks