Description

The issue is described here

You cannot possibly be held responsible for all contingencies for every system, that would be unreasonable. However, it would benefit the community, especially those of newcomers, were this issue at least mentioned as known in your docs. A timestamped solution would be most advantageous.

Whether or not this is normal behaviour is irrelevant, most other projects which encounter these issues make mention of the fact. The reality is that this particular problem is not documented and has fallen between the cracks, rendering your getting started doc unhelpful as completing it is left up to chance for the uninitiated. It is cost-free to add this and would speed up the education of those learning the framework.

It serves no-one and nothing to omit this problem and solution from your docs and it should be noted there are 5 or 6 disparate solutions listed on SO, where only one is necessary.

More importantly, these solutions vary in their awareness and consideration of security measures. This alone makes it necessary to guide the user based on your framework's limited requirements.

What is the affected URL?

No response

Please provide the steps to reproduce the issue

On a fresh Windows 10 install, your getting started examples do not work do to limitations on the Execution Policy.

Please provide the expected behavior vs the actual behavior you encountered

Your starting examples should provide adequate information for execution, including minimal permissions required on a system-by-system basis.

Please provide a screenshot if possible

No response

Please provide the exception or error you saw

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version.

No response