Clarified setup of kvm

[DanThiffault]

I had to run the command as an administrator or it wouldn't work.

[victorhurdugaci]

Hi, @DanThiffault, unfortunately we can't just yet take contributions - we're ironing our the process for that as we speak.

You shouldn't need to explicitly run kvm.cmd as administrator. An UAC prompt should popup if you don't run as admin. Didn't that happen?

[clintkolodziej]

I'm having the same issue as @DanThiffault. If I run as a normal user I get a UAC prompt, I grant access, then a powershell pops open and closes quickly with an error. After a number of attempts I managed to grab a screenshot, just as the window was closing. Looks like it is saying running scripts is prohibited and throwing a PSSecurityException. I am on a clean install of Windows 8.1, just installed it last night, so if there is any setup needed to run the install it should probably be documented.

Also, when I run setup with command prompt (admin), I'm able to install and run everything, though when I close the prompt any environment variables seem to not be committed, and I'm not able to run "kvm", "kpm", or "k" commands under a normal command prompt at a later time (or even under a normal command prompt while the command prompt (admin) is still open). If I re-open a command prompt (admin) I can re-run setup and run though the "kvm install ..." command, which indicates everything is already there, and the commands work again only while that prompt is open. Basically the variables aren't sticking around so the system doesn't know the commands are installed once things are closed down.

[loudej]

Thanks for catching that screenshot - that's a great lead! I think when the powershell launches the elevated script it might need to provide the execution policy switch like the original kvm.cmd does.

[clintkolodziej]

I was able to get around the above error as follows:

1. Run Powershell as Administrator
2. Run command set-executionpolicy RemoteSigned
3. Close Powershell
4. Follow procedures listed in the readme to run kvmsetup

After that was done I ran steps 1-3 again, with the command set-executionpolicy Restricted to restore the value back as it was previously set on my system.

Hope that helps others get around this problem, at least until it is fixed in the kvmsetup script itself.

[DanThiffault]

Problem solved. I'll close this at least until you're ready to accept PRs. Thanks everyone.