I've just installed Kali Linux (Debian) in a VirtualBox VM. I want to install the VBOX Additions that will allow me to configure things like screen resolution (hopefully).

My problem is running the install script. I'm root, I've chmoded everything, I have the rights to execute the script but I still get 'Permission Denied'. I've tried with sudo as well.

Check the screen below:

enter image description here


It might be that the /media/cdrom0 filesystem has the noexec flag set. You can check this with:

mount -v | grep cdrom0

If there is noexec between the parentheses, files on the filesystem are not executable. (like (noexec,nosuid,nodev))

You can try remounting the filesystem with the exec flag:

sudo mount -o remount,exec /media/cdrom0

Alternatively you can copy all files to disk and run the scripts from there.

  • 6
    Running bash < ./autorun.sh should also work. – Kenster Jun 13 '14 at 14:06
  • 5
    Indeed, never thought about that. As a variation, sh autorun.sh is more commonly used. – mtak Jun 13 '14 at 15:03
  • 1
    Moreover, one needs build-essential, module-assistant and kernel's headers. Here there is a nice summary of things to do for getting VBoxLinuxAdditions.run to play nicely. – Atcold Nov 2 '15 at 5:57
  • copying the files is the fastest way. – Tomáš Zato Mar 23 '16 at 10:41

The file you want to run is VBoxLinuxAdditions.run , the files named runasroot.sh and autorun.sh will return that error even if you do change the attributes.

After you copy the contents of the Guest additions ISO to a folder on the guest machine if it appears in green text when listed in a terminal then it is already executable. If not you can type into a terminal after navigating to the directory where you saved the files on the guest machine. chmod -x VBoxLinuxAdditions.run or just right click on it and select properties and then select the permissions tab and click the execute checkbox - allow executing as a program.


The problem is due to the permission not set to executable to fix this



chmod -x filename.sh


it should work..

Fix 2

Change the permission of the file system in which the *.sh file is located.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.