Yeah, downloaded and installed 21343.1000 as a clean install and it seems to work OK with WMC 8.8.5 but it is an insider preview so I guess it will expire at some point. Edition Windows 10 Pro Insider Preview Version Dev Installed on 25/03/2021 OS build 21343.1000 Experience Windows 10 Feature Experience Pack 321.7401.0.3
sweet, that's good to know, lets hope when it gets released, there aren't differences to kill WMC thanks for taking the time to have a try do you only use the BackupRestoreSettings.cmd? if so, try what i did and use epg123 and Seans WMC Backup.exe as well to begin with i install 8.8.5, run through all my settings and setup tv signal and then make a backup using BackupRestoreSettings.cmd then i restore my recording schedule using Seans WMC Backup.exe, or you can add what you want to record and then make a backup using Seans WMC Backup.exe I then make a backup using epg123 when i reinstall, i install 8.8.5, then i restore from BackupRestoreSettings.cmd, i can either then use Seans WMC Backup.exe to restore schedule recordings, or epg123. i have had to use epg123 of late because Seans WMC Backup.exe has been saving duplicates, even though inside WMC there is still only single entries??? Hope that helps
I use the free edition of the VEEAM Agent to create a daily incremental back of all my PCs on my NAS. That way, I can do a bare metal or file by file restore to any point in the past 30 days. I also use BackupRestoreSettings to make a backup on a monthly basis then move the resultant files to a different folder. Before an upgrade, I make a new backup then restore after reinstalling, I have also tried using the EPG123 backup and restore features. If the update or re-install messes up the database, I use the EPG123 transfer tool to put back my scheduled recordings. I found that Sean's WMC Backup doesn't restore everything so I don't use it any more.
Nope. Being only a minor Registry-only upgrade (aka fake mockup build), it will not expire. Exactly as 20H2, it is technically 20H1. Expect problems once 20H2 impacts, with all that Sun Valley stuff aboard. Testing WMC regularly on the true Dev builds is much better to check if it will be with us for a long time to come or not.
As you I'm sure you can tell, I am not a long term tester and normally run stable releases on all my PCs. I install new stuff on a spare HDD every now and then to see if it s going to break WMC then revert to my 'production' HDD once I have satisfied my curiosity.
@technodevotee hmmm strange, Seans WMC Backup.exe had been fine up until recently. I am the same as you but use a spare ssd and occasionally select to boot into the test ssd to test. I have just made 21343.1000.210320-1757.RS_PRERELEASE_CLIENTPRO_OEMRET_X64FRE_EN-GB.ISO from the dev channel on uup dump, took 28 mins to make @everyone the one from the insider preview is Windows10_InsiderPreview_Client_x64_en-gb_21286.iso , its older and larger in size
I can answer part of that I think. The version number and experience number on the fully up-to-date insider PC I'm currently running is the same as the one I installed from scratch using the ISO I downloaded and built from UUP files yesterday - and that is the same file you now have.
ty, i will clean install 21343.1000.210320-1757.RS_PRERELEASE_CLIENTPRO_OEMRET_X64FRE_EN-GB.ISO from the dev channel on uup dump, on my spare ssd, as we know 21H1 will work ok and test every now and then and report any problems here, for the more technically adapt people to comment on. is this the same from the official insider preview? How often do updates get distributed?
When I was running a PC on Insider Channel in the past, I was getting an update at least once a week and it got to be rather annoying. As you know Windows 10 updates tend to be roll ups now and the recent ones take ages to install on my spare PC. I've had one every few days recently so I probably won't be able to run it for long before getting bored and disconnect it again :> And I thought the amount of updates we get forced on us on stable builds were annoying.
did the updates require a reinstall of WMC, as in did it rewrite the whole OS? I can boot to my test ssd once a week
spare ssd is all setup, ill install WMC when i have some spare time and be prepared for reinstalling each week
Dev channel is where the real changes are rolled out and tested, the ones with a potential to break compatibility. So, checking it out in a dev channel build once in a while provides a good reflection of what to expect in the future. Many of the tested changes eventually end up in the release builds, though not all.
I have a problem when starting live tv, it takes really long time to start up but when started it shifts smoothly between channels, what could the problem be? Almost forgot to say that I'm running WMC 8.8.5 with the latest Windows function update
This might be to do with PlayReady which is required for material protected by DRM. If you don't use protected media, you can probably safely rename the datafile MSPR.HDS and it will create a new file. (%programdata%\microsoft\PlayReady\mspr.hds). Note however that if you do use protected media this will cause issues when trying to play existing recorded TV.
I have a problem with my WMC remote on a new install. I setup an HTPC with windows 8.1 (some of the hardware is a bit old and the drivers work better in Win 8.1). I used the latest installer v8.8.5 to add WMC, which worked great. However none of my WMC (RC6) remotes work out of the box. I used some instructions FROM the kodi site to hack the registry so I can use an Xbox Media Remote, that I had handy and that works ok, but the regular RC6 remotes won't work (I have the original Microsoft one and a Phillips). I would like to use them as they have some key features missing from the xbox remote (especially the color-coded buttons). Has anyone dealt with this before? I assume another registry hack will be needed...