VMhide killed my vm?

[kstartups]

I simply changed the SN etc in config and also added VMHide. Since then, my vm won't start and it's stuck like this

I'm really really upset because it took many tries to get it to work. I don't know how i messed it up. any ideas?

 

[Edhawk]

Did you create a backup before making these changes?

Can't you simply change the SN back and remove VMHide from your setup?

 

[kstartups]

Did you create a backup before making these changes?

Can't you simply change the SN back and remove VMHide from your setup?

Like backup the VMware itself? No I did not do that. Also, apparently VMHide isn't for Windows or VMware at all, according to the dev. Don't know how I missed reading that line. That's probably why it all got screwed up. I guess I'll start over.

 

[kstartups]

Did you create a backup before making these changes?

Can't you simply change the SN back and remove VMHide from your setup?

How do I backup?

 

[chanmina]

such as backing up the VMware itself? No, that is not what I did. Additionally, the developer claims that VMHide isn't compatible with either Windows or VMware. I'm not sure why I didn't read that line. That's most likely why everything went wrong. I suppose I'll begin anew.
io games

 

[Anthona]

Did you create a backup before making these changes?

​

Can't you simply change the SN back and remove VMHide from your setup?

drive mad​

To back up your VM in the future, you can simply copy the entire VM folder to another location before making any changes.

 

[jack ma]

To back up your VM in the future, you can simply copy the entire VM folder to another location before making any changes.
veckio

That’s usually what happens when a .vmx / config line is invalid or duplicated (VMware) or when a hiding option toggles something that your VM/guest can’t boot with. The fastest recovery path is to undo only the risky edits, then re-apply changes one at a time.