Windows Security Center won't turn on

cottonball · 01 May 2014

When you get done with Kactussoft and gregrocker, please do the following:

RogueKiller did not identify malware, so let's press on with FRST64, and run another fix.

Please open notepad (Start > All Programs > Accessories > Notepad)
Copy the entire contents of the code box below (Do not copy the word 'code') to Notepad.
Save it to the pen drive where FRST64 is located, and name it: fixlist.txt

Code:

start
S2 WindowsSVC; C:\Windows\SysWOW64\winthemes.dll [151552 2014-04-11] ()
2014-04-11 06:40 - 2014-04-11 06:40 - 00151552 _____ () C:\Windows\SysWOW64\winthemes.dll
2014-04-11 06:40 - 2014-04-11 06:40 - 00062464 _____ () C:\Windows\SysWOW64\common2.dat
2014-04-11 06:40 - 2014-04-11 06:40 - 00062464 _____ () C:\Windows\SysWOW64\common1.dat
DisableService: MsMpSvc
DisableService: NisSrv
DisableService: MpFilter
DisableService: NisDrv
DisableService: MpNWMon
HKLM\...\Run: [MSC] => c:\Program Files\Microsoft Security Client\msseces.exe [1271072 2014-03-11] (Microsoft Corporation)
end

NOTICE: This script is written specifically for this computer!!!
Running this on another computer may cause damage to the Operating System.

Now, with the pen drive( containing FRST64 and fixlist) connected, restart the computer, and once again enter System Recovery Options and select: Command Prompt

Get to FRST, as you did before, and press the Fix button, just once, and wait.

When done, the tool creates a report on the pen drive called: Fixlog.txt

Please post the Fixlog.txt in your reply.

Let us know if the computer boots to Windows.

Jackie1 · 01 May 2014

Kaktussoft said:

What is the windows system didk drive letter in windows7 recovery environment? It isn't necessary C!

Code:

dir c:\users
dir d:\users

Do you see your username? Then you know the correct drive letter. Assuming it's C:

Code:

sfc /scannow /offbootdir=c:\ /offwindir=c:\windows

SFC /SCANNOW : Run in Command Prompt at Boot

Post results

My user account is on D:

I did the command and it says: "Beginning system scan. This process will take some time. About 10 seconds later it said: There is a system repair pending which requires reboot to complete. Restat windows and run SFC again.

This isn't going to try tand run chkdsk again for 17 hours is it? Now what? I found this article, but want to be sure I do the correct thing...

Cancel sfc /scannow: "There is a system repair pending which requi..."

Kaktussoft said:

When booting normally... do you see the logon screen?
Did you normally see the logon screen, or do you have only 1 user account?
When seeing the mouse pointer on black background: Press CTRL-ALT-DEL... what happens?

No, when rebooting, you see the windows logo and flag, then a few seconds after that, it goes to black screen with pointer. You cannot hit ctrl alt delete, it does nothing, I've tried that on every reboot. Normally, when the system worked, there were two accounts, mine and a guest account....

Jackie1 · 01 May 2014

Also, the extended test for the WD harddrive that gregrocker had me run ...took 6 hours and finished with 0 errors.

Kaktussoft · 01 May 2014

So you did:
sfc /scannow /offbootdir=D:\ /offwindir=D:\windows
???

Code:

DIR  C:\windows\system32\config\regback

Which date/time are those files?

When did non-boot problems begin?

Kaktussoft · 01 May 2014

Can you revert back to this state? #1
The system was booting then. Did you make a backup when system was fine? Did you make backup before advanced troubleshooting/cleaning?

Jackie1 · 01 May 2014

Kaktussoft said:

So you did:
sfc /scannow /offbootdir=D:\ /offwindir=D:\windows
???

Code:

DIR  C:\windows\system32\config\regback

Which date/time are those files?

When did non-boot problems begin?

Correct on the above command. I added a screen shot to my last post ^

I had to put in DIR D:\windows\system32\config\regback instead of C: (it lists windows under D in this command area)

The dates are 4/23/14 for the 5 files in config/regback. The problems started on the 4/28 around 6pm. I think I replaced these before with regback, and that's when it tried to do that chksdk for 17 hours... If we do again, I want to make sure that scan doesn't happen again.:)

Also, FRST made a folder on my machine that has saved hives in it, before this issue started too.

Jackie1 · 01 May 2014

Kaktussoft said:

Can you revert back to this state? #1
The system was booting then. Did you make a backup when system was fine? Did you make backup before advanced troubleshooting/cleaning?

That's the problem, I had 3 restore points at that time, even labeled one of them, and now it shows none when I try to do a restore...

The sfc scannow wouldn't work, scroll up to see what it said. I put a screen shot.

Kaktussoft · 01 May 2014

Code:

 
D:
cd  \windows\system32\config\regback
copy/y *.*  ..

So "space 2 dots" at end. It's for copying one level up.
then do:

Code:

sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

Post results. You can cancel the chkdsk on normal boot by pressing space bar I think. It's on your screen how to do it.

Jackie1 · 01 May 2014

After doing to copy *.* .. it says Overwrite... \default, yes, no or all. Yes?

Kaktussoft · 01 May 2014

Code:

 
dism /image:D:\ /get-packages |more

What has been installed last few days? Which one are pending?