The VM uses a portion of the host computer’s RAM, a part of the hard disk and some of its CPU time.
Guest: Windows 7 SP1, build 7601, July 2019 Update, 32-bit.The purpose of this tutorial is to demonstrate how to set up a Windows 10 Virtual Machine (VM) using the Oracle VirtualBox software.Ī Virtual Machine (VM) is a fully running copy of an operating system that runs concurrently (at the same time) with the host operating system. Host: Windows 8.1 圆4 July 2019 Update. I think that the idea in the other ticket (to publish the details of the affected and not affected systems) is very useful and do so for my systems here. But in spite of the different causes the issue itself is the same in the end: something in file operations in the share folder cause the BSOD in the driver, which causes the guest display resolution reducing just before the crash. Other difference is the code of the BSOD: in our case it’s 0x1e (KMODE_EXCEPTION_NOT_HANDLED) and not the because of aforementioned differences, I think that also has this issue and not the other one. But not every executable triggers this behavior, only the mentioned one. I can’t see what in the folder, because BSOD happens as I choose the folder in Windows Explorer. The BSOD happens already because I access the folder with the executable in it. The first difference: I don’t have to and can’t access the executable in the shared folder. I think that this is different issue as in the two other tickets ( #18766 and #18768). I would like to report, that the newer version of the file (5.74) also causes this. Single-click on any directory in there and I get a BSOD. 
When I open explorer.exe and go to \\vboxsvr everything is fine (there's a pdf, zip, and some directories)ĭouble-click on sysinternals and everything is fine I've then exposed ~/shared_directory as a Shared Folder with the Windows 7 圆4 guest running Guest Additions 6.0.10
I've since taken the sysinternals suite, put it on my host at ~/shared_directory/sysinternals/ and split its contents into directories containing only 10 files each (with one of them actually only containing one file) exe installer in my shared directory and the Windows guest BSOD'd as soon as I went to \\vboxsvr\shared_directory exe file (or at least the ones I've tested) Worse still, for me, this seems to happen when you click on any directory in explorer.exe under \\vboxsvr\ if that directory contains a. Only when I upgrade to Guest Additions 6.0.10 do the problems occur. My guest is snapshotted with Guest Additions 6.0.8. Host: Debian Linux running Virtualbox 6.0.10.
0 kommentar(er)
