Lisa - what are you doing ?
you really need a lesson in "safe use of snapshots"
same mistake again I believe - you used the basedisk alone
run the dsfi.cmd with the fix*.binfile again
it should work again
but you really need to understand that your actions will sooner or later destroy your VM
not kidding - serious warning
What I have done is unforgivable. I need to take a lesson in "safe use of snapshot" as you said. It did not work this time. When I switched to other snapshots, it created new 000014.vmdk files. Still had error not able to go. Thank you.
I re downloaded the dsfi.cmd and fix-parent from the case history and run dsfi.cmd again. It worked this time. Once again, sorry for the inconvenience and I appreciate so much for your help. I'm not touching it anymore.
Wish you all the best and God bless you!
Lisa - if you come again with the same error I will help again - but not before you listened to half an hour of my music.
Prepare yourself ...
I have the same issue... I have updated my kali and then it happened. I even tried to use a snapshot from 2016 but I get the same error
Can you please assist me? I have attached the rar with all the bins
That doesn't seem to be "the same issue". In your case it looks like the base disk has been resized/expanded without first deleting/consolidating the snapshots.
Please explain what exactly you did so far (e.g. how you did resize the virtual disk, whether you already changed the guest partitions, ...).
Do you have a recent backup?
Additional note: Please open a new discussion, rather than replying to old discussions. This way you will get more attention.
Updated Kali ($ sudo apt update and $ sudo apt upgrade). Maybe the host froze during that time? I can't remember.
I tried go back to a snapshot capured in 2016 but I get the same error (now with another file)
No backup as the content isn't important excpet 1-2 scripts I can re-create.