socratis wrote:For you maybe. But there's a ton of threads that have been marked as [Solved], so I'm not sure where you came up with that conclusion. Let me guess; your own case and your own case only.
socratis wrote:You're replying to a thread that's already marked as [Solved] for the love of bytes!!!
socratis wrote:Talk about yourself. The OP has clearly solved his issue in the thread that they started. So, unless you want to share the same success story in this thread, I'd suggest by start reading: Do not hijack other threads, create your own. Choose the title carefully.
Please, pardon my lack of imagination, but am I not also experiencing the same error in Windows 10 v1903 as the original poster? Yes, his issue may have been solved, but mine has not. I specifically replied to this thread because the OP had the same error messages that I get, and I was hoping for further investigation.
But if you really must know how I came to the conclusion that Oracle VirtualBox is not working in Windows 10 v1903? I started it by selecting the icon on my start menu, clicked "Windows 7 x86" to select the virtual machine I wanted, then clicked "Start" on the toolbar. I few seconds later the error dialog box came up. If that isn't enough from which to draw a conclusion, then I don't know what is.
socratis wrote:VirtualBox *does* work on 1903, otherwise everybody and their cousin would be screaming "murder". I have one sitting right next to me actually. And I know that one data point doesn't make a case, but there are a lot of data points out there.
It might work on your installation of Windows 1903, but not on mine, even though it was working flawlessly on 1809. And I know that a single data point will not provide an answer. You are assuming that I have read only this thread. I read several threads on the subject, some of which had more than 100 replies themselves, but to no avail. None provided an adequate answer, and this is why I posted a reply to
this thread.
socratis wrote:Just fix your computer so that you can continue to operate your VMs () as you have been doing for years.
There, I fixed it for you... If the APIs are missing or your installation is incomplete, there's not that much that VirtualBox can do.
Not need to get cynical, as your attitude will serve no purpose other than alienating your users. In the other related thread on this subject I have read, the one thing I have noticed clearly is your (socratis) attitude towards those you're supposed to be helping. You threat those seeking assistance with contempt and distrust. It's almost as if you are not actually willing to help at all.
socratis wrote:BTW, you're getting a hardening error for your ATI drivers:
00:00:05.591089 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection:
rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x5 fAccess=0x2
\Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\c0342855.
inf_amd64_e2ef814e68f7dc8c\B342717\atikmdag.sys: NumberOfSections=101,
implementation max is 42
Please read
really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas.
This is the first bit of possibly useful advice I have read. But it did not work. Rolling back my ATI drivers to an earlier version didn't help as VirtualBox still gave me the errors "VERR_NEM_MISSING_KERNEL_API", "VERR_SVM_NO_SVM". So I restored my drivers to the latest versions, and still no luck.
Sorry, Socratis, but I have not yet found a solution to this problem, other than one you, and Oracle as a whole, may not approve of, as it involves the use of competing virtualization software. This is what I did:
- I used the Oracle VirtualBox Virtual Media Manager ("File" -> "Virtual Media Manager" or <CTRL>+<D>) to convert my virtual hard disks to VMDK format.
- I installed VMWare Workstation Player 15 and created a VM that used the converted virtual drive.
- Instead of booting to the converted drive, I booted the virtual machine using Acronis True Image, and used the "Universal Restore" options to allow the Windows 7 system to boot into "radically different hardware". If not for this step, then the internal differences between VirtualBox and VMWare would have caused havoc with the Windows installation on the virtual hard disk.
- So now I get to continue using my virtual machines as always, and I do not need to use Oracle VirtualBox to do it. And the kicker of the deal is, VMWare provides far better performance and VirtualBox ever did, including seamless integration via it's "Unity" function.
But now here is the real facepalm moment, and the reason why Oracle will not like my solution:
- On an entirely different computer that also runs Windows 10 v1903 and VirtualBox 6.0.8, I was experiencing the same errors.
- But instead of repeating the rather lengthy procedure listed above, all I did was install VMWare Workstation Player 15.
- Surprise! Oracle Virtual Machine 6.0.8 started working again, as it always should have.
So really, it would appear that my problem does NOT lie with my drivers as you so eloquently stated. Instead the problem does indeed exist within VirtualBox itself. I have no explanation as to why installing a competitors product (VMWare Workstation Player 15) solved the problem, but it did. So maybe if your can ask your developers to
fix their software I may be convinced to once again continue using VirtualBox as I always have.
"for the love of bytes!!!", "Just fix your computer" or "there's not that much that VirtualBox can do"
Socratis, on a completely off-topic side note, you should really lighten up on your treatment of members on these forums. Your apparent "holier than thou" attitude does not garner very much confidence in your abilities, and completely exposes your unwillingness to be of any help at all. Your attitude in truth is the prime reason why I'll no longer be recommending Oracle VirtualBox to my clients.