Sign In

Why do I have to log in into my single user Windows 10 desktop? And before I can sign in, I also have to click on an ugly lock screen image, which for some reason displays unasked for advertisement. Why do I have to sign in each time I close laptop lid or after screen goes dark?

Learn to change settings.
Also that's what you get for not using OSX or *BSD.

I had a 7 and edited it so hard it is now accusing me of piracy.

>>2

There is no way to disable login screen in Windows 10, other than patching the machine code.

I kind of like the login screen, it displays an interesting picture at random and then I learn more about it. At least it's not as bad and cringey as the ads were in Windows 98 SE.

>>4
Try googling instead.

>>6

I googled. There is absolutely no way to disable lock-screen.

>>7

There is one way using gpedit, but it is available only in enterprise versions.

>>8

after latest auto-updates, gpedit doesn't work either: "With Windows 10’s Anniversary Update, Microsoft no longer lets you disable the lock screen using a group policy setting or registry hack."

>>9

"The group policy setting that disables the lock screen is still available, but it only works on Enterprise and Education editions of Windows. Even Windows 10 Professional users can’t use it."

>>6

Currently, the only way to get rid of lock-screen is to patch Microsoft.LockApp

>>11

And even if you hexedit lockapp, this still leaves that separate Sign In screen.

https://www.ghacks.net/2016/08/05/disable-windows-10-lock-screen/
Hi guys,

I found a much better way of solving this problem. I decompiled the file that was causing the key to be set back on and successfully disabled it. The culprit is in C:\windows\system32\LogonController.dll

You will need to get a hex editor to do this. This is for the 64-bit version, 10.0.14393.0, with md5sum of 3a12a4ce74b958564c0e4346869fcd8c.

This address location jump to file location 0x156EE, It should look like this:
75 4A 48 8B 8C 24 etc
Change the 75 to 74 (jump not zero to jump zero), save it and replace the LogonController.dll in your system folder.

You'll have to take ownership and then rename the file, and drop the new one in its place. Reboot and voila!

Some details of what is going on:
.text:0000000180016270 ; __int32 __fastcall CProcessStateManager::put_IsLockScreenAllowed(CProcessStateManager *__hidden this, unsigned __int8)
.text:0000000180016270 ?put_IsLockScreenAllowed@CProcessStateManager@@UEAAJE@Z proc near

text:00000001800162E4 call cs:__imp_RegCreateKeyExW
.text:00000001800162EA mov ebx, eax
.text:00000001800162EC test eax, eax
This line below is what we're patching:
.text:00000001800162EE jnz short loc_18001633A
.text:00000001800162F0 mov rcx, [rsp+78h+hKey] ; hKey
.text:00000001800162F8 lea rax, [rsp+78h+Data]
.text:0000000180016300 mov [rsp+78h+samDesired], 4 ; cbData
.text:0000000180016308 lea r9d, [rsi+3] ; dwType
.text:000000018001630C xor r8d, r8d ; Reserved
.text:000000018001630F mov qword ptr [rsp+78h+dwOptions], rax ; __int32
.text:0000000180016314 lea rdx, aAllowlockscree ; "AllowLockScreen"
.text:000000018001631B call cs:__imp_RegSetValueExW
.text:0000000180016321 mov rcx, [rsp+78h+hKey] ; hKey
.text:0000000180016329 mov ebx, eax
.text:000000018001632B cmp rcx, 0FFFFFFFF80000002h
.text:0000000180016332 jz short loc_18001633A
.text:0000000180016334 call cs:__imp_RegCloseKey
.text:000000018001633A

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-updates-brick-my-machine/84591c45-012b-4f7e-8b5e-3a1f7a658d71?auth=1
This is my last ditch effort to get some kind of help before giving up on Windows 10 forever. I tried calling support for help but it was frustrating and pointless and I was ultimately just given an 800 number to call to speak to engineers in a different group. Honestly, I don't know if I can handle speaking to another guy with a thick accent who is obviously just reading off of a script in an MS knowledge base.

For the past 5 months, I've been fighting an endless battle against forced updates that render my machine completely inoperable. I've had to roll-back to an earlier restore point and run the show/hide updates tool on a monthly basis just to keep the thing up and running. That, of course, means that I've spend many many hours trying to work around a broken update process that Microsoft seems either unwilling or unable to fix.

For whatever reason, the cumulative updates never complete when they run and I'm left with a blue screen with spinning white dots. When this happens, the only way to get the machine running again is to rollback to an earlier restore point. The show/hide update tool prevents the update from running again for about a month but then the whole ordeal repeats. ...I guess when the newest patches come out?? So, I'm constantly having to rollback and re-install whatever was added after the restore point was set.

What convinced you to make this thread in a programming board?
No, really. Did you mistake this board for /comp/ or /tech/? Or maybe /g/?

>>15
Let's be honest, not a shred of programming discussion goes on any of these boards. It's all shitposting in tiny, goat, etc.

>>16
Two wrongs don't make a right.

>>15

This thread is related to debugging and programming in machine code, because that is the only way you can configure Windows 10

>>18
Or you can try using a real OS instead of a toy one.

>>17
Two Wongs also don't make a white.

>>19
Lennart Poettering destroyed Linux and FOSS software ecosystem with systemd.

>>20
...I was talking about *BSD.

>>21
FOSS software ecosystem is part of *BSD

>>22
And what does it have to do with FOSS Ecosystem?

>>23
The FOSS ecosystem is tied into systemd because of the network effect of many more people using Linux distributions over *BSD, making *BSD community have to conform and modify their systems to use those programs that are using the various features of systemd and Linux breaking operability across Unix and Unix-like platforms. Going back to using SysVinit would solve this problem, as systemd has no benefits, except maybe in embedded systems.

>>19

I had OSX, but my MacBook Pro was confiscated by Putin's FSB.

>>25
Then go with BSD. Why Windows 10?

>>26

BSD has no drivers or software.

>>27
Nice memes, nikita

>>27
You purchase your hardware for the operating system you want, not the other way around.

>>29

I don't have money, so I'm limited to the cheapest hardware.

>>30
Stop being a lazy bum and make some money instead of whining like a spoiled bitch.

>>31
How do you know he's lazy, maybe he's stupid.

>>32
He's both, I guess. How does he plan to make money with his unfinished shitty Battletoads remake is beyond me.

>>33
It's a warcraft 3 remake......

>>34
It's not an RPG.

>>31
A lot of people are in the same position, you privledged kike.

>>36
Those people don't compare to him unless they're just as whiny.

>>35

It is roguelike.

Another incredible annoying Windows 10 feature: when you open a folder with audio files, Windows hides file name, date, size and extension, showing instead "Track Number", "Title", "Contributing Artist" and "Album". That is entirely worthless, when you open a folder with sound effects used for a game, and I never listen to these audio albums with track numbers, because music is for retards. Even less I care about "contributing artists". How have they managed to fuck up such a basic functionality, like showing a file size and modification date?

>>39

And as always, there is no way to disable that, proving it is made intentionally to annoy people.