Closed DaveTheBatMan closed 5 years ago
Hey @DaveTheBatMan ,
One of the first few lines of my script is;
Set-ExecutionPolicy -ExecutionPolicy Bypass -Force
In saying that, it would probably be easier if people didn't have to see the prompt.
I think I'll just put something to copy and paste in the readme so people have to avoid seeing this in the future, thanks!
Hey @Francommit,
At the outset, I again thank you for your efforts -- not many people, nowadays, who'd do such a thing. :-)
Regarding your note: Yes, the first two lines of your script are a comment and then the "Set-ExecutionPolicy -ExecutionPolicy Bypass -Force" command, which is all good stuff. However, in my situation, this was a chicken-and-the-egg proposition -- the Set is inside the script, but I can't run the script until the Set is done.
From what I can tell, if someone's machine has (already) been (permanently) set to bypass (which can be checked with "Get-ExecutionPolicy -List"), then their LocalMachine setting will reflect that, and they can simply run the script as-desired. However, if the setting is (default) "Restricted" (and possibly others), then you get what I got:
Obviously, not everyone is going to have this issue, but I simply thought it worth noting to those who do.
On a different note, is there any way to have the script display any type of progress indicator? While it was doing all of its downloads, I never had any indication how far along it was in its total downloads; while it told me it was getting a certain file, I had no way of knowing if that file was the first of eight or the first of eight thousand. Just a thought.
Thanks again -- have a great Saturday!
Dave
Hey @DaveTheBatMan ,
Updated the readme.md, instructions seem clear and concise?
Thanks for pointing it out!
Hey @Francommit --
Thanks for the update, and (again) for your hard work with this.
Happy Sunday (and every day)!
Dave
On Sun, Aug 11, 2019 at 5:21 AM Chris Franco notifications@github.com wrote:
Hey @DaveTheBatMan https://github.com/DaveTheBatMan ,
Updated the readme.md, instructions seem clear and concise?
Thanks for pointing it out!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Francommit/win10_emulation_station/issues/23?email_source=notifications&email_token=AL3WBDNECHMP6IUPJFMPJQ3QD7R2ZA5CNFSM4IHE5JI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4A6ANQ#issuecomment-520216630, or mute the thread https://github.com/notifications/unsubscribe-auth/AL3WBDL74JJZJNRCM4LSORTQD7R2ZANCNFSM4IHE5JIQ .
-- David C. Battistoli ("Dave") davethebatman@gmail.com davethebatman@gmail.com (312) 550-2529 (Mobile)
Thank you for your pretty awesome work -- it's amazing!
When running this on the current (for now) version of Windows 10 (May 2019), I get the following error:
_prepare.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_ExecutionPolicies at https:/go.microsoft.com/fwlink/?LinkID=135170.
The workaround is pretty simple. In the same (elevated) PS prompt, simply run:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
... and then answer the prompt that yes, you really do want to do this.