New
#41
Attachment 264474
Sorry, I had to put it in a .zip file. Otherwise it exceeds the .txt file size limit.
This is all I found:
00003e0a [SR] Beginning Verify and Repair transaction
00003e0b [SR] Cannot repair member file [l:20{10}]"Garden.jpg" of Microsoft-Windows-Mail-App, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
00003e0c [SR] Cannot repair member file [l:20{10}]"Garden.jpg" of Microsoft-Windows-Mail-App, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
00003e0d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
00003e0e [SR] Could not reproject corrupted file [ml:520{260},l:122{61}]"\??\C:\Program Files\Common Files\Microsoft Shared\Stationery"\[l:20{10}]"Garden.jpg"; source file in store is also corrupted
00003e10 [SR] Verify complete
00003e11 [SR] Repairing 1 components
00003e12 [SR] Beginning Verify and Repair transaction
00003e13 [SR] Cannot repair member file [l:20{10}]"Garden.jpg" of Microsoft-Windows-Mail-App, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
00003e14 [SR] Cannot repair member file [l:20{10}]"Garden.jpg" of Microsoft-Windows-Mail-App, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
00003e15 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
00003e16 [SR] Could not reproject corrupted file [ml:520{260},l:122{61}]"\??\C:\Program Files\Common Files\Microsoft Shared\Stationery"\[l:20{10}]"Garden.jpg"; source file in store is also corrupted
00003e18 [SR] Repair complete
=============
So only Garden.jpg (a jpeg picture) used as staionary for windows mail is missing. Not important at all! You most likely never use that stanionary at all. And is is definitely not the cause of boot problems.
No, I do not use it. I didn't even know it was there to begin with.
You can copy Garden.jpg from a working machine form folder C:\Program Files\Common Files\Microsoft Shared\Stationery
put on stick and copy to C:\Program Files\Common Files\Microsoft Shared\Stationery on sick machine.
sfc command will fix the problem then. run sfc again and no more errors.
start repair only fixes 1 error at a time. But since sfc check is the last test startup repair does... repairing the sfc problem doesn't force it to check more things.
So .. "startup repair" actually finds no errors. And that's correct.... system is actually booting.
What happens exactly if you try booting to "safe mode"? You see all drivers loading (ending with CLASSPNP.SYS)? You see login screen? You can enter username/password? What happens next. Please exactly
"The system cannot find the path specified.Code:copy "e:\garden.jpg" "c:\programfiles\commonfiles\microsoftshared\stationary"
0 file(s) copied."
I'm doing something wrong again.
Found my problem. Spelling error...[/facepalm]
Now with the sfc command, do I use "verifyfile" or another command?
unmountable boot error 0x000000ED. This was the initial problem. But did startup repair fix it. Or chkdsk? You didn't take notice of what it did fix... we don't know what was wrong. Volume C has some severe errors... most likely fixed by chkdsk (startup repair does [almost] the same).
startup repair=>no errors anymore (except sfc)
chkdsk=>disk is fine now
sfc gives only 1 problem.... not related to boot problems. System actually boots fine until logon.
Did you try to logon as another user already?
I only have one user on there, except for the Guest account (which is disabled).