Author

Topic: "Error opening file for writing:" (Read 152 times)

HCP
legendary
Activity: 2086
Merit: 4314
July 23, 2020, 06:31:46 PM
#10
I would concur that it is most likely a "permissions" error of some description... Caused by either an antivirus/antimalware app preventing writing to the system drive... or Windows Security settings doing the same.

Two questions:

1. Are you running the installer as Administrator? ie. right click -> "Run as administrator"? Huh
2. If you already have Bitcoin Core on the PC, did you shutdown Bitcoin Core before attempting to install/update? Huh
legendary
Activity: 2170
Merit: 1789
July 21, 2020, 06:51:35 AM
#9
What exactly should I see on event viewer?

Anything related to the bitcoin exe app error. I also believe this is permission issue even though most of the time Windows will ask for permission if you run an installer. Maybe something screw that up.

What happens if you install it on a different drive? Got the same error?
legendary
Activity: 2394
Merit: 5531
Self-proclaimed Genius
July 20, 2020, 09:57:17 PM
#8
I disabled HIPS. Still get the error. The issue on the other thread is from another laptop.
It's a permission issue then.
Have you tried to run the application installer as administrator as suggested by hosseinimr93 above?
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
July 20, 2020, 06:34:35 AM
#7
-snip- so anvir might be the culprit.
I'm using ESET NOD32.
Your "HIPS" rules (reference) might have been preventing any application/installer from changing files in your system storage.
You might need to add some folder or file exceptions.

Remember you other thread about the bitcoin.conf file? (/index.php?topic=5262146.msg54824582)
I have found out that you'll get that error if the file is read-only, similar when the app doesn't have write access to a file.

I disabled HIPS. Still get the error. The issue on the other thread is from another laptop.
legendary
Activity: 2394
Merit: 5531
Self-proclaimed Genius
July 20, 2020, 02:46:30 AM
#6
-snip- so anvir might be the culprit.
I'm using ESET NOD32.
Your "HIPS" rules (reference) might have been preventing any application/installer from changing files in your system storage.
You might need to add some folder or file exceptions.

Remember you other thread about the bitcoin.conf file? (/index.php?topic=5262146.msg54824582)
I have found out that you'll get that error if the file is read-only, similar when the app doesn't have write access to a file.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
July 20, 2020, 02:05:52 AM
#5
Check the event viewer for more details. If you have any anvir that uses real-time protection, it might be worth mentioning it too, as most of the time when you run an installer Windows will ask you permission, so anvir might be the culprit.

I'm using ESET NOD32. What exactly should I see on event viewer?

legendary
Activity: 2170
Merit: 1789
July 20, 2020, 01:30:11 AM
#4
Check the event viewer for more details. If you have any anvir that uses real-time protection, it might be worth mentioning it too, as most of the time when you run an installer Windows will ask you permission, so anvir might be the culprit.
legendary
Activity: 2380
Merit: 5213
July 19, 2020, 03:41:57 PM
#3
The problem is probably from security permissions you have. It might be helpful to run the file as administrator.

A quick google search gave me the following link.
Error opening file for writing
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
July 19, 2020, 03:06:18 PM
#2
How much space do you have left on the drive. Can you access that folder yourself? Have you tried clicking retry also?

For people to help you it'd:
1. Be a good idea to list your OS version and type.) ie Windows 10 premium/enterprise with last update kb56782 (random letters).
2. Check the contents of that folder to see if anythings already been made. Potentially if the bitcoin-cli and bitcoind binaries have been built.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
July 19, 2020, 02:58:58 PM
#1
Hi, I'm trying to install v0.20.0 but this is what it returns me:



What's the solution?
Jump to: