Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PIN Texbox doesn't appear and switch account button not working at all (can't do anything) #40

Open
polishplayer9 opened this issue Oct 5, 2024 · 9 comments

Comments

@polishplayer9
Copy link

polishplayer9 commented Oct 5, 2024

the other buttons work fine
used the latest version 1.0.7
image

unnamed

@wiktorwiktor12
Copy link
Owner

this is why i currently recommend NOT using a microsoft account atm for clh, it is using some other credential type other than pin or password

@polishplayer9
Copy link
Author

this is why i currently recommend NOT using a microsoft account atm for clh, it is using some other credential type other than pin or password

i'm using a local account though

@xdmcwaxiest
Copy link

I have the same issue too, the password box is gone and ctrl+alt+del shows up an error box. I just recently reinstalled windows and reinstalled ConsoleLogonHook and this time, it does not work.

@wiktorwiktor12
Copy link
Owner

this likely happens because some other credential provider appeared, i don't know exactly what one it would be, try to use regular consolelogon.dll and see what you have as options to sign in with

@xdmcwaxiest
Copy link

earlier today i tested to rename the Windows.UI.Logon.dll file on a VM with the same edition and build of windows 10 that i use on my real hardware. And the bug "the sign in process could not display security and sign in options bla bla bla" appeared when inserting CTRL+ALT+DEL (i did not install CLH on the VM). So i think that it's not a bug from CLH, we're maybe just missing something for CLH to fully work. Normally when renaming that file a console themed logon screen should appear. If the console themed logon screen works, then CLH should also work i assume.

@polishplayer9
Copy link
Author

earlier today i tested to rename the Windows.UI.Logon.dll file on a VM with the same edition and build of windows 10 that i use on my real hardware. And the bug "the sign in process could not display security and sign in options bla bla bla" appeared when inserting CTRL+ALT+DEL (i did not install CLH on the VM). So i think that it's not a bug from CLH, we're maybe just missing something for CLH to fully work. Normally when renaming that file a console themed logon screen should appear. If the console themed logon screen works, then CLH should also work i assume.

it might also be something we have installed that's breaking CLH

@wiktorwiktor12
Copy link
Owner

earlier today i tested to rename the Windows.UI.Logon.dll file on a VM with the same edition and build of windows 10 that i use on my real hardware. And the bug "the sign in process could not display security and sign in options bla bla bla" appeared when inserting CTRL+ALT+DEL (i did not install CLH on the VM). So i think that it's not a bug from CLH, we're maybe just missing something for CLH to fully work. Normally when renaming that file a console themed logon screen should appear. If the console themed logon screen works, then CLH should also work i assume.

what version of windows 10 are you running? Does it have ConsoleLogon.dll in system32?

@xdmcwaxiest
Copy link

Its 19044/21H2 and yes, ConsoleLogon.dll exists in system32.

@xdmcwaxiest
Copy link

earlier today i tested to rename the Windows.UI.Logon.dll file on a VM with the same edition and build of windows 10 that i use on my real hardware. And the bug "the sign in process could not display security and sign in options bla bla bla" appeared when inserting CTRL+ALT+DEL (i did not install CLH on the VM). So i think that it's not a bug from CLH, we're maybe just missing something for CLH to fully work. Normally when renaming that file a console themed logon screen should appear. If the console themed logon screen works, then CLH should also work i assume.

it might also be something we have installed that's breaking CLH

If there is a program that is breaking CLH then it has to be something pre-installed, because i did not install any programs on the VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants