Skip to content

Some cmdlets and config require writing to $PSHOME\SessionConfig folder #9278

@SteveL-MSFT

Description

@SteveL-MSFT

Summary of the new feature/enhancement

For Snap and AppX packages of PSCore6, $PSHOME is effectively read-only. Any configuration stored in $PSHOME needs to be in a different location. On Windows 10, it would make sense to be in $env:SystemDrive\ProgramData.

Register-PSSessionConfiguration stores the config file in $PSHOME\SessionConfig folder.

powershell.config.json for the system is stored in $PSHOME, this means that admins can't set system wide config and cmdlets like Enable-ExperimentalFeature -Scope AllUsers won't work.

Update-Help -Scope AllUsers also won't work as it's stored in $PSHOME.

When this is fixed, test changes relying on Test-CanWriteToPsHome should be reverted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Committee-ReviewedPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugPackage-MSIXIssue occurs with MSIX packageWG-RemotingPSRP issues with any transport layer

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions