Reply to thread

Message

<blockquote data-quote="ears" data-source="post: 1129563" data-attributes="member: 83203">Thanks J - it's not an issue with the build, it's happened across a few builds for me but nobody else has reported these issues. It's something to do with my system but I'm damned if I know what. It can work OK 4 or 5 times, them just go bonkers with a whole load of corruption.. Errors in SDT, errors in BAT, you name it, the grabber finds errors in it. Then it ends with a bunch of corrupt data and assumes that none of my channels exist any more, promptly deleting them. Strange old affair.I might -&nbsp; just might - have stumbled upon something. I've had it being relatively well behaved for the last 5 or so updates by adding .ts files as an exemption in Windows endpoint protection. As it has a real time scanner I'm wondering if it's locking new ts files when they're first created and causing a bit of havoc.Don't let this put you off the 1.10 build - like I said, this one's unique to me.</blockquote>

[QUOTE="ears, post: 1129563, member: 83203"] Thanks J - it's not an issue with the build, it's happened across a few builds for me but nobody else has reported these issues. It's something to do with my system but I'm damned if I know what. It can work OK 4 or 5 times, them just go bonkers with a whole load of corruption.. Errors in SDT, errors in BAT, you name it, the grabber finds errors in it. Then it ends with a bunch of corrupt data and assumes that none of my channels exist any more, promptly deleting them. Strange old affair. I might - just might - have stumbled upon something. I've had it being relatively well behaved for the last 5 or so updates by adding .ts files as an exemption in Windows endpoint protection. As it has a real time scanner I'm wondering if it's locking new ts files when they're first created and causing a bit of havoc. Don't let this put you off the 1.10 build - like I said, this one's unique to me. [/QUOTE]

Verification