Hmm, just applied the usual patch Tuesday stuff to my 1809 playback box and got a Decoder Error so something reverted one of the DLLs to the new busted ones that aren't compatible with old recordings. Just checked the recording machine and it's similarly got a Decoder Error. Ran my DLL fixer and playback succeeded, no doubt one of technodevotee's fixes will work for others. Sorry if this is covered already but posts here don't seem to predate patch Tuesday and I'm not seeing others complain of Decoder Errors. AFAIK that's the first time we've seen normal security patches bork WMC. I have a note to myself about maybe denying the trusted installer permission to the those DLLs, guess it might be time to act on it...
I've had to roll back one or other of the DLLs a number of times. As you say, it is easy enough to do and this time, it was just msvidctl on 1909.
Thanks to Kevin's work, you are immune to that problem on 8.8.4. Proves that it works though doesn't it.
Yeah, I've noticed if you ever run SFC the DLLs revert. Have you tried stashing "our" DLLs in the WMC directory? Windows used to go to great lengths to keep versions of DLLs for different processes with the same names separate from each other, kinds a paradoxical that MS itself should be a cause of another instance of it. I was thinking perhaps having the DLL in that WMC directory would be preferentially used but I guess if the function that loads the DLL for the WMC process includes the path that probably won't work.
Discovered a typo in the script of my updated utility 'roll_back_dlls' that means the changes weren't working properly. Embarrassingly, there was also an error in 'fix_thumbnails'. Please download the utilities again. Sorry about that.
is there an easy button to get WMC working on 2004 yet? I just upgraded one of my media PCs, attempted to install 8.8.4 & v13 with no success. The install finishes, but WMC will not launch. I've had success running this in every other version of W10.
@DanPFW, You need to reinstate MSSQLLite. There is a tool to do it in V13 and you can download the tool from my website for other installers.
I've downloaded replace_dlls.zip, roll_back_dlls.zip, fix_mssqllite.zip. I thought it was included in one of the first two?
it is in roll_back_dlls now but unfortunately there was a typo in it and it didn't work so I uploaded a fixed version. fix_mssqllite should work though
Yeah, I just goosed the sacrificial laptop into installing 2004 and switched it to using 8.8.4 and sure enough it needs fix_mssqllite so my guess is Kevin's got more DLL Hell in his future...
HI All, I have just tried an upgrade to 2004 and can't get ehome to start - I've on V13 and have run fix_mssqllite but still no go. MC has worked fine on all other versions for the last 18 months (with an occasional replace_dlls) The event log shows Application: ehshell.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Security.SecurityException at System.ThrowHelper.ThrowSecurityException(System.ExceptionResource) at Microsoft.Win32.RegistryKey.OpenSubKey(System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.GetClientId(Boolean) at MediaCenter.Store.SqlLite.ObjectStore.Open(System.String) at MediaCenter.Store.SqlLite.ObjectStoreManager.Open(System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, System.Reflection.Assembly, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.AddObjectStoreReference() at Microsoft.MediaCenter.Store.ObjectStore.get_DefaultSingleton() at ServiceBus.UIFramework.UserControlPoint.Launch(System.String) Anyone able to suggest a solution? Many thanks
Did you run the fix mssqllite script n the installer folder or a different one? The one I put on my website had a typo in it and I had to upload a new version. The other things to try is WMC multi tool or make the changes manually.