bspach

I used Import-Module to demonstrate the problem. If I just run my script, it occasionally fails instantly (#requires is L1). I want to eventually run this script as a scheduled task, so I won't always have a terminal open to see it fail.

Data source type is Devolutions Server

RDM v2025.3.32.0 installed locally

PowerShell module v2026.1.4 installed via Install-Module (PowerShell Gallery)

PowerShell v7.6.0

Windows 11

I'm getting inconsistent behavior when doing Import-Module Devolutions.PowerShell. Sometimes it loads as Devolutions.PowerShell, sometimes as Devolutions.PowerShell.Extension, which is messing up #requires in my script. See output below.

One session I get:

> Import-Module devolutions.powershell
> get-module | ? Name -like "Devo*" | select Name,Path,ImplementingAssembly,Version | format-list

Name                 : Devolutions.PowerShell.Extension
Path                 : C:\Users\USERNAME\Documents\PowerShell\Modules\Devolutions.PowerShell\2026.1.4\Devolutions.PowerShell.dll
ImplementingAssembly : Devolutions.PowerShell, Version=2026.1.4.0, Culture=neutral, PublicKeyToken=null
Version              : 2026.1.4

Next session I get:

> Import-Module devolutions.powershell
> get-module | ? Name -like "Devo*" | select Name,Path,ImplementingAssembly,Version | format-list

Name                 : Devolutions.PowerShell
Path                 : C:\Users\USERNAME\Documents\PowerShell\Modules\Devolutions.PowerShell\2026.1.4\Devolutions.PowerShell.dll
ImplementingAssembly : Devolutions.PowerShell, Version=2026.1.4.0, Culture=neutral, PublicKeyToken=null
Version              : 2026.1.4