Hello, 

none of my computers wont report to my WSUS Server, but show up in the Update Services Manager.

I have one Windows Server 2016 and one 2012, both wont report. 

The WSUS is using WID, not SQL.

WSUS was installed by the official Microsoft Manual.

I have tried serveral things including the following: 

On the 2012 Server:

wuauclt.exe /detectnow

 wuauclt.exe /reportnow

wuauclt.exe /resetauthorization /detectnow

On the 2016 Server:

$AutoUpdates = New-Object -ComObject "Microsoft.Update.AutoUpdate"

$AutoUpdates.DetectNow()

Tried to re-index the WSUS Database with this:  gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

Changed the Port for the Reporting Server in the GPO, which is the wsus itself, to 80 instead of 8530

Restarted all servers several times.

The Permission for the Network Service Account should be right too,unfortunalty im not able to post screenshots now.

Am i supposed to get a IIS Default site when i enter http://wsusname:8530, because right now im only getting it when i use port 80. Im not getting an error page when i try with 8530, the page is just blank.

We have WSUS installed on server 2012r2.

We are currently unable to download and install updates to 2016 servers.

Updates are working fine on all of our 2012r2 servers and 7 / 10 (1703-1809) desktops.

When I press retry to install updates on 2016, the updates briefly appear to start downloading, and then we get "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet.".

In the eventlog of the 2016 servers we get:

Source Windows Error Reporting EventID 1001

Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.14393.594
P2: 80072ee6
P3: 6C9FE01B-DAE1-44FB-9770-61DFD0D958CE
P4: Download
P5: 201
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 73a47fdc-e7ec-11e8-ade2-00155d368f27
Report Status: 262144
Hashed bucket: 

I've tried to get the windows update log by running 

Get-WindowsUpdateLog -SymbolServer https://msdl.microsoft.com/download/symbols

But it doesn't seem to be decoding the logs correctly.

I have tried updating manually installing the latest servicing stack https://support.microsoft.com/en-ae/help/4465659/servicing-stack-update-for-windows-10 - this didn't help.

I have also made some changes to the WSUS application pool settings:

This hasn't made a difference.

Hi Support,

We have not configured WSUS server in our network but we are getting “0x8024401f”  error in windows server 2016.

Please help us to rectify this error.

Hi support,

We have an issue in Windows server 2016 .

We are not able to update of windows server where WSUS is configured. 

Please help to rectify this issue.

Thanks

Tanmaya

Tanmaya.mahandru@knackglobal.com

I am trying to get the Windows Update logs on a System with Windows Server 2016 and Windows 10 build 1607 using powershell commandlet Get-WindowsUpdateLog. However, the output that I get, has random guids as below:

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 25): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 207): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 12): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 13): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 14): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 15): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 16): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 20): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 10): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 126): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 146): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 57): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 10): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 125): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 145): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 185): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 194): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 241): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

I connected the system to internet to update the SymCache. After connecting to the internet, few guids were resolved. However, most of the log is still unreadable.

Is there a way to resolve the entire update log without internet connection?

The size of my current SymCache folder is around 18 MB. What is the expected size of this folder?

Cross-post reference on Microsoft Answers : https://answers.microsoft.com/en-us/windows/forum/all/windows-update-logs-are-not-generated-properly-for/09479264-e1ad-4a68-b619-f752264a0926

computer A is in WSUS group B and WSUS Group C.

update D is approved for install on WSUS Group B, and Not Approved for Group C.

is computer A going to detect/install update D?

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

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

What is the issue here? A bug?

Best regards

Birdal

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?

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

I am trying to find the date/time when these 2 updates were installed and why before the specified date/time in GPO?

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)

Hi,

 Windows Malicious Software Removal Tool x64 - April 2019 (KB890830) doesn't install via WSUS but can be installed manually on some of our servers. This has increased our workload by having to install this tool manually and running it on affected servers to get a 100% completion report. I have looked at the logs and have not found anything unusual. The client simply reports back to WSUS as it requires this update but doesn't install it even if I have set a deadline against it on WSUS. I would appreciate if anyone can help.

Thanks

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,

I have a bunch of machines pointed to my WSUS Server for updates.

I would like to enable Delivery Optimization - Local PC's Only on my machines via a reg key (Non domain).

Overall, when I look at my DO DownloadMode and change the value from 1 to 1, this does not change the delivery optimization in the GUI.

I am not sure what I am missing here?

Once again, I want machine to get updates via WSUS.. but also utilize delivery optimization. 

Eventually, I will be using WSUS for report only and have all my client's go directly to the web for updates & also utilize delivery optimization.



Any assistance would be appreciated. Thanks

WSUS says my clients and servers need either KB4489488 and KB4489486 (.NET), depending on the OS. WSUS lists these as "Updates". However, if I go straight to Microsoft Update it says I don't need it, it isn't listed as an option update either. I am struggling to figure Microsoft out. I can't tell if this is a WSUS issue (don't think so).

Jason

Everything seemed normal but I realize that I'd not yet set up AD completely.  So, going through the steps and when I get to NEXT and INSTALL, they are both grayed out on the page.