I not sure I'm getting the question. Are you asking why we used the b134 instead of b135 or did you test both and you noticed that 134 is more stable?
Only thing, what still fails, is downloading of EPG info... (Also auto-download of PlayReady failed and had to be downloaded and installed manually.)
Same question here: ...why you guys used b10134 instead b10135 or b10136? ...and why you used LP from b10036
Personally because I never download the 135 or 136. 134 was the last one I had handy with the WMC. On the other hand I was aware of the EGP problems on the lather builds. But the ones where the problems was non existent (say 10036) proved to be worse in our scenario. The initial wizard was stuck forever waiting for the TV setup data. It's the last publicly available version that includes them
Ok, it works for me now somehow. I installed the LAV decoder even though that is the wrong thing to do. I got the error about protected content but when I changed WMC from full screen to windowed it started playing protected channels. The default codec is set to the MS codec still,not LAV, so there is something that registering the LAV codecs did to make it work I guess?
Each time I run _TesRights.cmd as Administrator I get the following Message (see screenshot) Using Windows 10 build 10532
Copy the folder to the Root of the drive and try again....Some people have reported that because the folders go so deep it errors out. Something to try...
Just a thought for the folks diligently trying to get this to install without a hitch... How difficult would it be to modify whatever files control the "Add/Remove Windows Components" in Control Panel in order to have Windows actually install WMC the "proper" way instead of using all of the Trusted Installer shenanigans? Not sure if it would even work with patched files but just thought I'd throw it out there. (I know it's probably easier to test things with the batch files, but as things near a more stable workable solution I thought it might be something to keep in mind)
This makes no difference at all. Keeps saying the same thing, that it cannot find the path specified and runassystem.exe is not compatible with the version of Windows I am running!
I'm getting the same error on my 32-bit Windows 10 build 10532. I suspect runassystem.exe is compiled only for 64-bit systems. Bummer.