Error with logon screen after installing bootscreen

System Restore

or

Command Prompt (As Admin)

sfc /scannow

reboot

Tried the system restore, told me that the disk has errors and i need to scan it first, so i clicked that and it said it can't scan it while the disk is in use, asked if I wanted to scan on startup, said yes, (schedule scan) and restarted, but no scan ever happened. When I tried your other suggestion, it found problems, and was unable to repair some of them, when I looked in the log file it created, I was unable to figure out what any of it meant haha. Your help is appreciated.

What's the make and flavor of your lap?

Make and flavor huh? haha Cherry? HP TX2000 with Windows Vista Home Premium. That what you wanted to know?

HP TX2000 was what I needed.....no Vista DVD...correct?

Thats mostly correct, I do have a upgrade version of Vista used on a different laptop. While I don't have that disk with me now, I'll have access to it after Sunday.

Is it only the Fingerprint not working?

It's not really that its not working, its just that none of the text below it is working, I can still swipe my fingerprint to log in, it has just removed the "Swipe your fingerprint to log in" and any other messages that come from swiping. But yes, that is the only obvious problem I see right now, just the lack of some text on the log on screen.

Try two things:

Device Manager > USB Controllers > HX2LP. Roll back driver. (no roll back: un-install/re-install)

Reboot

(if Personal Security Devices appear in Device Manager skip and go to #2)

No joy....

Open Command Prompt (admin): chkdsk /R

Reboot

no luck on either I'm afraid. HX2LP does not exist under USB Controllers. And with chkdsk /R, again it tells me it needs to activate on restart, and when i say yes, it never shows up when i restart my computer...

That ain't good....sounds like the Master File Table is borked. You certainly have more wrong then the Fingerprint text. I guess it would be too much to hope you just got this and there's not much of your stuff on it.....

Let's toy with Vista and see if we can get it to cough up it's problem.

Command Prompt (admin):

sfc /VERIFYONLY=c

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Jesse>sfc /VERIFYONLY =c

Microsoft (R) Windows (R) Resource Checker Version 6.0
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Scans the integrity of all protected system files and replaces incorrect version
s with
correct Microsoft versions.

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
    [/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory>
]

/SCANNOW        Scans integrity of all protected system files and repairs files
with
                problems when possible.
/VERIFYONLY     Scans integrity of all protected system files. No repair operati
on is
                performed.
/SCANFILE       Scans integrity of the referenced file, repairs file if problems
 are
                identified. Specify full path <file>
/VERIFYFILE     Verifies the integrity of the file with full path <file>.  No re
pair
                operation is performed.
/OFFBOOTDIR     For offline repair specify the location of the offline boot dire
ctory
/OFFWINDIR      For offline repair specify the location of the offline windows d
irectory

e.g.

        sfc /SCANNOW
        sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
        sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDI
R=d:\windows
        sfc /VERIFYONLY

C:\Users\Jesse>

Thats what came up when I did that

One thing that makes me very curious is what did BootScreen Vista from Objectdock do that caused this problem? It has to have been the problem, because i had restarted my computer, isntalled bootscreen, added a skin, and restarted with the problem...

Shit.....I screwed that up. I was going to have you verify the Windows kernel and decided not to. I should have deleted the "=c" part. 

Run:

Command Prompt (admin);

sfc /OFFWINDIR =d:\windows     

No idea, but for something that people see for 2 seconds I wish they'd take a pass. That said, it may not have anything other than bad timing to do with your problem.

When that's done:

Command Prompt (admin):

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

If any entries are listed as 'Unable to Repair' you're going to have to do a DVD repair. The only other option is the HP Recovery and I would avoid that for obvious reasons.

Did you copy/ paste it? 

yup, no joy there

My typing skills suck....do it again:

sfc /OFFWINDIR=d:\windows  

hmmmmmmm still no dice...?

Ok....run the sfc /scannow again (it's the only thing working) and then pull up the log as noted in #16

is there any way to attach the results? they are WAY too long to copy and paste in here

Just give me a flavor...copy/paste some of the un-repairables.

I think this is mainly what you want:

POQ 73 ends.
2009-04-22 02:33:53, Info                  CSI    0000018a [SR] Verify complete
2009-04-22 02:33:53, Info                  CSI    0000018b [SR] Repairing 1 components
2009-04-22 02:33:53, Info                  CSI    0000018c [SR] Beginning Verify and Repair transaction
2009-04-22 02:33:53, Info                  CSI    0000018d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6001.18000_none_e1f3ed49c1c122ef\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:+sVtVcOvvQFPc6fcRy1D2nKrd0mJEHS2XdqqhcuNEmc=} Expected: {l:32 b:qOUF+ctsOCM2TYmwdnxjaIw2MyNLU16DyI+ZtapP4nY=}
2009-04-22 02:33:53, Info                  CSI    0000018e [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-04-22 02:33:53, Info                  CSI    0000018f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6001.18000_none_e1f3ed49c1c122ef\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:+sVtVcOvvQFPc6fcRy1D2nKrd0mJEHS2XdqqhcuNEmc=} Expected: {l:32 b:qOUF+ctsOCM2TYmwdnxjaIw2MyNLU16DyI+ZtapP4nY=}
2009-04-22 02:33:53, Info                  CSI    00000190 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-04-22 02:33:53, Info                  CSI    00000191 Hashes for file member \??\C:\Windows\System32\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:gmYJ9O881/LlQ3I9Re4GGxccS7Y7be+FDjJh/KiDEtM=} Expected: {l:32 b:qOUF+ctsOCM2TYmwdnxjaIw2MyNLU16DyI+ZtapP4nY=}
2009-04-22 02:33:53, Info                  CSI    00000192 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6001.18000_none_e1f3ed49c1c122ef\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:+sVtVcOvvQFPc6fcRy1D2nKrd0mJEHS2XdqqhcuNEmc=} Expected: {l:32 b:qOUF+ctsOCM2TYmwdnxjaIw2MyNLU16DyI+ZtapP4nY=}
2009-04-22 02:33:53, Info                  CSI    00000193 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2009-04-22 02:33:53, Info                  CSI    00000194 Repair results created:
POQ 74 starts:

Definitely Windows Core files (thought it might be HP). Boot into Safe Mode and run: Restore. Failing that run:

sfc /OFFWINDIR=d:\windows