The chance of something going wrong is very high when you have a parallel development in two different companies like microsoft and Kaspersky and both dealing with the same subject virtualization.
The Kaspersky programmer may be developing something in an environment that microsoft changed a few seconds ago and microsoft for its part is implementing changes that it may not think will disturb Kaspersky's work environment and when it comes to security both companies make continuous and quick implementations, so it is to be expected that things like this will happen at some point .
I believe that in the not-too-distant future, when activating Virtualization in Kaspersky, the program itself will automatically deactivate it in Windows and take every precaution to ensure that everything works correctly without the need for users to rack their brains, as this guarantees the best functioning and to the company less hassle with complaints.
It's all very complex and always done with a lot of speed and in several companies simultaneously, at one point the car skids on the curve.
