This computer appears to be a virtual machine.

[BodoOTH]

Describe the Bug
When running an SEB configuration that previously worked without any issues, the following error message now appears on some computers:

“This computer appears to be a virtual machine. The selected configuration does not allow SEB to run in a virtual machine.”

We have already tried removing all programs that could potentially cause this behavior, but unfortunately without success. According to the log files, the issue seems to be related to Hyper-V; however, we have already disabled it as well.

Does anyone here have experience with how to further analyze this error message or narrow down the root cause more precisely?

As a workaround, we have temporarily enabled the VM option in our SEB configuration so that we can continue operations. In the long term, however, we would like to disable this option again and resolve the actual root cause of the issue.

LogFile:
2026-05-07_18h09m24s_Runtime.log

Version Information

• OS: WINDOWS 11 Education & Enterprise
• SEB-Version Build 3.10.1.864

[gitterdude]

The log file says "Computer appears to be a virtual machine (Hyper-V artifact (not an actual VM)" and the Google AI says "Hyper-V artifact" indicating a virtual machine (VM) means the system detected evidence of Microsoft’s virtualization technology. This is commonly caused by enabled Windows features like Core Isolation/Memory Integrity, Windows Subsystem for Linux (WSL), or Docker
Do you have any of those enabled/installed?

[dbuechel]

Please try the latest release version 3.10.2 and verify whether the issue still occurs.