Windows 7 No Go!!

Amadeus said:

One thing I've learned is there is always an answer. It may ultimately be to reinstall. but, until then there may be something short of that. It is this process that helps my learning. Good thing I have two other computers here :)

Right, but an answer is quite different from a 'solution'.
The solution is the more difficult, and usually gets stonewalled by not knowing exactly what any Windows does, given the circumstances.
MS documentation is pretty good, but the 'nitty-gritty' that I look for is never there.
One has to 'put it together' by observing the behavior and maybe pick up a detail or two, as you're doing now.
Your current process is helping my learning too. (And a few thousand forum readers.)

Here is what I've learned about SFC so far. It hasn't quite worked but I think it is on the right track.
1. I boot up to the screen to [using HDD, not DVD]
2. select the OS (Win 7 in my case), [W7_Real for me]
3. F8 to options,
4. Repair,
5. enter password for Admin.,
6. select command prompt from menu
7. for the C:>. [typing C: to get to partition]
8. for there SFC /scannow /offbootdir=c:\/offwindir=c:\windows

This generates the screen for MS Resource Checker Version 6.0 and all the possible options for use with SFC.

Excellent catch, with the /Off options!

I went ahead and immediately tried this sequence, with a slight mod.
Your 'generates screen' implies a 'window' pops up...
My try had everything in the same DOS-box.

Here's what I got, from my functioning system: (cutting out a lot)

X:\windows\system32>c:

C:\>set
Path=X:\windows\system32;X:\windows;X:\windows\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
SystemDrive=X:
SystemRoot=X:\windows
windir=X:\windows

C:\>diskpart
Microsoft DiskPart version 6.1.7201
DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- ---------
Volume 0 G GRMCULFRER_ UDF DVD-ROM 2384 MB Healthy
Volume 1 C C_NewGW_90G NTFS Partition 88 GB Healthy
Volume 4 F R_W7_Real NTFS Partition 16 GB Healthy
DISKPART> exit
Leaving DiskPart...

C:\>sfc /scannow /offbootdir=F:\ /offwindir=F:\windows

Beginning system scan. This process will take some time.


Windows Resource Protection did not find any integrity violations.

C:\>
C:\>

Took about 5-8 mins, while I grabbed another cuppa..
Note (from SET) that he's booted and using an image file here, too.
What's in core is not the real C:\Windows installation,
and he's executing X:\windows\system32\sfc.exe

No time to experiment further. Each time I enter a new variation it repeats the screen dump of info.

If you got anything other than the above, that should be starting you down the 'fix' path, I believe.
I don't think the other variations are of any importance - you want the 'replace' the bad guys.
Since you say your screen dump shows something, it looks like he's trying (or wanting) to fix something - surely bad system files.
It's my understanding (from XP) that when a bad sysfile is encountered, he copies a good one from the 'Install CD' and puts it into \sys32\cache or something, while also replacing the (bad) \sys32 version...

Let 'er rip and replace. Maybe that'll be the 'solution'.
There just might be a connection between the "chkdsk /r fixup" and your \Win system files.
And remember, you're working with RC_32, I'm working with 7201_32, and others probably got (a free) RTM_64.

Amadeus said:

Thanks. No pop up just bad syntax :) It all appears in one DOS box. The next post shows the results of SFC and running the repair option again. Digging deeper.

A 'quick' one:
Since you're working with the dos-box, thought you might make some use of this:

Command Prompt - Copy to Clipboard

Lotta people didn't know...

Works OK w/boot from .wim image file, so you can cut n paste from dos and

drop it into C:\>notepad <Enter>.... (which gets loaded from X:\ etc.)

Amadeus said:

Was able to run SFC.
Result:
"unspecified changes to system configuration might have caused the problem.
Repair Action: System files integrity check and repair
Result: failed. Error Code=0x490"

This 'looks like' you ran SFC under the auspices of a Repair function, because of the "Repair action" label.

Next ran the Repair function from the DVD.

Try to do only 1 thing at a time, it seems he could get confused when there's more than one 'pending' task, either at Shutdown and/or at Startup.
Have you tried running SFC exactly the same as your first post, shutting down, then boot again from HDD, selecting the Win 7 single entry in BootMgr screen, F8, then Safe mode?
i.e.:

