I apologize for getting everyone worked up here, it appears that it was all user error on my part! After a clean install of windows, everything is back to working normally. My problem started when my WMC told me it couldn't find any tuners when my HDHomeRun was working just fine. I jumped the gun and tried to reinstall the patched WMC, when I should have read the "Work Arounds" file and attempted the fix for my problem first. After a few failed uninstalls and reinstalls, I had my system completely jacked up. Anyway, thank you guys for the help!
I rebooted. WMC working fine. Only my taskbar icons were wiped. I am using StartIsBack++ 1.3.1. Just had to place back all my taskbar icons.
Is this with v8.6 on 10586? This has been working for me for a while on the insider builds with x86 v12. It does not work for me on 10586. I tried your suggestion of installing Windows N and then using Total Uninstall and creating a backup of the Media Feature Pack install. And then installing that on an insider build, unfortunately no Windows N insider builds that I can find. And unfortunately this made no difference on WMC being able to setup a HDHomerun Prime. I did notice that msdri.dll was present in my install of Windows N before installing the Media Feature Pack. According to procmon, msdri.dll is loaded when playing live tv and setting up a HDHomerun Prime on a working machine. On the insider builds, using procmon I can see ehrecvr. exe successfully querying the HDHomerun, but somewhere after that it obviously fails. I'm curious to find out if the other cablecard tuners work on the insider builds.
Edit Local Group Policy to Enable Ceton Echo Extender I was all over Local Group Policy Editor...At least in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\ All of my experimental changes did not effect the Ceton Echo Extender in any way...Positive nor Negative. A little farther down the list...in the User Configuration\Windows Components\Remote Desktop Services. This area looks a little more promising. For one, the components in this list look very similar (if not the same) as Windows 7. A little digging in here has revealed that MY Win10\Mcx2-WIN10 is actually using this area. Over in Event Viewer it appears that Local Group Policy\User Configuration\Windows Components\Remote Desktop Services makes Policy for Event Viewer's TerminalServices-LocalSessionManager I am going to try a few changes in here and see what the results are...if any. Likely the Registry has the same confusing naming convention. I may be totally incorrect on this one but it appears Local Group Policy\User Configuration\Windows Components\Remote Desktop Services is a component of Server 2008.....and Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services is a component of Server 2012 Does Local Group Policy actually change anything? What is it's purpose?
SSDP (udp 1900) Can different things share UDP Ports? Just noticed in the registry Inbound rule for Wireless Portable Devices to allow use of the Simple Service Discovery Protocol. [UDP 1900] As I recall 3rd party extenders need SSDP (UDP 1900) Answered my own question. Port 1900 is used for UPnP send and receive. so there could be a lot of devices on the network that use it. There it is again (in the 3rd picture) Wireless Portable Devices using the same port (TCP 2869) Firewall Port Settings Application Protocol/port Direction Network svchost.exe UDP 1900 In Local Subnet svchost.exe UDP 1900 In Local Subnet svchost.exe TCP 2177 Out, In Local Subnet svchost.exe UDP 2177 Out, In Local Subnet system TCP 10244 Out, In Local Subnet ehshell.exe TCP 554 Out, In Local Subnet ehshell.exe UDP 5004, 5005 Out, In Local Subnet ehshell.exe TCP 8554-8558 Out, In Local Subnet ehshell.exe UDP 5004, 5013 Out, In Local Subnet ehshell.exe UDP 7777-7781 Out, In Local Subnet mcrmgr.exe Random Out, In Internet mcx2prov.exe Random Out, In Internet
Ceton Echo Firewall Errors Not sure if it makes a difference. I think I might have found a mistake. Firewall Port Settings Application Protocol/port Direction Network svchost.exe UDP 1900 In Local Subnet svchost.exe UDP 1900 In Local Subnet svchost.exe TCP 2177 Out, In Local Subnet svchost.exe UDP 2177 Out, In Local Subnet system TCP 10244 Out, In Local Subnet ehshell.exe TCP 554 Out, In Local Subnet ehshell.exe UDP 5004, 5005 Out, In Local Subnet ehshell.exe TCP 8554-8558 Out, In Local Subnet ehshell.exe UDP 5004, 5013 Out, In Local Subnet ehshell.exe UDP 7777-7781 Out, In Local Subnet mcrmgr.exe Random Out, In Internet mcx2prov.exe Random Out, In Internet The suggested setting is ehshell.exe UDP 5004, 5013 Out, In Local Subnet One rule for in and another for out. No mention of UDP 50004-50013 Inbound rule for Media Center Extenders to allow WMDRM-ND and RTP/RTCP AV Streaming. [UDP 7777-7781, UDP 5004-5005, UDP 50004-50013] and the Outbound Rule (Outbound rule for Media Center Extenders to allow WMDRM-ND and RTP/RTCP AV Streaming. [UDP]) has no ports specified. Picture 47 is a list of all my Extender Rules in the Firewall. I would imagine the Echo installer added a couple. Picture 48 is Ceton Echo in the registry
Well looky there... Here is the T-S install... Entry Points.... DAFUPnPProvider.... Renderer.... Generic Software Device....
who can explain this win 10 pro with wmc working scannow and restorehealth both fail BUT have working wmc on enterprise 10 2016 restorehealth wont work but sfc /scannow works great both updated to 494 ?
Try w8.6 if it works well for you just stay with it (no dism hassles at all), if instead has something that doesn't work for you, uninstalling it will clean your system making it V12 ready
I asked a question a while back regarding sfc /scannow and dsim returning error on W10 with WMC installed (v12) for me. It would make sense these would fail as these utility do not have the info of where the original files are. So I am curious if DSIM can in fact works in that configuration (once WMC is installed) Note: Although sfc and DSIM fail, WMC is running just fine by the way
AFAIK when sfc fails it's because some wmc related files can't be retreived. But it's still works and fixes other errors. So basically the answer is yes. That said the dism way is a tricky way, that's why I tried to evolve a bit the non dism way with 8.6
T-S Thanks sfc/scannow works with 8.6 but I screw up and didn't change from green to blue any way after already installed
You need to change also the hardlinked file (use the hardlink shell extension to follow the right path). Alternatively just uninstall and reinstall, after the dll rename. Uninstallation and reinstallation of v8.6 should be painless
Understood, but it means that unless you go check the (extensive) log, you cant be sure if there are other real issues not being fixed when sfc fails because of the WMC files. Jut an annoyance