Failed to start Windows 10 VM from VirtualBox

I am unable to start my Windows 10 VM from VirtualBox

When trying, it aborts, and I get this message:

Failed to open a session for the virtual machine Windows 10.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

VirtualBox 6.1.36-lp154.2.7.1
Kernel 5.14.21-150400.24.11


**machine:/home/djviking/ #** zypper search --installed-only -s VirtualBox
Laster pakkebrønndata...
Leser installerte pakker...

S  | Name                   | Type  | Version                                  | Arch   | Repository
---+------------------------+-------+------------------------------------------+--------+-----------------------
i+ | virtualbox             | pakke | 6.1.36-lp154.2.7.1                       | x86_64 | Main Update Repository
i+ | virtualbox-guest-tools | pakke | 6.1.36-lp154.2.7.1                       | x86_64 | Main Update Repository
i+ | virtualbox-host-source | pakke | 6.1.36-lp154.2.7.1                       | noarch | Main Update Repository
i+ | virtualbox-kmp-default | pakke | 6.1.36_k5.14.21_150400.24.11-lp154.2.7.1 | x86_64 | Main Update Repository
i+ | virtualbox-qt          | pakke | 6.1.36-lp154.2.7.1                       | x86_64 | Main Update Repository
**machine:/home/djviking/ #** uname -a
Linux arcturus 5.14.21-150400.24.11-default #1 SMP PREEMPT_DYNAMIC Sun Jul 17 20:46:33 UTC 2022 (be260ca) x86_64 x86_64 x86_64 GNU/Linux


**machine:/home/djviking/.config/VirtualBox #** tail -f VBoxSVC.log
00:00:00.231518 nspr-2   VirtualBox: object created
00:00:06.642591 nspr-3   Launched VM: 1006643888 pid: 4716 (0x126c) frontend: GUI/Qt name: Windows 10
00:00:07.818266 nspr-6   Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] vrc=VINF_SUCCESS
00:00:08.078558 nspr-2   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:08.112814 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan1: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:08.188975 nspr-3   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan1: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:08.565945 main     Saving settings file "/home/djviking/VirtualBox VMs/Windows 10/Windows 10.vbox" with version "1.15-linux"
00:00:09.022588 Watcher  Reaper: Pid 4716 (126c) was signalled: 11 (0xb)
00:01:58.004490 nspr-5   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan1: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:01:58.016279 nspr-2   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan1: VBoxNetAdpCtl: ioctl failed: Operation not supported

I installed the Oracle VM VirtualBox Extension Pack for version 6.1.36
I just thought about it might be that which causes the abort.
Then I was able to start the Windows VM.

Wish the error message I got could have described it better, and suggested it.

Happened to me a few times, usually due to mismatched vbox and extension pack versions, AFAIR.

Since yesterday, after a restart because of an kernel update, I get the same error, just when I want to start my Windows VM. I still use openSUSE Leap 15.3 and VirtualBox 6.1. How can I fix the issue best? Should an update to openSUSE to 15.4 help? This needs to be done anyhow, but I wanted to wait a bit because currently I do have less time for such administrative work.
I can not switch the extension pack because I can not start Windows at all. Also it worked since years…

Extension:
Ah, sorry! I mixed it up with the extension in the Windows VM! I just updated the extension pack to 6.1.36 and all works fine again! So, my problem is solved too! Thanks for the hint, sorry for not reading it right in the first try.

I can not switch the extension pack because I can not start Windows at all. Also it worked since years…

Extensions are not the Guest Additions.

Extensions have to installed on the Host in the Virtualbox-Menu:
File----Preferences—Extensions

Download:
https://download.virtualbox.org/virtualbox/

Yes, found out my own. But thanks for the answer and the detailed description.