New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error : "This computer appears to be a virtual machine" #604
Comments
Could you please specify what computers you are using? And please also post the log files of the affected SEB session(s), they can be found under |
We are using Dell Latitude 3420 |
Thanks for the information. This could indeed be a false positive, which would be most unfortunate. Are you using any virtualization solutions resp. are there any installed on your systems (e.g. VMware, VirtualBox, Hyper-V etc.)? |
No we aren't using any of virtualization solutions on our computers. |
Could you please execute the following line in the command prompt of Windows and post the results here:
|
Here you go.
|
Thanks a lot, we will analyze the output and report back our findings. |
I had the same issue and was able to get past incorrect detection by removing the device named "Microsoft Virtual Disk" device in device manager. After the exam was over I had the students press the "Scan for hardware changes" button to make the device reappear in device manager. |
Thanks a lot for the input @Tim455. That is indeed a false positive then, as we assume that to be part of a Hyper-V machine, see https://github.com/SafeExamBrowser/seb-win-refactoring/blob/master/SafeExamBrowser.SystemComponents/VirtualMachineDetector.cs#L20. We'll definitely need to fix that for the next release version. |
The issue should be fixed and can be tested in the latest beta version of SEB 3.6.0: https://sebdev-let.ethz.ch/api/buildjobs/ah1rr6cvqsd5yhaa/artifacts/SEB_3.6.0.558_SetupBundle.exe. |
The beta version seems to work! |
Hi,
When starting SEB from Bookwidgets we get the error "This computer appears to be a virtual machine"
The issue is since the latest upgrade to 3.5.0.
we have several computers that hasn't upgraded yet. (which run on the 3.4.1) these work fine.
The text was updated successfully, but these errors were encountered: