Error cannot open file for writing

This article has been updated to stay relevant for Windows 11 and 10 users. 

Errors that appear during installation are surely the worst kind. The error opening file for writing has been reported by many users for a long time, and it appears while trying to install certain applications.

This error mainly appears for writing MSI Afterburner, Steam, vcredist_x86.exe, VLC, and some other commonly used applications.

Here we have discussed how to solve this error, so keep reading!

Why You Cannot Open File For Writing?

As per reports, this error is most common when setup files lack the required permissions as the setup file can’t open the file to write.

But, there can be other causes for this error, such as:

• If the installation file is not compatible with your system, then it can cause such an error.
• The antivirus is known to stop files from writing that it considers a threat to the computer, including installation files. Thus, the antivirus can be responsible for the error while opening the file.
• The installation file itself can be corrupted causing this error.
• If the installation process of the file is already running in the background and you try to start the installation again, then this error can get triggered.
• Problems in registry or excess of junk files in the computer can also cause this error.

This error can be fixed with the following solutions. So, perform all of them and see which one solves it for you.

Solution 1: Close All Background Installation Processes

If one installation is already in process in the background and you are trying to start another installation, then this error can get triggered.

To ensure there are no installation processes in the background, follow the steps given below:

1. Press Ctrl + Shift + Esc keys on your keyboard to open the Task Manager.
2. Select the Processes tab, and check if any installation process is running.
   If yes, then right-click on it and click on the End task option.

Try installing the file again. This solution should fix the problem if it was caused by another installation in the background.

Solution 2: Delete Junk files

If your computer has excess junk files, then it can cause this type of installation errors.

Fortunately, there are some in-built junk file cleaners in your Windows like the Storage sense and the Disk cleanup tool, which can be used to delete the junk files present in your computer.

After the junk files are removed, try to install the application again and check if the error persists.

Solution 3: Run The Compatibility Troubleshooter

If the installer file is incompatible with your Windows, then the installer can’t open the file to write and thus trigger this error.

Fortunately, there is an in-built compatibility troubleshooter in Windows that you can use to check the file’s compatibility.

To run the compatibility troubleshooter, follow the steps given below:

1. Locate the installer file of the application that is causing this error for you and right-click on it.
2. Click on the Properties option from the pop-up menu.

1. Select the Compatibility tab and then click on the Run compatibility troubleshooter option.
2. Select the Try recommended settings option and follow the instructions given by the wizard to run the compatibility troubleshooter.

Try to install the file again and check if the installer is facing the same error. 

Solution 4: Run The Installer With Administrative Rights

This error mostly happens if the installer doesn’t have the required permissions to install the file. Running the installer as an administrator can fix the problem.

Here is how you can do it:

1. First, locate the installer in your computer and right-click on it.
2. Select the Run as administrator option.
3. The application will now install while having administrator rights.

If the error doesn’t arise again, then you will have to open this program each time in administrator mode to work around this problem or you can give this application permanent administrative rights.

To set the application to run as administrator whenever you open it, follow the steps given below:

1. Locate the application on your computer and right-click on it.
2. Click on the Properties options from the pop-up menu.

1. Select the Compatibility tab and then select the Run this program as an administrator box.
2. Finally, click on Apply and then OK to save the changes.

Solution 5: Change Security Permissions

If running the installer as an administrator didn’t work, the check if you are signed in as a regular user account.

Regular users are not allowed to install applications if denied by the administrator. So, they can face this error when they try to install the application.

You can try changing the security permissions to allow the installer to function. To change the security permissions, follow the steps given below:

1. Right-click on the application and select Properties.
2. Next, select the Security tab and then click on the Edit option.

1. Click on your account username in the Group or user names section.
2. In the Permissions for Users section, locate the Write option and then check the box in the Allow section.

1. Finally, click on Apply and OK to save the changes.

By changing the security permissions, you should now be able to install the program without triggering the error during the installation.

Solution 6: Change Advanced Security Permissions

If changing the security permissions didn’t fix this error, then try changing the Advanced security permissions.

To change the Advanced security permissions, follow the steps given below:

1. Follow Solution 5 and open the Security tab.
2. Next, click on the Advanced option.

1. Click on the Add option and click on the Select a principal option.

