The WMI object contained an invalid value in property BIOSNumLock

Posted March 11, 2010
Filed under: Uncategorized |

Not an error I’ve come across before, but trying to start up a Configuration Manager VM I’ve not used in a while, Hyper-V Manager stated “The WMI object contained an invalid value in property BIOSNumLock” and that the machine was in in “saved-state-critical”.

Opening up the properties of the machine and selecting then deselecting the Num Lock option in the BIOS configuration made this go away.

Very odd.

Like this:

Be the first to like this post.

1 comment so far

Bobby on March 11, 2010

This sounds like a problem with your pRAM.
I always find that tweaking your pRAM will fix the problem.

Reply

Leave a Reply Cancel reply

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Not published)

Name (required)

Website

You are commenting using your Twitter account. ( Log Out / Change )

You are commenting using your Facebook account. ( Log Out / Change )

Cancel

Connecting to %s

John Quirk's Blog