HWinfo64 svm detection

wawans1975

Well-Known Member
Hi Martin,

HWinfo64 detects my CPU as no svm function, although i have enabled SVM at BIOS. Is this HWinfo64 bug?
Windows Sandbox tested running btw.
Thanks.

Edit: CPU-Z has not detected AMD-V either  :huh:
 

Attachments

  • Annotation 2019-04-06 191710.jpg
    Annotation 2019-04-06 191710.jpg
    226.5 KB · Views: 11
  • cpu-2901.jpg
    cpu-2901.jpg
    69.7 KB · Views: 13
I don't think this is a bug in HWiNFO, it should be showing this properly and I verified it many times.
 
Martin said:
I don't think this is a bug in HWiNFO, it should be showing this properly and I verified it many times.

my other machine (using r7 1700, b450 i gbyte, latest BIOS) not showing svm either.. probably windows prevent your software then?
 
Martin said:
Can you verify with some other tools?

currently im runing older machine (kaveri, bios not updated,  just windows), samething svm not listed, but i can creat virtual machine using hyper-v manager from windows, installling windows on vm now..
 

Attachments

  • Screenshot (342).png
    Screenshot (342).png
    319.8 KB · Views: 9
Can you check detailed features in the main window, especially "Secure Virtual Machine" ?
 
Martin said:
Can you check detailed features in the main window, especially "Secure Virtual Machine" ?

only these from my kaveri desktop's Settings app> Update & Security Page > Windows Security Page:
 

Attachments

  • Screenshot (344).png
    Screenshot (344).png
    424.4 KB · Views: 7
  • Screenshot (343).png
    Screenshot (343).png
    429.2 KB · Views: 6
  • Screenshot (346).png
    Screenshot (346).png
    315.1 KB · Views: 7
  • Screenshot (345).png
    Screenshot (345).png
    364.6 KB · Views: 7
Hi Martin, 
I just turned off SVM at BIOS,  AMD-V appeared then  and 'Secure virtual machine' present  :huh:
 

Attachments

  • securevirtualmachine.jpg
    securevirtualmachine.jpg
    108.7 KB · Views: 6
  • svmdisabled.jpg
    svmdisabled.jpg
    344.7 KB · Views: 5
AMD-V in read means the feature is supported but disabled at BIOS level.
That's strange and looks like BIOS would be doing things upside down - with SVM enabled the system reports it's not supported.
 
Anti-virus software can "block" the virtualization features of modern processors, meaning that they use it for themselves so other software can't use it. Avast is known to do something like this (had a case with their Free Antivirus and VMware/VirtualBox some time ago). I can imagine that the OS can do something similar which prevents applications to use, or even see, virtualization.

Regards
Dalai
 
Back
Top