[DISCUSSION] VirtualBox - Update, SLP & SLIC

You need to login to view this posts content.

 

Both VBOX 7.1 and 7.0 in newest versions make error about NT Kernel and something like that type "
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a
permissionproblem with /dev/vboxdrv. Please reinstall the kernel module by
executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package
first. This package keeps track of Linux kernel changes and recompiles the vboxdrv
kernel module if necessary."

Or that "
34c.754: supR3HardenedWinReadErrorInfoDevice: 'RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume2\Windows\S'

134c.754: Error -626 in supR3HardenedWinReSpawn! (enmWhat=3)

134c.754: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e)

VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume2\Windows\S

2ea4.2960: supR3HardenedWinCheckChild: enmRequest=2 rc=-626 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e)

VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume2\Windows\S

2ea4.2960: Error -626 in supR3HardenedWinReSpawn! (enmWhat=3)

2ea4.2960: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e) VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume2\Windows\S"

Earlier version weren't making that things. It are examples.


Edut: are posts on forum virtualbox about that bugs in versions from January and they working over fix. I saw they made out some compilation 7.1.6 with other number to tests if it fixed. I didn't tested. I actually let's stay me on version from October 2024.

Someone saw too?

 

Are some comments about that error kernel wasn't fixes in newest virtualbox still when click on number bug and details will opened forum.

Me interesting, Vista black screen is finally fixed? We mean updated with windows server 2008 patched and turned on Windows protections type vbs. Because 7.1.4 or 7.1.7 (test) still that had. But with turn off that vbs and all, it worked.

Here helped turn off option about protect ketnel stack in windows 11 24H2. Theory on windows to 11 23H2 shouldn't had that problems. I tell theory, because we know how is 11.

 

Sorry to ask about something you commented on last month. Is the problem with > 1 core only for the paravirtualization options he mentioned?


Windows 10 Ent LTSC worked right out of the VirtualBox without any tweaks. Win 11 Latte hung at the first installation start-up icon without any interface. This is in VirtualBox 6.1.22 on a Win 7 host.


I wonder if my difficulty with the Win 11 Latte comes from having selected only one core in the VirtualBox settings? Microsoft's website says Win 11 requires 2 cores (and does not specify such a requirement for Win 10).

 

maybe "Lite"

 

Yes, latte seems a bit easier to type than IoT LTSC.

My rationale for virtualizing Win 10 or 11 is to be able to adapt to the historic lack of reliability of system restore in these O/S. If system restore fails in a virtual system, then I can seamlessly restore via snapshot instead. However, I'm hoping system restore will fail less often with a lite version.

Trying to browse the internet with a virtual lite Win 10 or 11, since the internet seems to suggest that Linux versions of system restore are slower and more cumbersome than windows system restore.

Thanks so much! Knowing this, the approach I'm taking is to divide system resources between real-mode Win 7 (with which I run office) and virtual Win 10 or 11 (which handles internet). It's on upscale hardware that runs Win 10 very fast in Virtual Box, but I'm guessing that running a Win 11 latte will delay my system's obsolescence, when compared with the Win 10 latte, which only lasts until 2032.

I guess the internet is indicating that I'll have to run VirtualBox 6.1.28 (or later) for Win 11? Unfortunately 6.1.28 is not working for me either. Hoping I can find a quick-and-easy answer for virtual 11 on the internet. Otherwise, I'll just have to begin with the Win 10 latte for now, and maybe later upgrade to 11 if I ever figure out how to get it working virtually on my Win 7 hosts.

 

Ahhh, nice, thanks! What I'm not seeing in the VirtualBox GUI is how to activate UEFI & Secure Boot, and where to enter the virtual TPM.

On the internet I found instructions for these steps for VMWare, but now that you've said this can be done in VirtualBox I'm intrigued.

 

Ahhh, thanks. So it seems the quick-and-easy approach to running an 11 guest on a 7 host may be VMware. I'll have more issues to learn to do this with VirtualBox.