latest Windows update. Killed WMC once again
-
- Posts: 11
- Joined: Sun Dec 24, 2017 12:20 am
- Location:
- HTPC Specs:
latest Windows update. Killed WMC once again
Just got the latest windows update ( KB5031356 (OS Builds 19044.3570 and 19045.3570) 10/13/2023. WMC gives me the ALL CURRENT TUNERS IN USE when I try to go to live TV or recorded TV as well. So uninstalled and reinstalled WMC v13. No change. Did this happen to anybody else?
-
- Posts: 147
- Joined: Mon Oct 08, 2018 12:00 pm
- Location:
- HTPC Specs:
Sounds similar to https://www.thegreenbutton.tv/viewtopic ... 97&t=14392. Have you tried with the 8.x branch? It should be more resilient to such updates as it embeds a copy of EncDec.dll, MSVidCtl.dll and CPFilters.dll instead of relying on the global version in System32.
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
Assuming you are running on 64bit, I agree that a newer version of WMC would be a better option.
But I'm running V13 and had the same problem and saw that some of those DLLs had been updated so had to run the procedure to reinstate the required versions with the batch files to get it working.
But I'm running V13 and had the same problem and saw that some of those DLLs had been updated so had to run the procedure to reinstate the required versions with the batch files to get it working.
-
- Posts: 147
- Joined: Mon Oct 08, 2018 12:00 pm
- Location:
- HTPC Specs:
Hey technodevotee, it's been a long time. Hope you're doing well.technodevotee wrote: ↑Sun Oct 15, 2023 7:54 am Assuming you are running on 64bit, I agree that a newer version of WMC would be a better option.
Amusingly, abbodi1406 on MyDigitalLife just released a 8.10 installer earlier this week: https://forums.mydigitallife.net/thread ... st-1810045
It's based on the 8.8.5 version I released a few years ago but it also offers a x86 package that uses the same registration-free COM approach introduced in in 8.8.2 and 8.8.4.
Here's the changelog:
########## WMC 8.10.0 ###########
- Updated patching for ehReplay.dll / ehtray.exe / Mcx2Filter.dll / mcmde.dll
- Reviewed ACL permissions and removed hardcoded C:\ paths
- Converted Install.reg to Install.inf to remove hardcoded C:\ paths and correctly process Svchost registry
- Added missing registry for Settings Management Infrastructure (SMI)
- Improved GAC and NGEN assemblies installation and removal
- Improved .lnk shortcuts handling
- Apply conditional fixes (Microsoft SQL CE / CPFilters.dll / MSVidCtl.dll and EncDec.dll) based on OS build
- Added zh-TW mui files
- Removed Mcx2Prov.exe.XB360 and ntrights.exe
- Replaced NSudoC.exe with superuser.exe
- Improved auto elevation for the outer main scripts
- Green skinned WMC can now be installed as addon after main pack
- Created 32 bit / x86 pack
Author: abbodi1406
Code: Select all
File: WMC-v8.10.0-x64.7z
SHA-1: 2ae5c768256336bc4c205ee019ee9d69bf001502
SHA-256: f96f227f3f6c80727bb6ebfbdda4b027e7f63295332bf0a3ae33a6d1712d3715
https://www.mediafire.com/file/xqzllsj0mlf5e0n
https://drive.google.com/file/d/1_qM3rDoj5EnwvVajNqhlm-9Ku7tVfE39
https://mega.nz/file/OotgkDBY#BOV1wJFapvGVJ30Q7H_UAFcfUQODRuRZAMjaNlogdj4
Code: Select all
File: WMC-v8.10.0-x86.7z
SHA-1: 21f7db59cad08ae542c7674e770467bca364eece
SHA-256: 30c61292690ceab7900777600836929a9fed0c6f8853eb97af945a456f14aef8
https://www.mediafire.com/file/21epefjz372mhio
https://drive.google.com/file/d/1bg3oTmQZUD87Yp-3_oOCL1n65Tlya5xN
https://mega.nz/file/298FQCLR#a71Wf_ovSwvsPBMtRdJewsCOHXcBXRSfCcGm6rAayWw
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
Hi Pinpoint - yeah, I'm fine thanks.
I'm sure quite a few people will be delighted to see that.
As you know,V13 was only ever intended a stop gap.
T
I'm sure quite a few people will be delighted to see that.
As you know,V13 was only ever intended a stop gap.
T
-
- Posts: 136
- Joined: Fri Dec 13, 2019 4:19 pm
- Location:
- HTPC Specs:
OK, so I'm confused. This is different, even tho the numbering is similar, than the "installer" based ones from Gary, correct? These are more bat/script based? This scripting is something that could be run to attempt a fix after update issue regardless of what version you have installed and whether it is x86 or 64.
Or am I totally confused?
Thanks much
Or am I totally confused?
Thanks much
- garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
I agree the numbering system is confusing here. It looks like 8.10 is to install WMC on Win8? May or may not work with Win10/11?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 147
- Joined: Mon Oct 08, 2018 12:00 pm
- Location:
- HTPC Specs:
Yup. Gary will correct me if I'm wrong, but his installer is based on the 8.x branch and includes the workarounds I mentioned earlier, that allow using WMC on recent versions of Windows 10/11.
It also comes with a few changes (e.g WMC is installed in C:\Program Files and the default "tuners of the same type" limit is 32 instead of just 4) and it's worth mentioning that unlike the 8.x branch, you can't watch live TV via RDP (but on the other hand, you can use WMC fullscreen via RDP).
The 8.x branch is really an installer, just using good old scripts instead of an MSI-based approach like Gary's installer.
I wouldn't recommend using 8.10 at all to try to fix/update a WMC setup made with Gary's installer or the 13.x branch.
No, the 8.10 package is really for Windows 10/11 (I haven't tested as my headless Windows Server 2022 TV server is still on 8.8.5, but it should also work great on Windows Server 2016/2019/2022).
The "Windows 8 without the Media Pack" installer is separate:
WMC 6.2.9200.16384 for Windows 8 with no Media Center
- based on the alternative branch pack concept
- only for Win8 (not recommended for Win10, but you can edit the scripts to remove that)Code: Select all
File: WMC_9200-x64-v2.7z SHA-1: a4adfe9a3e152a4372dc89cede9915a862f22279 SHA-256: a92be236091dd9fcca26bad7954f3b59a6545b2bf1a2df4bdccbb6176284e5cf https://www.mediafire.com/file/kjvyrr73sj4otk8 https://drive.google.com/file/d/1Q1lhPCE859GQWynaNdPeCDhKT3pfRNdO https://mega.nz/file/i0lgnSzZ#uUgGK4kgBZQ6D0ltUEM53vRSFPr54dBEYMTolGgpN4o
Code: Select all
File: WMC_9200-x86.7z SHA-1: 87085eb4e1488ac395dfacdb43672ef0499f1673 SHA-256: 336db715348bf45d2b5fd2b7b30f3f477b66ad2943bd5be450d0c69bdc34762d https://www.mediafire.com/file/curq752vhn3085t https://drive.google.com/file/d/1XLSiQHH_z7CoMpq8aNkZlQmw-gFzEFMM https://mega.nz/file/ewsESCza#u_yQz6gzsunZHohmWvyac8pVR5DAqtiA6GKZV2t_OMo
-
- Posts: 11
- Joined: Sun Dec 24, 2017 12:20 am
- Location:
- HTPC Specs:
Busy weekend but finally got around to installing the new pack. Worked like a charm! Thanks to all the folks who keep WMC running.
- garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Ah, I see. I was looking at the wrong post.Pinpoint wrote: ↑Sun Oct 15, 2023 6:20 pm Yup. Gary will correct me if I'm wrong, but his installer is based on the 8.x branch and includes the workarounds I mentioned earlier, that allow using WMC on recent versions of Windows 10/11.
It also comes with a few changes (e.g WMC is installed in C:\Program Files and the default "tuners of the same type" limit is 32 instead of just 4) and it's worth mentioning that unlike the 8.x branch, you can't watch live TV via RDP (but on the other hand, you can use WMC fullscreen via RDP).
No, the 8.10 package is really for Windows 10/11 (I haven't tested as my headless Windows Server 2022 TV server is still on 8.8.5, but it should also work great on Windows Server 2016/2019/2022).
My 8.9.0 msi version is based on 8.8.x and progresses from 8.8.1 - 8.8.5 depending on OS version. Version 8.9.1 is the same except it is a blend of 8.8.5 and v13 for some of the files. I see 8.10 follows the same method outside of an msi, but there are newer updates. If I hadn't jumped in there with 8.9.x, it would have probably been considered 8.8.6?
So what are these updates in response to? If needed, I can incorporate into an 8.9.2.
Code: Select all
- Updated patching for ehReplay.dll / ehtray.exe / Mcx2Filter.dll / mcmde.dll
...
- Added missing registry for Settings Management Infrastructure (SMI)
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 147
- Joined: Mon Oct 08, 2018 12:00 pm
- Location:
- HTPC Specs:
Haha, I guess so
No idea for the second one, but for the first one, abbodi1406 posted more details here: https://forums.mydigitallife.net/thread ... st-1810227garyan2 wrote: ↑Mon Oct 16, 2023 2:09 am So what are these updates in response to? If needed, I can incorporate into an 8.9.2.Code: Select all
- Updated patching for ehReplay.dll / ehtray.exe / Mcx2Filter.dll / mcmde.dll ... - Added missing registry for Settings Management Infrastructure (SMI)
it's just for the decoder licenesing check (don't matter if current SKU already allow them)
for ehReplay.dll / Mcx2Filter.dll / mcmde.dll i noticed the previous patch only bypass msmpeg2vdec-MPEG2VideoDecoder, but not msmpeg2adec-DolbyDigitalDecoder
for ehtray.exe, previous patch bypass IsMCEAllowedOnThisMachine result, i update it to even suppress IsMCEAllowedOnThisMachine check
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
The version numbering is very confusing isn't it - especially for newcomers.
I'm still not sure how it was that 8.X.X was being developed long after V12 was abandoned. I can only assume it was so that the developer(s) wasn't/weren't seen to be treading on people's toes.
I tussled with the numbering when I created my version and settled on V13 so that it was obvious that it was built with the same files as 12 rather than the ones in later versions of 8.X.X.
Still don't know if that was the right decision.
I'm still not sure how it was that 8.X.X was being developed long after V12 was abandoned. I can only assume it was so that the developer(s) wasn't/weren't seen to be treading on people's toes.
I tussled with the numbering when I created my version and settled on V13 so that it was obvious that it was built with the same files as 12 rather than the ones in later versions of 8.X.X.
Still don't know if that was the right decision.
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
Has anyone had a chance to try out the 8.10 installer yet?
I don't have a PC that I can properly try it on at the moment.
I don't have a PC that I can properly try it on at the moment.
-
- Posts: 2
- Joined: Sun Oct 29, 2023 8:42 pm
- Location:
- HTPC Specs:
I found the problem of “ALL CURRENT TUNERS IN USE” when watching Live TV, and no recordings play (just a blue screen).
Removed V13 and installed 8.10, problem of recordings play was fixed, but the “ALL TUNERS IN USE” issue is still there, no Live TV.
I will re-try tomorrow the entire process.
Removed V13 and installed 8.10, problem of recordings play was fixed, but the “ALL TUNERS IN USE” issue is still there, no Live TV.
I will re-try tomorrow the entire process.
-
- Posts: 2
- Joined: Sun Oct 29, 2023 8:42 pm
- Location:
- HTPC Specs:
Today I removed V13, reboot, installed 8.10, reboot, problem fixed. It currently works... until the next W10 Update!
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
It should be possible to fix problems with V13 that are caused by Windows Updates without uninstalling by using the scripts provided in the installer folder.
Information about the scripts is provided in the included file, 'known issues.txt'.
However, V13 was only ever intended as a stop gap until a long term solution was found so, unless there is a compelling reason to use V13, it is far better to use one of the more recent versions.
Information about the scripts is provided in the included file, 'known issues.txt'.
However, V13 was only ever intended as a stop gap until a long term solution was found so, unless there is a compelling reason to use V13, it is far better to use one of the more recent versions.
-
- Posts: 136
- Joined: Fri Dec 13, 2019 4:19 pm
- Location:
- HTPC Specs:
Please post if you've installed the Feb updates and whether they caused any wmc issues. Thanks
-
- Posts: 963
- Joined: Thu Sep 10, 2015 4:10 pm
- Location: West Midlands
- HTPC Specs:
I'm running 19045.4046
February 13, 2024—KB5034763 (OS Builds 19044.4046 and 19045.4046) installed 2 days ago and didn't cause any issues with V13
February 13, 2024—KB5034763 (OS Builds 19044.4046 and 19045.4046) installed 2 days ago and didn't cause any issues with V13
-
- Posts: 136
- Joined: Fri Dec 13, 2019 4:19 pm
- Location:
- HTPC Specs:
Thanks! Much appreciatedtechnodevotee wrote: ↑Tue Feb 20, 2024 6:28 pm I'm running 19045.4046
February 13, 2024—KB5034763 (OS Builds 19044.4046 and 19045.4046) installed 2 days ago and didn't cause any issues with V13
-
- Posts: 136
- Joined: Fri Dec 13, 2019 4:19 pm
- Location:
- HTPC Specs:
Anyone updated thru April without issues? Sorry to waste the bandwidth on this.
Thanks much
Thanks much