1. I boot up to the BootMgr screen [using HDD, not DVD]
2. Select the OS (Win 7 in my case)
3. F8 for 'Advanced options', *** Didya try SAFE mode after F8 ? ***
4. Select 'Repair computer'.
5. Enter password for Admin.,
6. Select 'Command prompt' from menu.
7. Then type C: to get to prompt C:\> ______v___ = Space in here
8. Then, typing: SFC /scannow /offbootdir=C:\ /offwindir=C:\windows

At this point, he should finish running SFC and end up with the cmd prompt C:\>
What has happened, at this point ? Error msge? the CBS file thing?
(Your results should show what I posted above, in red, if no error msge.)
1. Type EXIT, to leave DOS.
2. Click: Shutdown for full pwr-off. "Restart" might get him confused, or even leave open a possibility for Win7 to goof something up.
3. Boot HDD and try (minimal) Safe-mode, now.

This is after running the MBR suggestion yesterday.

You don't need to do this any more - just the one time yesterday.

------------------------------------------------------------------

This is the result:
"Startup repair cannot repair this computer automatically. (then options to send or not send data to MS).
Problem Signatures:
Event Name: Startup repair offline
Signature 01: 6.1.7100.0
Signature 02: 6.1.7100.0
Signature 03: unknown
Signature 04: 21201225
Signature 05: external media
Signature 06: 5
Signature 07: NoBootFailure
OS Version: 6.1.7100.2.0.0.256.1
Local ID: 1033
Windows Resource Protection found corrupt files but was unable to fix some of them. See the CBS.log file"
Needless to say there is no updated CBS.log file.

I have a: R:\Windows\Logs\CBS\CBS.log, with the latest entries appended to the Bottom of the file.
Unfortunately, all entries are in Microsoft-ese, so that normal people cannot interpret whats in there.
Unless you're a programmer: (Here's the entry for my 02:11 time-mark)

2009-08-27 02:11:55, Info CBS Reboot mark refs incremented to: 1
2009-08-27 02:11:56, Info CBS Scavenge: Starts
2009-08-27 02:11:56, Info CSI 00000009@2009/8/27:08:11:56.044 CSI Transaction @0xdd608 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

2009-08-27 02:11:56, Info CBS Scavenge: Begin CSI Store
2009-08-27 02:11:56, Info CSI 0000000a Performing 1 operations; 1 are not lock/unlock and follow:
Scavenge (8): flags: 00000017
2009-08-27 02:11:56, Info CSI 0000000b Store coherency cookie matches last scavenge cookie, skipping scavenge.
2009-08-27 02:11:56, Info CSI 0000000c ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
2009-08-27 02:11:56, Info CSI 0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
2009-08-27 02:11:56, Info CSI 0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x1fc
2009-08-27 02:11:56, Info CSI 0000000f@2009/8/27:08:11:56.832 CSI perf trace:
CSIPERF:TXCOMMIT;289271
2009-08-27 02:11:56, Info CBS Scavenge: Completed, disposition: 0X1
2009-08-27 02:11:56, Info CSI 00000010@2009/8/27:08:11:56.841 CSI Transaction @0xdd608 destroyed
2009-08-27 02:11:57, Info CBS Reboot mark refs: 0
2009-08-27 02:11:57, Info CBS Idle processing thread terminated normally
2009-08-27 02:11:57, Info CBS Ending the TrustedInstaller main loop.
2009-08-27 02:11:57, Info CBS Starting TrustedInstaller finalization.
2009-08-27 02:11:57, Info CBS Ending TrustedInstaller finalization.

------------------------------------------------------------------
Now I have to say a few words about my opinion of the MS Win7 'Recovery' process, on my computer.
My computer is 100% functional with ALL Win7 installations, save for the 2 USB entries, which are specifically for testing bootup from USB HDD/Thumbdrive.
And, I have a COPY of the R:\Windows directory, specifically for testing, and does not show on the BootMgr startup screen.
Here is his proposed fix:
(Ran this afternoon, specifically to paste here)

