-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Resolution-DuplicateThe issue is a duplicate.The issue is a duplicate.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
- Download the MSI for v7.2.2 and run it.
a. Use a custom directory (in my case I chooseD:\PowerShell)
b. Untick the options to update automatically through Windows Update or WSUS. - Now download the MSI for v7.2.3 and run it.
- When you reach the page for the installation directory, it shows the default directory in
C:\Program Files. - When you reach the page for automatic updates, both options are ticked.
Expected behavior
The installer for a new version should respect the options that were selected for the previous verison.
Actual behavior
The installer for a new version uses the default options.
Error details
No response
Environment data
Name Value
---- -----
PSVersion 7.2.3
PSEdition Core
GitCommitId 7.2.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Visuals
No response
Related Issues
This could be related to #17211, which is about the original installation directory not being respected when PowerShell is automatically updated through Windows Update.
Metadata
Metadata
Assignees
Labels
Resolution-DuplicateThe issue is a duplicate.The issue is a duplicate.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors