I had never thought much about this until the only account on my home PC somehow lost admin privileges (changing to guest - I suspect this is a Microsoft bug but will probably never know). So, eventually, I solved this problem by doing a safe boot, logging in with the never-before-used built-in "Administrator" account and its blank password, and then making my real account an administrator.

Since it seems that anybody can safe boot my computer (e.g., from the off state by booting and cutting the power three times in a row), I guess I need to change my Administrator password, right? If I don't change it, even if I encrypt my hard drive, this Administrator has access to all my files, right?

It seems Windows 10 should at least have told me something like "The built-in Administrator password is blank - Would you like to change it?" to give me a conscious decision when I first bought this computer, so I'm doubting myself...am I making some sort of mistake about how serious this is?


The default built-in admin account for home users has no password by default, but the account is also not enabled by default.

You can get to it if you have physical access to the machine, but if you have that, then you have access to everything. That's why full drive encryption is so important, because it prevents access to Windows, and therefore blocks access to the Admin account, too.

  • Ok, and maybe I'm wrong here, but I believe that Administrator could have changed my own password, so that full drive encryption does not protect me in this case. In other words, if someone had stolen my computer while the Administrator password was blank, they could have gotten all of my data even if I used full drive encryption, right? – bobuhito Aug 17 '18 at 9:44
  • How would they get past full drive encryption? Is that not a separate password or login process? – schroeder Aug 17 '18 at 10:49
  • I'm thinking the Windows password decrypts some bits in the TPM, to form the Bitlocker key, to decrypt the drive, so it really is not a separate password. I'm afraid to test this on my own system since it's already shaky, but it's possible. – bobuhito Aug 17 '18 at 11:32
  • Also, regarding your point that Administrator is "not enabled by default", in my case, all I did was a "shift-reset" to get it enabled. I was already logged in to do that "shift-reset" and the PC then said it was enabling safe boot. I guess you're saying a thief could not enable safe boot unless the screen was unlocked to begin with (or if I had done so in the past). I wish some authority from Microsoft could post an answer here. – bobuhito Aug 17 '18 at 12:23

Some of the biggest Information Security headaches come from not changing default passwords.

If your system was ever stumbled upon either online or in person you can be sure that anyone with a working knowledge would start hammering away with all the default passwords to see if they can get access.

Once the administrator account is compromised it is pretty much game over as the admin account has the rights to access pretty much anything on the system.

Even if your drive was encrypted, a patient attacker would install a keylogger or other surveillance tool using the compromised admin account to capture the information they want.

What I would consider to be best practice would be to...

  1. Create a new admin account (not called administrator, system, root etc.)
  2. Set a good password for the new admin account.
  3. Disable or lock the built in admin account.
  4. Create an "Everyday" account with non-admin rights.
  5. Set a good password for that non-admin account.

The non-admin account is for your day to day stuff and the admin account is only used when you want to make changes or install/remove software.

This has been recommended in various sysadmin publications since the 70's and still holds true today.

  • So, like I pointed out at the end of my question, why would Windows not even warn me about such an obvious risk? And, the password was even simpler, just blank. I feel like there's something more to this. – bobuhito Aug 17 '18 at 8:54
  • Good question. I am not privy to the inner workings of Windows Development so I would have no idea as to why not. – Ben Aug 18 '18 at 10:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.