Combo issue out gate: 1) stuck on Launching PowerShell, & 2) "banned from using svc"

Hello GitHub Folks,

Just tried my first Win 11 upgrade from Win 10 Pro, on "currently unsupported" Dell OptiPlex 5040's, i5-6500 @ 3.20GHz, 16GB seated RAM w/Win 10 Pro v.22H2. The hard drives are all new, combo of hdd or ssd. Lil hitch in my giddyup...

Tried **Floobe v.1.0** instead of Flyby11. Of 3 download options, I selected "**Download ISO using Fido**". Resulted in "_Fido script downloaded successfully. Launching PowerShell..._" inside Flyoobe. Problem is, remained in that state w/that mssg, for about 30mins.

Instead of waiting longer, **I attempted 2nd option**, "_Download ISO via Media Creation Tool_", which immed resulted in an OS popup mssg: "_Error: We are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies [ugh, they neglected a hyphen there!] when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists you may contact Microsoft Support - Contact Us page for assistance. Refer to message code 715-123130 and 5bd2cb40-3173-42d5-8af6-6de30544496f._"

Win 10 Pro Settings\Location is toggled On. Any thoughts on what else could be triggering either of the above mssgs, and, what solid solutions might be? I'm an expert generalist, but not intimidated by tech, just not a formal IT person (ergo, I'm apt to take the longer route, which I'd like to avoid if poss!). Appreciate your time, in advance.

If we press go now, there will be 6-7 machines in total I need to use same process with. These machines all pass the hardware requirements (TPM 2.0; etc et al), except the wee requirement for 8th gen intel® core™.

Start by reproducing both ISO download paths in FlyOOBE v1.0 on the reported Windows 10 Pro setup, focusing on the Fido step that remains at “Launching PowerShell.” Also capture the Media Creation Tool response with codes 715-123130 and 5bd2cb40-3173-42d5-8af6-6de30544496f; done means the relevant failure is isolated and a verified resolution or clear diagnostic is documented.

Written by the indexing model from the issue text.