Locked out of Client Laptop

All0verITAll0verIT
in General
OK, So I did something REALLY stupid. I was looking at MultiOTP for the first time. I installed the Hyper-V Server on my Laptop, all working fine, but set to manual start up. I then started fiddling around with Credential Provider on the same laptop. Next time I reboot the Laptop I get the multiOTP Login screen. When I enter the local Creds, I get the request for a OTP, which I cannot supply because the Server is not running and nothing is really fully configured. I am not locked out of my laptop . . . Is there some way to disable the multiOTP login and return to the local login so I can clean up my laptop? Geoff

Comments

  • All0verITAll0verIT
    Sorry, should read "I am NOW locked out of my laptop . . . Is there some way to disable the multiOTP login and return to the local login so I can clean up my laptop? Geoff
  • YannJYannJ
    edited February 17
    Hello,
    Thanks for trying multiOTP Credential Provider. If you just activated the credential provider for local login, you should be able to login using remote desktop.
    If remote desktop is also using the credential provider or if remote desktop is not activated you need to start Windows in safe mode and delete the files : c:\Windows\System32\multiOTPCredentialProvider.dll and c:\Windows\System32\multiOTPCredentialProviderFilter.dll
    Best regards
  • All0verITAll0verIT
    Thanks for that Yannj, While waiting for comments I found another way . . . however yours sounds simpler. FYI. I removed the Hard Disc and connected it via USB to another W10 workstation. Ran the Registry editor and loaded the Hive from the USB drive Made the manual edits as per the multiOTPCredentialProvider-unregister.reg file (some of these were a bit tricky but we got there. Unloaded the Hive, replaced the SSD back in the laptop, and it booted to the Local Account OK I then removed the multiOTP CredentialProvider app and all seems to be OK for now . . . I will be MUCH more careful in future . . . Thanks again Geoff
This discussion has been closed.

© Vanilla Keystone Theme 2025