TWL-KB-028 · PowerShell · IT / scripting

Module not found or cannot be imported

Identify the exact module and host before installing anything.

Applies to: Windows PowerShell and PowerShell 7.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Import-Module: module was not loaded (wording varies). Identify the exact module and host before installing anything.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Import-Module: module was not loaded (wording varies)The module may be missing, in the wrong location, incompatible or blocked.Identify the exact module and host before installing anything.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Read the full import error; Check requirements; Check approved deployment; Use the support route
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Read the full import error

    Do this
    Note the module name and error text, with personal paths removed.
    What you should see
    A missing module can be told apart from a load error.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Check requirements

    Do this
    Compare the documented module and PowerShell edition with the current host.
    What you should see
    They match or differ.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Check approved deployment

    Do this
    Ask IT whether the module comes from an internal package.
    What you should see
    A trusted source is identified.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Use the support route

    Do this
    Ask the owner to install or review it. Do not download similarly named modules.
    What you should see
    No untrusted module is loaded.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.