New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd prompt #1935
Comments
I had the same problem. I restarted Etcher using "run as administrator" and it works ok now. |
I'm no Windows expert, but I believe that's exactly what the "UAC screen" is asking. We use https://github.com/jorangreef/sudo-prompt to get the administrative privileges that Etcher needs to be able to perform low-level disk writes. |
The writer process / the cmd is elevated on Windows (hence the UAC prompt), but there were some issues we fixed recently, which might be related: #1950 and #1910 – those will be released in the next version shortly, and maybe fix it. PS: @lurch on Windows we're using a native binding that @jviotti wrote, not sudo-prompt, because there were issues with that |
Ahh, I thought we were using sudo-prompt because it's still in EDIT: Oh, I see. We're only using sudo-prompt on non-Windows platforms :-) https://github.com/resin-io/etcher/blob/master/lib/shared/permissions.js#L161 |
We use `sudo-prompt` for GNU/Linux and macOS, but our custom native
module on Windows.
…On Mon, Jan 08, 2018 at 04:58:52AM -0800, Andrew Scheller wrote:
Ahh, I thought we were using sudo-prompt because it's still in `package.json` ? https://github.com/resin-io/etcher/blob/master/package.json#L93
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1935 (comment)
--
Juan Cruz Viotti
Software Engineer
|
Not sure if this comment will post since this issue is closed but... I had this issue and the problem was that hope this helps someone. |
@captainmustard See also #3621 |
Humor me on a theory. I am using windows 10 x64 and I have issues with other programs running cmd prompts in the past with out administrative permissions . I've actually had to run command prompt with Administrative permissions to get certain programs to run correctly
now here is my point. I have had no luck getting my image to burn I noticed that it runs a cmd prompt and my theory is maybe the cmd prompt needs to be run with administrative privileges for it to work. because after i get the UAC screen asking if its ok to run the cmd prompt and i say yes it just doesn't go any further then that. I was trying to figure out a "work-around" for this but have had no luck to test my theory.
let me know your thoughts
i was wondering if testing by "hard coding" it to run the cmd prompt as administrator if that might fix the problem.
The text was updated successfully, but these errors were encountered: