I'm still installing the August 2015 HDHomeRun package for WMC - not any of the "DVR" beta firmwares. That continues to work fine. The link is just to a Windows Store/Metro app for viewing content. It doesn't break anything, it just doesn't work with anything other than ClearQAM channels (encrypted channels return only black screens).
Is there any way to remove the RDP patches from the latest 8.8.1 installer? I'm pretty sure it's breaking my ability to Remote Connect (just get a black screen that I can't do anything with), plus I prefer Windows Media Center to kick out when my other computer connects.
Nope, WMC is full screen (usually sitting at the guide screen) though. When I connect, I just see a black screen and can alt-tab to see WMC on the taskbar, but it refuses to let me see the desktop. So I kind of just get stuck at this point. Before, with the old installers, WMC would just force close and tell me it's not allowed over RDP, which was preferable for me heh.
This is normal if you're in full screen mode, just use actual multiple monitor and /or the maxifier to solve the problem Anyway just replace ehshell.dll and Microsoft.MediaCenter.UI.dll with the unpatched ones if you really want to get rid of this useful feature
and, if you dont want to get rid of it, but prefer to workaround it, you can also click the restore button for WMC from your Remote Desktop Connection. Restore button is invisible, but it is there...
I also get the black screen post hibernation wake up and I can't do anything but reset the PC, Al-F4 doesn't work. I'm using v12 x64 WMC non-anniversary build
I don't have an always on system and I need it to wake when I have scheduled recordings, and I don't have issues with it waking to do a recording. 99% of the time it's fine.
WMC may be fixed, but sometimes the fix is in the bios, or in the OS. It depends how they screwed it up. Oh, I see what you are saying .....did you integrated the fix in the link I posted?
On a real WMC mcupdate_scheduled and StartRecording tasks aren't part of the installation, they are created by WMC itself (or one of the other tasks), this doesn't happen on W10, likely because one of the involved users doesn't have the rights to create new tasks. Hence the two tasks were exported and integrated like all the other 21 tasks, but this way they lacked the ACL infos. The fix consist just in using the same ACLs as the other 21 tasks for the remaining two.