OSDeploy PSModule and site pages are currently in preview until mid-September
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Get-OSDeployModulePath

Return and use the root path of the currently loaded OSDeploy module.

Get-OSDeployModulePath returns the absolute path to the root directory of the OSDeploy module loaded in the current PowerShell session. Use the returned path to locate module-relative catalogs, configuration files, templates, and other resources without assuming where PowerShell installed the module.

Requirements

Install OSDeploy and run the command from PowerShell 7.6 or later. See Module Setup for installation and import instructions.

Import OSDeploy before using the function in a script that must control which installed module version is loaded:

Import-Module -Name OSDeploy -Force

Parameters

Get-OSDeployModulePath has no function-specific parameters and does not accept pipeline input. It supports PowerShell common parameters through CmdletBinding, but they do not change path resolution.

Examples

Return the loaded module path

Return the root directory of the OSDeploy module loaded in the current session:

Get-OSDeployModulePath

Build a path to a module resource

Use Join-Path to create a platform-safe path to core\module.json:

Read module configuration

Locate and parse the module configuration as structured JSON:

Verify the loaded installation location

Compare the function result with the module metadata reported by Get-Module:

Select and import a specific installed version

List installed versions, import the required release, and then return its root path:

Replace 26.8.0 with a version installed on the computer.

Path Resolution

The function reads the ModuleBase property from the module associated with the running command. It does not search PSModulePath, inspect other installed releases, or choose the newest available version.

The returned path therefore follows the module import performed by PowerShell. When multiple OSDeploy versions are installed side by side, use Import-Module -RequiredVersion before calling the function to select a specific release.

Use Join-Path for child resources instead of concatenating strings. The returned value identifies the module root and does not include a trailing resource path.

Session Behavior

The function does not search installed releases, modify files, install modules, or change the current location. It does not support -WhatIf or -Confirm because it does not declare SupportsShouldProcess.

Output

The function returns one System.String containing the absolute ModuleBase path of the loaded OSDeploy module.

Assign the result directly when another command requires a path:

See Module Setup for the installation workflow or the Get-OSDeployModulePath command reference for compact syntax and output information.

Last updated

Was this helpful?