VirtualBox Shared Folder - cd: permission denied: /media/sf_shared

I have the same issue.

sf_name is the shared folder name

Steps to reproduce:

  • Followed the Kicksecure guide to setting up a shared folder to the letter (even folder name)

I am also getting the Permission denied for any other action such as
sudo apt update or other

Running Whonix XFCE workstation persistent mode version 17.3.9.9 on Ubuntu 25.04 with Virtualbox 7.0.20_Ubuntu

No help can be provided until a proper bug report has been posted.

This is a very different ā€œissueā€. You need to ā€œfixā€ that first. Please do not mix that discussion into this topic. Please read:

The bug report is that following to the letter the guide doesn’t work.

Step 1. Create folder on host named ā€˜shared’
Step 2. Add it as a shared folder within Virtualbox UI

Step 3. Try to access it from Workstation

[workstation user ~]% cd /media/sf_shared
cd: permission denied: /media/sf_shared
zsh: exit 1

I included the other observation as I thought it might be relevant as it’s also a permission issue.

1 Like

I moved this to its own forum thread because there is no mention of sf_name in your issue report.

Failed to open directory ā€œsf_nameā€. Error opening directory ā€˜/media/sf_name’: Permission denied might be related or might be different.

For some reason, file permissions are no longer already prepared by vm-config-dist This might be a usablity bug, that will be investigated later and will likely be fixed in version 17.4.0.7 and above. (Unreleased at time of writing.)

But there is no need to wait for a fix. Users might be able to easily fix this.

Try this:
Shared Folder Permission Fix
(written just now)

Thanks for putting that together.

I actually managed to work around it.

I had to remove user-sysmaint-split (using the splash screen option at boot).

As outlined in the wiki:

If using unrestricted admin mode: Not applicable.

Actually I was still getting the issue with unrestricted admin mode, I had to launch thunar with sudo perms: sudo thunar and after transferring files to the user Desktop, I had to edit the permissions to be usable by user.

If there’s a way to reinstall sysmain-split, I’ll gadly test your group configurations!

Only means the sysmaint notice isn’t applicable. Doesn’t mean to skip the rest of the instructions.

Graphical Applications and Root Rights

sysmaint, Installation

The guide you provided worked, adapting the commands (after installing sysmaint again):

sudo addgroup user vboxsf throws an arg error

ended up using sudo usermod -a -G vboxsf user and it works like a charm.

1 Like

Command has been corrected in the wiki. (Not using usermod but, see wiki.)