Win 10 + extenders WORKS!

[soapdishbandit]

I decided to take the plunge and upgraded to Win 10 64-bit Pro yesterday. I did the upgrade from Win 7 Ultimate 64. Then I did a Windows reset (in-place reformat). Installed Nvidia drivers and then WMC v12. Installed DCA 64 and PlayReady 64. Worked like a charm (had to retun Ceton tuners to recognize all 6 tuners (was only detecting 4).

Trying to add the extenders was another story. Trying to add extenders after updates was a no-go. So I reset PC again and foklowed Gareth Norths directions to the T. The only issue I had was when step 6 said to hide certaim updates, it didn't find them. So I proceeded to do everything else and it works perfect!

Win 10 Pro x64
Intel Core i5 2500k
16GB DDR3 RAM
Nvidia 970 GTX
Ceton InfiniTV 6 Pci-E
2 Xbox 360's

[soapdishbandit]

Going to have to sell my Ceton Echo now, unfortunately. Served me well but won't work with Win 10 (or 8/8.1 for that matter). Will purchase another Xbox 360 to replace.

[SpencerC]

Going to have to sell my Ceton Echo now, unfortunately. Served me well but won't work with Win 10 (or 8/8.1 for that matter). Will purchase another Xbox 360 to replace.

I think Crash2009 got the Ceton Echo working, hit him up for details.

[DavidinCT]

Going to have to sell my Ceton Echo now, unfortunately. Served me well but won't work with Win 10 (or 8/8.1 for that matter). Will purchase another Xbox 360 to replace.

I think Crash2009 got the Ceton Echo working, hit him up for details.

I've been watching it, Getting 3rd party Exenders (Echo, linksys, etc) is not working as far as I know. He was trying but, I dont think he was successfull.They use a different method of connecting than 360's do, after 8.1 they no longer worked due to changes in 8.1, the same problem is in Windows 10.

Would love to see if someone could get them working but, there was some major sub system changes in 8.1 and 10 that I dont see it happening, at least an easy way.

[Crash2009]

Nope, boots and displays the MMC splash screen. Needs more work.

[soapdishbandit]

Nope, boots and displays the MMC splash screen. Needs more work.

Appreciate all your hard work on it!

[Crash2009]

Nope, boots and displays the MMC splash screen. Needs more work.

Appreciate all your hard work on it!

Try setting up echo, maybe you'll get farther.

[DavidinCT]

Nope, boots and displays the MMC splash screen. Needs more work.

Appreciate all your hard work on it!

Try setting up echo, maybe you'll get farther.

I'll try my DMA2100 when I get v12 running fully on Win 10...

If I can get that one running, I am sure you wont have a problem running an echo...

[soapdishbandit]

I'll try my DMA2100 when I get v12 running fully on Win 10..

If I can get that one running, I am sure you wont have a problem running an echo...[/quote]

Good luck sir!

p.s. what part of CT do you live? I'm in Derby. Small world for us WMC users, ehh?

[glugglug]

Have you tried replacing terminal services related binaries with the ones from Windows 7?
The extender session is mostly RDP on port 3390. Windows 8 changed the RDP protocol to support RemoteFX and also broke most Linux and Mac RDP clients at the time.

[Crash2009]

Have you tried replacing terminal services related binaries with the ones from Windows 7?
The extender session is mostly RDP on port 3390. Windows 8 changed the RDP protocol to support RemoteFX and also broke most Linux and Mac RDP clients at the time.

No, but I am willing to try anything within my skill level....which is not a very high level by the way.

I linked your post to MDL. http://forums.mydigitallife.info/thread ... ost1246538

We will see if your suggestion creates an interest.

Code: Select all

Log Name:      Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational
Source:        Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
Date:          7/11/2016 12:25:51 PM
Event ID:      135
Task Category: RemoteFX module
Level:         Information
Keywords:      
User:          NETWORK SERVICE
Computer:      Win10
Description:
The multi-transport connection finished for tunnel: 3, its transport type set to TCP: Reason Code: 2 (Forced by Server Configuration).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS" Guid="{1139C61B-B549-4251-8ED3-27250A1EDEC8}" />
    <EventID>135</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>4</Task>
    <Opcode>15</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-11T16:25:51.394314900Z" />
    <EventRecordID>1022523</EventRecordID>
    <Correlation ActivityID="{F420BF52-898E-4CC5-96D5-FC8FAC2B0000}" />
    <Execution ProcessID="88" ThreadID="7608" />
    <Channel>Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational</Channel>
    <Computer>Win10</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="TunnelID">3</Data>
    <Data Name="TransportType">TCP: Reason Code: 2 (Forced by Server Configuration)</Data>
  </EventData>
</Event>

Log Name:      Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational
Source:        Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
Date:          7/11/2016 12:25:51 PM
Event ID:      135
Task Category: RemoteFX module
Level:         Information
Keywords:      
User:          NETWORK SERVICE
Computer:      Win10
Description:
The multi-transport connection finished for tunnel: 1, its transport type set to TCP: Reason Code: 1 (No Client UDP Support).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS" Guid="{1139C61B-B549-4251-8ED3-27250A1EDEC8}" />
    <EventID>135</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>4</Task>
    <Opcode>15</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-11T16:25:51.394304800Z" />
    <EventRecordID>1022522</EventRecordID>
    <Correlation ActivityID="{F420BF52-898E-4CC5-96D5-FC8FAC2B0000}" />
    <Execution ProcessID="88" ThreadID="7608" />
    <Channel>Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational</Channel>
    <Computer>Win10</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="TunnelID">1</Data>
    <Data Name="TransportType">TCP: Reason Code: 1 (No Client UDP Support)</Data>
  </EventData>
</Event>

Log Name:      Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational
Source:        Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
Date:          7/11/2016 12:25:51 PM
Event ID:      101
Task Category: RemoteFX module
Level:         Warning
Keywords:      
User:          NETWORK SERVICE
Computer:      Win10
Description:
The network characteristics detection function has been disabled because of Reason Code: 1(Client not supported)..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS" Guid="{1139C61B-B549-4251-8ED3-27250A1EDEC8}" />
    <EventID>101</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>4</Task>
    <Opcode>16</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-11T16:25:51.394299100Z" />
    <EventRecordID>1022521</EventRecordID>
    <Correlation ActivityID="{F420BF52-898E-4CC5-96D5-FC8FAC2B0000}" />
    <Execution ProcessID="88" ThreadID="7608" />
    <Channel>Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational</Channel>
    <Computer>Win10</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="ReasonString">Reason Code: 1(Client not supported).</Data>
  </EventData>
</Event>

Log Name:      Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational
Source:        Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
Date:          7/11/2016 12:25:51 PM
Event ID:      100
Task Category: RemoteFX module
Level:         Information
Keywords:      
User:          NETWORK SERVICE
Computer:      Win10
Description:
The server has confirmed that the client's multi-transport capability.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS" Guid="{1139C61B-B549-4251-8ED3-27250A1EDEC8}" />
    <EventID>100</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>4</Task>
    <Opcode>15</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-11T16:25:51.394296700Z" />
    <EventRecordID>1022520</EventRecordID>
    <Correlation ActivityID="{F420BF52-898E-4CC5-96D5-FC8FAC2B0000}" />
    <Execution ProcessID="88" ThreadID="7608" />
    <Channel>Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational</Channel>
    <Computer>Win10</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
  </EventData>
</Event>

No Client UDP Support This log agrees with your statement.

[XXXBerto55]

Just wanted to chime in and say following directions got me working as well. Ideally someone would aggregate all the steps with a little more direction and more direct links. I might try to myself if I get time. The links for the files are not super easy to find but I am pretty novice and I managed it. I didn't even know what to do with the bat file but figured it out. That forum is a nightmare. Also a key is you have to have pro.... I bought a Windows 7 key on eBay to upgrade to Pro though for like $11.

[Crash2009]

Just wanted to chime in and say following directions got me working as well. Ideally someone would aggregate all the steps with a little more direction and more direct links. I might try to myself if I get time. The links for the files are not super easy to find but I am pretty novice and I managed it. I didn't even know what to do with the bat file but figured it out. That forum is a nightmare. Also a key is you have to have pro.... I bought a Windows 7 key on eBay to upgrade to Pro though for like $11.

It appears the product isn't quite finished yet. Different versions need different directions. What I have done as a temporary measure is added some links to my signature. v8, v10, v11, v12, Those links will take you to the first day the version was released. Usually the first 10 or 20 people find out pretty quick what has to be done to make the version work. We have "Started" a Table of Contents in Post #1. PM Rick to add whatever you think is worthy of being listed in the TOC.

A few of the smaller projects such as RDP and Xbox are scattered throughout as they were sort of put on the back burner in favor of higher priority projects and new versions of WMC. It appears the current trend is a reworking of past versions, with expectations of different results. As an example there is now a v8.5 and a v8.6