Win10 Guest Dies After Clipboard Select on Win11 Host

[DSB Cloudian]

Windows 10 guest dies after selecting a URL from the host's browser (Firefox Private Browsing).

I have a very old and very reliable Windows 10 Pro guest running on a Windows 11 host. The guest was created about 7 (maybe 8 ) years ago on a Windows 10 host and exported it to a newer faster Win11 host. Both the guest and the host are fully updated.

I use the guest for a lot of things, but mainly to download packages using jDownloader.
I find and select the packages / files using the Win11 host's Firefox browser and right-click the link. jDownloader (on the guest) is always checking the host's clipboard and if it looks like a URL, it will use that URL to find packages / files that it can download from that URL. This has worked perfectly with no issues for years.
A few days ago, I removed McAfee and some other apps from the Win10 guest and everything seemed to be normal.

After many hours of use or sitting idle (75 hrs), instantly after a right-click on a URL, the guest died - just poof, it's gone.
The VBox Manager didn't show it was Aborted, and I restarted it.
It's ran for 12 or 13 hours (6 or 8 hours of use and the rest idle) and it happened again today instantly after a right-click on a URL. And this time the VBox manager shows it Aborted.

I'm attaching the log of the last run where is Aborted. But, the last 2 hours of running, the log has the same error message

Code: Select all

12:08:03.571870 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 5120x1392
12:08:03.571987 GUI: UIMachineLogic: Host-screen available-area changed
12:08:35.158010 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:09:13.745301 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:09:49.379113 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:12:39.887605 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:13:41.989042 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:15:08.532485 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:15:38.568908 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:17:22.834046 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:17:38.711804 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:17:56.115587 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:25:44.557694 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:25:44.559120 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:33:32.738505 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:34:12.856834 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:34:32.162583 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:36:09.945859 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:36:24.657068 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:41:59.567175 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
12:59:24.156902 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:01:09.999837 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:01:54.971217 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:02:06.280907 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:02:19.316411 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:02:51.960603 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:03.524254 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:03.527114 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:20.428512 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:20.430041 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:54.373758 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:03:54.376416 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:04:18.715631 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:04:18.718126 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:06:45.854143 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:06:59.195512 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:07:50.644856 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:10:20.365098 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS
13:10:20.367608 VMMDev: Guest Log: shclwnd  *** Error: Shared Clipboard: Setting host data buffer to clipboard failed with VINF_SUCCESS

That is the last line in the log file.

The log file from the day before also ends with this 1-line error message. But it ran for 75 hours and the log file is too long to upload.
It is uploaded VBox.log.3.zip

[DSB Cloudian]

The Win10 guest failed about 6 hours after it restarted.
And this time it didn't happen while I was using it. I came back after being out for 3 hours and the VM was locked up with the pop-up on the screen.
The VirtualBox Manager shows the VM is powered off (not Aborted)

I hope someone can offer some guidance on how to get this problem solved.

The latest VBox.log (882KB) are attached.
And there is "VirtualBox - Guru Meditation" pop-up:

[DSB Cloudian]

There has been some helpful input on this from the Reddit r/virtualbox group (https://www.reddit.com/r/virtualbox/com ... ?context=1).

Even though Hyper-V was disabled in the host system's "Windows Features" control panel, the log file for the guest machine was showing Hyper-V was active and it's related to "Windows Security > Core Isolation" control panel as "Memory Integrity" being enabled.
This is not a recent change I made, and I don't remember when I enabled it. Maybe I enabled that because it is described as "Prevents attacks from inserting malicious code into high-security processes" or maybe it was recommended by some Windows security blog.
Whatever. It is disabled now.

While the guest was running on this host for several months with no problems, the intervals were getting shorter and shorter between lockups.
If this helps I'll post something to mark this as solved.

[DSB Cloudian]

That didn't work. It failed after 17 hours with the Guru Meditation pop-up.

The log file is attached.
But somehow VB still thinks Hyper-V still has something enabled:

Code: Select all

00:00:07.353027 NEM:
00:00:07.353028 NEM: NEMR3Init: Snail execution mode is active!
00:00:07.353028 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:07.353028 NEM:       To see VirtualBox run at max speed you need to disable all Windows features
00:00:07.353028 NEM:       making use of Hyper-V.  That is a moving target, so google how and carefully
00:00:07.353028 NEM:       consider the consequences of disabling these features.
00:00:07.353029 NEM:

But, this does not tell me that Hyper-V is a death sentence, it just says the guest will not run at full speed.

I'll dig around to see if there is anything else that lights up a Hyper-V warning.
But, I suspect Hyper-V is a red-herring is the easiest thing to point to.

[Elwexo]

It's not clear (to me, at least!) if you disabled memory integrity? You'll need to do this to completely disable Hyper-V.
There's a checklist at viewtopic.php?f=25&t=99390.

[DSB Cloudian]

It's not clear (to me, at least!) if you disabled memory integrity? You'll need to do this to completely disable Hyper-V.
There's a checklist at viewtopic.php?f=25&t=99390.

I followed the recipe - and that was included.
And it still craps out.

I gave up on VBox for Windows. I converted the VDI to a VHD and the VHDI and it's now running on a Win 2019 server. Then I use the Remote Desktop Connection to connect from my desktop to the guest VM. It's been stable as rock and I get all the copy & paste functionality connectivity to the "shared" folders that I had before.