ModuleStatus Step Failure

Patch Remedy 5 is the next generation of the Plugins4Automate Patch Remedy family of products.
This forum is used to support Patch Remedy 5 only, if your using a previous version of Patch Remedy please see the forum for that version below.
Inside you will find the documentation project for the plugin were you can get insights on how to operate and use Patch Remedy 5.
Post Reply
mikey090tx
Posts: 9
Joined: Wed Sep 27, 2023 8:31 pm
1

ModuleStatus Step Failure

Post by mikey090tx »

@Cubert-

Recently we have seen a failure during the P4A Patch Remedy Scans script and it appears in the Module status steps. I have observed a variety of agents return the following error: import-module : The specified module 'PSWindowsUpdate' was not loaded because no valid module file was found in any module directory.

User avatar
Cubert
Posts: 2549
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: ModuleStatus Step Failure

Post by Cubert »

Interesting,


The `PSWindowsUpdate` PowerShell module is a third-party module that allows you to manage Windows updates from the command line using PowerShell. It provides cmdlets to check, download, install, and remove updates on local or remote computers.

- **PowerShell Gallery**: The official page for the `PSWindowsUpdate` module on the PowerShell Gallery provides detailed information, including the latest version, dependencies, and usage examples. You can visit it at (https://www.powershellgallery.com/packa ... dowsUpdate).

- **Documentation**: The module's documentation, including cmdlet descriptions and examples, can be found on the PowerShell Gallery page or within the module itself using the `Get-Help` cmdlet.



On the agent in question, execute the following command and see what it returns.

Code: Select all

Install-Module -Name PSWindowsUpdate -Force -Scope CurrentUser
You can verify module installed using the following cmd

Code: Select all

Get-Module -ListAvailable PSWindowsUpdate
If that is good then import the module with the following cmd

Code: Select all

Import-Module PSWindowsUpdate
Lastly, test that the module is working as expected with this cmd

Code: Select all

Get-Command -Module PSWindowsUpdate
It should return a list of available cmds in the module.

Lets see if we can get through this on one of your affected agents. hopefuly it will return an error that we can then resolve.

Post Reply

Return to “Patch Remedy 5”