After "Preparing for Transfer": Compressed .pvmp File for Win11 VM: Configuration File is invalid

R

RobertP69

Bit poster
Dear Parallels Team,

Today, I received my new MacBook (M4 Pro) and attempted to transfer my Windows 11 Parallels VM from my old MacBook (M1) to the new MacBook host (M4 Pro).

To do this, I used the Parallels function "Prepare for Transfer", which compresses the VM, including the virtual HDD and config file (resulting in a .pvmp file).

However, on the new machine, I receive the following error message: "Invalid / corrupt Config File (pvs)." (see screenshot in German)

I then tried to start the virtual Windows 11 machine again on my old computer to manually copy the data, but I am now prompted for a password. It seems to be a centrally set admin password: My company's IT department was able to enter it remotely to unlock it, but I still receive the same error message.

Could you assist me with the "corrupt configuration/pvs file" error after the .pvmp compression?
As I did not expect having these kind of troubles of accessing my VM again, I would appreciate a quick and working solution to revert this compression process and have at least a working HDD again.

upload_2025-3-12_12-34-59.png

PS: Since this is a Business Edition license, I am unable to create direct support tickets through my personal Parallels account. Please advise on the best course of action in this case.

Thank you and best regards,
Robert
 
I have transferred my VM in the past from one machine to another without going through the compression step, and assuming that both machines are either side-by-side, or you have an SDD disc larger than the VM size (usually <100Gb). If you have this situation, try moving the VM over directly.
 
Hi SamS4,
well that is exactly my problem:
The "PREPARE FOR TRANSFER" was placed VERY compelling, so I just clicked without spending a second thought on it.
Parallels then compressed the VM without further notice and especially without making any kind of backup (my Apple time machine was only available for the last two hours, so when I realized the problem, the original uncompressed VM files were gone already).

This means: I do not have accessed to the uncompressed version of my current VM any more.
And if I knew before that this "PREPARE FOR TRANSFER" process by Parallels is this buggy and unreliable up to the point of full loss of data, I would never have clicked it and just gone through the standard "copy-paste" process you just suggested. However, due to the situation (see above), this is not an option any more.

In fact, the only option I see is someone from Parallels undoing the compression step with their tools and thereby recovering the original uncompressed VM - but from user-side, I did not see any other options for this.

I hope this helps for further clarification!
 
@SamS4 I do backups, however the Apple time machine time frame for recovery of the previous VM files was a few minutes beyond the compressed version when I realized the issue with the corrupted configuration file -
And from the entire machine, I only have a backup from September 2024 - which is better than nothing but still not very satisfying.

Meaning: As I did not expect this very prominently placed option to go that wrong, and thinking that there is still Apple time machine, there were a few (unfortunate) circumstances leaving me without a recent backup
 
Robert - I know how you feel, and I know this should just work. Given the circumstances, though, I suggest you try installing the September backup and see how that goes. There have been a few updates to the Windows 11 OS and to Parallels since September, but unless you're interested in setting up a new VM, I would give this a shot.
 
You must log in or register to reply here.
Back
Top