Why a virtual machine reports unusual device information
Learn why a virtual machine can show unexpected processor, graphics, screen, or network details, and how to tell guest settings from a hardware problem.
Your virtual machine may show a processor name you do not recognize, a basic graphics adapter, or screen and network details that do not match the computer running it. That can look like a hardware fault, but a virtual machine presents a simulated set of devices to its guest operating system and browser.
Use the System Info tool inside the virtual machine to see what the browser can detect. Then compare the results with the host computer and check which details you can change in the virtual machine settings.
Check the information from inside and outside the virtual machine
- Open System Info in the virtual machine. Note the processor, graphics, screen, battery, and network details that appear.
- Open the same tool in a browser on the host computer, if you can. Compare the results, but remember that the browser may expose different details in each environment.
- Check the guest operating system's own settings. Compare its processor, display, and network information with what System Info shows.
- Look at the virtual machine's configuration in your virtualization app. Check the assigned processor cores, memory, display options, and network mode. The names and locations of these settings depend on the app.
- Write down the guest operating system, virtualization app, and the details that seem wrong. This makes it easier to spot which value changes after you adjust a setting.
Do not expect the guest to report every physical part of the host computer. A virtual machine can expose a virtual device, a simplified device name, or only the resources assigned to that guest.
What the results mean
The processor name or core count looks different
The virtual machine may identify its processor as a generic or virtual model, even when the host has a familiar CPU name. It can also show fewer available cores than the host because the VM is assigned only some of them. The browser may report the logical processors available to the guest, not the full processor configuration of the host.
If the guest reports fewer cores than you expect, check the VM's processor allocation. A browser result is not a complete hardware inventory. For more on why a browser may see fewer processors, see why browsers report fewer logical CPUs in a container.
The graphics adapter is generic or performance seems low
A virtual graphics adapter is not necessarily the host's physical graphics card. The VM app may provide a basic display adapter, a virtual GPU, or limited access to graphics acceleration. Some apps show a generic name even when graphics acceleration is enabled.
System Info can describe browser-visible graphics details, but it cannot prove that the host graphics card is defective. Compare performance with the same browser task on the host before treating a generic name as a fault.
The screen size or scale does not match the host
The guest sees its virtual display, which can have a different resolution and scale from the physical monitor. A guest window may also change size when you resize the VM window or switch to full screen.
Check the guest's display settings and the virtual display options in the VM app. A mismatch in resolution or scaling usually points to display configuration, not a damaged monitor.
Battery details are missing
Many desktop virtual machines do not expose a battery to the guest, so battery information may be absent even when the host is a laptop. Battery Meter appears only when the browser reports battery data. Its absence inside a VM does not mean the host battery has failed.
The network name or connection details seem unusual
A VM often connects through a virtual network adapter. Depending on the network mode, the guest may appear to share the host's connection, or it may have a separate address on the local network. The adapter name in the guest may not match the host's Wi-Fi or Ethernet device.
Memory information is rounded or incomplete
Browsers provide only a rounded hint about memory, not a precise report of installed RAM. In a virtual machine, the guest also has an assigned memory limit that can be smaller than the host's total. For context, see why a virtual machine reports unusual memory results.
How to fix misleading or unexpected details
- Check which computer you are inspecting. Make sure the tool is open in the guest browser if you want guest details, or on the host if you want host details. A browser page inside a VM cannot directly list every physical host component.
- Review the virtual machine's assigned resources. Check its processor cores and memory allocation in the virtualization app. If the guest is limited to fewer cores than expected, adjust the allocation only if the host has enough resources to spare.
- Check the guest's display settings. In Windows 11, open Settings › System › Display. On macOS, open System Settings › Displays. Set a suitable resolution, then check the VM app's display or graphics settings as well.
- Check the guest's system details. In Windows 11, open Settings › System › About to see the processor and installed memory reported to Windows. On macOS, open System Settings › General › About. Compare those values with the VM configuration, not only with the host's specifications.
- Review network settings in the guest. In Windows 11, open Settings › Network & internet › Advanced network settings. On macOS, open System Settings › Network. If the guest cannot connect, check the virtual network mode and adapter in the VM app too.
- Install or update the VM's guest tools. Virtualization apps often provide guest additions or integration tools for display resizing, graphics support, and device communication. Use the package intended for your VM app and guest operating system.
- Restart the guest after changing its configuration. A shutdown and restart can make new processor, memory, display, or adapter settings visible. Reopen System Info and compare the results again.
Why the guest does not see the host directly
A virtual machine runs an operating system inside software that imitates parts of a computer. The host is the real computer, and the guest is the operating system running in the virtual machine. The virtualization app decides which devices and resources to present to the guest. That separation helps run multiple systems, but it also means device names and counts can differ.
Browser-based checks have another limit: they can report only information made available by the browser and operating system. Privacy settings, browser restrictions, and the virtualization layer can all reduce or change the details. A different value is not, by itself, evidence that a physical component is broken.
If the same unexpected behavior appears in the host operating system and in the guest, check the host settings or device next. If it appears only inside the VM, start with its resource allocation and guest tools.
