How do I use a custom log in screen at boot up with anniversary build

I have been researching this my self and only getting more and more confused, basically all I would like to do is turn of the lock screen and use a custom image when I log in at boot up (I have it working when I log out but not at boot) it was working flawless prior to the 1607 anniversary update.

I was hoping someone could tell me how to do this

dalchina said:

Hi, Winaero's Tweaker (free) has an option to trick Windows so the lock screen is disabled, with full explanation of how it works.

I have managed to disable the lock screen but my login is a solid color, at boot. I wanted it to be a custom picture. Will this tweaker allow me to do that?

dalchina said:

Hi,, I assume you mean the login screen background, rather than anything appearing after booting the PC.

Try
Sign-in Screen Background Image - Change in Windows 10 - Windows 10 Forums
and for completeness
Sign-in Screen Background Image - Enable or Disable in Windows 10 - Windows 10 Forums

Do have a look at the extensive Tutorial section.
Hope that helps.

Well see this is where I am getting confused. The lock screen is gone but my login screen when I first boot my pc is just a solid color. I would like that to be a picture.

Both of the programs in the tutorial won't work with the anniversary build of win 10

When I first start my computer it goes right to the login page, which is what I wanted.

I haven't been able to set a picture with out turning back on the lock screen (the one that appears which you need to click on in order to get to the log in page)

How ever said login has a solid color background. Not a custom picture like it did before the anniversary update. I am trying to get a picture back there.

dalchina said:

If I change the setting in the screenshot I showed above to off, my login screen becomes solid blue instead of a picture.

It used to be the case that the picture would change automatically. At some point that stopped.

I have that turned on already, could it be that it's because the lock screen is disabled? What build are you running?