Update-Help Fails (and previos issue was closed on outdated and wrong fix)

[eabase]

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

In the previously reported and detailed issue #17067, your developer prematurely closed the issue on by citing an old and outdated blog, that has nothing to do with the issue.

Please reopen.

Expected behavior

That Developers doesn't prematurely close open issues on the wrong basis.

Actual behavior

none

Error details

No response

Environment data

n/a

Visuals

No response

[eabase]

This has nothing to do with the scope. Please read the linked thread.

[SteveL-MSFT]

cc @sdwheeler

[sdwheeler]

The previous issue was answered and closed with this comment #17067 (comment).

Are you having a problem not answered by that comment?

[eabase]

@sdwheeler

Are you having a problem not answered by that comment?

Yes. This:

The Windows modules are not maintained by the PowerShell team. To prevent the error, the module owners on the Windows team must fix the modules. For modules that ship in Windows, open a support case with Windows Support or send feedback via the Windows Feedback Hub. For more information, see Send feedback to Microsoft with the Feedback Hub app.

The Feedback Hub is like black hole for issues that MS does not intend to do anything about. I have filed stuff there in the past and never had any response or feedback, ever. At the end of the day, we're just slightly more advanced regular users of your product, so when we file for issues, we kind of expect that MS will take care of it. In this sense, I think it is really you who should file the issue on that Hub and ensure it gets to the correct team for a planned solution.

Second, I have no idea why someone thinks that it is the right procedure to close open issues, when they have not been fixed, completed or otherwise dealt with, regardless the team who's responsible for the actual fix.

[sdwheeler]

You still haven't provided information about the specific modules you are having trouble with.

The PowerShell team can't fix the broken modules owned by other teams. We have communicated the problem to those teams. It is up to them to provide fixes.

[microsoft-github-policy-service]

This issue has been marked as answered and has not had any activity for 1 day. It has been closed for housekeeping purposes.

[microsoft-github-policy-service]

📣 Hey @eabase, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms