I have noticed that too. I would assume that watching TV would attract many from the illiterate population. Here in the US some of the younger generation, think that YouTube is a textbook. Personally, I would rather watch the movie than read the book. The collapse of Barnes and Noble is an example that reading is on the decline. Then there are the others that are just TFL. There likely are some stats on that somewhere.
Moving files to sxs does nothing. it's just a store from where the files are hardlinked to the right location. You can even delete it and windows will still boot and work normally. sfc /scannow will be broken and any optional component installation will be broken as well
Would this be a good suggestion as "part of" a second step? Code: C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a> fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\blackbox.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\blackbox.dll \Windows\System32\blackbox.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\drmmgrtn.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\drmmgrtn.dll \Windows\System32\drmmgrtn.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\drmv2clt.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\drmv2clt.dll \Windows\System32\drmv2clt.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\msnetobj.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\msnetobj.dll \Windows\System32\msnetobj.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\msscp.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\msscp.dll \Windows\System32\msscp.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmdev.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmdev.dll \Windows\System32\wmdrmdev.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmnet.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmnet.dll \Windows\System32\wmdrmnet.dll C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a>fsutil hardlink list "C:\Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmsdk.dll" \Windows\WinSxS\amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_10.0.10586.0_none_fab3b39b6f24217a\wmdrmsdk.dll \Windows\System32\wmdrmsdk.dll
Not sure about what's the first or second step in your schema. Anyway it's one year and half that I suggest to install the hard link shell extension, to have a clear idea about how the windows directory is organized since Vista. The SXS directory is a sort of install media, all the files of a definite windows installation, are there. Then they are hardlinked to the right place by dism. Say, if you remove explorer, from the control panel, dism will delete some hard links. IE will be still in the SXS directory but it will removed by the program files directory. The space occupied by windows will not vary, because no files were actually deleted or added. So, in our case, the SXS directory matters only if you manage to fool dism like Abbodi did with WMC V12. In that case the files will be placed there and will be hardlinked, just like any official package.
I installed 8.7 (thanks T-S) but it would not recognize the tuners until I removed playready and reinstalled playready from crash2009 link. Everything seems to work, I haven't checked out the wake-up to record function yet. Also checked and my radio feature works again. I am only using OTA in the States
(my thinkin might be stinkin) What I was thinkin, was, copy the 1st package from 10586, copy the package over to RS1, get the hardlink list from 10586, use copy y to copy the files and update the hardlinks in RS1. Then come back here and say..."What is the best way to deal with .Net"
Yea, I knew that but, was wondering where Crash was going with it. Sigh...No bit closer to getting cablecards working on WIndows 10 Anniversary.... Just wondered what changed on this aspect in this new update that completely broke this connection. Anyone figure out a way to hack into a Extender RDP session ? The 3rd party Extenders used part of RDP to do their connection, Now if we can figure out so I can setup Windows 7 for that, maybe I wont need this after all.
I'm certain it is the removal of the WMDRM system in favor of PlayReady; in redstone all of the WMDRM files are missing except wmdrmsdk.dll, which is replaced with a 5 kB stub that probably simply returns the 0xc00d271d error in post #6004. Basically, where I'm going with it is: 1. Copy the files out of the old WinSxS store (or another 1511 installation) to the appropriate parts of the new filesystem (amd64 goes to system32; wow64 and x86 go to syswow64; .mof files go to the wbem subdirectory under each; .admx and .adml files look like they can be ignored for now as duplicates of what's still in Windows\PolicyDefinitions and en-us subdirectory). 2. Use regsvr32 to register DLLs; this creates most of the necessary registry entries for you 3. Find and add other missing registry entries by comparing redstone installation to working 1511 installation 4. Try... and repeat steps 3-4. I'm well into 4. WMC no longer instantly says no tuners are present, but shows the wait icon for 10-15 seconds before returning the message. I've only registered DLLs that showed up in my registry hunt (msnetobj.dll; msscp.dll; wmdrmsdk.dll; and portabledevicewmdrm.dll) so far. I'm looking through error logs, looking for the x64 logging tool, and generally trying to wade through a reverse engineering of the install process. I'm also still trying to figure out how to use the MCDiag_x86 tool. I simply get an error/exception. If we could determine how the WMDRM component is installed during installation or update, that would get rid of the need for hacking through registry entries to figure out what must be added.
No need to update the hardlinks, unless (like in wmc files) they are more than two. In such case you have one file in ehome, one (useless) in sxs, and a third one in the .net directory A file in the SXS directory does noting unless dism is aware of it, so copy or hard link a file there (manually) is just a waste of time with nothing in return.
Because HDHomeRun PRIME ... 16. Uncheck any channels you do not want to be available in NextPVR, such as those that are marked as copy-protected by your cable provider. That's why. One of the bigger reasons to buy the HDHomeRun PRIME is for encrypted QAM channels, like pretty much everything on TWC. Otherwise I could save time and effort buying a ClearQAM tuner. Not trying to be snarky; just trying to get across to you, like others, why the effort is being invested in WMC/cablecard.
Must be too little sleep, but I'm not figuring out where to pull the Ceton diagnostic from your posts. Gettin tired of having to edit out every URL...
HDHomeRun VIEW will show ClearQAM through cablecard, and works for me on both 1511 and Anniversary Update. I'm pretty sure others have figured that out as well. The MCE/cablecard issue appears to be specific to MCE, and likely due to a failure of of DRM initialization, which MCE requires for cablecard regardless of whether the per-channel signals are ClearQAM or encrypted QAM.