Skip to content

Docs (readme): Add notes about Windows Powershell being included Windows 10 and 11, and not to use Windows Powershell ISE#152

Merged
leojonathanoh merged 1 commit intomasterfrom
docs/readme-add-notes-about-windows-powershell-being-included-windows-10-and-11-and-not-to-use-windows-powershell-ise
Feb 5, 2023
Merged

Docs (readme): Add notes about Windows Powershell being included Windows 10 and 11, and not to use Windows Powershell ISE#152
leojonathanoh merged 1 commit intomasterfrom
docs/readme-add-notes-about-windows-powershell-being-included-windows-10-and-11-and-not-to-use-windows-powershell-ise

Conversation

@leojonathanoh
Copy link
Copy Markdown
Member

@leojonathanoh leojonathanoh commented Feb 5, 2023

In #125, it was thought that Windows Powershell 5.x on Windows 11 did not support long path using the \\?\ prefix, e.g. \\?\C:\path\to. However, further investigation identified that Windows Powershell ISE did not support the \\?\ prefix, but Windows Powershell did.

Now, Windows Powershell 5.x is known to be fully compatible with this script. There is not need to install Powershell Core, since Windows 10 and 11 already include Windows Powershell. A note is added in requirements section.

Closes #125

@leojonathanoh leojonathanoh self-assigned this Feb 5, 2023
@leojonathanoh leojonathanoh added this to the v2.19.2 milestone Feb 5, 2023
@leojonathanoh leojonathanoh added the docs Improvements or additions to documentation label Feb 5, 2023
@leojonathanoh leojonathanoh force-pushed the docs/readme-add-notes-about-windows-powershell-being-included-windows-10-and-11-and-not-to-use-windows-powershell-ise branch 3 times, most recently from 417711d to ce59b06 Compare February 5, 2023 00:36
…ows 10 and 11, and not to use Windows Powershell ISE

In #125, it was thought that Windows Powershell 5.x on Windows 11 did not support long path using the `\\?\` prefix, e.g. `\\?\C:\path\to`. However, further investigation identified that Windows Powershell ISE did not support the `\\?\` prefix, but Windows Powershell did.

Now, Windows Powershell 5.x is known to be fully compatible with this script. There is not need to install Powershell Core, since Windows 10 and 11 already include Windows Powershell. A note is added in requirements section.

Closes #125
@leojonathanoh leojonathanoh force-pushed the docs/readme-add-notes-about-windows-powershell-being-included-windows-10-and-11-and-not-to-use-windows-powershell-ise branch from ce59b06 to 601d72a Compare February 5, 2023 00:43
@leojonathanoh leojonathanoh merged commit cb45bcd into master Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error while renaming file references - Illegal characters in path

1 participant