We have several Win7 Pro machines with XP Mode. The Win7 machines were rolled out with the latest updates installed a few months ago. So far, so good. However, after installing all critical updates for Win7 this week, all of the XP Mode VMs are taking
up to tens of minutes to start, only to fail with an AppCrash from vmsal.exe.
I have triple checked all settings, defragged, chkdsk /R, sfc /scannow, etc. All the usual "make sure it's not something really basic" tests pass.
Googled around, found barely a full page of hits for vmsal.exe. Can't find any info about this issue.
Users do not have roaming profiles; this is not an issue with stuff being loaded over the network.
I can sometimes boot into the full VM if I disable integration features. However, if integration features are enabled, the VM will take easily 10+ minutes to come up, if at all. Using the full seamless integration features is impossible, and always results in a vmsal.exe AppCrash.
About to just toss it all and go with another virtualization solution for legacy XP software, but want to give it one last shot.
I have triple checked all settings, defragged, chkdsk /R, sfc /scannow, etc. All the usual "make sure it's not something really basic" tests pass.
Googled around, found barely a full page of hits for vmsal.exe. Can't find any info about this issue.
Users do not have roaming profiles; this is not an issue with stuff being loaded over the network.
I can sometimes boot into the full VM if I disable integration features. However, if integration features are enabled, the VM will take easily 10+ minutes to come up, if at all. Using the full seamless integration features is impossible, and always results in a vmsal.exe AppCrash.
About to just toss it all and go with another virtualization solution for legacy XP software, but want to give it one last shot.