Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CountryBumkin]

Last week I noticed when Microsoft did its last big upgrade that MC went from version 23.90 to 23.69.

I reinstalled the latest version which was 23.91. I made sure the Update Channel had "Automatic Updates" turned off (unchecked), and furthermore I have the box checked for "Beta" updates.

A couple of days ago, I noticed MC was back to version 23.69. Then I reinstalled 23.91 and double checked that the Automatic Updates are Off.

Now today, I check and its back to version 23.69.

I assume this is Microsoft'd doing. Any idea what is going on and how to stop it?

[RoderickGI]

Definitely Microsoft's doing. Well, it could just be your anti-virus or firewall application I guess. But let's blame Microsoft. That is my latest hobby.

Something is reverting to the "Last known good" version of the program when it finds the new version and decides it is/could be a virus. I had a recent installation where Norton 360 had to be whipped in order to get it to allow MC to run. Discussion here: https://yabb.jriver.com/interact/index.php/topic,113364.msg783702.html#msg783702

I assume that it is Windows Defender that is doing it. Microsoft is turning on bits of that even when it is supposed to be disabled and a different anti-virus application is being used. Or seem to be. I've had some messages from Windows Defender and Windows Firewall after recent Windows updates and I use neither.

So check your anti-virus solution first, your firewall next. Make sure the current version of MC is allowed. If that doesn't work, start researching what in Windows reverts to a previous version silently.

[godt]

I am having this problem as well. 90 reverts to 70, for example. I have bored myself witless searching as suggested, but all results are to do with reverting Windows, not programs installed. Any other suggestions as to how this issue might be approached?

[godt]

I took the shotgun approach and killed Windows Defender antivirus in the registry. For 2 days I was able to run 94, before it reverted again to 70. If there are bits of Defender which keep initiating themselves, how might this be stopped?

[MGD_King]

What build of Windows 10 are you using? And what kind of processor do you have? Intel or AMD?

[Awesome Donkey]

I took the shotgun approach and killed Windows Defender antivirus in the registry. For 2 days I was able to run 94, before it reverted again to 70. If there are bits of Defender which keep initiating themselves, how might this be stopped?

This is a bad idea. Windows Defender is deeply rooted in Windows 10 now, trying to disable and/or remove it may cause system issues. Instead of doing that, try adding exceptions for Media Center's directories, executable (EXE) files and DLL files. In addition, you might want to exclude file types of your media (e.g. flac, wav, m4a, m4v, avi, etc) and exclude the location(s) you store your files.

[godt]

I have the latest version of Windows 10 - 1709, build 16299.192, 64 bit on an AMD Phenom II X3 720 with 8gb RAM. Yes, I've read that disable Defender antivirus is a bad idea, but I thought it worth - in the absence of any other path of action - following up RoderickGI's suggestion that Defender was indeterminately firing up bits of itself.

I have no sign of any bad behaviour as a result of disabling Defender Antivirus through the registry. But what I can't find in Defender is how to add exceptions. This seems to be missing - or I am missing something.

[RoderickGI]

Maybe something is triggering a System Restore. (I trust that you aren't doing that manually, or you would have mentioned it!)

Take a look at this then:

Start up the Windows Restore process, Choose a different Restore Point, Next, Show more restore points. Is there an item in there that says "Restore Operation"? See attached image.

If yes, and you didn't know about it, something is doing a Restore by itself.

If no, try this:

Install the latest version of MC. Note version, date, and time you did that.
Create a Restore Point and name it suitably so you know it was for MC testing.

See what happens. If MC reverts to an earlier version, check for a "Restore Operation" as soon as you notice it, since those notifications don't stay around forever.

[godt]

Cheers. I'll give it a go!