Computer won't run any programs and system restore keeps failing

[FreestoneDallas]

Once again.. what problem did startup repair fix ????? see "view diagnostics" or someting like that when performing startup repair. please tell me, Because once fixed it stays fixed. Unless... you have a really nasty rootkit

Here are the problem details from Startup Repair:

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21201106
Problem Signature 05: AutoFailover
Problem Signature 06: 5
Problem Signature 07: NoRootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033


This is the message from the Diagnoses and Repair Details:

Test Performed:
Name:Boot status



Root Cause Found:
Unspecified changes to system configuration might have caused the problem.

 

[FreestoneDallas]

The bootsect command recreates the standard MBR... so doesn't damage anything. So why it give you any problem?
Do a offline scan with hitman pro to check if you have a rootkit virus!!

My computer won't load Windows. Even if it could, I can't open any programs remember? Whatever it is, it's stopping Windows from loading.

 

[Kaktussoft]

in recovery environment go to "command prompt"
Dir C:
Dir D:

what is windows drive letter in recovery environment? So where are windows files located? Assume it's D:
bootsect /nt60 d: /force
bootsect /nt60 d: /force /mbr

bcdedit /enum {bootmgr}
bcdedit /enum {default}

comaands ran succesfully? Please tell me what's listed at device and osdevice line

example:
C:\Windows\system32>bcdedit /enum {bootmgr}
Windows-opstartbeheer
---------------------
id {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale nl-NL
inherit {globalsettings}
default {current}
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 10
C:\Windows\system32>bcdedit /enum {default}
Windows-opstartlaadprogramma
----------------------------
id {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale nl-NL
inherit {bootloadersettings}
recoverysequence {fa1a7fa1-ab26-11df-bc4f-ce7145d50d35}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
nx OptIn
C:\Windows\system32>

 

[Kaktussoft]

Perform a chkdsk as well, so:
chkdsk /f C:

if C is windows driveletter in recovery environment
check other disks as weel

 

[FreestoneDallas]

in recovery environment go to "command prompt"
Dir C:
Dir D:

what is windows drive letter in recovery environment? So where are windows files located? Assume it's D:
bootsect /nt60 d: /force
bootsect /nt60 d: /force /mbr

bcdedit /enum {bootmgr}
bcdedit /enum {default}

comaands ran succesfully? Please tell me what's listed at device and osdevice line

example:
C:\Windows\system32>bcdedit /enum {bootmgr}
Windows-opstartbeheer
---------------------
id {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale nl-NL
inherit {globalsettings}
default {current}
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 10
C:\Windows\system32>bcdedit /enum {default}
Windows-opstartlaadprogramma
----------------------------
id {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale nl-NL
inherit {bootloadersettings}
recoverysequence {fa1a7fa1-ab26-11df-bc4f-ce7145d50d35}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
nx OptIn
C:\Windows\system32>

Is this what you wanted?

X:\windows\system32>bcdedit /enum {bootmgr}
Windows Boot Manager
--------------------------
ID: {bootmgr}
Device: partition=C:

X:\windows>bcdedit /enum {default}
Windows Boot Loader
--------------------------
ID: {default}
Device: partition=C:

 

[FreestoneDallas]

Perform a chkdsk as well, so:
chkdsk /f C:

if C is windows driveletter in recovery environment
check other disks as weel

It says:

The type of the file system is NTFS.

What other information do you need from that?

 

[Kaktussoft]

Perform a chkdsk as well, so:
chkdsk /f C:

if C is windows driveletter in recovery environment
check other disks as weel

It says:

The type of the file system is NTFS.

What other information do you need from that?

It did check your C-drive for disk errors. Any errors on disk? Fixed succesfully?
you can do a chkdsk /f /r C: as well to check for bad clusters. It will run a few hours

 

[Kaktussoft]

X:\windows\system32>bcdedit /enum {bootmgr}
Windows Boot Manager
--------------------------
ID: {bootmgr}
Device: partition=C:

X:\windows>bcdedit /enum {default}
Windows Boot Loader
--------------------------
ID: {default}
Device: partition=C:

C-drive is your windows drive. So far no problem. DIR C:\ gives you windows files.
bcdedit /enum {default}
should give you a line starting with osdevice. This is partition=C: as well I assume

 

[Kaktussoft]

Are you system files corrupt?

[COLOR=black][B]sfc  /scannow  /offbootdir=c:\  /offwindir=c:\windows[/B][/COLOR]

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[FreestoneDallas]

Are you system files corrupt?

[COLOR=black][B]sfc  /scannow  /offbootdir=c:\  /offwindir=c:\windows[/B][/COLOR]

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

I did this. It says that corrupted files were found but that some of them could not be fixed.

Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

 

[Kaktussoft]

Are you system files corrupt?

[COLOR=black][B]sfc  /scannow  /offbootdir=c:\  /offwindir=c:\windows[/B][/COLOR]

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

I did this. It says that corrupted files were found but that some of them could not be fixed.

Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

Post x:\windows\logs\cbs\cbs.log
and c:\windows\logs\cbs\cbs.log

One of them has the details

 

[Kaktussoft]

from another thread that tells CBS.LOG isn't created in recovery environment:

For future Googlers, I ran into this same problem and was able to solve it: you can redirect the log by using an environment variable. I'm my case, I did

set WINDOWS_TRACING_LOGFILE=C:\TEMP\CBS.log

Before running sfc. Also the recovery console doesn't have findstr, but you can easily use find instead to extract relevant entries from the log, like so:

md C:\TEMP
find "[SR]" C:\TEMP\CBS.log > C:\TEMP\sfcdetails.txt

There, now you have a log! I hope the hours I spent on this help someone else.

 

[Kaktussoft]

Perform a chkdsk as well, so:
chkdsk /f C:

if C is windows driveletter in recovery environment
check other disks as well

no disk errors?

 

[Kaktussoft]

Are you system files corrupt?

[COLOR=black][B]sfc  /scannow  /offbootdir=c:\  /offwindir=c:\windows[/B][/COLOR]

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

I did this. It says that corrupted files were found but that some of them could not be fixed.

Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

So a very crucial file has been damaged. Can you press F8 at startup and boot in "safe mode". Tell me exact what happens.

 

[d 5k1nny g33k]

You may wan to consider using a boot-able disc (Win PE and the like) so that you can scan for viruses if an offline Windows.

You can also try this Beta tool from Windows

Microsoft Standalone System Sweeper Beta | Microsoft Connect

Good luck!