[English]Zum 15. April 2025 haben Oracles Entwickler Virtualbox Version 7.1.8 freigegeben. Diese Version ist ein Wartungsupdate zur Fehlerkorrektur.
Gemäß Changelog soll das Update der Version 7.1.8 folgende Fehler in früheren Virtualbox-Ausgaben beheben.
Anzeige
- VMM: Fixed issue when VM clock went backwards in rare circumstances (bug #22334)
- GUI: Fixed issue when accelerated cursor image was not displayed correctly (bug #22096)
- DevVirtioSCSI: Fixed issue with restoring saved state
- Graphics: Fixed issue when assertion was triggered on restoring VM state if VMSVGA graphics adapter was used without 3D acceleration (bug #21955)
- Main: Fixed issue when VBoxSVC was crashing on saving machine config through VirtualBox web service (bug #22259)
- Main: Fixed issue when wireless network adapters could not be discovered on modern Linux distributions (bug #22362)
- Main: Fixed issue when deleting running VM snapshot was leaving the .sav file on disk (bug #21345)
- NAT: Fixed connectivity loss on Windows host (bug #22364)
- VBoxManage: Updated User Manual to correct the 'VBoxManage modifyvm' invocation for configuring a VM to use host-only networking (bug #22158)
- VBoxManage: Fixed issue when it was not possible to set disk bandwidth with 'VBoxManage bandwidthctl' command (bug #22328)
- Windows installer: Automatically load the support driver after a successful installation (bug #22292)
- Linux Host Installer: Fixed issue which sometimes resulted in installation failure due to incorrect check whether previous VirtualBox installation is running or not
- Linux Guest Additions: Fixed issue when VBoxClient could crash in XWayland guest (bug #22345)
- Linux Guest Additions: Fixed issue which resulted in cursor image corruption when VM was using VBoxVGA graphics adapter
- Linux Guest Additions: Fixed issue when installation could fail on the system which does not have X11 libraries installed
- Linux Guest Additions: Added initial support for kernel 6.14
- Linux Guest Additions: Introduced initial support for RHEL 9.7 kernel
- Linux Guest Additions: Introduced additional fixes for RHEL 9.4 kernel, (bug #22277)
- Linux Guest Additions: Improved 'rcvboxadd status-kernel' check
- Windows installer: Various bugfixes for the new installation code
- Windows installer: Implemented a new fatal error dialog with the ability to open the installer log file directly
- Windows Guest Additions: Fixed mouse driver installation on Vista guests
- Windows Guest Additions: Fixed uninstallation integrity issues (bug #22290)
- Windows Guest Additions: Fixed driver installation error
- RROR_AUTHENTICODE_TRUST_NOT_ESTABLISHED (bug #22300)
- Windows Guest Additions: Fixed 100% CPU usage of VBoxTray which happened under certain circumstances (bug #22123)
- Windows Guest Additions: Now also ships the VBoxAudioTest binary for performing guest audio testing / diagnosis
- Windows Guest Additions: For older Windows versions (Windows 2000 to Windows 7) install alternative Shared Folder driver which avoids some compatibility glitches of the usual driver
Die neue Version der Virtualisierungssoftware lässt sich für Windows, Mac OSX und Linux von dieser Download-Seite herunterladen. Zu beachten ist, dass auch eine aktualisierte Version des VirtualBox Oracle VM VirtualBox Extension Pack herunterzuladen und zu installieren ist. VirtualBox kann frei verwendet werden, für das Extension Pack gibt es jedoch spezielle Lizenzbedingungen. (via)
Anzeige
Für diejenigen, die vielleicht noch auf dem (stabileren) 7.0-er Zweig sind, es wurde auch dort noch eine weitere Version (7.0.26) am gleichen Tag freigegeben:
https://www.virtualbox.org/wiki/Download_Old_Builds_7_0
Falls (wie hier) beim Starten einer virtuellen Umgebung nach der Aktualisierung der Fehler "NtCreateFile(\Device\VBoxDrvStub) failed" auftritt, dann den Treiber VBoxDrv.inf
aus dem Unterverzeichnis
\Program Files\Oracle\VirtualBox\drivers\vboxdrv\
installieren und den PC neustarten – nun sollten sich erstellte virtuelle Maschinen wieder starten lassen!
Danke für den Hinweis.
Das selbe Problem habe ich auch und dein Tipp funktioniert.
Danke.
Bei mir hat ein einfacher Windows-Neustart ausgereicht.