VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Ah yeah, the website is not updated yet but the file is already live on the servers, software-download.microsoft. com/download/pr/MediaCreationTool1903.exe
But if the point of our argument is that I am using pre-release Software then okay, we could still treat it as that as long as MS does not update their websites, fine by me. Doesn't change the fact that this will ship to many users next month.
I installed VirtualBox-6.0.5-129923-Win.exe now and will report back if anything changes after I restart my system for the setup to complete.
Edit: Yeah still broken
But if the point of our argument is that I am using pre-release Software then okay, we could still treat it as that as long as MS does not update their websites, fine by me. Doesn't change the fact that this will ship to many users next month.
I installed VirtualBox-6.0.5-129923-Win.exe now and will report back if anything changes after I restart my system for the setup to complete.
Edit: Yeah still broken
Last edited by socratis on 15. Apr 2019, 17:59, edited 2 times in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Uninstalling Windows Sandbox (https://techcommunity.microsoft.com/t5/ ... a-p/301849) got rid of the error, still not able to boot my old VM fully, working on providing more details.
Last edited by socratis on 16. Apr 2019, 08:45, edited 1 time in total.
Reason: Fixed obfuscated URLs.
Reason: Fixed obfuscated URLs.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Very interesting finding @Stanzilla! From the linked article:
Yet another thing to add to my "disable the following" list...Prerequisites for using the feature
- Windows 10 Pro or Enterprise Insider build 18305 or later
- AMD64 architecture
- Virtualization capabilities enabled in BIOS
- At least 4GB of RAM (8GB recommended)
- At least 1 GB of free disk space (SSD recommended)
- At least 2 CPU cores (4 cores with hyperthreading recommended)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Updated VirtualBox to 6.0.6 but still unable to boot. Logs attached. No idea why
- Attachments
-
- Windows 10-2019-04-17-00-24-58.log
- (74.29 KiB) Downloaded 149 times
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Build 1709 18362.53
Vbox 6.0.6 r130049 (Qt5.6.2)
Vbox 6.0.6 r130049 (Qt5.6.2)
Still NGCall to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Last edited by socratis on 17. Apr 2019, 22:19, edited 1 time in total.
Reason: Enclosed the information in [quote] tag for better readability
Reason: Enclosed the information in [quote] tag for better readability
-
- Posts: 1
- Joined: 17. Apr 2019, 23:43
Upgraded to VirtualBox V6.0.6 and my VM wont start any more
Hi,
I get this error after updating VirtualBox 6.0.6:
I get this error after updating VirtualBox 6.0.6:
This box was functional until the update.Failed to open a session for the virtual machine xxxx.
Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
- Attachments
-
- NZQA-VPN-2019-04-18-09-36-09.log
- Most recent log
- (31.6 KiB) Downloaded 109 times
Last edited by socratis on 18. Apr 2019, 03:02, edited 1 time in total.
Reason: Enclosed the information in [quote] tag for better readability
Reason: Enclosed the information in [quote] tag for better readability
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Which update? VirtualBox or the Windows pre-release?SchlauFuchs wrote:This box was functional until the update.
You're running a Windows pre-release, which is not supported until it becomes a release and the changelog/manual says "supported", that's why I merged your topic with the thread that deals/records suck reports.00:00:01.838067 OS Release: 10.0.18362
PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 1
- Joined: 12. Apr 2019, 15:59
Error when starting a VM (Failed to open session)
Dear all,
I'm running Windows 10 Enterprise 64 bits version 1903 (build 18362.53) and VirtualBox 6.0.6.
Before the last windows update, I could run a VM running Opensuse 64 bits without problems.
Now, as soon as start the CM, it shows an error
Nevertheless, it keeps not working. Can anyone help please?
I'm running Windows 10 Enterprise 64 bits version 1903 (build 18362.53) and VirtualBox 6.0.6.
Before the last windows update, I could run a VM running Opensuse 64 bits without problems.
Now, as soon as start the CM, it shows an error
I was looking in the Web and some people were saying that I should install Hyper-V and Hyper-V Platform. I have already done it and Intel VT is enabled.Failed to create session (Call to WHvSetup Partition VERR_NEM_VM_CREATE_FAILED Oxc000000d/87
Nevertheless, it keeps not working. Can anyone help please?
Last edited by socratis on 19. Apr 2019, 03:43, edited 1 time in total.
Reason: Enclosed the information in [quote] tag for better readability
Reason: Enclosed the information in [quote] tag for better readability
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
@Pedro Roseiro
I got to admit; I was really impressed that at your 1st post, you managed to find your way through the forums, and actually find the "VirtualBox on Windows Hosts" » "VirtualBox on Windows pre-releases" area!
But then you missed the related thread, one thread down from the area start!
I merged your post with the thread that you missed...
I got to admit; I was really impressed that at your 1st post, you managed to find your way through the forums, and actually find the "VirtualBox on Windows Hosts" » "VirtualBox on Windows pre-releases" area!
But then you missed the related thread, one thread down from the area start!
I merged your post with the thread that you missed...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
1903 ISOS are now on MSDN, might be time to move this thread
-
- Posts: 696
- Joined: 20. Nov 2013, 01:07
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Still not avail to public yet . .
This release strategy, this time around, sure is strange!
This release strategy, this time around, sure is strange!
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
The thread is going nowhere, until we all have our hands on the final, *and* there's a new version of VirtualBox that specifically and explicitly declares 1903 as supported.
And I don't mean a test or a development build...
And I don't mean a test or a development build...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 696
- Joined: 20. Nov 2013, 01:07
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
Well, we can continue to document the problem And devs can probably pretty easily reproduce it, if they tried, by getting Insider builds. Nothing stopping them from being proactive.
We testers will be ready to test a fix, for sure!
We testers will be ready to test a fix, for sure!
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
So what I don't quite understand is, do VirtualBox devs work/investigate this issue? Or are you guys waiting until the "final" version is out and only then start working on it? Because that would be pretty bad.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362 (#18536)
@Stanzilla,
Unless you hear from a poster that has an "Oracle Corp." on the right side of the post in their Profile, the rest can only be an educated guess... And since I've been "educating" myself for quite some time, I can "guesstimate" that there will be nothing official (as far as VirtualBox goes) until there's a final 1903. Doesn't make sense otherwise...
As far as knowing what the devs are doing? See https://www.virtualbox.org/timeline
As far as knowing what the devs are thinking?
Unless you hear from a poster that has an "Oracle Corp." on the right side of the post in their Profile, the rest can only be an educated guess... And since I've been "educating" myself for quite some time, I can "guesstimate" that there will be nothing official (as far as VirtualBox goes) until there's a final 1903. Doesn't make sense otherwise...
As far as knowing what the devs are doing? See https://www.virtualbox.org/timeline
As far as knowing what the devs are thinking?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.