Search Results for 'PSWindowsUpdate'

I tried the PowerShell approach from

https://www.minitool.com/news/how-to-check-update-history-on-windows-11.html :

++++

PS C:\Windows\system32> Install-Module PSWindowsUpdate

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘2.8.5.201’ or newer to interact with NuGet-based repositories. The NuGet provider must be available in ‘C:\Program Files (x86)\PackageManagement\ProviderAssemblies’ or
‘C:\Users\User\AppData\Local\PackageManagement\ProviderAssemblies’. You can also install the NuGet provider by running ‘Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force’. Do you want PowerShellGet to install and import
the NuGet provider now?
[Y] Yes [N] No Suspend [?] Help (default is “Y”): y

Untrusted repository
You are installing the modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure you want to install the modules from ‘PSGallery’?
[Y] Yes [A] Yes to All [N] No [L] No to All Suspend [?] Help (default is “N”):

+++

Is it trustable?    Even so, it is a surprise to be asked since NuGet is (apparently) already installed:  version 2.8.5.208.  (… ProviderAssemblies and … Roaming).  What to  do?

 

Specific to Windows 11 computers, has anyone else experienced any issues with running an update after the 07-2024 cumulative update was installed?

I specifically run the powershell PSWindowsUpdate remotely on a few computers to force updates on the few Windows 11 machines we have. However, the following error appears for the two updates it finds to apply:

Are you sure you want to perform this action?
Performing the operation “(7/12/2024 8:46:02 AM) Windows Malicious Software Removal Tool x64 – v5.126 (KB890830)[70MB]” on target <hostname>.
[Y] Yes [A] Yes to All [N] No [L] No to All Suspend [?] Help (default is “Y”): y
Get-WindowsUpdate : Something goes wrong: Windows Malicious Software Removal Tool x64 – v5.126 (KB890830); Object reference not set to an instance of an
object.
At line:1 char:1
+ Get-WindowsUpdate -Download -Install
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [Get-WindowsUpdate], Exception
+ FullyQualifiedErrorId : Debug,PSWindowsUpdate.GetWindowsUpdate

Get-WindowsUpdate : Something goes wrong: Windows Malicious Software Removal Tool x64 – v5.126 (KB890830); Object reference not set to an instance of an
object.
At line:1 char:1
+ Get-WindowsUpdate -Download -Install
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [Get-WindowsUpdate], Exception
+ FullyQualifiedErrorId : Debug,PSWindowsUpdate.GetWindowsUpdate

X ComputerName Result KB Size Title
– ———— —— — —- —–
1 <hostname> Rejected KB5007651 18MB
1 <hostname> Rejected KB890830 70MB

The out put in the CBS.log file pertaining to the error:

