What you’re seeing
- The script refuses to start with a message that it requires a module that is missing from the system.
- Installing the module fails or reports that it needs a newer version of PowerShell.
- A message stating the script requires PowerShell 7 while the machine is running Windows PowerShell 5.1.
- The script runs on a colleague's laptop but not on the server or workstation where it is needed.
- Module commands appear to load but then throw errors about missing assemblies or unsupported editions.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The script declares a #requires statement for a module or PowerShell version that the machine does not have.
- The module is built for PowerShell 7 (the cross-platform "Core" edition) and does not support Windows PowerShell 5.1.
- PowerShell 7 is installed side by side with 5.1, but the script is being launched with the older built-in version.
- The module was installed only for one user, so it is invisible to other accounts or to service accounts.
- A conflicting older copy of the module on the system is loaded first and fails the version check.
Why it matters
Modern admin tooling for Microsoft 365, Azure and many vendors increasingly targets PowerShell 7, while most Windows machines still ship with 5.1. The mismatch blocks routine work like license reports, mailbox changes and security audits, and often surfaces at the worst moment, such as during an offboarding or an incident. Installing modules in a hurry can also leave several versions scattered across a server, making future scripts behave unpredictably.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Will installing PowerShell 7 break our existing scripts?
No. PowerShell 7 installs alongside Windows PowerShell 5.1 rather than replacing it, so older scripts keep working. We confirm which scripts need which version before changing anything.
Why can't Windows just update PowerShell automatically?
Windows PowerShell 5.1 is part of the operating system and PowerShell 7 is a separate product. Windows Update does not move you from one to the other.
Can this be set up so every admin has the same modules?
Yes. An engineer can install modules at the machine level so every account, including scheduled tasks, sees the same versions.