Hey Guys. I'm still running version 6.3.9600.16384 on my 64bit machine and the same 32bit version on my HTPC. Haven't screwed with either since they've been running well. That is, with the exception of being able to use either as an extender for my XBox 360 or having the ability to watch HBO. Both are running off a HDHomerun Prime. Still try to keep up on the thread, in case anything changes, but haven't seen any entries suggesting that one or both of these issues have been resolved with V.11. Seems the HBO thing is hit and miss, but would really like to get that working. (Winter is coming, ya know) Has V.11, or even V.10, fixed these issues?
hi guys ... I install v 11 ... and work good ... when press record bottom to record live channel but do not ant thing and don't record .....
That's the way good since w311 to start any program. But there is also a more drastic way: use WMC as shell. In that way explorer (windows explorer) will be replaced by ehome as the default shell, and you will gain memory and a faster boot time. But then you have to use the task manager to launch the file explorer and you will loose the taskbar, the start menu, the systray and any other stock shell item. This method is clearly the preferred one for low powered HTPCs fully dedicated to WMC and little more (eg file server, ftp server...) Just replace explorer.exe with C:\Windows\ehome\ehshell.exe here HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon\Shell and reboot. For the record you can use almost whatever you want as shell, say the task manager, the progrman.exe from nt 3.51/NT4, or just cmd.exe or powershell for a minimalist approach. The more adventurous users can even experiment with KDE, GNOME and other Linux shells, to get a linux gui and a windows kernel.
OK, here is the solution to the wake up for recordings - it works perfectly in sleep mode or after a reboot/shut down. The Network Service to the Administrator Group thing is a HUGE security risk and a bad idea. 1) Right-click the Windows start button in the lower left of your desktop. 2) Select Run. 3) Under Open: type "services.msc" (without quotes) 4) Scroll down to the "Windows Media Center Receiver Service". 5) Right-click the service and select "properties". Alternatively, you may double-click it. 6) Under the General tab, change the Startup type from Manual to Automatic. 7) Under the Log On tab, change the "Log on as:" radio button to Local System Account. Leave the "Allow service to interact with desktop" box unticked. 8) Select "Apply" at bottom. You will be prompted that you need to stop and restart the service. Right-click the service, select Stop. Right-click it again, select Start. 9) Go to the "Windows Media Center Scheduler Service" and repeat steps 5-8. 10)Close out the Services window. That's it. You're done. I would like to see this added to the Workaround.txt file if everyone finds that it works for them, replacing the Network Service to Administrator Group instructions. It works for me consistently. I'm using Windows 10 OS Build 10586.36 x64 at the moment. This is a stand-alone PC, not networked, running OTA broadcasts. If you're networked, you may need to play around with the login type in step 7. Otherwise, everything else is the same.
There's an even better fix that doesn't even require giving more permissions to the receiver service: forums.mydigitallife.net/threads/61061-DISCUSSION-Patch-WMC-to-run-on-Windows-10-final-amp-possible-alternatives/page296?p=1192012#post1192012
It's not so much giving it any more permissions, it's just changing the properties. Having the services start automatically is not harming anything. It's works well for me, so I'm sticking with it.
You are giving it more permissions. Network service is a very limited account. If you change it to the Local system account, you're basically giving it Godlike permissions. SYSTEM has even more permissions than local administrators. The change you're proposing is overkill compared to just fixing the ACLs on the tasks so that the service can do its job.
edechamps - thanks for all your recent input. As you can tell, I'm kind of supporting your position in regards to Network Services and hoping a v12 installer could be built to follow your suggestions. Is there a potential issue with PlayReady with your install scenario? Or was I misunderstanding something about that portion of the conversation? Still hopeful a v12 installer could be created based on your findings for new installs.
I don't know what the deal is with PlayReady when doing a clean DISM-only install as described in my post. I don't use PlayReady so I don't really care. Furthermore I don't have a test system anymore (I was doing these investigations for my parents' system when I was there), so I can't really help with anything.
Gentlemen,,, I simply like to have my emc as I use to in my win7,, is it realy no other way forward than to read 300+ forum pages and still not be 100% able to run wmc ??.... if so it is very depressing and calls for a serious talk to Bill Gates.. Its like the car manufacturer suddenly exclude the 4th Wheel and requests me to invent it,,, plain stupid.
I have 6 machines to update, and I guarantee you, each one will have its own individual hiccup to deal with.
Please can you help me I've intalled WindowsMediaCenter_6.3.9600.16384_x86_v10 the installation work but I Cannot access my c:\ProgramData directory Can you help me? Any IDEA?
c:\ProgramData is a hidden folder. Open file explorer click C:\ type Program Data File Explorer will remember ProgramData next time you return.