Changes between Version 1 and Version 2 of Ticket #20627, comment 6

Ticket #20627, comment 6

v1	v2
1	1	I know that disabling this feature is a workaround. Unfortunately we cannot disable this feature because it is enabled by our administrators.
2	2
3		And I really don't understand why ~~3.1.26 doesn't have this problem while in 3.1.28 and 3~~.1.30 the error occurs; without any changes by Microsoft!
	3	And I really don't understand why 6.1.26 doesn't have this problem while in 6.1.28 and 6.1.30 the error occurs; without any changes by Microsoft!
4	4
5	5	Anyway: I really don't want to change to Hyper-V, but if the problem persist in VirtualBox I got no other possibility...