USB's not passing through to VM's on VirtualBox 7.2.2 LINUX

Hello everyone. New user here. =).

Host: POP_OS  |  fresh install with latest updates/upgrades | Ubuntu 22.04 LTS
Guest: Win 10 Home N  |   fresh install with latest updates/upgrades

VirtBox is a fresh install updated to latest 7.2.2
Extension pack is installed and updated to the latest 7.2.2
Confirmed that Guest Additions are installed on Win 10 Home VM. 

Additional Info:
Host is running USBGuard. (Was having this issue before usbguard was installed)
Host is running SELinux. (Was having this issue before SELinux was installed)  

Confirmed that user on host is member of vboxusers
 
VirtualBox Manager Console:
USB Controller is enabled with USB 2.0 (OHCI + EHCI) Controller selected.
When clicking on the Plus+ icon displays a little drop down box where I added the target USB storage device. 
I've tried selecting USB 1.0 and 3.0 as well. No luck. 

Made sure the target USB storage device was unmounted and ejected plus rejected by POP_OS host (via USBGuard) in order to allow it to pass the host through to the VM.  Command used : sudo usbguard reject-device <id> (I replaced id with the id of the storage device I needed to reject). 


Some things I've tried so far:
1. rebooted host. This at least allowed the usb devices to show up in the VirtBox console under the add button.
2. Reintstalled dkms and headers along with virtulabox.deb official package from virtualbox.org. 
3. Rescaled the vm out of scaled mode. wierd I know but someones claims this fixed the issue for them.
4. Tried different USB storage devices to make sure the issue wasn't isolated to one USB device. This issue is effecting all USB devices. 
5. I also tried different VM's both Windows and Linux. Confirmed that all USB devices are not being passed through to all VM's in VirtualBox. 

Additional Info : commands ran on host machine

sudo dkms status

system76/1.0.20~1751390871~22.04~79f5488, 6.12.10-76061203-generic, x86_64: installed
system76/1.0.20~1751390871~22.04~79f5488, 6.16.3-76061603-generic, x86_64: installed
system76_acpi/1.0.2~1719257749~22.04~7bae1af, 6.12.10-76061203-generic, x86_64: installed (original_module exists)
system76_acpi/1.0.2~1719257749~22.04~7bae1af, 6.16.3-76061603-generic, x86_64: installed (original_module exists)
system76-io/1.0.4~1732138800~22.04~fc71f15, 6.12.10-76061203-generic, x86_64: installed
system76-io/1.0.4~1732138800~22.04~fc71f15, 6.16.3-76061603-generic, x86_64: installed

lsmod | grep vbox

vboxnetadp             28672  0
vboxnetflt             40960  0
vboxdrv               696320  3 vboxnetadp,vboxnetflt
kvm                  1441792  2 kvm_amd,vboxdrv

VirtBox Logs 
I have log, log1, log2, and log3. Please let me know which one I need to post along with how much of it. They are long. 

After letting ChatGPT send me on a wild goose chase for 3 days and coming to dead ends with every forum post I've read I'm finally throwing in the towel.  =/

Use VMware Workstation pro its free you'll have less issues.

If your car get's a flat tire do you buy a new car or do you repair the tire? 

I can appreciate the recommended workaround however I'm not looking to migrate over to a new platform. I'd like to find someone who understands logs so they can guide me to finding the root cause of the issue.

https://askubuntu.com/questions/377778/how-to-add-users-to-vboxusers-to-enable-usb-usage

Keep in mind this may need to be constantly done per update unlike with VMware Workstation.

Migrating from vbox to VMware is seamless and you'll enjoy VMware more.

I'll keep your workaround in mind. As per my post I've already verified that I'm a member of vboxusers. 

Check again the groups file in /etc may have been over written with an update

Everything is a fresh install after all updates have been applied but I checked anyways. It says:

vboxusers:x:134:cam 

I have VirtualBox under FreeBSD, and USB2 passthrough is an issue because Oracle made the feature proprietary.  I also have VirtualBOX under Debian Linux and USB2 passthrough is OK because Oracle's binary module has been installed.  Plus, Oracle use Debian Linux to test their releases.  Since you are using a different Linux flavor, my recommendation would be to ask for support on their forums if they exist.  Unless there's a Linux developer/maintainer here, your logs will be very difficult for us to understand.
 
I really like VirtualBox, but in your case, cryptodan's suggestion may be more than relevant, at least worth a try.  Can't hurt!

I have VirtualBox under FreeBSD, and USB2 passthrough is an issue because Oracle made the feature proprietary.  I also have VirtualBOX under Debian Linux and USB2 passthrough is OK because Oracle's binary module has been installed.  Plus, Oracle use Debian Linux to test their releases.  Since you are using a different Linux flavor, my recommendation would be to ask for support on their forums if they exist.  Unless there's a Linux developer/maintainer here, your logs will be very difficult for us to understand.
 
I really like VirtualBox, but in your case, cryptodan's suggestion may be more than relevant, at least worth a try.  Can't hurt!

I'll be looking into this. Thank you.

[SOLVED]

Main issue: target usb storage device needs to be mounted to host before launching VM. I was unmounting the storage device before launching the vm. (as per what the forums were recommending) It was the communities idea that a device had to be unmounted from the host in order for the guest vm to be able to detect it. In other words the host would keep the usb device from the guest untill it was umounted. This turned out to not be true for my machine. 

Steps:

1. Re-added user to vboxsergroup for safe measures : sudo usermod -a -G vboxusers <username>   |  rebooted host

2. Set USB from 2.0 to 3.0 in VirtBox Manager. For some reason 3.0 is the only one that works POP OS. When I was Windows only 2.0 worked. Same USB port used. 

3. Kept target usb storage device mounted to host. Once the vm was launched the storage device automatically switched from the host to the guest vm.  

With VMware you dont need to connect it prior to launching the vm. That's another reason I recommended VMware its far easier and much better.

I can respect your prefernce for VMWare as it does seem to perform better than VirtBox by 10% on Linux and 15% on Windows. The truth is that solutions such as migrating to new platforms, switching OS's, and replacing hardware should always be the last resort if a fix cannot be found or if the fix is so time consuming or expensive that replacing it would be faster and more cost effective.

RCA is the best course of action becuase it revents repeat issues which in turn allows users to maintain production. RCA also allows organizations to learn and become proficient with the technology they use. 

Replacing applications with other applications just because something isn't working correctly seems irresponsible to me. With this method you're potentially replacing a problem with another problem. VMWare has it's issues too. Every application has bugs and compatibility issues. Then you have to learn the new application and learn how to solve the issues that comes along with that new application. It's just not practical. 

The solution to my issue was very trivial and certainly didn't warrant migrating to a new platform. 

Your solution would be practical in certain scenarios. Just not in mine.