Windows Not Booting

[Kaktussoft]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

Also do:

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

Post results

 

[MamuMogambo]

So Partition 2 Primary 71GB 101MB is ACTIVE?? Very sure?
Why do you have a 100MB partition that is normally used for bootmanager and bootmenu?
Give me drive letters of partition 3 and 4 as well

It was created by Windows during the installation.
Also, (this is completely unrelated) during my last Windows installation I had my to-be Windows partition boot table as GPT and had to change to MBR using bootable ISO of Partition Wizard)

 

[MamuMogambo]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

Windows found no problems in C: but there's also a statement "Failed to transfer logged messages to the event log with status 50

 

[MamuMogambo]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

In D: Windows discovered free space marked as allocated in the volume bitmap.
Windows made corrections to the file system.
Also "Failed to transfer..............status 50"

 

[MamuMogambo]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

Windows found no problems in E: and F: but again
"Failed..................status 50"

 

[Kaktussoft]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

In D: Windows discovered free space marked as allocated in the volume bitmap.
Windows made corrections to the file system.
Also "Failed to transfer..............status 50"

"Failed to transfer..............status 50" is normal in recovery environment! it wants to log the stuff in eventlog but eventlog service isn't running. test D again. No errors anymore?

 

[MamuMogambo]

chkdsk/f  c:
chkdsk/f  d:
chkdsk/f  e:
chkdsk/f  f:

No errors? all repaired? If repaired... run it again to be sure no more errors.

In D: Windows discovered free space marked as allocated in the volume bitmap.
Windows made corrections to the file system.
Also "Failed to transfer..............status 50"

"Failed to transfer..............status 50" is normal in recovery environment! it wants to log the stuff in eventlog but eventlog service isn't running. test D again. No errors anymore?

I will scan D: again but i am running the sfc right now. It'll take time. I will post back just after the scan.
And thank you for all the help you are providing. I am really grateful

 

[MamuMogambo]

sfc results:
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

 

[MamuMogambo]

I scanned D: again and found no problems

 

[Kaktussoft]

bcdedit

Do you see this?

Windows-opstartbeheer
---------------------
id                      {bootmgr}
device                  boot [B](can be C as well)[/B]
path                    \bootmgr
description             Windows Boot Manager
locale                  nl-NL [B](your language)[/B]
default                 {default}
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]
displayorder            {default}
timeout                 10 [B](can be another value, not important)[/B]
Windows-opstartlaadprogramma
----------------------------
id                      {default}
device                  partition=C: [B](can be boot as well)[/B]
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium [B](not important)[/B]
locale                  nl-NL [B](your language)[/B]
recoverysequence        {current}
recoveryenabled         Yes
osdevice                partition=C: [B](can be boot as well)[/B]
systemroot              \Windows
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]

 

[MamuMogambo]

bcdedit

Do you see this?

Windows-opstartbeheer
---------------------
id                      {bootmgr}
device                  boot [B](can be C as well)[/B]
path                    \bootmgr
description             Windows Boot Manager
locale                  nl-NL [B](your language)[/B]
default                 {default}
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]
displayorder            {default}
timeout                 10 [B](can be another value, not important)[/B]
Windows-opstartlaadprogramma
----------------------------
id                      {default}
device                  partition=C: [B](can be boot as well)[/B]
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium [B](not important)[/B]
locale                  nl-NL [B](your language)[/B]
recoverysequence        {current}
recoveryenabled         Yes
osdevice                partition=C: [B](can be boot as well)[/B]
systemroot              \Windows
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]

yes I see this
but a few things are different

 

[Kaktussoft]

sfc results:
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

Set the variable for the log file, so SFC doesn't attempt to store to log to the read-only media:

set  WINDOWS_TRACING_LOGFILE=F:\CBS.log

Run SFC with offline parameters:

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

Once that command has finished, its output should be logged to F:\CBS.log, or wherever else you specified.
So to pull the errors out of the file, run:
if you want that output to go to a file instead, run:

find /i  "[SR]"  F:\CBS.LOG > F:\sfcdetails.txt

Now your details regarding the failed repairs should be contained in F:\sfcdetails.txt

Transfer F:\sfcdetails.txt to an usb stick and post it here. Afterwards you can delete F:\sfcdetails.txt and F:\CBS.log

This shows what's in it

notepad  F:\sfcdetails.txt

 

[MamuMogambo]

Values that are different
1. path \bootmgr (I don't see this code)
2. inherit {bootloadersettings} (I have this extra line)

 

[Kaktussoft]

bcdedit

Do you see this?

Windows-opstartbeheer
---------------------
id                      {bootmgr}
device                  boot [B](can be C as well)[/B]
path                    \bootmgr
description             Windows Boot Manager
locale                  nl-NL [B](your language)[/B]
default                 {default}
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]
displayorder            {default}
timeout                 10 [B](can be another value, not important)[/B]
Windows-opstartlaadprogramma
----------------------------
id                      {default}
device                  partition=C: [B](can be boot as well)[/B]
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium [B](not important)[/B]
locale                  nl-NL [B](your language)[/B]
recoverysequence        {current}
recoveryenabled         Yes
osdevice                partition=C: [B](can be boot as well)[/B]
systemroot              \Windows
resumeobject            {9dc4384c-ed0f-11e1-a017-806e6f6e6963} [B](you have another value. not important now)[/B]

yes I see this
but a few things are different

Tell me the differences

 

[MamuMogambo]

sfc results:
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

Set the variable for the log file, so SFC doesn't attempt to store to log to the read-only media:
set WINDOWS_TRACING_LOGFILE=F:\CBS.log

Run SFC with offline parameters:
sfc /scannow /offbootdir=c: /offwindir=c:\Windows

Once that command has finished, it's output should be logged to F:\CBS.log, or wherever else you specified.
So to pull the errors out of the file, run:

findstr  /c:"[SR]"  F:\CBS.log

This will output all error lines to the command prompt, if you want that output to go to a file instead, run:

findstr  /c:"[SR]"  F:\CBS.log > F:\sfcdetails.txt

Now your details regarding the failed repairs should be contained in F:\sfcdetails.txt

Transfer F:\sfcdetails.txt to an usb stick and post it here. Afterwards you can delete F:\sfcdetails.txt and F:\CBS.log

This shows what's in it

notepad  F:\sfcdetails.txt

Will do this after the scan completes

 

[Kaktussoft]

Values that are different
1. path \bootmgr (I don't see this code)
2. inherit {bootloadersettings} (I have this extra line)

1 is in my code!! Look again.
inherit is not source of problem.

Please post C:\Windows\System32\LogFiles\Srt\SrtTrail.txt as well

 

[MamuMogambo]

when I type findstr /c:"[SR]" F:\CBS.log I get that this is not a recognized internal or external command

 

[MamuMogambo]

C:\Windows\System32\LogFiles\Srt\SrtTrail.txt
I am getting no error in this

 

[Kaktussoft]

when I type findstr /c:"[SR]" F:\CBS.log I get that this is not a recognized internal or external command

try to use:

find /i  "[SR]"  F:\CBS.LOG > F:\sfcdetails.txt

dir  C:\Windows\System32\LogFiles\Srt\SrtTrail.txt

Realy no SrtTrail.txt?

 

[MamuMogambo]

when I type findstr /c:"[SR]" F:\CBS.log I get that this is not a recognized internal or external command

try to use:

find /i  "[SR]"  F:\CBS.LOG > F:\sfcdetails.txt

file not found