2024-07-12 08:47:01, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:01, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:01, Info CBS Failed to create open package. [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:01, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2024-07-12 08:47:02, Info CBS Session: 31118425_2541975050 initialized by client WindowsUpdateAgent, external staging directory: (null)
2024-07-12 08:47:02, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:02, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:02, Info CBS Failed to create open package. [HRESULT = 0x800f0805 – CBS_E_INVALID_PACKAGE]
2024-07-12 08:47:02, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

The KB in the errors points to a Windows Technical Preview December Update from 2014.

I’m not sure what is going on, but it’s only happening on the Windows 11 computers in our environment.

@RetiredGeek

Ran into this issue myself today..

Carter/Guest, if you are still around as a guest and see this, thank you for posting the details as well.

From what I can tell, somewhere along the way of updates to PSWindowsUpdate, the developer/maintainer must have changed the way the modules “Get-WUSettings/Set-WUSettings” commandlets/functions work and introduced a issue/bug..

I found today that if any policy/config for WindowsUpdate exist in:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

or below in a sub key it seems… and the value named “UseWUServer” is not present at:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

The module’s function for reading the values encounters an error. Although there are policies that can be configured without configuring the use of a WSUS server, it appears that if  “UseWUServer” is not present (set to either 0 or 1, with 0 being to not use a WSUS Server and 1 being to use a WSUS Server) but any other setting is present, you will receive an error:

Object reference not set to an instance of an object.

Possibly the same issue noted in the GitHub issue for the module at the followin:
https://github.com/mgajda83/PSWindowsUpdate/issues/21

 

Eric,

You can completely control windows updates via PowerShell as follows:

Start PowerShell as Admin

Install the PowerShell PSWindowsUpdate Module:

Set-ExecutionPolicy RemoteSigned -Force
Install-Module -Name PSWindowsUpdate -Force

Retrieve a list of Updates:

PS> get-wulist

ComputerName Status     KB          Size Title                                 
------------ ------     --          ---- -----                                 
DELLXPS8920  -------    KB890830    68MB Windows Malicious Software Removal ...
DELLXPS8920  -------    KB5038350   55MB 2024-05 .NET 6.0.30 Security Update...
DELLXPS8920  -------    KB5038351   55MB 2024-05 .NET 7.0.19 Security Update...
DELLXPS8920  -------    KB5037591   66MB 2024-05 Cumulative Update for .NET ...
DELLXPS8920  -------    KB2267602    1GB Security Intelligence Update for Mi...
DELLXPS8920  -------                 3MB HP - Printer - 4/22/2009 12:00:00 A...
DELLXPS8920  -------               336KB Qualcomm Atheros - Net - 9/9/2016 1...
DELLXPS8920  -------                 5MB Dell. - Firmware - 0.1.0.23           
DELLXPS8920  -------    KB5037771  128GB 2024-05 Cumulative Update for Windo...

Hide an update:

PS> Hide-WindowsUpdate -KBArticleID KB5037771

ComputerName Status     KB          Size Title                                 
------------ ------     --          ---- -----                                 
DELLXPS8920  ---H--     KB5037771  128GB 2024-05 Cumulative Update for Windo...

Check for Hidden updates:

PS> get-wulist -IsHidden

ComputerName Status     KB          Size Title                                                           
------------ ------     --          ---- -----                                                           
DELLXPS8920  ----H--    KB5037771  128GB 2024-05 Cumulative Update for Windows 11 Version 23H2 for x64...

Note: the H Status flag above.

Unhide a hidden update:

PS> UnHide-WindowsUpdate -KBArticleID kb5037771

ComputerName Status     KB          Size Title                                                           
------------ ------     --          ---- -----                                                           
DELLXPS8920  ------     KB5037771  128GB 2024-05 Cumulative Update for Windows 11 Version 23H2 for x64...

Check to see things are back as started:

PS> get-wulist

ComputerName Status     KB          Size Title                                                           
------------ ------     --          ---- -----                                                           
DELLXPS8920  -------    KB890830    68MB Windows Malicious Software Removal Tool x64 - v5.124 (KB890830) 
DELLXPS8920  -------    KB5038350   55MB 2024-05 .NET 6.0.30 Security Update for x64 Client (KB5038350)  
DELLXPS8920  -------    KB5038351   55MB 2024-05 .NET 7.0.19 Security Update for x64 Client (KB5038351)  
DELLXPS8920  -------    KB5037591   66MB 2024-05 Cumulative Update for .NET Framework 3.5 and 4.8.1 fo...
DELLXPS8920  -------    KB2267602    1GB Security Intelligence Update for Microsoft Defender Antivirus...
DELLXPS8920  -------                 3MB HP - Printer - 4/22/2009 12:00:00 AM - 10.0.17119.1             
DELLXPS8920  -------               336KB Qualcomm Atheros - Net - 9/9/2016 12:00:00 AM - 2.1.0.26        
DELLXPS8920  -------                 5MB Dell. - Firmware - 0.1.0.23                                     
DELLXPS8920  -------    KB5037771  128GB 2024-05 Cumulative Update for Windows 11 Version 23H2 for x64...

Note: Do not type the PS> in the above examples that is the PowerShell prompt.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

2 users thanked author for this post.

Blizzard, windbg

Thanks Susan for the update. MSFT patches have become more frustrating vs being helpful I feel. I think they just don’t care for about the consumer any longer nor the MSPs/IT Tech companies that have to fix their “SHTUFF”.
When you posted this earlier this year I created a blog (https://jvhconsulting.com/2024/01/13/windows-10-kb5034441-security-update-fails-with-0x80070643-errors/) to show how to resize the partition to install but also found quick powershell means to just block the patch which I run on all my supported endpoints:
Set-ExecutionPolicy Unrestricted -Force 
Install-Module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll

Works like a charm. Can also run: Get-WindowsUpdate -IsHidden to show which patches are hidden on the computer.

On another note, has anyone noticed a trend lately of more computer systems blue-screening – I have in the past few weeks has about a dozen computers run into this problem Varios BSOD stop errors but all have similar resolutions: Run Verifier.exe /reset (or verifier /bootmode resetonbootfail) to get the systems to stop having BSODs.
In the words of Elmer Fudd, dere’s something skewy going on here!

2 users thanked author for this post.

windbg, kewlputergeek

RetiredGeek wrote:

You can do this very easily with PowerShell and without external software.

Apart from installing PSWindowsUpdate from an untrusted repository?

In the Searchbar, type PowerShell
Right click on “Windows Powershell” and choose “Run as Administrator”
Copy and paste each of these lines intoPowerShell, one at a time, press Enter after each one

Set-ExecutionPolicy Unrestricted -Force
install-module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll

Close PowerShell
This will hide KB5034441

2 users thanked author for this post.

windbg, WSBirdLady

suggest hiding update using powershell:

Set-ExecutionPolicy Unrestricted -Force
install-module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll

 

2 users thanked author for this post.

rc primak, Win7and10

Thanks Susan for this post… I too have found this patch incredibly frustrating and have setup via my RMM to block the install and if not used the powershell commands to block it

Set-ExecutionPolicy Unrestricted -Force
install-module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll

I put all this in my blog at jvhconsulting.com where I linked your previous newsletter about solutions.

Glad to be a part of this newsletter as it is incredibly good information to share.

thanks
Joost van Haaren

Hello all

Thanks for posting this information. I was troubleshooting this yesterday and found a site that showed how to resize the Recovery Partition in order to get the patch to install… I found that the Recovery had to be resized to 1GB or greater. I wrote a blog about it here: jvhconsulting.com – https://jvhconsulting.com/2024/01/13/windows-10-kb5034441-security-update-fails-with-0x80070643-errors;

it uses Diskpart to remove, recreate recovery partition based on MBR or GPT disk types after shrinking space off OS drive (550mb). After doing this the patch installs okay.

Today after reading your article and also trying the WUHowHide.diagcab tool to block /hide the KB5034441 article I figured there must be a way to do this via powershell – especially since in my RMM I had about 35 Machines needing this fix.

While I haven’t gotten the RMM script to work successfully (yet), the commands do work from a remote command prompt-powershell.

Here are the commands for Win10/11 machines to Hide this KB5034441 patch from the system and remove the error
Set-ExecutionPolicy Unrestricted -Force
install-module -name PSWindowsUpdate -Force
Hide-WindowsUpdate -KBArticleID KB5034441 -AcceptAll

After running above the output below shows, indicating the KB is Hidden by the H in Status Column:
ComputerName Status KB Size Title
———— —— — —- —–
<PCNAME> D–H– KB5034441 23MB 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems

Hope this helps! I plan to update my blog with this info. (jvhconsulting.com).

Regards
Joost van Haaren
JVH Consulting, LLC

1 user thanked author for this post.

kewlputergeek

Good Morning, Afternoon, Evening, or Night,

I have found the problem,
Apparently PSWindowsUpdate does not like it when there is no updateserver url set at
“HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\WUServer”
and
“HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\WUStatusServer”
keep in mind that WUServer and WUStatusServer are not folders but are instead items of the folder WindowsUpdate in the registery

So if you were to remove one it would look like this:
Remove-ItemProperty -Path “HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate” -name “WUServer”
hope this helps!

Susan

While this all makes sense – none of it is applicable to my scenario. WSUS in a small WORKGROUP scenario where we have never used WUfB – or ever used ConfMgr or any other tools.

After spending an extraordinary amount of non-productive time on this – I finally decided that enough was enough and finally began a planned transition to using Powershell (PSWindowsUpdate) to handle our updates for the future.

I inherited this rickety old WSUS layout some time ago and it’s clear that since MS is not exactly showing WSUS any further long term love – neither can I. Making sure our little community office is properly updated is more of a priority than troubleshooting WSUS.

For the small amount of client machines (15) in my scenario – using PSWindowsUpdate is fast, furious and completely hands off (once I got my script exactly the way I wanted it).

Thanks for the updates and continued success.

Cheers

Sonic.

 

 

Thank you, Paul T.  I failed to find this problem under the AskWoody Knowledge Base, but did verify your response from the software author’s WUMgr Issues list on GitHub.

From Issue #59,  https://github.com/DavidXanatos/wumgr/issues/59

“The problem is the Windows Update API returns a update size based on ‘maximum size’ and how MSFT calculated this is unknown. If you were to use something like PSWindowsUpdate Powershell Module for comparison you’d see the same size.

If you actually download the update via the API or tools that use it, it will only download the 839MB it actually needs.

So sadly its not something that can probably be fixed in this tool as its an issue or limitation of the upstream data”

Here we go again!

Brand new just out of the box Beelink Ser 5500u w/Windows 11 Pro.
I thought surely this would work but it’s not to “bee”, get it?, same error.
GPEdit works fine on this machine so that’s not the problem.

Installing the previous version of the PSWindowsUpdate module didn’t work either.

Grrrrrrrrrrrrrrr!

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

MBS,

Well, that got me to thinking… Possible solution…

Uninstall-Module -Name PSWindowsUpdate -Force
Install-Module -Name PSWindowsUpdate -RequiredVersion 2.2.0.2 -SkipPublisherCheck -AllowClobber

So that got the right module loaded, however it did not solve the problem in either WindowsPowerShell 5.1 or PowerShellCore 7.3.4.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs