Secureable - Virtualization question

It's a tool from GRC I'm sure many are familiar with... I mentioned it in here not long ago. Here is a screeny of my CPU I got with this Dell Inspiron 530 I recently got. When I tested it at a friends house I'm sure it just said "Yes" for the virtualization part. But now it says "Locked On". I can't think of what I could have done to do that. I didn't change any settings in the bios. I did password protect the bios settings though. And I'm running VirtualBox now. Could either of those 2 things have done it?

Here's the screeny:

 

Kinda surprised there's no responses to this. Hasn't anyone else ever seen their virtualization status as "Locked On"?... or just the "Yes" like normal?

Again, the only thing I can think that would've done it is adding a Bios password. Just looking for some reassurance here...

My new/old box/VM is up & running GREAT! I didn't think XP could possibly get any faster than it was on my old box, but it is indeed, here on this one even with .NET FW 2.0 SP2 & EMET 3.0.

 

I think this is related to the BIOS password.

Remove the BIOS password and see what happens!

 

Hey now... that's just too logical a solution ; )

I was looking for a long winded explanation confirming my theory instead.

 

That experience can confirm your theory as well. Did you try it? What were the results? I'm curious now, lol.

 

Sorry... it was a long time ago you posted this, but I just now noticed it.

I removed my Bios PW, but it still showed up as "Locked On". If I disable hardware virtualization altogether in the Bios then it simply shows as "Off". So not sure how to get it to simply show as "On". It's either locked or off altogether.

Not sure why. Maybe one of the thousand or so hardening tweaks I've made is responsible? I'm hardly ready to undo each one, one by one, and check if it's changed. That would be a monumental undertaking.

 

You could try a fresh install just to test. Or maybe run it in BartPE/WinPE.