Page 1 of 1

WMC has corrected a problem with your recording data

Posted: Tue Jul 09, 2019 2:50 pm
by technodevotee
I’m sure that a lot of people have had this happen:
WMC reports "Windows Media Center has corrected a problem with your recording data and will download the Guide again. You should review your recordings to verify they are still scheduled correctly."

It then rebuilds the database and you get no recordings until it has repopulated - something that could take several days given how often the download from Microsoft seems to fail.

It has happened to me a few times when the PC has been running perfectly happily for a few months and it has even happened since I’ve been using EPG123. Whatever causes it, unless I've had a recent backup available, it has created a lot of work for me. Lost recording history, resulting in duplicated recordings, missed scheduled recordings and, possibly worst of all, a severe reduction in WAF.

I’ve found that if you edit the entry in the registry that tells WMC which database to use so that it points to the old database, it quite often works perfectly. It also usually seems to work fine after manually importing the most recent MXF file so I’m not convinced that it is being caused exclusively by a corrupted data download and wondered if it isn't even so much that the database is being corrupted as something else.

I've noticed that it quite often happens after restoring the programdata\ehome folder and registry on a PC that has just had WMC reinstalled and while investigating the issue, I discovered that the aforementioned entry in the registry is missing after WMC has been freshly installed.

So I've added a default setting in the install.reg file of my V13 installer in the hope that it might help and I've built a function into backuprestoresettings.cmd that checks for the entry and creates one if needed before doing a backup and after doing a restore.

I've also made a standalone/add-on version that can be used with any other version of installer, which is available here: ...

Note that while this isn't exclusively a problem that occurs in Windows 10, my modifications and add-on utility is intended primarily for Windows 10.