You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug - HOME env not set, error message is not clear on what the issue is #2299
HOME environment varable not set results in a error message which is hard to determine the actual fault.
If calling powershell from another tool, HOME may not be part of the environment space. Powershell should report better error message.
Steps to reproduce
$ unset HOME
$ powershell
PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Management.Automation.ConfigPropertyAccessor' threw an exception.
Expected behavior
$ unset HOME
$ powershell
PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
Please set the HOME environment variable before using powershell, as powershell stores configuration items in $HOME/.configure/powershell
Actual behavior
PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Management.Automation.ConfigPropertyAccessor' threw an exception.
Mike Richmond (@mirichmo) this is due to the ConfigPropertyAccessor requiring that HOME be both set and writable, but that's something that can be expected.
Activity
andyleejordan commentedon Sep 19, 2016
Same problem as #2205.
Mike Richmond (@mirichmo) this is due to the ConfigPropertyAccessor requiring that HOME be both set and writable, but that's something that can be expected.
andyleejordan commentedon Sep 19, 2016
I'm going to close as duplicate; but thank you for filing. This is indeed a bug.