Forum Discussion
An unexpected error occurred (file '', line , function '')
Hi,
After installing on several devices and noticing that some returned errors while others didn’t, I compared the system information of each one and found that the issue, in this case, is related to AVX CPU extension support. One of the VMs didn’t inherit this extension from the host, and once it was enabled, the error disappeared.
We can conclude that the error is related to CPUs lacking the AVX extension.
Best Regards.
Hi Nuno_Santos ,
Thank you for keeping us updated on the issue and confirming that it’s still unresolved. Once you hear back from the support team, please do share the response here, it will be helpful for others who may encounter a similar issue.
Thank you.
Hi,
After installing on several devices and noticing that some returned errors while others didn’t, I compared the system information of each one and found that the issue, in this case, is related to AVX CPU extension support. One of the VMs didn’t inherit this extension from the host, and once it was enabled, the error disappeared.
We can conclude that the error is related to CPUs lacking the AVX extension.
Best Regards.
Hi Nuno_Santos ,
Thank you for the update — glad to hear the issue has been resolved!
Please consider accepting your answer as the solution so others facing a similar issue can easily find it.
Regards,
Pallavi.Nuno_Santos answer is not the resolution , it might be spotting what is the problem.
What am I supposed to do if I'm using Mac and my CPU doesn't support AVX ?
AnonymousHi Anonymous ,
Thanks for sharing your experience. As mentioned earlier, I had suggested raising a support ticket for this issue.Nuno_Santos ,could you please update us on the response you received from the Microsoft Support team? That insight might help others facing similar issues, especially since some users are still encountering the error despite enabling AVX.
Appreciate your help in keeping the community informed!
Thank you.
this was the issue at our end the VM Machine , cpu was selected as core 2 duo...
which does not support avx extension....
when updated to when updated to xeon gold 6226R..
the visual started to showing again..We have had the same issue. Enabling the AVX CPU extension support resolved it.
Thanks Nuno_Santos for finding and reporting this.I just hit this issue today, and the solution noted for this post allowed my Network Admin to zero in on the solution. To paraphrase, "Skylake (L8), supported by all 6 hosts, has AVX 512". He had to upgrade the VM cluster AVX, then set a flag so that when individual VMs are rebooted they pick up the new setting. I did the reboot on my full PBIRS TEST installation, and it immediately fixed the issue in multiple reports with no other changes needed.
