this is so frustrating - whenever i run SFC and restart, everything comes back up as it should - aero and all, basic view is gone and everything's fine.
if i shut down or restart w/o SFC, it'll start windows with the yucky basic view.
any idea how i can find out what's causing this? cuz the SFC finishes the scan with "did not find any integrity violations".
hi sometimes you have to run the scan a few times even though windows does not tell you all it does it does hidden repairs check your aero settings graphic card driver etc.
ok i found the corrupt file in SFC:
C:\Windows\Resources\Themes\aero"\[l:26{13}]"aero.msstyles"; source file in store is also corrupted
do i replace it?
does this mean the "aero" feature is ****ed up?
nope. here's the log:
2010-12-18 13:32:46, Info CSI 000001aa [SR] Verify complete
2010-12-18 13:32:46, Info CSI 000001ab [SR] Repairing 1 components
2010-12-18 13:32:46, Info CSI 000001ac [SR] Beginning Verify and Repair transaction
2010-12-18 13:33:22, Info CSI 000001ad [SR] Cannot repair member file [l:26{13}]"aero.msstyles" of Microsoft-Windows-aero, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-12-18 13:33:42, Info CSI 000001ae [SR] Cannot repair member file [l:26{13}]"aero.msstyles" of Microsoft-Windows-aero, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-12-18 13:33:42, Info CSI 000001af [SR] This component was referenced by [l:238{119}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~6.1.7600.16385.Microsoft-Windows-Client-Features-Update"
2010-12-18 13:34:06, Info CSI 000001b0 [SR] Could not reproject corrupted file [ml:520{260},l:72{36}]"\??\C:\Windows\Resources\Themes\aero"\[l:26{13}]"aero.msstyles"; source file in store is also corrupted
2010-12-18 13:34:06, Info CSI 000001b1 Repair results created:
POQ 82 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\cb36a17aa79ecb0129240000a808bc04._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\3f48a27aa79ecb012a240000a808bc04.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:216{108}]"\SystemRoot\WinSxS\Temp\PendingRenames\920ba37aa79ecb012b240000a808bc04.$$_resources_fbee56ab048ab2 39.cdf-ms", Destination = [l:128{64}]"\SystemRoot\WinSxS\FileMaps\$$_resources_fbee56ab048ab239.cdf-ms"
3: Move File: Source = [l:230{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\f6f5a37aa79ecb012c240000a808bc04.$$_resources_themes_4d0d491 0e83c2273.cdf-ms", Destination = [l:142{71}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_4d0d4910e83c2273.cdf-ms"
4: Move File: Source = [l:240{120}]"\SystemRoot\WinSxS\Temp\PendingRenames\cfacaa7aa79ecb012d240000a808bc04.$$_resources_themes_aero_3f d78bf4cb5fa2c4.cdf-ms", Destination = [l:152{76}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_3fd78bf4cb5fa2c4.cdf-ms"
POQ 82 ends.
2010-12-18 13:34:06, Info CSI 000001b2 [SR] Repair complete
2010-12-18 13:34:06, Info CSI 000001b3 [SR] Committing transaction
2010-12-18 13:34:06, Info CSI 000001b4 Creating NT transaction (seq 2), objectname [6]"(null)"
2010-12-18 13:34:06, Info CSI 000001b5 Created NT transaction (seq 2) result 0x00000000, handle @0x1d84
2010-12-18 13:34:07, Info CSI 000001b6@2010/12/18:11:34:07.035 CSI perf trace:
CSIPERF:TXCOMMIT;603131
2010-12-18 13:34:07, Info CSI 000001b7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
im trying to find the answer for you will ask another guru for you try and run the scan again but this time put your windows disc in the drive but dont start it run the scan after the disc is in.
you could try this How to Do a Repair Install to Fix Windows 7 tutorial by brinkRepair Install
i have an "windows.old" folder, since i upgraded to 7 Ultimate from 7 Starter.
Could a clean version of the corrupt file be there? should i try to replace it?
Quote