Windows Update Sensor Error after update

Is this about the Windows Updates Status (Powershell) Sensor?

If so, run this command in Powershell on (at least) one the affected target hosts: $searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher();$searcher.Search("Type='Software'").Updates | Sort-Object -Property Dates -Descending | ft -autosize IsInstalled, MsrcSeverity

What output do you get?

Kind regards.

Hi

Thank you for the answer. I don't have any output with that command.

PS C:\Users\_ddata> $searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher();$searcher.Search
("Type='Software'").Updates | Sort-Object -Property Dates -Descending | ft -autosize IsInstalled, MsrcSeverity
PS C:\Users\_ddata>

Best Regards

Sorry, about the sensor, it is:

Windows Updates Status (Powershell)

Then it looks like the sensor's assumption (Could not retrieve update data) is correct :)

The command is basically the same the sensor let's the target execute, then it processes the reply. Try restarting Windows Update Service to see if that helps. Other than that a reboot of the target should fix the issue in case there's nothing else going wrong with WSUS configuration that we can't tell from the sensor's result alone.

Kind regards.

Hi,

I got the same error after removing and re-installing WSUS due to that KB3148812 issue. https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

I did that on 4 different customer Servers.
Three throwing the PE205 error message, one working.

Any assumption what might cause this problem.

Regards W.

I'm afraid that we can't tell why this happens on some systems, we suggest contacting the vendor in this case.

Hi,

I have a similar problem: I can run the command on an affected host an I get an output. If I run this command from the probe with Enter-PSSession [AffectedHost] I don't get an output.

On the affected hosts and on the probe I've installed .NET 3.5, .NET 4.5, PS 2.0 and PS 4.0

Do you have any ideas what else we can do or check?

Thank you!
Bastian

Hello Bastian,
thank you for your reply.

This most likely indicates an issue with PSRemoting, which would explain why the sensor doesn't work. Unfortunately we cannot troubleshoot powershell remoting, it is a windows component/feature. Do other commands work if you perform an Enter-PSSession from the probe to one of the monitored systems?

You might also want to check the following articles:

• Windows Updates Status (Powershell) not working
• Windows Update (powershell) Timeout (code: PE018)
• Windows Updates Status (Powershell) sensor is failing with error 0x80244007
• Windows Update Status (powershell) sensor on Windows Server 2012

Best Regards,
Luciano Lingnau [Paessler Support]