NovaDelta
Sophomore Member
i am me
Posts: 174
OS: Windows 10 22H2
Theme: Unfortunately, 10 theme
CPU: i7-6700HQ
RAM: 16GB of sticks of RAM
GPU: Nvidia Quadro M1000M
|
Post by NovaDelta on Jun 23, 2018 10:50:03 GMT -8
Would there be any way to change what the logon screen looks like or at least enable a logon window similar to the one from WIndows 9x?
|
|
|
|
Post by anixx on Jun 24, 2018 3:48:51 GMT -8
Try to replace the file LogonUI.exe with the one from WinXP or Win2000 (I did not try this).
I think for Win8/10 to call Logonui.exe, the text mode logon should be enabled.
|
|
NovaDelta
Sophomore Member
i am me
Posts: 174
OS: Windows 10 22H2
Theme: Unfortunately, 10 theme
CPU: i7-6700HQ
RAM: 16GB of sticks of RAM
GPU: Nvidia Quadro M1000M
|
Post by NovaDelta on Jun 24, 2018 11:02:30 GMT -8
Try to replace the file LogonUI.exe with the one from WinXP or Win2000 (I did not try this). I think for Win8/10 to call Logonui.exe, the text mode logon should be enabled. Thanks |
|
|
|
Post by R.O.B. on Jun 24, 2018 12:09:22 GMT -8
Replacing LogonUI.exe with the one from XP is highly unlikely to work for a number of reasons, the main one being Microsoft completely redid the boot/logon process in Windows Vista. Even if it did, the classic logon screen wasn't handled by LogonUI.exe, but rather by msgina.dll (in NT-based systems). There is no way to get msgina.dll to work in newer versions of Windows, as Microsoft removed the GINA architecture entirely when they redid the boot process in Vista.
Honestly, I think our best bet would be to create a replacement of LogonUI.exe from scratch, which would load an interface that looks like the old GINA logon screen. This would likely be a huge project, and who knows what Windows 10 support for something like that would look like (or if it would even be possible).
|
|
|
|
Post by anixx on Jun 24, 2018 12:45:41 GMT -8
People successfully had replaced the logon interface, for instance making it on XP like on Win7
|
|
|
|
Post by R.O.B. on Jun 24, 2018 17:08:56 GMT -8
People successfully had replaced the logon interface, for instance making it on XP like on Win7 Yes, but those are just modifications of the XP login screen's UIFILE made to look like 7's, not a port of the Windows 7 one. The files aren't interchangeable, and that's mainly because XP's LogonUI.exe is still designed around the GINA architecture. Also, Windows XP's welcome screen interface is stored in LogonUI.exe itself, while the classic login screen is stored in msgina.dll (the classic login screen works just fine without LogonUI.exe, while the welcome screen is very much dependent on msgina.dll). In Vista/7, it's stored in authui.dll, with some resources in imageres.dll. Windows 8 and 10 also pull some stuff from a few other DLLs, such as Windows.UI.Logon.dll. So XP would have no idea how to handle a port like that anyway. |
|
|
|
Post by anixx on Jun 24, 2018 21:35:19 GMT -8
Also, Windows XP's welcome screen interface is stored in LogonUI.exe itself, while the classic login screen is stored in msgina.dll (the classic login screen works just fine without LogonUI.exe, while the welcome screen is very much dependent on msgina.dll). In Vista/7, it's stored in authui.dll, with some resources in imageres.dll. Windows 8 and 10 also pull some stuff from a few other DLLs, such as Windows.UI.Logon.dll. So XP would have no idea how to handle a port like that anyway. What is clear now is that the console logon screen in Win10 is produced by LogonUI.exe. So I think if we replace it with something that could be working when written into UIHost registry key under XP. |
|
|
|
Post by powerplayer on Aug 21, 2018 18:20:10 GMT -8
Also, Windows XP's welcome screen interface is stored in LogonUI.exe itself, while the classic login screen is stored in msgina.dll (the classic login screen works just fine without LogonUI.exe, while the welcome screen is very much dependent on msgina.dll). In Vista/7, it's stored in authui.dll, with some resources in imageres.dll. Windows 8 and 10 also pull some stuff from a few other DLLs, such as Windows.UI.Logon.dll. So XP would have no idea how to handle a port like that anyway. What is clear now is that the console logon screen in Win10 is produced by LogonUI.exe. So I think if we replace it with something that could be working when written into UIHost registry key under XP. I get it your saying to add a gui for classic logon win2000 style over the cmd interface and name the program Windows.UI.Logon.dll Why has nobody bothered doing that? Edit im case you guys didnt understand this is the gui frontend for command prompt i was talking about  |
|
|
|
Post by namensloser on Aug 6, 2019 14:04:48 GMT -8
if I replace my logonui with that of vista or 7? does it work?
i use win 10
|
|
|
|
Post by powerplayer on Aug 9, 2019 15:45:44 GMT -8
nope it doesnt do anything replacing files will not work but you can modify the background and the round login to a square png found in then u need to make a .reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer] ![]() ![]() "UseDefaultTile"=dword:00000001 install it and your logo will make windows respect png transparency at logon  after tinkering with the png files what i use on my hp as login pic big one user-192.png small one user-48.png  ![]() ![]() |
|
|
|
Post by leet on Oct 13, 2019 15:07:06 GMT -8
I'm getting some mixed signals over here. What executable gets called to display logon screen and in what dll's are the screens for it? And powerplayer, how did you achieve the screenshot you sent? |
|
|
|
Post by Spitfire_x86 on Oct 14, 2019 0:34:48 GMT -8
He didn't. It's a mockup.
|
|
|
|
Post by powerplayer on Oct 14, 2019 16:10:53 GMT -8
I'm getting some mixed signals over here. What executable gets called to display logon screen and in what dll's are the screens for it? And powerplayer , how did you achieve the screenshot you sent? technically there was a dll file you could remove that would give you the command line instead , you could probably do some clever replacement on that using processhacker to analyze whats going on... |
|
|
|
Post by leet on Oct 15, 2019 5:44:24 GMT -8
Basically, If I know what syscall logs into the user, I can probably easily make a UI using Win32 or MFC
|
|
NovaDelta
Sophomore Member
i am me
Posts: 174
OS: Windows 10 22H2
Theme: Unfortunately, 10 theme
CPU: i7-6700HQ
RAM: 16GB of sticks of RAM
GPU: Nvidia Quadro M1000M
|
Post by NovaDelta on Oct 15, 2019 14:14:36 GMT -8
Basically, If I know what syscall logs into the user, I can probably easily make a UI using Win32 or MFC Thatd be interesting to see |
|
|
|
Post by leet on Oct 15, 2019 15:00:13 GMT -8
Well, it will just be replacing LogonUI.exe with my EXE and make the appropriate syscalls to the system to handle logging in. But it's really hard to analyze the login sequence as all open System windows will close upon logon so Process Explorer wouldn't work for this.
|
|
|
|
Post by leet on Dec 24, 2019 18:34:25 GMT -8
Decided to try some stuff out today. Here's a quick sum-up of what I did:
Replace LogonUI with cmd.exe -WORKS
Running userinit as a different user -WORKS
Switching to the other users environment -WIP
If the last step works we can basically create our own loginui.
|
|
|
|
Post by anixx on Dec 25, 2019 0:15:48 GMT -8
Did you try to replace LogonIU with that from Win2000 (rather than with cmd.exe)?
|
|
|
|
Post by leet on Dec 25, 2019 6:00:19 GMT -8
no, i quickly made a console gui that asks for login but as soon as that works i;ll try making a gui almost identical to win2k
|
|
|
|
Post by leet on Dec 25, 2019 8:33:15 GMT -8
It's not as easy as I thought. I actually have to make a new Windows Session, switch to that and run userinit there. Luckily Microsoft has documented this part of Windows really well.
|
|
