How to correctly ignore Import-Module errors in PowerShell

Question

I'm currently having issues whilst calling Import-Module with Powershell and would be grateful for some advice.

According to previous questions and answers here, the following error, when received whilst trying to import a module using PowerShell, can be ignored:

File skipped because it was already present from "Microsoft.PowerShell".

The problem is that it will get caught if the import command is within a try / catch statement.

I've read a number of posts regarding this (example PowerShell on SCOM fails to import module) and one did mention to try adding "-ErrorAction SilentlyContinue" to the Import-Module command, but unfortunately this makes no difference.

Below is the code I'm currently using to test the issue which should give you a better understanding of what I am trying to achieve.

Has anyone managed to successfully ignore these warnings on module import whilst wrapped in a try / catch before?

Thanks for your time,

Andrew

function load_module($name)
{
    if (-not(Get-Module -Name $name))
    {
        if (Get-Module -ListAvailable | Where-Object { $_.name -eq $name })
        {
            Import-Module $name  

            return $true
        }
        else
        {   
            return $false
        }
    }
    else
    {
        return $true
    }
}

$moduleName = "ActiveDirectory"

try 
{
    if (load_module $moduleName)
    {
        Write-Host "Loaded $moduleName"
    }
    else
    {
        Write-Host "Failed to load $moduleName"
    }
}
catch 
{
    Write-Host "Exception caught: $_" 
}

Do you get the error you mention when you load the AD module with your test code, cause I don't — Shay Levy
– Shay Levy, Commented May 8, 2012 at 12:33
Hi Shay, yes, running "Import-Module ActiveDirectory" on its own will give me this error. — AndrewB
– AndrewB, Commented May 8, 2012 at 12:37
Do you get "loaded"? Import-Module ActiveDirectory; Write-Host "loaded" — Shay Levy
– Shay Levy, Commented May 8, 2012 at 12:43
I do get "loaded" if I try that, after multiple lines of the above error. — AndrewB
– AndrewB, Commented May 8, 2012 at 12:51
So, the error is not a terminating error which means that the try/catch has no value. Can you ignore the warning with: Import-Module ActiveDirectory -WarningAction SilentlyContinue ? — Shay Levy
– Shay Levy, Commented May 8, 2012 at 12:53

David Brabant · Accepted Answer · 2012-05-08 17:07:41Z

9

function Load-Module
{
    param (
        [parameter(Mandatory = $true)][string] $name
    )

    $retVal = $true

    if (!(Get-Module -Name $name))
    {
        $retVal = Get-Module -ListAvailable | where { $_.Name -eq $name }

        if ($retVal)
        {
            try
            {
                Import-Module $name -ErrorAction SilentlyContinue
            }

            catch
            {
                $retVal = $false
            }
        }
    }

    return $retVal
}

edited May 8, 2012 at 17:07

answered May 8, 2012 at 14:12

David Brabant

44k16 gold badges93 silver badges119 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

AndrewB Over a year ago

Apart from missing the $ on retVal in the catch, this is getting closer. Adding a try / catch around the import module will hide the error and prevent it being caught in the main try / catch. Thanks. We only want it to hide the error if it's the specific "File skipped because it was already present" message though but this can be performed by checking the exception message.

Collectives™ on Stack Overflow

How to correctly ignore Import-Module errors in PowerShell

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related