file permission errors in updater with 22.1.0
See original GitHub issue-
Version: 22.1.0
-
electron-updater: 4.2
-
Target: mac and windows
Both Mac and Windows seem to give issues updating because of file permissions (or timing?) using the above combination.
Mac:
Error: ENOENT: no such file or directory, rename '/Users/admin/Library/Application Support/Caches/polypane-updater/pending/temp-Polypane-2.0.1-mac.zip' -> '/Users/admin/Library/Application Support/Caches/polypane-updater/pending/Polypane-2.0.1-mac.zip'
Windows:
Error: EPERM: operation not permitted, open 'C:\Users\admin\AppData\Local\polypane-updater\pending\temp-Polypane-Setup-2.0.1.exe'
Followed by
Error: ENOENT: no such file or directory, rename 'C:\Users\admin\AppData\Local\polypane-updater\pending\temp-Polypane-Setup-2.0.1.exe' -> 'C:\Users\admin\AppData\Local\polypane-updater\pending\Polypane-Setup-2.0.1.exe'
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Failed upgrade from 22.1.0 to 22.2.0 - Nextcloud community
This could be a permission issue (or full disk). Who is the owner of the file and which user is running the upgrade?...
Read more >Fortify Software Release Notes 22.1.0 - Micro Focus
This document provides installation and upgrade notes, known issues, and workarounds that apply to release 22.1.0 of the Fortify product suite.
Read more >"Windows cannot access the specified device, path, or file ...
Method 1: Check the permission of the file or folder · Right-click the file or folder, and then select Properties. · Select the...
Read more >An error occurred attempting to download
The installation or update was interrupted, usually by a spotty internet connection or because of antivirus, firewall, or Windows permissions issues. Solutions.
Read more >22.1.0 - GraalVM
See OpenJDK 11.0.15 Updates; 17.0.3 for Java 17-based GraalVM Community. ... This means that, by default, linking errors are now thrown at ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We do set
autoUpdater.autoDownload = false
and use theautoUpdater.downloadUpdate()
and still receive this error:EPERM: operation not permitted, open 'C:\Users\<user>\AppData\Local\<app>-updater\pending\0-temp-<app>-win.exe'
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.