Changes between Initial Version and Version 1 of Ticket #15831, comment 18

Ticket #15831, comment 18

initial	v1
2	2	> Fix is part of VBox 5.1.8. Please open separate tickets for unrelated issues.
3	3
4		Workaround for V5.1.4, Windows hosts: (not 100% sure but looks optimistic after a couple of tries) - whatever you do, wait that access of VBoxSVC.exe stops accessing your .vmdk files! So i.e. if you delete a snapshot, wait for these accesses to dissapear from the list in Resource Monitor before doing other actions that might have an impact or be impacted by them snapshots.[[Image(ResourceMonitor)]]
	4	Workaround for V5.1.4, Windows hosts: (not 100% sure but looks optimistic after a couple of tries) - whatever you do, wait that access of VBoxSVC.exe stops accessing your .vmdk files! So i.e. if you delete a snapshot, wait for these accesses to dissapear from the list in Resource Monitor before doing other actions that might have an impact or be impacted by them snapshots.[[Image(ResourceMonitor)]]. After you delete the snapshot and do the prescribed waiting, close and open the VBox Manager. You will still see the state of "deleting snapshot". Redo the procedure - delete the snapshot again. It should be fine now.