1. Type Everyone in the Enter the object name to select (examples) section and then click on the Check Names option. Click OK to save the changes.

1. In the Basic permissions section, check the Full control box and click on OK to save the changes.

1. Now, from the Permission entries list, locate the Everyone element and select it.

Now, you should be able to install the application without triggering the error opening file for writing during the installation.

Solution 7: Create New User As Administrator

If you don’t want to change the security permissions, then try creating a new user account as an administrator and then install this application there.

To create a new user account as an administrator, follow the steps given below:

1. Right-click on the Windows start button and then click on the Settings option from the pop-up menu.

1. Locate the Accounts option and open it.
2. Now, select the Family & other users option (only Family for Windows 11).

1. Then scroll down and click on the Add someone else to this PC (or only Add Someone for Window 11) option.

1. Click on the I don’t have this person’s sign-in information option.
2. Next, click on the Add a user without a Microsoft account option. You will have to use another Microsoft account in Windows 11.

1. Now, enter the name and the password of the user account and then click on Next.
   This should create your new user account and you will be able to see it in the Other users section.
2. Select the user account you just created and click on the Change account type option.
3. Now, click on the Account type menu and select the Administrator option from the drop-down list.
   Click Ok to save the changes.
4. Now, sign out of your current account and log in to your new user account.

Once you have switched to the new user, try installing the program and check if the setup still cannot open file for writing.

Solution 8: Disable Your Antivirus

Antiviruses are known instigators when it comes to stopping other files from opening or stopping installers.

Though the antivirus will only target those that it considers threatening to your PC, but sometimes what they consider and what the reality is can differ.

If your Antivirus is stopping the installation of the program, then disabling the antivirus should fix the problem.

To disable Windows Defender, follow the steps given below:

1. Type Windows Security in the Windows search bar and select the top option.

1. Select the Virus and Threat protection option and then click on the Manage settings option under the Virus and threat protection settings.

1. Disable the Real-time Protection toggle to disable Windows Defender.

Once the antivirus is disabled, try installing the program and check if the problem arises again.

If the problem still arises, then follow the above steps again to turn on Real-time protection, as the error is most likely not caused by the antivirus.

Solution 9: Disable The User Account Control Feature

Whenever there is a system related change that requires administrator privileges, the User Account Control notifies you about the change.

This feature was included as a way to protect the user, but it is also reported by many users as the cause of this error.

Disabling User Account Control can fix this error. Here is how you can disable it:

1. Type Change User Account Control settings in the Windows search bar and select the top option.

1. You will notice a slider on the left side of your screen. Drag that slider down until it says Never notify.
2. Finally, click on OK to save the changes.

Solution 10: Delete The Installer And Download It Again

If none of the above solutions worked for you, then the installer file itself may be corrupt. In this scenario, locate the installer file and delete it completely from your computer.

Now, download the installer of the program again from the official website and then try to install the program.

Wrapping Up

So, now you know what to do if you face the error opening file for writing during the installation of any program.

The above solutions should help you fix this issue so read and execute them carefully. And as always, feel free to share your thoughts on this article in the comment section below.

Vim can’t open file for writing error is one of the most common and frequent errors you will encounter, if you use Linux and vim editor. Whether you are a novice or Pro Linux user, «E212» is the error code, you don’t like seeing. Most of the time, this error occurs due to insufficient rights or a directory path or file that doesn’t exist, which you are trying to edit. In this post, I will let you know all the reasons and solutions to fix the «Vim can’t open file for writing» error.

When you use Linux, you can get the below-mentioned error, while you try to edit a file —

• /etc/apt/sources.list» E212: Can’t open file for writing
• Vim Can’t Save File (E212)
• Vim can’t open file for writing
• Root user can’t open file for writing
• Error in editing vimrc
• E212: cant open file for writing ec2

Possible causes of the above-mentioned issues —

• You don’t have access or you are trying to edit a file, which is owned by root user
• Path of the file, you are trying to edit doesn’t exist (non existing file, non existing directory)
• Trying to write a network drive and you don’t have access or partial access
• Trying to edit a read only file system
• Not enough space exists in your current partition or drive.

Let’s deep dive and fix errors and it’s causes one by one.

Install vim editor in Ubuntu, if not there already

If you get the error: «Command ‘vim’ not found, but can be installed with:» it means you don’t have vim (visual improved) editor installed. Run the following command to install the package in Ubuntu.

