On 05/14/2026 1:17 PM, Maria Sophia wrote:
....winston wrote:
That command won't work for most, unless they first install the PS
Windows Update module, which by design is not included by default.
Also, prior to use of that command a higher policy level is required
since the module is normally interpreted as originating from an
untrusted repository requiring either:
Set-ExecutionPolicy RemoteSigned
or use of the
Set-PSRepository commandlet option
Your printout doesn't mean much with respect to Windows May 2026
cumulative update.
- it's only showing(as expected) the 'other' type of updates
Available driver updates(Windows Update/'View optional updates' and an
available Defender update(one not yet installed, but available)
If your comment was intended to show 'what was installed' after updating
with the May updates, you should have run:
Get-WUHistory
....and looked at the first group of lines from the output for what was
installed in May 2026.
Hi Winston,
Thank you for pointing out that I should have clarified that I'm using the PSWindowsUpdate module from the PowerShell Gallery, which, as you noted,
does require bypassing the default restricted execution policy (most often via Set-ExecutionPolicy RemoteSigned) before the environment will even load the module. I must have done that long ago and forgot that I had done it.
Thanks for helping out as the command would fail for others without that!
And the whole point of providing the command/results is to help others.
You're also right that Get-WindowsUpdate only shows the pending state.
Those aren't pending. They've been present as noted in 'Other updates'
for most devices running Win10 for years.
- they're are optional drivers that can be installed if necessary.
Orignally submitted to MSFT by the OEM for the as-shipped os as an
option if later more current manufacturer or Windows provided drivers
appear to/cause a problem. In some cases, they could also be later than
the as-shipped drivers, submitted as updates(for inclusion in Windows)
as replacements or additional legacy drivers but only until end of
support for that OEM device(but...these are rare, and typically only
submitted to fix an existing, known currently installed OEM driver
problem or corruption.
My goal was to highlight that for those of us not on ESU, the queue is noticeably empty of actual OS patches, leaving only Windwows Defender definitions and OEM drivers as the typical non-ESU Windows updates.
See above w/r to OEM drivers
To your point about verification, here is the output of Get-WUHistory.
As we both would have expected, it's a ghost town for cumulative updates:
PS C:\Windows\system32> Get-WUHistory | Select-Object -First 10
ComputerName Operationname Result Date Title
------------ ------------- ------ ---- -----
E Installation Succeeded 5/14/2026 10:16:... Security Intelligence Update for...
E Installation Succeeded 5/13/2026 5:35:4... Windows Malicious Software Remov...
Despite Patch Tuesday having come and gone, the history is entirely
populated by KB2267602 (Security Intelligence) and the monthly MSRT. .
MSRT are monthly release, but also cumulative(i.e. one can skip a month
using any available option restricting Windows updates.
But OS security hardening has stopped for non-ESU boxes.
In summary, if it's not an ESU machine, then Patch Tuesday has
effectively become malware definition & driver Tuesday instead.
Old news, we knew this in 2022 that 22H2 was the fourteenth and last
feature update and it's last security update would occur in Oct. 2025
for devices not enrolled in ESU.
--
...w¤?ñ?¤
--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)