Stardock Logon Studio has compromised my ability to log on

from Stardock Forums

I installed BootSkin and Logon Studio on my Vista x64 laptop, since all the posts I'd seen about it showed this was supported.


But apparently my system has a conflict with this software.  I have a fingerprint reader installed.  When Logon Studio is installed, my Logon process is compromised.  First, I cannot log on via the keyboard.  When I click on a user icon, the screen pauses, then refreshes back to locked state with no option to enter a password.  The only way I can log on is by using the fingerprint reader.

Once logged on, I get an error on the desktop startup, indicating some sort of error with the User Logon.  I then find this in the application event viewer log:

Faulting application LogonUI.exe, version 6.0.6001.18000, time stamp 0x4791960d, faulting module authui.dll, version 6.0.6002.18005, time stamp 0x49e040d2, exception code 0xc0000005, fault offset 0x0000000000037ef7, process id 0x2c4, application start time 0x01cd30bdaf7c7608.

 

I am unfortunately unable to roll back to a previous restore point before the Stardock/Impulse software was installed.  I need to repair my system, hopefully in a minimally invasive way that won't take an entire day.  Otherwise, I fear I may need to do a complete system recovery.  Any help would be much appreciated.  Thank you!

4,255 views 7 replies
Reply #1 from WinCustomize Forums Top

Elevated Command prompt: sfc /scannow

Reboot

Reply #2 from Stardock Forums Top

Quoting yrag, reply 1
Elevated Command prompt: sfc /scannow

Reboot
End of yrag's quote

I did that.  Some errors were found, but nothing related to logon functionality that I can tell...  I rebooted and same issue remains.  Here's a snippet of the relevant log entries from the SFC scan:

 

2012-05-14 01:02:09, Info CSI 000002fc [SR] Repairing 3 components
2012-05-14 01:02:09, Info CSI 000002fd [SR] Beginning Verify and Repair transaction
2012-05-14 01:02:10, Info CSI 000002ff [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\PolicyDefinitions"\[l:24{12}]"inetres.admx" from store
2012-05-14 01:02:10, Info CSI 00000302 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:30{15}]"winload.exe.mui" from store
2012-05-14 01:02:10, Info CSI 00000304 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\PolicyDefinitions\en-US"\[l:24{12}]"InetRes.adml" from store
2012-05-14 01:02:10, Info CSI 00000307 [SR] Repair complete
2012-05-14 01:02:10, Info CSI 00000308 [SR] Committing transaction
2012-05-14 01:02:11, Info CSI 0000030c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2012-05-14 02:18:35, Info CSI 00000454 [SR] Repairing 2 components
2012-05-14 02:18:35, Info CSI 00000455 [SR] Beginning Verify and Repair transaction
2012-05-14 02:18:36, Info CSI 00000457 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\PolicyDefinitions"\[l:24{12}]"inetres.admx" from store
2012-05-14 02:18:36, Info CSI 0000045a [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\PolicyDefinitions\en-US"\[l:24{12}]"InetRes.adml" from store
2012-05-14 02:18:36, Info CSI 0000045d [SR] Repair complete
2012-05-14 02:18:36, Info CSI 0000045e [SR] Committing transaction
2012-05-14 02:18:36, Info CSI 00000462 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

If I run the SFC scannow again, the same errors appear.  Despite the repair being stated as complete and transaction committed, they aren't persisting for some strange reason.

Thankfully I can still log on via fingerprint, but the fact that I can't via text entry of password is something I must resolve.  What would you recommend as the next course of action?

Fences - Organize your desktop icons today!
Reply #3 from Stardock Forums Top

Well, I think I've gotten closer to narrowing down the problem...

 

It appears to me that the issue at hand is Stardock conflicting with fingerprint reader software installed (DigitalPersona).  Somehow, it created an issue in the registry.  The only other entry I found on-line that mentions this was by another user in this sub forum, and they also have an HP laptop with fingerprint reader.

So, I'm going to see if I can uninstall the DigitalPersona software and then install it again.  Maybe that will clean things up... I hope.

 

EDIT:  Yes, this worked.  Removing Digital Persona took care of the problem.  I no longer get any faults with LogonUI.exe and authui.dll.  Now, I'll have to see if installing the software back into place doesn't result in the problem appearing again.  I think what I'll try first is putting Logon Studio back on, then install the fingerprint reader software next.

Reply #5 from WinCustomize Forums Top

Both applications are layering on top of base windows and conflicting.  You may have to pick which item you want the most.

Reply #6 from Stardock Forums Top

Quoting Zubaz, reply 5
Both applications are layering on top of base windows and conflicting.  You may have to pick which item you want the most.
End of Zubaz's quote

It's rather peculiar... Stardock Logon Studio or Bootskin should have nothing to do with the fingerprint reader.  A fingerprint reader is a fairly common feature.  Stardock is the "add on" that comes afterward and should be respectful of what software is installed.

 

In any case, I had tried reinstalling the Digital Persona software with Logon Studio already in place, and that did not help.  I had to completely remove both software and then install Digital Persona again.  I have my Vista x64 laptop back to the way it was.  I'd rather have the fingerprint reader working and no errors in the Windows Logon services than have a different logon screen background.  Still... a big disappointment considering what I had to go through.

Reply #7 from WinCustomize Forums Top

Unfortunately, the way a lot of Windows systems work, the fingerprint reader and BootSkin are like two people trying to sit on the same chair, at the same time.  It just doesn't really work.