Skip to content
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

Closed
nitestryker opened this issue Dec 22, 2017 · 7 comments
Closed

cmd prompt #1935

nitestryker opened this issue Dec 22, 2017 · 7 comments

Comments

@nitestryker
Copy link

  • Etcher version: V1.2.1
  • Operating system and architecture: Windows 10 x64
  • Image flashed: No
  • Do you see any meaningful error information in the DevTools?

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.

@benp13
Copy link

benp13 commented Jan 3, 2018

I had the same problem. I restarted Etcher using "run as administrator" and it works ok now.

@lurch
Copy link
Contributor

lurch commented Jan 3, 2018

i was wondering if testing by "hard coding" it to run the cmd prompt as administrator if that might fix the problem.

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.

@jhermsmeier
Copy link
Contributor

jhermsmeier commented Jan 5, 2018

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

@lurch
Copy link
Contributor

lurch commented Jan 8, 2018

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

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

@jviotti
Copy link
Contributor

jviotti commented Jan 8, 2018 via email

@jviotti jviotti closed this as completed Oct 15, 2018
@captainmustard
Copy link

Not sure if this comment will post since this issue is closed but...

I had this issue and the problem was that C:\Windows\system32 was missing from the PATH on my windows install. Was a quick easy fix. Had to close and restart etcher for it to begin working.

hope this helps someone.

@lurch
Copy link
Contributor

lurch commented Feb 11, 2024

@captainmustard See also #3621

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants