Skip to content

Include more info in $PSVersionTable, like .NET version #17059

Closed

Description

Summary of the new feature / enhancement

Would be great if $PSVersionTable could include some more relevant information to its' environment. For instance:

OS agnostic

  • [New key] .NET version built upon
  • [New key] OS Architecture (x64, x86, ARM, ARM64 etc.)
  • [New key] Process architecture (x64, x86, ARM, ARM64 etc.)

Windows

  • [Existing key] Update "OS" key to include build number (cumulative)
  • [Existing key] Update "OS" key to include edition (Home / Pro / Enterprise)
    • If someone can't get BitLocker cmdlets to work, but running Windows 10 Home.. :)

I'm thinking suggested additions in addition to being useful for end users, might be helpful when adding $PSVersionTable to issues on GitHub too, to give some more context out of the box.

Proposed technical implementation details (optional)

Add more keys and more info to existing keys, to the hashtable that is $PSVersionTable.

image

Activity

  1. ArmaanMcleod commented on Mar 25, 2022

    @ArmaanMcleod
    Contributor

    I've also wondered why GitCommitId doesn't actually have a real commit ID? Seems to just mirror PSVersion.

  2. daxian-dbw commented on Aug 3, 2022

    @daxian-dbw
    Member

    Armaan Mcleod (@ArmaanMcleod) For the stable and preview versions, the commit id is the tag for the release, which happens to be the same as PSVersoin. If you are using a daily build, you will see the commit id as in hash code.

  3. JamesWTruher commented on Jan 9, 2023

    @JamesWTruher
    Collaborator

    The WG discussed this and we're concerned that the $PSVersionTable could grow to be unwieldy (and we would like to keep PSVersionTable from trying to have everything). However, we do see the need for diagnostic tools which collect this information (and perhaps more). We would be happy to entertain proposals for additional tools to provide that.

  4. added
    Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
    on Jan 9, 2023
  5. microsoft-github-policy-service commented on Nov 15, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  6. microsoft-github-policy-service commented on Nov 22, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

  7. removed
    Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
    on Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Enhancementthe issue is more of a feature request than a bugResolution-No ActivityIssue has had no activity for 6 months or moreWG-Enginecore PowerShell engine, interpreter, and runtime

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions