Hi @Kévin Chalet , I have done some work to prepare WMC for the upcoming 20H1. I copied the files sqlcecompact40.dll, sqlceoledb40.dll, sqlceqp40.dll and sqlcese40.dll to C:\Windows\ehome. Then I created the file Microsoft.Windows.SQLCE.manifest with this content: Code: <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity name="Microsoft.Windows.SQLCE" version="1.0.0.0" /> <file name="sqlcecompact40.dll"> <comClass clsid="{1FFDED41-8FC9-497D-BD70-B2E440736273}" description="Microsoft.WINDOWS.SQLLITE.Engine.4.0" progid="Microsoft.WINDOWS.SQLLITE.Engine.4.0" threadingModel="Both" /> <comClass clsid="{56F62E3E-8904-43F6-B841-DAC177F7FEB9}" description="Microsoft.WINDOWS.SQLLITE.Params.4.0" progid="Microsoft.WINDOWS.SQLLITE.Params.4.0" threadingModel="Both" /> <comClass clsid="{94510291-3DB7-4F61-B62B-A5790CE92645}" description="Microsoft.WINDOWS.SQLLITE.Errors.4.0" progid="Microsoft.WINDOWS.SQLLITE.Errors.4.0" threadingModel="Both" /> <comClass clsid="{E7F328B1-6095-41B0-94B7-3DD278EADAA1}" description="Microsoft.WINDOWS.SQLLITE.Param.4.0" progid="Microsoft.WINDOWS.SQLLITE.Param.4.0" threadingModel="Both" /> <comClass clsid="{EFDB73A6-192F-4944-979E-4153CC8E8715}" description="Microsoft.WINDOWS.SQLLITE.Error.4.0" progid="Microsoft.WINDOWS.SQLLITE.Error.4.0" threadingModel="Both" /> </file> <file name="sqlceoledb40.dll"> <comClass clsid="{3A5B4772-7946-4E58-9310-B0D423749C1D}" description="Microsoft.WINDOWS.SQLLITE.OLEDB.4.0" progid="Microsoft.WINDOWS.SQLLITE.OLEDB.4.0" threadingModel="Both" /> </file> <file name="sqlceqp40.dll"/> <file name="sqlcese40.dll"/> </assembly> Finally, I put the following snippet into each of the exe.manifest files: Code: <dependency> <dependentAssembly> <assemblyIdentity name="Microsoft.Windows.SQLCE" version="1.0.0.0" /> </dependentAssembly> </dependency> I deleted the sqlce*.dll files from C:\Windows\System32, and WMC still seems to work. I have not done any extensive tests, but so far I haven't found anything that does not work. Patrik
Quick question, I was running LTSB with WMC and all was ok, although felt HTPC needed a clean so I upgraded to LTSC (inc updates) with the latest version of WMC (thanks to all involved with the development of the application and integration). However now at times when I change channels there is no picture and on 2 occasions I got the BSOD and the system restarted, now do I revert to LTSB or is there anything I can do to minimise crashing and no picture on channel switching, and or is there any benefit going from LTSB to LTSC on a HTPC based system. Hardware of system : Gigabyte Z99 WiFi (M-ITX) i5 4690 8GB HDHomeRun Quattro Tuner (network) GTX1060 3GB 250GB SSD 6TB HDD PS : apologies in advance should this question be asked and answered and many thanks too for any info and help. @IT
I assume you read the known issues.txt file and used the scripts to apply the required workarounds? V13 isn't really the latest version because it is based on V12 files which haven't been altered since 2015. I just changed the installer, added workarounds to allow it to be used on newer versions of Windows and made it available as a stop gap while more permanent fixes to problems were applied. V8.8.4 has had a lot more development of the files and incorporates most of the things that are needed out of the box without affecting Windows system files so that it continues to run after ugdates. It is the recommended version to use really although I believe that there is a newer version in the pipeline. There are difference between the versions and some people find that one version works well while others find that another works best for them.
Hi again @technodevotee and really appreciate the replies, I thought v13 was the latest version and did all the script installs. So may I ask, would it be a simple as uninstalling v13 and installing v8.8.4 or for a truly bug and glitch free method is doing a complete reinstall of LTSC (probably my OCD would choose the latter method). Many thanks again. @IT
I haven't experience the issues you described using either V13 or 8.8.4 on any of the PCs I have (and I have quite a few - running different versions of Windows and different versions of WMC). I've only seen a few issues that were vaguely similar to what you describe reported and even then only a few people ever report back as to what resolved it. If you are running the same version of WMC and it was fine before the upgrade then I would suspect the upgrade but who knows? You could try removing V13 and installing V8.8.4 before doing anything more drastic. Just make sure that you use the uninstaller for the version you are uninstalling.
The WMC numbering is rather confusing isn't it. I probably didn't help the situation by naming mine V13 but it seemed logical at the time. What can I tell you?
@technodevotee I guess the confusing part like possibly many more is I didn’t read or chose to skip/miss or ignored that little formality. I appreciate your work and findings. I uninstalled v13 using the uninstalled and installed v8.8.4 everything seemed to work better on LTSC, however the OCD part of me took over and have just reinstalled a fresh install of the said LTSC, now to set all up take the updates, shouldn’t take to long and we’ll go from there, I’ll advise either way if you wish. Take it easy and stay safe wherever you may be. @IT
@technodevotee system flattened and rebuilt, so far all seems ok, all updates taken and will keep a close eye on the HTPC over the next day or so. Again many thanks for your replies, help and info. @IT
You obviously don't use satellite! A reinstall usually takes me two days to get back to how it was because the setup data is so out of date that 90% of the 4400+ channels listed don't work so I have to scan three satellites then sort through, rename and assign EPG listings to the ones that actually work. No wonder that I'm paranoid about backups.
so uh anyone had any luck with getting the Xbox 360 to work as an extender with Windows Media center on Windows 8.1 with a hacked WMC installer from one of these links here? I'm running W8.1, used that installer because I didn't get my Media Center pack when I could, and I need, NEED to use it with my 360.
(I can't reply, dammit forum rules) Well how would I set it up, for 8.1 of course. Plus, what version of the WMC installer should I use? The ones I could find, with that wrapper, just give an error when trying to add the extender.
After installing the wrapper, did you go into the configuration and set it as shown in the thread I linked to, then reboot and check that it shows listening, fully supported? If you don't have that, WMC won't configure the XBox and you need to troubleshoot RDP Wrapper before continuing. It doesn't matter what order you install in as long as you reboot after installing RDP Wrapper. I can set up the extender with either V12 or V13 but it only works properly with V12 (playback keeps stopping, IDKW) so I would definitely go with V12.
Well thing is that no matter what, it says "Listening, not supported". Same config as you. WMC V12. It also fails the extender setup the instant it is attempted (after putting the extender code in)...
Which version of RDP Wrapper did you install? Have you tried updating the ini file from one of the GitHub repos? It needs to contain an entry that matches the version of RDP you are using, which is shown in the configuration utility. As I said, if you don't get fully supported in the utility, it is a waste of time trying to configure the Xbox.
The latest one, I updated the ini file with the built-in updater. Windows 8.1 Pro, completely up-to-date, x64. termsrv.dll version 6.3.9600.19628. They must've not updated it for this version... Edit: I added some stuff from this to fix it, and make it supported. But it still is failing the instant adding an extender is attempted... htt\\ps://github.\\com/stascorp/rdpwrap/issue\s/993 (remove the \s)
I just booted up my Windows 8.1 PCs and let them update. This is the config in RDPWrap: I had to reconfigure the Xbox because I had it configured on Windows 10 since I used it on here last, but it is working fine again now. I can't say why it isn't working for you but what I can say is that if RDP is working properly, WMC should find the XBOX and attempt to configure it. If there are other issues it usually fails on stage 3 so if it fails instantly, that to me, means that RDP isn't working properly. My suggestion for the next move would be to try a different ini file because I had to do that on Windows 10 before WMC would even attempt to configure the Xbox. edited a few times because it didn't didn't make any sense.