All windows server boxes cant go through on a Fedora 41 VM

I have vagrant on a fedora 41 VM with VB, running any linux based box works fine. I tried to run a windows server box using

config.vm.define "win2k19web" do |win2k19web|
    win2k19web.vm.box = "gusztavvargadr/windows-server-2019-standard"
    win2k19web.vm.box_version = "1809.0.2407"
    win2k19web.vm.hostname = "win2k19-web"
    win2k19web.vm.network "private_network", ip: "192.168.56.40"

or

config.vm.define("win2k19web") do |win2k19web|
    win2k19web.vm.box = "jborean93/WindowsServer2019"
    win2k19web.vm.box_version = "1.2.0"
    win2k19web.vm.hostname = "win2k19-web"
    win2k19web.vm.network "private_network", ip: "192.168.56.40"
  end

It starts to create the VM

Bringing machine ‘win2k19web’ up with ‘virtualbox’ provider…
==> win2k19web: Clearing any previously set forwarded ports…
==> win2k19web: Clearing any previously set network interfaces…
==> win2k19web: Preparing network interfaces based on configuration…
win2k19web: Adapter 1: nat
win2k19web: Adapter 2: hostonly
==> win2k19web: Forwarding ports…
win2k19web: 22 (guest) => 2222 (host) (adapter 1)
==> win2k19web: Booting VM…
==> win2k19web: Waiting for machine to boot. This may take a few minutes…
win2k19web: SSH address: 127.0.0.1:2222
win2k19web: SSH username: vagrant
win2k19web: SSH auth method: private key

then it gets stuck for 5-10 minutes then I have a timeout as follows

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly
working and you’re able to connect to the machine. It is a common
problem that networking isn’t setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.

When I fire VB GUI, click on the VM > show, I see a windows server interface with a circle that never ends

Dore this mean that I cant run win boxes in a linux vagrant environment?