After upgrading to Windows 10 from 7, I can no longer seek while casting a video to my tv. My tv is a Samsung 55c-8000 which under Windows 7 "Play to", I was able to use my remote to seek and fast forward or rewind. Now under Windows 10 "Cast to Device", it always says "Seek is Not Supported". Is there a workaround for this?
Not with 10. A lot of features are going to disappear when Redstone comes out.
Network or Ad-Hoc peer to peer streaming is something that Microsoft has had a bad habit in chasing away.
That's annoying, intelligence should be improving, not withholding things that make everyone's experience better.
No clue in what you mean with that cryptic post.
Microsoft has been in the process of stripping out a bunch on legacy code to make Redstone lighter on the CPU's and faster.
Linux and Apple have done the same thing with their code bases.
Stuff that people are not using, or it is breaking the install, is what Microsoft is trying to do right now. They have learned from their mistakes hopefully and will not do a threepeat with Redstone.
Fortunately only a few of the .mp4's that I made won't allow seek. But what is odd is what causes it to happen to only those few. I'm encoding them all at the same settings. My Windows 10 Professional build is 1511 (OS Build 10586.589) with the latest updates to November 21, 2016.
I upgraded from 7 to 10 and am now on the latest RTM build 14393.447. I can seek while casting any of my videos to my Panasonic Viera, both from the 'Cast to Device' window on my PC and using my TV's remote. The PC sometimes reports 'Seek not supported' but I think this may be a timing issue - on a second (sometimes third) attempt it works, then continues to work while I'm casting that video.
One thing to check on your TV's menu is that 'DLNA Remote Control' and 'Network Remote Control' are turned on (those are Panasonic's name for these settings, at least).
Quote