Fix device agent setup for windows PowerShell instructions in quickstart.md

[Steve-Mcl]

Description

Updated instructions for windows running the installer in the quickstart guide.

In short, when the elevated command is ran, the new terminal always opens in c:\windows\system32. This will cause the downloads to occur in the system32 dir - if even permitted (depends on how terminal was fired up and by who). Essentially, this can lead to System errors (Access Denied) or stale versions running if previously executed.

The solution is to ensure the user dir is first selected before any web downloads occur.

Related Issue(s)

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
• Link to Changelog Entry PR, or note why one is not needed.

Labels

• Includes a DB migration? -> add the area:migration label

[Steve-Mcl]

@hardillb do you have a windows installation you can test this on?

[hardillb]

do you have a windows installation you can test this on?
@Steve-Mcl Not really

I have my windows box I use for my indoor cycling that I'd rather not stick work stuff on and a absolute minimum Windows 10 VM that I setup for the S7 config stuff.

[Steve-Mcl]

@hardillb vm is fine - if you can.

once tested, you can run it (the exe) again --uninstall to get rid of the service it will install