PowerShell command outputting 'System.__ComObject' on Windows 11 23H2

VM 31

I am working on a Windows 11 23H2 system and attempting to retrieve installed update details using the PowerShell command below, but it's giving me an output of System.__ComObject:

$UpdateSession = New-Object -ComObject 'Microsoft.Update.Session'

$UpdateSearcher = $UpdateSession.CreateUpdateSearcher()

$Updates = $UpdateSearcher.Search('IsInstalled=1')

$result.Updates | Format-Table Title

Attached is a screenshot of the code and output for reference:

User's image

JAMES DEVERALL 0 Reputation points

2024-07-05T16:58:49.55+00:00

Seeing exactly the same thing via a longstanding script which has never not worked until recently on some devices. The script pulls individual properties for each update (e.g. Title, KB#, Size, etc ..) but has suddenly stopped working on a number of devices in recent weeks.

Removing the specificity of property and just returning the raw update is only returning System.__ComObject

Note: QueryHistory is not the answer as that is simply local OS inspection of install history. The specified query is a direct enquiry with Windows Update servers for Installed or NotInstalled. It is these returns from WU which appear to malformed for 'some' devices now.
JAMES DEVERALL 0 Reputation points

2024-07-05T17:45:17.38+00:00

The ComObject is not holding the same properties therefore the data within can't be extracted as expected..

Working device

versus a device where API query is failing

This feels like an issue at source (e.g. MS/OS) presumably due to a recent update (?)

We've seen some experience of the issue disappearing when this update is uninstalled - https://support.microsoft.com/en-gb/topic/june-25-2024-kb5039302-os-builds-22621-3810-and-22631-3810-preview-0ab34e3f-bca9-4a52-a1a4-404bf8162f58 - though some other devices have not resolved.

Please help MS. What's going on here?

1 answer

MotoX80 32,556 Reputation points

2024-07-02T14:13:23.6733333+00:00
You have a slight problem because there is no $result variable. That doesn't matter because even if you use the $Updates variable, you still have the same problem. I found that your code works for me on Win10, but fails on my Win11 22H2 laptop.

To query update history you can use this code.

$UpdateSession = New-Object -ComObject 'Microsoft.Update.Session' $UpdateSearcher = $UpdateSession.CreateUpdateSearcher() $UpdateSearcher.QueryHistory(0,100) | format-table -Property ResultCode, Date, Title

You can also use the PSWindowsUpdate module. Here is what I use.

# Install-Module -Name PSWindowsUpdate # run this to install it Get-WUHistory -Last 100 | where-object -Property Title -notlike "Security Intelligence Update*" | format-list -Property Result, Date, Title

Note that Get-WUHistory hangs for me if I don't limit the search with a -Last parameter.
Please sign in to rate this answer.
VM 31 Reputation points

2024-07-02T15:28:16.9666667+00:00

Your code is giving no output.

As you said "You have a slight problem", can you assist to resolve that problem or help with more information what has caused to this problem?

Richard Rodriguez 0 Reputation points

2024-07-02T18:29:16.88+00:00

I'm seeing the same thing, but only when the WU Agent version is >1300.x.x.x

Until recently, I could force WUA back to 12xx.x.x.x

by flipping a seemingly experimental reg key from value=2 to value=1. Though this doesn't seem to do anything anymore as of the latest cumulative preview.

HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\1931709068

VM 31 Reputation points

2024-07-02T19:03:06.9666667+00:00

Will there be any serious issue if we modify the mentioned registry key like system will be vulnerable or we are opening any security on the system.

I actually tried that registry modification as well but after couple of days that registry value is reverting back to the original value that is 2.

Any chance we can report this to Microsoft as it seems some changes happened recently in the OS regrding Windows Update API that its not sending the proper output.

MotoX80 32,556 Reputation points

2024-07-02T21:14:52.25+00:00

Can you try the QueryHistory call on another machine? It's working for me on both Win10 and 11.

Is using the PSWindowsUpdate module an option?

Richard Rodriguez 0 Reputation points

2024-07-02T21:17:51.82+00:00

The registry key doesn't seem to help anymore, at least not on my machines.

I do think Microsoft may have a bug in the UUS Preview 1305.x and higher that is breaking this generally. But I don't know any way of submitting support issues or bugs to them.

Richard Rodriguez 0 Reputation points

2024-07-02T21:20:59.4+00:00

@MotoX80 What do you get back from this command on your Windows 11. If its less than 1300.x.x.x I would expect it to work fine. Though I have seen devices on 13xx work IF they are opted in to Insider Preview--which is pretty weird.

(New-Object -ComObject Microsoft.Update.AgentInfo).GetInfo('ProductVersionString')

Also, notably OP isn't using QueryHistory, he's using $UpdateSearcher.Search('IsInstalled=1')

MotoX80 32,556 Reputation points

2024-07-02T21:42:22.96+00:00

1306.2405.21022.0

Sure looks like a bug. That returned COM object doesn't have any properties. I can't do anything with it.

The Feedback Hub is the "free" way to report a bug. Premier Support is what I used back when I was working, but that's been a while.

Even if you get MS's attention it might a while to get a fix, so that's why I was asking about QueryHistory and PSWindowsUpdate.

VM 31 Reputation points

2024-07-03T08:21:22.4666667+00:00

Richard Rodriguez, MotoX80

Thank you for your input. We use the mentioned command in the initial description to fetch our client's patching status. The command is still working on other client and server Operating systems. It was also working on Windows 11 23H2 till a month ago and since May 2024 the mentioned command is getting failed on Windows 11 23H2.

Using alternate commands is not a solution until Microsoft confirms that it will not be going to work. We need a solution to resolve this issue with the same command.

As you guys also find the same issue, is there a way for us that from here we can forward this issue/forum discussion to Microsoft so that they can also take a view once?

MotoX80 32,556 Reputation points

2024-07-03T12:41:08.1433333+00:00

I am not affiliated with Microsoft, so my thought would be to follow the public MS web site links for support.

https://support.microsoft.com/en-us

Under "More support options", there is a link for "Support for business".

https://support.serviceshub.microsoft.com/supportforbusiness

Please post back here with what you find. If we can help out, just let us know.

MotoX80 32,556 Reputation points

2024-07-03T13:15:05.6966667+00:00

Concerning your "slight problem"....

$UpdateSession = New-Object -ComObject 'Microsoft.Update.Session' $UpdateSearcher = $UpdateSession.CreateUpdateSearcher() $result = $UpdateSearcher.Search('IsInstalled=1') # assign to result variable $result.Updates | Format-Table Title
Sign in to comment

Share via

PowerShell command outputting 'System.__ComObject' on Windows 11 23H2

1 answer