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

Eliminating popup asking to format disk on etcher #2024

Closed
aamm132 opened this issue Feb 7, 2018 · 2 comments
Closed

Eliminating popup asking to format disk on etcher #2024

aamm132 opened this issue Feb 7, 2018 · 2 comments

Comments

@aamm132
Copy link

@aamm132 aamm132 commented Feb 7, 2018

  • Etcher version: 1.3.1
  • Operating system and architecture: Windows

I just recently built etcher locally and can make my changes I need to on my machine. One thing I have been looking to want to change is the popup that appears frequently whenever an image is being flashed to a drive. The popup tells you that you need to format the disk first. Regardless of accepting to format it or not, the flashing process continues successfully anyway. Is there any possibility that this popup can be removed/prevented?

@lurch
Copy link
Contributor

@lurch lurch commented Feb 8, 2018

This popup is coming from Windows itself (it's getting "upset" that it can't read any filesystems on the drive), so no there's nothing we can do (currently) to prevent it.

Longer-term, we plan to do native drive-locking, so that Etcher will be able to grab exclusive access to the drive, and (I think) Windows wouldn't then ask you to format it. However this relies on a feature that's only recently been added to NodeJS, and we need to wait for that version of NodeJS to be incorporated into Electron, before we can then add this drive-locking functionality to Etcher.

Loading

@deng1604
Copy link

@deng1604 deng1604 commented Nov 9, 2020

Uploading image.png…
该如何应对?

Loading

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

Successfully merging a pull request may close this issue.

None yet
3 participants