VMware Workstation

 View Only

 Ubuntu - 'Moved' W10 VM now getting Error code 0x000000e upon bootup

Noe Gonzales's profile image
Noe Gonzales posted Nov 02, 2026 03:11 PM


PLEASE NOTE: The <Reply> button is missing on this thread for me even after viewing it on 3 different browsers on my Ubuntu OS (one of which had the internet cache cleared) AND on my W10 desktop. On other threads I can Reply but only to the person directly that originated the article and not to the community thread. If anybody could give a solution for that, that would be great. I'm not trying to ignore the responses but I can't respond. 

I also thought I attached the support bundle to this last edit but I"m not seeing at attached. Grrr.

=========================
I'm currently running VMware® Workstation Pro 26H1u1 (version 26.0.1.25688693) on Ubuntu 26.04.1 LTS. I have an HP Envy x360 laptop. My VM is from a Dell XPS 8700 desktop that was running W10. 

I WAS happily running VMware workstation Pro 25H2u1 (at a miniumum) on Ubuntu 24.04 - same hardware UNTIL I tried upgrading the OS. At which time upgrade went wonky and I ended up just wiping the drive and installing version 26.04.1. It was probably for the best as I'm sure it cleaned up installing patches upon patches, etcetera. Thankfully I had all of my data backup to a NAS so I just had to re-install software for the most part. 

I mistakenly thought that just copying down my VMWare folder with all of the files would be enough and that everything would just work automagically. Nope. I'm sure many of you reading this knows what came next . . . 

VMworkstation prompted me asking if the VM was Copied or Moved? I selected Moved. I don't know if there is a right answer looking back.

Now when I try to start my W10 VM I'm getting this error message:

Recovery - Your PC/Device needs to be reapaired, a required device isn't connected or can't be accessed, Error code: 0x0000000e

W10 vm boot up error


I've tried researching this but I'm finding somewhat similar circumstances that really don't match my configuration OR actually give a fix. I minimally understand that a new UUID and/or GUID was created (even though I'm using the same hardware BUT the OS and partitions identifiers changed entirely). 

So I'm hoping that somebody can guide me on how to fix this OR at least tell me if there is another way to MOVE a VM without having all of these problems?

I could recreate the VM as my desktop is still functioning but what happens if I have to upgrade/rebuild the OS again and this happens again? I may not have my original desktop to create another image from. 

I'm also wondering if I use a Windows Live Installation USB (as I have the Windows OEM License Key) and can get the VM to recognize that IF I can perhaps reinstall Windows. Although that still may not affect the VMX UUID/GUID at all. 

Any guidance/direction would be appreciated. Thx.

Gaurav Joshi's profile image
Broadcom Employee Gaurav Joshi

Can you please share the support bundle?  Specifically i need vmx logs for this particular Virtual Machine. I hope your other VMs are fine and powering on well. 

RaSystemlord's profile image
RaSystemlord

There is nothing wrong in your workflow, just the "I Moved It" is wrong.

There is a primarily thing and a secondary thing in this:

Foremost
When moving a VM between different system architectures, you need to say "I copied it". Then VM will update itself when starting and may ask for a reboot, too. (It was so ALWAYS, not sure if they have done something which works in some cases.) Anyway, what you see is what happens (I gather, not sure about your error messages, nevertheless it doesn't work how you did it.)

I just a couple of days ago copied a VM between different Intel architectures, from Win11 to Kubuntu, from 17.5.2 to 26H1u1 - there was no problem and this is how it always has been.

SECONDARY:

Windows GUI copying can fail without telling that it fails. Use a reliable way, like robocopy for copying. You need to redo your exercise, at least I don't know how to fix a VM after a wrong answer. I hope you have a backup or something.

TERTIARY:

If you have the VMware Workstation GUI open and in its TAB there is your VM, while copying, it is wrong, too. There are files open in your VM directory if you have that. OR if you even start the GUI while copying there are files changing in the VM directory, which is even worse.

RaSystemlord's profile image
RaSystemlord

Well, sorry, I mistakenly was talking about a Windows Host and you have Ubuntu. Anyway, the same principles apply. Although, in your case, it doesn't look like the copy itself is wrong .... although, you talk about NAS and thus network copying is always a suspect when done with GUI. I would use rsync or something, to make sure that the copy itself is fine.