Readiness Check Fails if certain PSGallery Powershell Modules are installed

Open

#272 opened on Apr 10, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: powershell
Domain: infrastructure

Research direction

Reproduce the failure by installing the VMFleet or cluster PowerShell module, then run a readiness check and get-solution update. Trace the readiness-check and update entry points to identify where the generic System error is produced; done means conflicting modules are named clearly and updates prompt for their removal.

Written by the indexing model from the issue text.

Description

Bug description
Readiness check completely fails to run if there are extra powershell modules installed, preventing any kind of update from running. The error produced from this failure doesn't provide any useful diagnostic information.
For example, running get-solution update results in this line:
HealthCheckResult : {Error reading readiness results for System}

Repro steps
Steps to reproduce the behavior:

Install VMFleet Powershell module on any node. (Or "cluster" powershell module from the PSGallery)
Attempt to run a readiness check

Expected behavior

Readiness check fails with an error that describes conflicting powershell modules that are installed.
When updates are run, there should be a prompt asking to uninstall the conflicting modules first.

Environment (please complete the following information):

Azure Local 12.2509 (Currently being upgraded now)
4 node cluster
Production
East US Region

Dominant language: PowerShell
Stars: 78
Forks: 60
Avg merge: 5h 24m
Merged PRs (30d): 1

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.