|
|
Post by pimposkini on Mar 19, 2023 14:53:55 GMT -8
hi, i've got a minor issue. it takes a second for this to show up when booting so i get a glimpse of the modern welcome screen, which is kind of immersion breaker, but no big deal. is there any way to prevent this?
EDIT: oh dear, now it's hanging eternally on setting up personal settings or whatever it was. have uninstalled now, but i don't know why it's doing that now :/
|
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 165 
OS: Windows 10
Theme: Shitbox Edition
|
Post by herit://that1cutie on Mar 20, 2023 0:40:20 GMT -8
hi, i've got a minor issue. it takes a second for this to show up when booting so i get a glimpse of the modern welcome screen, which is kind of immersion breaker, but no big deal. is there any way to prevent this? EDIT: oh dear, now it's hanging eternally on setting up personal settings or whatever it was. have uninstalled now, but i don't know why it's doing that now :/ So CLS is something that runs on top of winlogon.exe. It uses signals based on what screen you *should* be on in winlogon (but it's not always right). If the lock screen is on, then when you log in, it's sending the password text to the *wrong screen.* This would occur when the lock screen reactivates *after* CLS loads- CLS has no way of knowing when this happpens (and you cannot check the lock screen without exiting) and it appears to act normal, only to get stuck applying system preferences.
I don't exactly know how to prevent this from happening, but if it does happen simply press alt+F4 to close out of CLS, and you'll then be met with what winlogon is *actually* doing. This is actually more of a Windows issue than a CLS issue from what I can tell.
As for the delay; it is an expensive solution, but when I switched to an SSD that delay disappeared.
|
|
|
|
Post by db2k on Mar 22, 2023 12:33:04 GMT -8
Would this work on 7?
|
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 165
OS: Windows 10
Theme: Shitbox Edition
|
Post by herit://that1cutie on Mar 23, 2023 10:52:13 GMT -8
I don't know if it would work properly on 7. It may, it may not. However, I'm pretty sure there is a way to achieve the classic logon screen in Windows 7 without a third party program. It's been long enough since I used 7 that I don't remember how. However, if I remember correctly, it may require Windows 7 Pro.
|
|
|
|
Post by db2k on Mar 26, 2023 22:24:19 GMT -8
I don't know if it would work properly on 7. It may, it may not. However, I'm pretty sure there is a way to achieve the classic logon screen in Windows 7 without a third party program. It's been long enough since I used 7 that I don't remember how. However, if I remember correctly, it may require Windows 7 Pro. Time to do some googling, I guess. Glad my system runs 7 Pro! |
|
|
|
Post by ihatemetro on Mar 27, 2023 19:04:57 GMT -8
I don't know if it would work properly on 7. It may, it may not. However, I'm pretty sure there is a way to achieve the classic logon screen in Windows 7 without a third party program. It's been long enough since I used 7 that I don't remember how. However, if I remember correctly, it may require Windows 7 Pro. I don't think there is a way. The old classic login dialog was based on the GINA architecture, which was removed in Vista in favour of the modern login screens of today. Also, this program will not work on Windows 7, since it requires the shitty metro Windows 10/11 login screen. (Sadly this also means that it cannot be used with DWM off, and I am stuck with the basic console login screen). |
|
|
|
Post by OrthodoxWin32 on Apr 10, 2023 3:45:49 GMT -8
I added the French translation.
There is a slight problem : as in French, the sentences are much longer; as a result, the "The system could not log you on" dialog box and the "Shut down Windows" button have truncated text (not enough space).
|
|
|
|
Post by OrthodoxWin32 on Apr 13, 2023 3:49:08 GMT -8
I reported the bug in the dedicated page, but I'm copying it here: I use, in addition to ClassicLogonShell, a software called Surun: sourceforge.net/projects/surun/This is software that replaces UAC (User Account Control), present since Windows Vista. It has the advantage, unlike UAC, of making it possible to automate the opening of a program as administrator, without having the confirmation prompt all the time. Additionally, it has a classic-looking confirmation window, unlike UAC since Windows 10 (exactly like ClassicLogonShell compared to the default login screen). The problem is, when I enable ClassicLogonShell, Surun's confirmation prompt no longer works. Instead, I get a ClassicLogonShell login screen, which disappears as soon as I click on it. And the requested program does not run. The problem arises even for the programs where I have automated it (which therefore opens without a confirmation prompt). So I'm unable to run a program as administrator with Surun + ClassicLogonShell, and therefore unable to get both a classic UAC prompt and a classic login screen. Noted that the problem was not present the first days of installing ClassicLogonShell, it appeared after. I had already tried to install ClassicLogonShell a month ago, I had uninstalled it because of the same problem (which also appeared a day after the installation). I can't take a screenshot of the problem because my screenshot software crashes as soon as the login screen appears. |
|
|
|
Post by leet on Apr 13, 2023 8:46:54 GMT -8
I reported the bug in the dedicated page, but I'm copying it here: I use, in addition to ClassicLogonShell, a software called Surun: sourceforge.net/projects/surun/This is software that replaces UAC (User Account Control), present since Windows Vista. It has the advantage, unlike UAC, of making it possible to automate the opening of a program as administrator, without having the confirmation prompt all the time. Additionally, it has a classic-looking confirmation window, unlike UAC since Windows 10 (exactly like ClassicLogonShell compared to the default login screen). The problem is, when I enable ClassicLogonShell, Surun's confirmation prompt no longer works. Instead, I get a ClassicLogonShell login screen, which disappears as soon as I click on it. And the requested program does not run. The problem arises even for the programs where I have automated it (which therefore opens without a confirmation prompt). So I'm unable to run a program as administrator with Surun + ClassicLogonShell, and therefore unable to get both a classic UAC prompt and a classic login screen. Noted that the problem was not present the first days of installing ClassicLogonShell, it appeared after. I had already tried to install ClassicLogonShell a month ago, I had uninstalled it because of the same problem (which also appeared a day after the installation). I can't take a screenshot of the problem because my screenshot software crashes as soon as the login screen appears. Does pressing Ctrl+Alt+Del also show CLS2, or is that just the normal Ctrl+Alt+Del menu? Because that is displayed on the same desktop as the UAC prompt (and thus Surun's prompt). Maybe a check could be implemented to see if LogonUI is hosted inside of WinSta0\Winlogon, to make sure CLS2 is not displayed elsewhere. |
|
|
|
Post by OrthodoxWin32 on Apr 13, 2023 9:07:03 GMT -8
Does pressing Ctrl+Alt+Del also show CLS2, or is that just the normal Ctrl+Alt+Del menu? Because that is displayed on the same desktop as the UAC prompt (and thus Surun's prompt). Maybe a check could be implemented to see if LogonUI is hosted inside of WinSta0\Winlogon, to make sure CLS2 is not displayed elsewhere. Yes, it is indeed a CLS connection screen that is displayed, and which also locks the session automatically. Which in itself is already a problem, it is no longer possible to access the task manager in this way. The difference between the two is that the CLS login screen does not lock the session in the case of the UAC/Surun prompt. |
|
|
|
Post by leet on Apr 13, 2023 12:22:47 GMT -8
This forms a problem.
UAC and Ctrl+Alt+Del both display on the Winlogon window station of the current user. The main method is checking on what window station LogonUI is running. WinSta0 belongs to the SYSTEM and WinSta1+ belongs to the logged in user accounts. Unfortunately, this method is not fail-proof.
Normally LogonUI would be shown on WinSta0\Winlogon because WinSta1 is not yet created (no user logged in yet). But when the user is locked, it displays on WinSta1\Winlogon to allow for fast user switching. Fast Startup makes it so that the user is already logged in at boot, so WinSta1 is already created at that point.
So you can not really tell what is being displayed to the user at any given point. You can check the window station LogonUI is running on, but that will not help you that much as WinSta1 can be any of the screens. One thing is sure though: WinSta0 will always be either the login screen or the shut down screen.
|
|
|
|
Post by OrthodoxWin32 on Apr 13, 2023 14:47:36 GMT -8
leet Thanks for clarification. Effectively, the problem does not occur initially (when connecting to the session); the problem occurs when I put the computer to sleep, and I leave sleep mode. This happens even though I have activated sleep mode without locking the session. It looks very similar to your description.
|
|
rnk
Freshman Member
Posts: 29
|
Post by rnk on Jun 27, 2023 8:59:27 GMT -8
Works good, I just have a question; is there any way to make the "Shutdown" app functional outside of just manually clicking the .exe? I want to it when I click Shutdown through my start menu.
|
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 165
OS: Windows 10
Theme: Shitbox Edition
|
Post by herit://that1cutie on Jun 28, 2023 11:42:38 GMT -8
Works good, I just have a question; is there any way to make the "Shutdown" app functional outside of just manually clicking the .exe? I want to it when I click Shutdown through my start menu. Yes! Just not through the actual *Windows* start menu. You can configure the Open-Shell start menu to use the CLS shutdown EXE as its default target for its shutdown button. |
|
|
|
Post by animal on Jul 2, 2023 13:49:42 GMT -8
Well, I tried to install this... I restarted my computer to try and see how it looked and unforutanetly i no longer have a lock screen. I can no longer access my computer. Im fairly new to all of this, so I dont know what went wrong or how to fix this. I really cant afford to lose my computer, all of my art is on there. Can anyone please help me?
|
|
rnk
Freshman Member
Posts: 29
|
Post by rnk on Jul 2, 2023 16:33:27 GMT -8
Works good, I just have a question; is there any way to make the "Shutdown" app functional outside of just manually clicking the .exe? I want to it when I click Shutdown through my start menu. Yes! Just not through the actual *Windows* start menu. You can configure the Open-Shell start menu to use the CLS shutdown EXE as its default target for its shutdown button. Very good, thanks. The UAC is a bit immersion breaking but I don't think there's a way around that. animal: Boot your computer into safe mode and then just uninstall/delete the program and check off run at startup. I'm not sure if this program is compatible with a computer that doesn't have the actual classic theme enabled. |
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 165
OS: Windows 10
Theme: Shitbox Edition
|
Post by herit://that1cutie on Jul 3, 2023 10:37:40 GMT -8
Well, I tried to install this... I restarted my computer to try and see how it looked and unforutanetly i no longer have a lock screen. I can no longer access my computer. Im fairly new to all of this, so I dont know what went wrong or how to fix this. I really cant afford to lose my computer, all of my art is on there. Can anyone please help me? Yes! Sorry that happenned to you! If you find me on discord and describe your issue more specifically I think I can walk you through getting it back to normal, and even getting the program working properly as well if you're still up to it. My signature has an invite link to my server, I am the server owner. Send me a message there. If push comes to shove I can contact the current dev as well. Yes! Just not through the actual *Windows* start menu. You can configure the Open-Shell start menu to use the CLS shutdown EXE as its default target for its shutdown button. Very good, thanks. The UAC is a bit immersion breaking but I don't think there's a way around that. animal : Boot your computer into safe mode and then just uninstall/delete the program and check off run at startup. I'm not sure if this program is compatible with a computer that doesn't have the actual classic theme enabled. You can evade the UAC either by adding an argument to the target path Open-Shell runs when running the CLS Shutdown Menu, I just don't remember what that argument is. It can be found on Google pretty easily I think. Otherwise, you can pretty easily disable UAC altogether. This is what I did because I found it didn't really ever help me, it just slowed me down. It never came up on something I wasn't *already expecting* to be able to affect files outside its own directory which is mostly all UAC tells you about
|
|
|
|
Post by justaduckinacostume on Jul 13, 2023 3:18:20 GMT -8
Problem's in the title, upon logging in with CLS it gives me an error saying LogonUI not found. Does anybody know how to fix this? I can't find anything about this anywhere online. On another note, does anyone know how to actually get CLS to be my login screen?
|
|
Maya
New Member
Posts: 1
OS: Windows 11 22H2
Theme: SimpleClassicTheme
CPU: Intel i5 2400
RAM: 16GB DDR4
GPU: Nvidia Geforce GTX 1650
|
Post by Maya on Jul 28, 2023 6:29:52 GMT -8
For whatever reason, every time I try to log in with CLS2, I get stuck on applying personal settings or whatever. Is this a known issue with any workarounds?
Thanks;
Maya
|
|
|
|
Post by justaduckinacostume on Jul 28, 2023 15:22:36 GMT -8
I can't get ClassicLogonShell to work. After installing it, my logon screen doesn't change. I only get the standard Windows logon screen that's already there. Additionally, I attempted to start CLS directly from it's exe file, and while it did open correctly, it displays the error "LogonUI not found" after proceeding with it.
|
|
