This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 59%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
I have a Windows Server 2019 as a WSUS Server. I am having problems with WSUS Server 2019 clients. WSUS Server 2012 clients do not show the last reported status.
Hello @Jackson Pedrini I hope you are doing well
The "Not yet reported" or missing "Last Reported Status" in the WSUS console indicates that client machines (specifically Windows Server 2012 clients) are not successfully communicating with the WSUS server to report their update status. This could be due to network issues, WSUS misconfiguration, client-side problems, or Azure-specific restrictions. Since Windows Server 2019 clients are not mentioned as having the same issue, the problem may be specific to Windows Server 2012 compatibility or configuration differences.
Potential Causes in an Azure Environment
Troubleshooting Steps (Azure-Focused)
Get-Service -Name WSUSService, W3SVC Start if stopped: powershellCopyStart-Service WSUSService Start-Service W3SVCTest-Connection -ComputerName localhost -TcpPort 1433 If using WID, verify the database file (SUSDB.mdf) in C:\Windows\WID\Data is not corrupted.Restart-WebAppPool -Name WsusPoolThe "Not yet reported" or missing "Last Reported Status" in the WSUS console indicates that client machines (specifically Windows Server 2012 clients) are not successfully communicating with the WSUS server to report their update status. This could be due to network issues, WSUS misconfiguration, client-side problems, or Azure-specific restrictions. Since Windows Server 2019 clients are not mentioned as having the same issue, the problem may be specific to Windows Server 2012 compatibility or configuration differences. Potential Causes in an Azure EnvironmentGet-Service`` ``-Name`` WSUSService, W3SVC Start if stopped: powershellCopyStart-Service`` WSUSService ``Start-Service`` W3SVC Test-Connection`` ``-ComputerName`` localhost ``-TcpPort`` ``1433 If using WID, verify the database file (SUSDB.mdf) in C:\Windows\WID\Data is not corrupted.Restart-WebAppPool`` ``-Name`` WsusPool😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!
Just following up, Do you need more guidance or assistance ?
Yes, I did, but it didn't work.
Hello @Jose Benjamin Solis Nolasco , all configuration parameters are OK. As you can see in the attached image, through the connection test, the client can communicate normally with the WSUS server. The only problem is that it does not generate the last report.
Try this on one WS2012 client you can play with without affecting Production:
(Get-Item "C:\Windows\System32\wuaueng.dll").VersionInfo.FileVersion
Update the Windows Update Agent (WUA):
Enable TLS 1.2 on Windows Server 2012:
New-Item 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp' -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp' -Name 'DefaultSecureProtocols' -Value 0x00000800
New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Name 'Enabled' -Value 1
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Name 'DisabledByDefault' -Value 0
Clear WSUS Client State:
- Stop the Windows Update service, delete the SoftwareDistribution folder, and restart the service on affected clients: powershellCopy
net stop wuauserv Remove-Item -Path "C:\Windows\SoftwareDistribution" -Recurse -Force net start wuauserv wuauclt /detectnow /reportnowForce Manual Reporting:
>
- On affected clients, trigger detection and reporting:
```yaml
wuauclt /detectnow wuauclt /reportnow
I have already performed these actions and have not been successful. As you can see in the image, the client version is already the most recent.
Did you try also removing one of those WS2012 Server from WSUS and re-adding? last time that worked for me.
Follow my guide from top to bottom.
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/
It should get you going. Even if you think you've done it before, DO IT WITH MY GUIDE, especially the 1st part. It should get you going again with that client.