Since y few weeks, parallels 13 reading periodically several 10 GB and my virtual windows 10 (version 1709) get stuck. During the reading even the osx (newest one) stopps periodically for seconds. After reading XX GB by parallels everything works normal. What service or configuration is responsible? It it the same behaviour with parallels 12. Thanks in Advance
The solution is to deactivate the "activate trim" function of the virtual hard disk. I don't know, why this function suddenly causes these problems. Without trim functionality everything works normal. After reactivate the "activate trim", parallels starts immediately after starting the virtual W10 reading over the last 30 Minutes more than 60 Gigabytes and more and the Mac and the W10 ist nearly not usable.
The reason for these problems was an interrupted optimisation run to free unused blocks of the virtual disk by parallels.
