-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Windows 7 64 bits : Permission error #2617
Comments
@Nickduino Did you try running it as administrator too? |
I should have mentioned it but yes I did |
I'm using the SD card that came with my Raspberry Pi. Is it possible it is somewhat write protected? |
It sounds strange, but it looks like it happened already before. |
Same issue.
Yescopy pasted logs, Click to expandUmount on success: true
Validate on success: true
Fri Feb 01 2019 01:01:44 GMT+0530 (India Standard Time) Flash error ({"error":{"name":"Error","message":"EPERM: operation not permitted, write","stack":"Error: EPERM:
operation not permitted, write","code":"EPERM","syscall":"write","errno":-4048},"applicationSessionUuid":"a231da97-d139-4907-
9027-4fa24541105f","flashingWorkflowUuid":"2b07360d-f80a-44e1-9cce-1bc2283674dd","flashInstanceUuid":"6fa420ea-fae1-4064-8e85-0703b50d3e97","image":"F:\\Backup programs\\Linux OS for VM\\ISO files\\ubuntu
family\\kubuntu\\18.10\\kubuntu-18.10-desktop-amd64.iso","drives":["\\\\.\\PhysicalDrive2"],"driveCount":1,"uuid":"6fa420ea-fae1-4064-8e85-0703b50d3e97","unmountOnSuccess":true,"validateWriteOnSuccess":true})
Error: EPERM: operation not permitted, write
Fri Feb 01 2019 01:01:44 GMT+0530 (India Standard Time) Open modal ({"name":"warning","applicationSessionUuid":"a231da97-d139-4907-9027-4fa24541105f","flashingWorkflowUuid":"2b07360d-f80a-44e1-9cce-1bc2283674dd"})
{"stack":"Error: EPERM: operation not permitted, write","message":"EPERM: operation not permitted, write","name":"Error","code":"EPERM","syscall":"write","errno":-4048}
console.(anonymous function) @ C:\Users\trtsqwe\AppData\Local\Temp\nsz8224.tmp\app\resources\app.asar\node_modules\raven-js\dist\rave…:58
etcher:sdk:scanner start +10s true
Warning: Failed prop type: Invalid prop `disabled` of type `string` supplied to `ProgressButton`, expected `boolean`.
in ProgressButton
console.(anonymous function) @ C:\Users\trtsqwe\AppData\Local\Temp\nsz8224.tmp\app\resources\app.asar\node_modules\raven-js\dist\rave…:58
Flash results Object
cancelled: false
__proto__: Object
Terminating IPC server I used USB 3.0 port. Ran as admin. How I handled it:
I think Etcher got interrupted by Windows Security's 'Controlled folder access' feature.
the images:I hope it helps. |
could be similar #2547 I'll be unavailable for quick responses for a while. |
It did work flawlessly with a brand new Kingston. I'm convinced the other SD had some kind of write protection (not allowing to change the recovery partition) |
Taking #2617 (comment) into account, this becomes a task for improving experience on Windows 10. If I need to file a separate issue, please let me know. If yes:
I will try to see if I can find any more security settings/policies that stump Etcher. And try alternatives like Rufus. |
Rufus is out. I have read https://github.com/pbatard/rufus/wiki/FAQ#error-0x00000005-access-is-denied , but is it true for Etcher? (this should be easy to find) https://github.com/pbatard/rufus/wiki/FAQ#incompatible-software, is there a similar section for Etcher? |
My bad, I tried Rufus( portable version ) without changing my Anti-Ransomware( CFA ) settings, and it succeeded where Etcher( portable version ) failed. So, if Etcher fails and CFA is needed, try Rufus. It may work. |
I have to admit I don't follow you :-D What are you saying? That Rufus might be able to repartition partition-locked (or it seems) SD card? |
No, I used a flash drive. |
About filing a new issue:
|
The error message (I tried launching from a command line in case it displayed a feedback):
The devtool info:
5 minutes ago, I was using this very same SD in my Raspberry Pi. I'm not saying it's not broken...but it seemed to be working then.
The text was updated successfully, but these errors were encountered: