How can I get rid of the login requirement when booting into Win 10. It is bad enough that it DEMANDS a login on a home personal PC (If someone is in my house then I have been broken into), BUT MS goes farther and insists it has to be a passwork of a certain strength containing this many characters and so many upper and numeric - there has to be a way to defeat this. I tried leaving the field blank and it will have nothing to do with that.
Logon and Authentincation Technologies are immensely complex. To automate Windows logon in the era of side-by-side x86 and 64 bit technology, you need a 'quiet' Microsoft insider logon tool.
Mirosoft provides system administrator accounts with
control userpasswords2... Vista up to 10, Netplwiz is the critical actor. But there are two (2) Netplwiz sessions that must fire simultaneously during
winlogon.
System32 Netplwiz and
SysWOW64 Netplwiz are syskey tamper-resistant - running both separate is discouraged.
Please take note. The way to use control userpasswords2 is to open it using Windows Run. Uncheck "Users must enter a user name and password to use this computer." Unchecking this box should open another dialog where you enter your Windows logon user password twice, once for System32 and once for SysWOW64. Workstation users must enter same password in both password fields.
Since Vista, each new Windows version makes adjsutments that temporarily render 'quiet' advanced logons somewhat unreliable. Today, just got a notice from Windows 10 Upgrade Team:
"Your PC is setup to log in automatically. After upgrade, you may have issues logging in."
They also told me, "It's going to take months to get your 8 core monster situated." Lol. I could be one of those slotted for upgrade to 10 in March 2016.
"easily"
.
Networks are economic and security hubs, and the humble desktop stand-alone 'workstation' naturally has to wait a little longer. For example, Windows 8 logon was mostly sorted out March 27, 2013 (4 days shy of five months from release). During the
control downtime, manual edits for the two critical actors worked fine. Then as syskey was adjusted to remove Netplwiz temporal runtime variance allowance across the two system directories, active functional userpasswords2 user was enabled with a working
control feature. It may be something like that with Windows 10. You will have to consult with Tier 3 (Research and Development) engineers at Microsoft, to get a current fix on
whatever-whenever is being instituted for current Windows release... Windows logon automation is Region and location dependent.
Not to discourage anyone, but the new
Intel RealSense face recognition on a few new devices may slow down workstation keyboard logon automation updates for the Windows 10 Upgrade. Because the initial corporate staff panic is over, and facial recognition is moving in,
even on mobiles. Heck, even works in total darkness! You can get your 'today' at a
local retail Microsoft Store. Just saying, Microsoft's automated keyboard logon in its various incarnations is not going away anytime soon.