$ sudo apt install vim

Solution-1 Check the directory or path of file, create it if it doesn’t exist

First thing first, if you are getting vim can’t open file for writing error, check the path and directory of the file. Let’s understand it from an example.

I am trying to run a command «vim /home/tmp/sample.txt» and getting this error «/home/tmp/sample.txt» E212: can’t open file for writing» while saving it as shown in the image.

In this scenario, the «tmp» directory inside /home doesn’t exist. So if you will try to either create a new or edit the existing «sample.txt» file. This will not work and you will get errors.

In my case, I need to create the directory tmp inside the /home first to get rid of this "E21: can't open file for writing" error. This may happen in your case also. You may need to create the required directory or maybe you just need to correct the required path :-).

If you want to create a directory without closing the vim editor prompt because you have already edited the file and you don’t want to lose changes. Then follow these steps-

• Press «ESC» on your keyboard.
• Type «!sudo mkdir «path of directory that need to be created«. For example, in my case i need to create «tmp» directory inside /home.

E.g.

:!sudo mkdir /home/tmp/

As soon as you will run this command and press enter, It may ask you to give your sudo credentials, and your required directory will get created as shown in the image.

You can edit, save and exit your file now with the «:wq» command without any issue.

How to get the reason of error «E21: can’t open file for writing» using vim help

To find out the reason for the error, follow these steps in the vim editor prompt, where you are getting an error.

• Press «esc» key on your keyboard
• Then type :h e212 as shown in image «:h -« represents help and e212 error. Same way you can check for any error, you encountered in vim editor

• Press enter and you will get the error code and its reason. For example, in my case it is showing the follow —

For some reason the file you are writing to cannot be created or overwritten.
The reason could be that you do not have permission to write in the directory
or the file name is not valid.

Press the «ESC» key and then type «:q!» to exit from help.

How to fix etc/apt/sources.list» E212: Can’t open file for writing

If you use Linux, many times in your lifetime. You would have edited the sources.list file and I am sure, you would have encountered an E212 error. Follow solution-2 step by step to fix this issue.

Solution-2 Validate User or file permissions

If you are trying to edit a file and you have given the correct path but still you are getting «can’t open file for writing error«, then you are a victim of permission issues.

If you are logged in with a non-root user, make sure you start with the sudo command, if you are trying to edit a system file or file owned by root.

Let me show you an example, try editing /etc/apt/sources.list with a non-root user and you will understand, what I am trying to prove here.

If you will see the below image, the «sources.list» file is owned by root, so if you will try to edit it using a non-root-user with the following command

$ vim /etc/apt/sources.list

You will get «/etc/apt/sources.list» E212: Can’t open file for writing» error.

To fix it, you must edit this file using sudo permissions. run the following command to edit this file successfully.

$ sudo vim /etc/apt/sources.list

How to fix even if «Root user can’t open file for writing»

If you are a root or sudo user, Also you have given the correct path to directory or file but still, you are not able to open the file for writing. Then you are trying to edit a read-only file system or your disk space is full, which doesn’t allow editing and saving a file.

Solution3- Check for Read-only file system or Capacity issue

Use the «df» command to check the partition or disk space usage. If you see «disk» or «partition» available space is showing «0» bytes except for «/dev/loop».

Then make space by deleting or removing unnecessary files using the rm command. It will fix your «vim can’t open file for writing» issue.

$ df -h

If you have enough space, then make sure your file system is not mounted as read-only. Run the «mount» command and check for your device, it must be mounted as read-write (rw) not read-only (ro).

For example, /dev/sda5, which is my root (/) partition, mounted as rw.

$ mount

If it is showing mounted as read-only in your case, then remount it as rw. If it’s happening due to file system errors, then fix the file system errors and re-mount it to a read-write file system.

$ sudo mount -o remount,rw /partition/identifier /mount/point

or

$ sudo mount -o remount,rw /

You will be able to edit your file, once your file system will be rw and your «vim can’t open file for writing» will vanish.

Video tutorial

Conclusion

I am hopeful, that one of the 3 solutions shared in this post will fix your «E212: Vim can’t open file for writing» error. If you are still facing issues, You can let me know, via your comments. I will try to help you to the best of my knowledge.