brownjohn423

I've finally had some time to work on this, and I believe I may have resolved the issue by copying C:\Windows\System32\WindowsPowerShell\v1.0\Modules\FailoverClusters\ and C:\Windows\Cluster\ from a server that has the failover cluster module installed to the container image.

It still doesn't recognize RSAT-Clustering-PowerShell is installed, but I've been able to run Import-Module FailoverClusters and a few commands, like Get-Cluster and Get-ClusterNode with no issues, so I'm hopeful.

I'm going to work on getting my custom modules running on the container, and I'll update this again once I have more information.

Thanks, I can verify that 2026.3.3 is working properly.

Sorry about taking a while to get back to you, but I was finally able to get 2026.3.3 running, and I found that the RSAT-Clustering-PowerShell windows feature is still showing as removed, so I'm not able to install it in the image.

PS C:\> Get-WindowsFeature *cluster* | select Name, InstallState          

Name                             InstallState
----                             ------------
Failover-Clustering                   Removed
RSAT-Clustering                       Removed
RSAT-Clustering-PowerShell            Removed
RSAT-Clustering-AutomationServer      Removed
RSAT-Clustering-CmdInterface          Removed

Thank you for this! I was wondering where the comments from my other post went.

It looks like there's a problem with the 2026.3.X images for Windows Server 2022. I'm getting this message when running docker pull:

a Windows version 10.0.26100-based image is incompatible with a 10.0.20348 host

The first layer for the 2026.3.0 and 2026.3.1 images for ltsc2022 is this:

Apply image 10.0.26100.32230

However, on 2026.2.5, it's this:

Apply image 10.0.20348.2700

Since my docker host is running Windows Server 2022, I can't check the new version of PowerShell Universal. Should I make a separate forum post for this issue, or is this something you can look into?

Thanks for the update, I really appreciate it!

Docker image tag: devolutions/powershell-universal:2026.2.1-lts-windowsservercore-ltsc2022

The container host is running Windows Server 2022 with process isolation. It is fully up to date through June 2026 - I haven't installed the latest July updates yet.

My current production PowerShell Universal install is using the Failover Cluster module in Windows PowerShell 5.1 on Windows Server 2022.

PS C:\> $PSVersionTable                                                                                                                                                       

Name                           Value
----                           -----
PSVersion                      5.1.20348.2849
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.20348.2849
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\> Get-WindowsFeature RSAT-Clustering-PowerShell

Display Name                                            Name                       Install State
------------                                            ----                       -------------
            [ ] Failover Cluster Module for Windows ... RSAT-Clustering-Powe...          Removed

Get-Module FailoverClusters -ListAvailable returns nothing and Import-Module FailoverClusters -Verbose returns an error because the module does not exist on the server.

All of the RSATs for Failover Clustering have been removed from the image:

PS C:\> Get-WindowsFeature *cluster*

Display Name                                            Name                       Install State
------------                                            ----                       -------------
[ ] Failover Clustering                                 Failover-Clustering              Removed
        [ ] Failover Clustering Tools                   RSAT-Clustering                  Removed
            [ ] Failover Cluster Module for Windows ... RSAT-Clustering-Powe...          Removed
            [ ] Failover Cluster Automation Server      RSAT-Clustering-Auto...          Removed
            [ ] Failover Cluster Command Interface      RSAT-Clustering-CmdI...          Removed

I'm not sure if the Failover Clustering feature was removed as part of building the PowerShell Universal image, or if Microsoft removed it from their base docker image, but it would be helpful if I had a way to get it back.

Is there a way to get the FailoverClusters module running in the Windows docker container? It looks like the windows feature has been removed from the docker image, and I haven't been able to find a way to get it installed.

I tried copying the module files to the running container doesn't work, as PowerShell throws errors when importing the module.

I'm trying to migrate from the PowerShell module install of PowerShell Universal to the docker container, and this is the last thing that's holding me up. I have a custom module I created for my company that relies on the FailoverClusters module, and I would prefer not to have to re-write the module.

During my testing, I ran into some issues with getting the job output, but settled on this in one of my apps. I don’t remember if the issue was with trying to get the output with the -Job parameter, but I know that it works with the -JobId parameter:

Get-PSUJobOutput -Integrated -JobId $EventData.Id

Also, if you haven’t done so, I would also recommend that you verify that the your job produced output by sticking it in a toast or modal first.

I usually lean towards using Invoke-Command for running code on remote machines, and I haven’t had an issue yet.