Hi *,
I'm affected by this bug too. What I noticed:
When I run
```
$ strace -ff -o VBoxManage.trace VBoxManage startvm
92522455-ebd0-4a67-8a38-4ba05ca3fc00
```
and check the trace files for any "perm" I see
```
$ grep -i perm VBoxManage.trace.101*
...
VBoxManage.trace.10169:openat(AT_FDCWD, "/de
Add-on: I checked the sources provided at
https://download.virtualbox.org/virtualbox/6.1.22/ and I think the
responsible code snippet is in
VirtualBox-6.1.22/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp
```
$ cat -n VirtualBox-6.1.22/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp |
grep
Errm, I don't know what to say.
Today I rebooted and tried again... and it worked. o.O
```
$ VBoxManage startvm 92522455-ebd0-4a67-8a38-4ba05ca3fc00
Waiting for VM "92522455-ebd0-4a67-8a38-4ba05ca3fc00" to power on...
VM "92522455-ebd0-4a67-8a38-4ba05ca3fc00" has been successfully started.
```
I