TheGreenButton - Windows Media Center Forums

Media centre is not starting for me. I click the Green Button and I get a blue circle spinning briefly and then nothing. I have installed, uninstalled and reinstalled WindowsMediaCenter_10.0.10134.0v2.1. It was working prior to the latest MS Updates. Any suggestions?
Thanks.

Same happened for me. Probably not the answer you're looking for but it does work with a fresh install of 1703.

Uninstall the software (Windows Media Center) by right click the Uninstaller.cmd script and selecting “Run as administrator”.

After removing windows media center, go to C:\ProgramData\Microsoft\ and delete the eHome folder for a complete removal. NOTE: The ProgramData folder is a hidden folder so when you go the “C” Drive, click on “View” on top of the menu and click on “Options” that is located to the far right. A “Folder Options” window will open and click on View in that window. Select the “Show hidden files, folders, and drives” and click “OK”. Now you will be able to see the ProgramData folder in the “C” drive.

Reinstall the Windows Media Center v12 and voila.

Hope this helps.

Kusaywa, you mean uninstall 1703 and reinstall it and wmc will work?

Kusaywa wrote:Same happened for me. Probably not the answer you're looking for but it does work with a fresh install of 1703.

Interesting. Does DRM/Playready work too?

question on this version 1703 that messed up my wmc,,,,,,if I were to go back to version 1605 ?I think, would that solve the problem with wmc,,, it worked in that version well, and there is a way to go back????????

http://www.thewindowsclub.com/rollback- ... ors-update

pnielsen1@gmail.com wrote:Media centre is not starting for me. I click the Green Button and I get a blue circle spinning briefly and then nothing. I have installed, uninstalled and reinstalled WindowsMediaCenter_10.0.10134.0v2.1. It was working prior to the latest MS Updates. Any suggestions?
Thanks.

Sounds like you don't have a CableCard Tuner...WMC should work fine with any other tuner....

Download V8.8.1 and run the uninstaller to remove all traces of v2.1.

Also delete the 2 ehome folders previously suggested.

Then install v8.8.1

Read everything on this page...including the links...

https://forums.mydigitallife.net/thread ... ves.61061/

Hi Crash

I took window new version 1703 back to the version 1607 I had yesterday,,,,,,,,,,,the I uninstalled the wmc and reinstalled it, BUT it would not install the green skin, so I uninstalled the green skin and did a restart and installed the blue skin

IT WORKS, ,,,,,,,,,,,now to keep the new version 1703 from loading agian

dojo wrote:Hi Crash

I took window new version 1703 back to the version 1607 I had yesterday,,,,,,,,,,,the I uninstalled the WMC and reinstalled it, BUT it would not install the green skin, so I uninstalled the green skin and did a restart and installed the blue skin

IT WORKS, ,,,,,,,,,,,now to keep the new version 1703 from loading agian

Disable Updates

Works for me!, I reinstalled wmc v12 (green Button) on Windows 10 1703! Thanks a lot!

I was on version 10.... uninstalled, then installed v12. now it works on 1703

Version 1703 aka Creators Update broke all my 5 WMC installs. Solution, regardless of original version, was to simply uninstall using Uninstaller.cmd and clean up ehome then install V8.8.1 [V12.7 for the sole x86 OS]. I guess this will be an ongoing saga until M$ gets bored with spitefully trying to stop us using something they don't want anymore.

So, you guys have gotten the creators update to now work with a Prime cable card tuner? I'm stuck at 1511 10586.494 because it works and I locked out updates. Lately I keep getting nag screens that I need to update and I finally just told it to download to see what would happen but because I hard locked it out it then refused to download them and everything has stayed the same. Would be nice to update if it is now going to work but wont touch it if it isn't true.

I have tried all the solutions described above, including removing ehome folder, but now when I run the installer for WMC v12 I get this

An error occurred - Microsoft-Windows-MediaCenter-Package Error: 0x800f0922

Error: 0x800f0922

Any ideas how to get past this? I have tried rebooting.

The suggestions in Post Number 7 should fix yours as well

I have noticed the last few weeks sometimes my WMC will not start,,,,,,,,if i restart the computer it comes back on. Why i have no idea.

Even more strange for me. But as it is that strange I open another topic.

Grandpa Clyde wrote:I have tried all the solutions described above, including removing ehome folder, but now when I run the installer for WMC v12 I get this

An error occurred - Microsoft-Windows-MediaCenter-Package Error: 0x800f0922

Error: 0x800f0922

Any ideas how to get past this? I have tried rebooting.

0x800f0922 Means you have a broken windows. here is how to fix it

https://forums.mydigitallife.net/thread ... st-1380859

after you fix windows you might as well get the most recent version

Go get version v8.8.1
Use the v8.8.1 to uninstall whatever you have
then install v8.8.1

Go to this link and read a bit

https://forums.mydigitallife.net/thread ... st-1244333

Read the Readme file in the v8.8.1 install files

dxrnn wrote:Uninstall the software (Windows Media Center) by right click the Uninstaller.cmd script and selecting “Run as administrator”.

After removing windows media center, go to C:\ProgramData\Microsoft\ and delete the eHome folder for a complete removal. NOTE: The ProgramData folder is a hidden folder so when you go the “C” Drive, click on “View” on top of the menu and click on “Options” that is located to the far right. A “Folder Options” window will open and click on View in that window. Select the “Show hidden files, folders, and drives” and click “OK”. Now you will be able to see the ProgramData folder in the “C” drive.

Reinstall the Windows Media Center v12 and voila.

Hope this helps.

Thanks dxrnn, after the Creators Update I could not run WMC, it would just change the pointer to an hourglass for a split second, but would not start. I had already tried uninstalling and reinstalling to not avail, but with your added step of removing the folder, it now works.

Tim