Windows 10: Issue with creating a picture password

I am not able to create a picture password. It does not recognize my verification passwordI tried with my Microsoft account password and Windows Hello password.

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Windows 10 picture password not appearing on sign in screen

Thanks for following up. This seems to be a rather odd issue, but nevertheless, we shall investigate further on this so we can provide a proper troubleshooting step. First, can you walk us through on the steps you did to set up the picture password? Also,
give us the current build version of your operating system so we can check.

Another step that you can try is to create a new (test) user account, and set up the picture password from there. We are suggesting this step to check if this is a case of a corrupted user profile.

All the best.

 

Quick Access not searching Pictures folder

Summary, that last suggestion didn't work.

• I moved the pictures to another folder temporarily.

• Then I tried to remove the Pictures folder with option one at Add or Remove Folders from This PC in Windows 10 | Windows 10 Tutorials. Even after rebooting, the Pictures folder remained.
• So I tried using option two. Same thing: reboot >> Pictures folder still there.

• Since there were no troubleshooting steps for this scenario, just for the heck of it, I ran through the restore steps. Copied some pictures into the Pictures folder, ran a Quick Access search and initial problem remains: Searching all of QA doesn't find any files in Pictures folder, running search on just the Pictures folder does. I want to run a global search and find matching files in any/all of the Documents, Music, Videos, and Pictures folders.

That article dates from 2015 and I'm guessing is out of date. I hope it didn't create potential future problems in my registry.

Bottom line: I'm still looking for a fix.