I guess it's time to throw in the towel. It's one thing to stop the anniversary edition from installing, but I don't think it's smart to roll back the updates from now on. At least I still have the Win 7 version working on a dual boot, and I can watch the local channels on the HDHR app. I wish SD would get their DRM update working someday.
From what I believe and feel free to correct me if I am wrong but the whole purpose of LTSB edition is to forestall updates for many years as many corporate environments do.
Sure, you should be relatively safe with LTSB (no feature updates), anyway is not 100% guaranteed that a "security update" doesn't break something on an unsupported program. After all sometimes happens that updates breaks supported programs, WMC itself has suffered several times in its history because some updates.
Can LTSB forestall security updates as it does feature updates? Can't the entire Windows Update Service be turned off in LTSB?
You can tun it off in any Windows. The point of LTSB is to not disable it, and to get the security updates only.
I thought, obviously incorrectly that you could only defer for a short term not completely turn off updates.
You are confusing Feature updates with All updates. In a regular windows version, you can turn off All Updates completely, but that means no security updates and a vulnerable system. You can also delay Feature updates for a while but continue to get security updates, but that is only for a short term. LTSB gives you the later (no feature update but security updates for many years.
You can turn off the updates everywhere, just disable the WU service You can officially defer the updates on Enterprise and Server only, so also on Enterprise LTSB (not sure about Education/Professional education and so on) You can defer the updates on home and pro as well using the metered connection trick On LTSB you will get get, by design, security updates only. Features updates aren't just provided.
T-S, thank you for the VERY thorough info. One follow up, if one turns off the Windows Update Service can you still download security updates from a Non Microsoft source once they have been proven NOT to break WMC?
Obviusly you can install MSUs and CABs at your will. But is not straight forward to follow the evolution of updates. Anyway there are some tools that helps a lot like WUMT, just follow the dedicated discussions here int the W10 room and/or on the MDL projects one.
Sandy The TL;DR version is you don't need to read all the pages before you install and it's actually pretty easy and fast once you understand a few key variables. As one who has gone through many of these posts and just wanted a "what do I need to do right now to get WMC installed and working on Windows10" ... here's the latest as of 10/15/2016 & page 740 (frustrating part is that this stuff changes so frequently but it is what it is : 1. Download T-S's latest files - links on page 1. It's this one: V8.8.1 minor update [12/08/2016] 1.a. I'd use V8.8.1 over the V12 (which as essentially the same) b/c T-S has done a great job of making the installer more resilient. I've done multiple installs/re-installs/fixes on a number of machines and have had a few issues with V12 but *knock on wood* zero issues with T-S's installer and uninstaller. 1.b. Read through all of T-S's notes in post #5314 - great descriptions and info there. 2. Make sure the file isn't blocked 3. Unzip the downloaded file to an easy install location (recommended C:\) and just follow the instructions in the root of the newly created folder (_Readme.txt file and the just-in-case Workarounds.txt file) 4. I won't re-type all the instructions but it's really as easy as just running the "_TestRights.cmd" file and then running either the "InstallerBLUE.cmd" or "InstallerGreen.cmd". The blue will install WMC w/ a blue background and the green will create a green background. FWIW - my family thought the green was too florescent so we went with blue. You can switch colors after the install - instruction in the _Readme.txt file 5. Once you have WMC up and working as you like I would strongly recommended imagining your machine/backing it up so you can restore if/when WMC stops working. At least go into Windows 10, turn on System Protection (if not already on), and create a System Restore point. ... This has saved me some serious headache more than once. Bottom line - it's just running the installer.cmd file and your done in 5 minutes. The frustrating part is that WMC may not "just work" once your done and or Microsoft fixes have been breaking WMC functionality for me so here are my important words of warning that you should know. 1. There's an issue with the latest version of Windows 10 (the Anniversary update = 1607) so if you have that installed you either have to roll back (Google it - it's not hard but it does take a while) or if it's been more than a few weeks you lose the ability to roll back so you have to reinstall Windows 10 (super annoying). 2. As of a few days ago, there's a new KB security update that Microsoft released - KB 3192441 - it has the exact same effect as the Anniversary update - so you have to uninstall the update to have WMC work. 2.a. Hide the offending KB 3192441 with Microsoft's "wushowhide.diagcab" tool so it doen't re-install itself automotically 2.b. If either the Anniversary update or KB 3192441 is installed - WMC will not recognize my HDHomeRun tuner. There are some other's affected but I can't speak to all of them. My understanding is that an OTA (Over The Air) HD tuner will still work however. 3. If there's some funky behavior with the install (watch the command prompt window when installing and confirm that you see success during the installation process) and/or you ever need to uninstall/re-install - make sure you reboot (it's in the instructions/recommendations but it's important) I'm using a HDHomeRun CableCard tuner that requires uPNP network functionality and some setup on it's own. For that specific card - here's the troubleshooting guide that I go through to confirm functionality: **** Silicondust Support = troubleshooting/#no-tuners-found **** ERROR MESSAGE: Tuner Not found. The TV signal cannot be configured because a TV tuner was not detected. If you have a tuner, ensure it is installed correctly. .... Windows Media Center reports No tuners found when trying to complete TV setup - HDHomeRun PRIME Back to top Open HDHomeRun Setup and verify that the tuners are found and that no UPnP error is received. Open Control Panel, select View network status and tasks, and make sure the network is listed as Home/Private network. Click on Change advanced sharing settings. Verify that Turn on network discovery is selected, and click Save Changes if needed. Open Computer Management (right click on Computer, choose Manage) and click on Services in the left column. Verify that the SSDP Discovery Service is not Disabled, and is Started. Verify that the HDHomeRun Service is not Disabled, and is Started. Verify that the Windows Media Center Receiver Service is not Disabled, and is Started. Close the Services Management window. Open Command Prompt as Administrator (Start > All Programs > Accessories > right click on Command Prompt > Run as Administrator). Run: c:\windows\ehome\ehprivjob.exe /OCURDiscovery The command must be typed exactly as shown. Anything that is already present in the command prompt window should be ignored. Just type in the above command. This should list the HDHomeRun PRIME tuners. Reopen Windows Media Center and access the TV setup wizard again. Hope this helps you and others out. Bottom line is it's actually quite easy and quick if you use T-S's latest file, use your tuner's latest drivers, and you're fully aware of the Microsoft patches that are blocking/breaking many tuners.
Understood, but if one opts too in LTSB once can turn off security updates by disabling WU service like in the other versions? Lastly, in ALL versions of WIN 10, by disabling Windows Update service, does it remain disabled permantely, and if the service is off does that prevent guide data for WMC too? Thanks !
For you AMD/Radeon video card users out there, I was having trouble with hdcp and drm occasionally (usually after sleep or video screen blank, but sometimes after a channel change) that could be fixed by either shutdown/restart. I was wondering if it was caused by some recent updates to the video drivers, so I tried disabling/re-enabling the video driver, and that also temporarily fixed the problem. Did a search on my issue and found someone else had a similar issue on Windows 7 with the later drivers even though they are whql. I uninstalled the lastest "Crimson" amd drivers and put in the same version mentioned in the post, 15.12, but for Win 10 64bit. No issues since! To double check I upgraded to the next higher version whql and the problems returned so I again put in 15.12 and it has been working fine for the last few days.