Hello. I am experiencing the same issue as OP.
I am running kernel 6.12
I have done the exact same thing as described in the previous posts and still have the same issues.
On sudo vboxreload i get
Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/6.12.19-1-MANJARO
modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/6.12.19-1-MANJARO
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.12.19-1-MANJARO
Please advice
Your post has been moved to a dedicated topic.
Please do not post your issue on another memberās topic; thatās usually referred to as hijacking; and especially not a topic thatās a year old, typically referred to as necrobumping.
Yes, thereās probably a name for everything. 
Please list everything you have done to solve your issue.
Note that;
doesnāt particularly help anyone understand a problem specific to your environment. Telling us directly, will go further toward that goal.
Please also provide system information as described (below). It might also be beneficial to re-familiarise yourself with forum rules, generally.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. Itās equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
This:
should set you on the right track.
Perhaps there is a wiki here specific for Manjaro - I didnāt look.
But the differences are minor.
It might have been obvious from the topic you attempted to hijack that those instructions may not have been complete; or, that those helping were only responding to specific parts of the process.
The best resource is invariably The Wiki (either Arch or Manjaro). Itās only if you need help with those instructions that a Support topic might be needed.
Regards.
For VirtualBox to function you need to identify your kernel
Example
$ uname -r
6.14.1-1-MANJARO
Please adjust the commands to match your kernel. Then you choose
either dkms, kernel headers and vbox host modules
sudo pacman -Syu linux614-headers dkms virtualbox-host-dkms
or the appropriate host modules for the running kernel
sudo pacman -Syu linux614-virtualbox-host-modules
Only then will it be possible to use virtualbox
sudo vboxreload
As for the below comment - @jrichard326 - could you please provide a link to the statement ?
I see that you are running kernel 6.12. Please read the following:
āIn [Linux] kernel 6.12, KVM initializes virtualization on module
loading by default. This prevents VirtualBox VMs from starting,ā
said the devs. āIn order to avoid this, either add
ākvm.enable_virt_at_load=0ā³ parameter
into kernel command line or unload the
corresponding kvm_XXX module.ā
So, try adding the kernel parameter to grub:
Virtualbox Kernel 6.12 kernel command line parameter in GRUB:
ākvm.enable_virt_at_load=0ā³
Then sudo update-grub
Reboot for good measure and see if any progress was made.
Also, do you have linux612-headers and linux612-virtualbox-host-modules installed?
@linux-aarhus The source was at the following url, but when this issue first arose, I think it was also mentioned on the virtualbox website.
Changelog:
https://www.virtualbox.org/wiki/Changelog 7.1.4
vb ticket:
https://www.virtualbox.org/ticket/22248#no1
That is quite strange - on my laptop with Linux 6.12 - I have an ubuntu vm running in virtualbox - they have never heard of this - they just work.
I am not aware this should be added on a host running Manjaro - apparently SUSE had issues - I have no record of it being an issue on Manjaro.
This is pure speculation - theoretically it could be an issue - perhaps even necessary if you were to extend the CPUs virtual capabilities onto the vm - something like running a vm inside a vm - but such scenario is highly specialised and not likely to happen with a Manjaro Linux host system.
Thank you for the clear instructions.
Yes I posted on that thread thinking is was still active. (was a little fast and didnāt register that is was from 2024).
I have tried all instructions and variants listed in both the Manjaro wiki and the Arch wiki. Still getting the same issue.
I have not tried to change kernel, but will do that as next step
Reboot your system after a kernel upgradeā¦ 
Current linux612 is:
mbn info linux612 -q ī² 99 ā ī² 9s ļ
Branch : unstable
Name : linux612
Version : 6.12.22-1
Repository : core
Build Date : Mon 07 Apr 2025 15:38:37
Packager : Manjaro Build Server <build@manjaro.org>
Branch : testing
Name : linux612
Version : 6.12.21-4
Repository : core
Build Date : Tue 01 Apr 2025 20:45:30
Packager : Manjaro Build Server <build@manjaro.org>
Branch : stable
Name : linux612
Version : 6.12.20-2
Repository : core
Build Date : Mon 24 Mar 2025 07:33:36
Packager : Manjaro Build Server <build@manjaro.org>
Thank you for the detailed responce. I have tried all these and followed the guide both in the arch wiki and the manjaro wiki.
Virtual box starts fine and when i try and launch a new VM i get the following message
Problem is that /sbin/vboxconfig does not exist.
Should I try and change kernel and see if that fixes the issue?
Thank you.
A final reboot did the trick.
I feel extremely stupid not to check this as the first thing.
Everything seems to work as it should right now
Thank you @linux-aarhus @soundofthunder @Nachlese for the support
Thanks. Based on your comment, I removed the kernel parameter and virtualbox is working fine without it. I havenāt checked with 6.12 as I am running 6.14. I do recall needing the kernel parameter to get virtualbox to run on my Manjaro Host at one time. It didnāt occur to me to test a few months down the road now, without the kernel parameter.
I still have that parameter in my setup.Thanks for the suggestion of not needing it anymore I will remove it as well. 
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.