KACE Product Support Question

K2000: Latitude E5430 stuck key?

09/05/2013 2304 views

I have a brand-new, just out of the box Latitude E5430. I set it up, boot it from the NIC, and connect to the KACE 2000. I hit the 64-bit Deployment and Recovery Environment and the box pops up for the password. So far, so good except asterisks start immediately appearing as if I were pressing a key or a key were stuck. Except I'm not and none are. I booted to Windows just to make sure and nope, no keys are stuck. I can go to the BIOS or a command prompt just fine, too. Only when I get to the KACE do I get the phantom characters. Any ideas because I'm totally stumped and I really don't want to configure this computer from scratch since it's one out of a batch of 300!

1 Comment   [ + ] Show comment


  • Have you tried another keyboard just for S&G?

All Answers


I'm not sure exactly what stage you are in setup, etc.  However, astericks are perfectly normal for a password field.

Lead L3 Enterprise Solutions Consultant, K2000
If my response was helpful, please rate it!

Answered 09/05/2013 by: cserrins
Red Belt

  • I'm not typing anything. Asterisks are appearing as if I were typing or as if a key was stuck. But I haven't typed the password yet and no keys are stuck. I can't type the correct password because the other characters (asterisks) are there.
    • so this is the password to start the KBE (after you have selected the one you want)?
      Have you tried hooking up an external keyboard (just to check)?
      In the K2 webui, go to Settings and Maintenance | General Settings. What is the Boot Manager Style and the Local Hard Disk Boot Method set to be?

      Lead L3 Enterprise Solutions Consultant, K2000
      If my response was helpful, please rate it!
  • Yes, this is the password to start the KBE. I tried attaching an external keyboard but I still got the phantom keystrokes in the password field. Boot manager style is Graphical Menu and Local Hard Disk Boot Method is Chain Boot (default). I've already deployed the image to 80 computers from this batch and everything works fine except this one.
  • I tried a different external keyboard and plugged it in before booting instead of afterwards. I managed to get the password in so it's imaging now.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