VMware Communities
hobbes444
Contributor
Contributor
Jump to solution

Failed to open the file vmem

My Windows 10 x64 VM currently cannot resume. When I try to resume, it tells me:

Failed to open the file "/path/to/my/Windows_7_x64-3e5f9400.vmem": could not find the file.

My VM was previously a Windows 7 (and called the same), thus the name of the vmem file I assume (hadn't noticed so far). The name of the VM is now Windows_10_x64 and I have changed the OS type in the settings.

When I suspend the VM, I can see inside the package that Windows_7_x64-3e5f9400.vmem is being created. But at the very end of the suspension, the file suddenly disappears. Only the .vmss file is left.

Seeing all other issues related to Apple's new way of handling files over 2GB, I did change my RAM to 2GB, but it didn't resolve this issue.

Any idea what I should try to fix it?

1 Solution

Accepted Solutions
peter_w2019
Enthusiast
Enthusiast
Jump to solution

hi there

I had the same problem and apparently I resolved it (for now at least) by removing the two settings I experimented with:

mainmem.backing = "swap"

mainmem.useNamedFile = "FALSE"

if you don't have these settings in your .vmx file I am not sure what did resolve it. hope this helps.

cheers,

p

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

3 Replies
hobbes444
Contributor
Contributor
Jump to solution

Forgot to say:

  • I am running VMware Fusion Professional 11.1.1
  • I have another Windows 10 64bit VM which does not have this issue.
0 Kudos
peter_w2019
Enthusiast
Enthusiast
Jump to solution

hi there

I had the same problem and apparently I resolved it (for now at least) by removing the two settings I experimented with:

mainmem.backing = "swap"

mainmem.useNamedFile = "FALSE"

if you don't have these settings in your .vmx file I am not sure what did resolve it. hope this helps.

cheers,

p

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

hobbes444
Contributor
Contributor
Jump to solution

Amazing. Fixed.

I only had:

mainmem.backing = "swap"

I removed it, problem solved. Thanks a lot @peter_w2019!

PS: for some weird reason I can't mention you, your handle is not listed.

0 Kudos