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

electron builder update emit error: {"code":"EBUSY","dest":"C:\\Users\\andyc\\AppData\\Local\\vipthink-updater\\pending\\vipthink_win_2.13.0.exe","errno":-4082,"path":"C:\\Users\\andyc\\AppData\\Local\\vipthink-updater\\pending\\temp-vipthink_win_2.13.0.exe","syscall":"rename"} #6031

Closed
StitchC opened this issue Jul 7, 2021 · 9 comments

Comments

@StitchC
Copy link

StitchC commented Jul 7, 2021

  • Electron-Builder Version: 22.7.0
  • Node Version: 12.22.0
  • Electron Version: 4.2.12
  • Electron Type (current, beta, nightly):
  • Target: win32

and another error emit so:

{"code":"EPERM","dest":"C:\Users\David\AppData\Local\vipthink-updater\pending\vipthink_win_2.13.0.exe","errno":-4048,"path":"C:\Users\David\AppData\Local\vipthink-updater\pending\temp-vipthink_win_2.13.0.exe","syscall":"rename"}

should i upgrade my electron builder version to resovle this ? or how to avoid this problem?

@mmaietta
Copy link
Collaborator

mmaietta commented Jul 8, 2021

You're running into a file lock issue so this may not explicitly be electron-builder: https://stackoverflow.com/a/44014485

Please update to latest 22.11.7 first though 🙂

@StitchC
Copy link
Author

StitchC commented Jul 12, 2021

You're running into a file lock issue so this may not explicitly be electron-builder: https://stackoverflow.com/a/44014485

Please update to latest 22.11.7 first though 🙂

sorry, i thought my word let you puzzle. i say clear now and let you know the detail

i use the autoUpdater of electron-builder to let our app update, and some of our user will emit the error after downloaded the latest version app .zip and ready to install, not emit when npm install 😂

some code here:

init() {
autoUpdater.on('error', err => {
    // sth code
})
autoUpdater.autoDownload = false
autoUpdater.allowPrerelease = true
autoUpdater.allowDowngrade = true
}
// and when i install the update i will set parameters like this

autoUpdater.quitAndInstall(isSilent, isForceRunAfter)

so, this error will be resolved in the latest version ? or how i can resolve this error, thanks~

@mmaietta
Copy link
Collaborator

emit the error after downloaded the latest version app .zip and ready to install, not emit when npm install

Whoops, I definitely had misunderstood that. My bad 😅

so, this error will be resolved in the latest version ? or how i can resolve this error, thanks~

I just recall various electron-updater fixes occurring between 22.7 and 22.11, aaaand it's more efficient for the two maintainers of this project to only investigate on latest versions. 22.7.0 is also long before I joined the team.

@StitchC
Copy link
Author

StitchC commented Jul 15, 2021

emit the error after downloaded the latest version app .zip and ready to install, not emit when npm install

Whoops, I definitely had misunderstood that. My bad 😅

so, this error will be resolved in the latest version ? or how i can resolve this error, thanks~

I just recall various electron-updater fixes occurring between 22.7 and 22.11, aaaand it's more efficient for the two maintainers of this project to only investigate on latest versions. 22.7.0 is also long before I joined the team.

okay, i try to upgrade the electron-builder version

@theAV
Copy link

theAV commented Jul 22, 2021

@StitchC Did you get any solution? I am also getting the same, error no -4082, code "EBUSY" in windows 7.

@StitchC
Copy link
Author

StitchC commented Jul 22, 2021

@StitchC Did you get any solution? I am also getting the same, error no -4082, code "EBUSY" in windows 7.

no, but i ready to try upgrade the latest version

@stale
Copy link

stale bot commented Sep 21, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Sep 21, 2021
@theAV
Copy link

theAV commented Sep 23, 2021

@StitchC My antivirus was blocking it. I stopped my antivirus and then auto-update worked as it should. So when I need to update I stop my antivirus.

@stale stale bot removed the backlog label Sep 23, 2021
@stale
Copy link

stale bot commented Apr 17, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

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

3 participants