-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Closed
Labels
Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aNeeds-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.Resolution-AnsweredThe question is answered.The question is answered.
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
Installed 7.2.2, launch from installer, immediately see problem:
[0x7FF89B045090] ANOMALY: meaningless REX prefix used
[0x7FF89B018A30] ANOMALY: meaningless REX prefix used
[0x7FF89B6E7E10] ANOMALY: meaningless REX prefix used
Expected behavior
On pwsh open, start with PS> prompt
Actual behavior
On pwsh open, displays the following
[0x7FF89B045090] ANOMALY: meaningless REX prefix used
[0x7FF89B018A30] ANOMALY: meaningless REX prefix used
[0x7FF89B6E7E10] ANOMALY: meaningless REX prefix used
then opens PS> prompt
Error details
No response
Environment data
Name Value
---- -----
PSVersion 7.2.2
PSEdition Core
GitCommitId 7.2.2
OS Microsoft Windows 10.0.19044
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
Metadata
Metadata
Assignees
Labels
Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aNeeds-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.Resolution-AnsweredThe question is answered.The question is answered.