Windows Media Center won't even launch.

[Theg0pher]

I recently tried to use windows media center to connect to my xbox. I've had my hp laptop for over 2 years now and may have never even used WMC. But whenever I try to launch it, the blue wheel next to the mouse pops up for a second and then nothing. Nothing happens at all.

I've tried going to programs and features and turning off both WMC and WMP, restarting, and then re-enabling them. This has done nothing. I've even gone into Windows\ehome and deleted all the files in it and did the disable/enable thing (I did, of course, make a backup of the folder). I looked through the programs and features themselves, hoping to find WMC so I could see if there was a repair option, but it doesn't show up. How can I make WMC work?

 

[kegobeer]

Try creating a new user on your laptop, then try accessing Media Center. Does that work?

 

[Theg0pher]

Nope. Also, Windows Media Center doesn't show up when I search the start bar on the new user, but it does on my normal user account.

Edit: I had to go to windows\ehome and use the ehshell manually, which is where the WMC shortcut leads

 

[kegobeer]

Go to add remove programs and click "Turn Windows features on or off". Look under Media Features and see if Media Center is enabled.

 

[Theg0pher]

I've tried that already. Sorry, when I said I went into programs and features, I meant I went to the windows features and turned it off and then on. Multiple times.

 

[Sardonicus]

Go to Start, Default Programs, Set program access and computer defaults.
Select Custom and make sure that Windows Media Center is enabled (Enable access to this program).

 

[Theg0pher]

It was enabled.

 

[Sardonicus]

It may not help, but........
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

 

[Theg0pher]

Some of the files it couldn't repair, which are in the ehome folder that the WMC files are located:

2012-07-03 00:40:42, Info CSI 000001e1 [SR] Cannot repair member file [l:22{11}]"ehshell.dll" of ehshell, Version = 6.1.7600.16648, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-07-03 00:40:45, Info CSI 000001e3 [SR] Cannot repair member file [l:22{11}]"ehshell.dll" of ehshell, Version = 6.1.7600.16648, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-07-03 00:40:45, Info CSI 000001e4 [SR] This component was referenced by [l:156{78}]"Package_3_for_KB2284742~31bf3856ad364e35~amd64~~6.1.1.0.2284742-14_neutral_GDR"
2012-07-03 00:40:45, Info CSI 000001e7 [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:22{11}]"ehshell.dll"; source file in store is also corrupted


2012-07-03 00:45:12, Info CSI 0000030d [SR] Cannot repair member file [l:22{11}]"ehshell.dll" of ehshell, Version = 6.1.7600.16648, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-07-03 00:45:12, Info CSI 0000031e [SR] Cannot repair member file [l:22{11}]"ehshell.dll" of ehshell, Version = 6.1.7600.16648, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-07-03 00:45:12, Info CSI 0000031f [SR] This component was referenced by [l:156{78}]"Package_3_for_KB2284742~31bf3856ad364e35~amd64~~6.1.1.0.2284742-14_neutral_GDR"
2012-07-03 00:45:12, Info CSI 00000322 [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:22{11}]"ehshell.dll"; source file in store is also corrupted


So yeah. If the source files are also corrupted, what do I do?

 

[redgreen]

Backup and complete a clean install. Consider creating a Ghost image after you have everything back up so that you can always revert to that "clean" state.

 

[boohbah]

hold fire on the complete install,
run sfc scan twice more.
then consider a repair install if the sfc is not helpful.

http://www.sevenforums.com/tutorials/3413-repair-install.html