Share via

Please help me report this annoying typo to Microsoft

Anonymous
2024-03-19T14:01:26+00:00

First, let me say that Microsoft has perhaps the all-time worst bug reporting process. Unless you have Windows installed, you can't use the Feedback Hub, which is absolutely atrocious.

Now, I have been trying to report this issue for 6 months and never get any responses from Microsoft. Run "Get-ComputerInfo" and you can see the typo "BiosSeralNumber" appear instead of "BiosSerialNumber". I don't know why this still hasn't been fixed and I never get a response.

Windows Server Devices and deployment

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-19T14:51:42+00:00

    I believe the issue is tied to PowerShell 5.1. The issue has been addressed in newer PowerShell revisions (6.2 and higher). The only reason the issue has been around for quite some time (since 2016) is because that version is bundled and tied with the OS. Until Microsoft decides to make a newer version of PowerShell that addressed the issue as the new baseline the issue will be around. Microsoft tends to be slow to change things in this regard to maintain backwards compatibility.

    0 comments