The following startup option will be repaired: __100% OK
Name: Windows Boot Manager
Identifier: {9DEA862C-5CDD-4E70-ACC1-F32B344D4795}

The following startup options will be deleted:

Name: Hana - Win7E_J.vhd <--- 100% OK, vhd boot
Identifier: {66CA788F-3A3C-11DE-AB10-9155F4246F0C}
Windows Device: Partition=Not found

Name: Boulders - Win7_I.vhd <--- 100% OK, vhd boot
Identifier: {66CA7895-3A3C-11DE-AB10-9155F4246F0C}
Windows Device: Partition=Not found

Name: USB Hammer_2 - NG <--- USB HDD boot testing
Identifier: {8FA6F7BE-4D09-11DE-A025-0015581F6A93}
Windows Device: Partition=Not found

Name: USB (Q: ) - NG <--- USB stick boot testing
Identifier: {66CA7899-3A3C-11DE-AB10-9155F4246F0C}
Windows Device: Partition=Not found


The following startup options will be added:
Name: Windows 7 Ultimate (recovered)
Path: Win_7I_copy\Windows <--- Copy, for testing
Windows Device: Partition=D: (78269 MB)

A copy of the current boot configuration data will be saved as: C:\Boot\BCD.Backup.0002

I can understand the 2 USB entries, because there's no HDD or 'stick' plugged in.
I can understand him wanting to add-in my "Copy-for-tesing",
But, I believe the MS "Fixer-upper" has -no clue- about his own MS .vhd installations.
Could be some surprised people if they allow "Automatic Repair" of their computer!!!

c:\windows\logs\recoverydisk\ and c:\windows\logs\systemrestore - is there any help in these?

I don't have the \recoverydisk\ folder.
My \systemrestore\ folder has 4 files in it, RestoreUI.0.etl through ~.3.etl
They're compressed, quite tightly.
These may be the ones he can't find, to 'restore' to a previous time...
OTOH, they might not...

Amadeus said:

Chuck, FWIW, attached is the CBS.log file when I try running SFC from X:\ after booting into the HDD.
Looks like the failure SxS and a failed send of an error file to MS might be part of the problem. Thoughts?
Mike

This is all Guess and Opinion, no official blessings from Anybody.
Had a look, couldn't get much.
I doubt the 'send to MS' has anything to do with the error, therefore all lines with "SQM:" can be ignored.
You either phone-home or not, and I believe that the 'flag' Windows opt-in being cleared to 'False'
(since you opted for NoSend) lets him do a little 'garbage-collection' and end with a "Warning", not an Error.
Warning being, he didn't phone-home.

The real error, I believe, begins at:

CBS ** Failed to load SxsStore.dll [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND] <===<
CBS ** Failed to initialize SxS. [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND]

and this is probably because of the X:\ .wim winimage thing, a few posts prior.
Having no idea of what CBS or CSI are, or what they do, I would guess that the SFC is actually these sw modules
(Almost has to be - theres no SFC anywhere in there)

I notice that it took 10 minutes (while he was theoretically doing something) between the major log entries.
Did it, in fact, take about 10 minutes for the ordeal? Just for info...

There's other 'bits and pieces' in there, like disabling registry and kernel stuff,
time-stamps as local, but entries are GMT, etc. but nothing really important.

So, you're back to Square-1:
All conventional wisdom says 'Clean install', get back on the air.
You were thinking 'partition and fresh-install', for possibly (but not necessarily) learning more about the original problem.
I really don't know if one w7 install can "Check/Verify/Troubleshoot" a different, idle w7 install.
Maybe somebody can say...

It just seems strange that what was supposed to fix a problem (chkdsk /r) actually created the real problem.
Was this the w7 chkdsk, or run from a Hirens CD, BartPE, etc ???
Just read something that said they're different.
Strikes me as a magnetic media problem...

When you boot BartPE, can you see, and access 'folders', and files (Rclk, Properties) ???

Another alternative, and probably the best, is to go for a thorough "HDD scrub", then reinstall, here:

Hard Drive MBR Corrupt

(saving your data first, of course.)

Where's all the other guys? No opinions, options, info?
Can one live w7 install, check another 'dead' installation, on the same HDD?