Print

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

[Cinelder]

I haven't been able to successfully update MC 34.23 to MC 34.024.  The installer seems to run normally but then never opens MC 34 after seeming to complete the installation.  I've tried unimstalling MC 34 and reinstalling, rebooting after uninstalling and re-installing, but nothing seems to help - MC 34 gets stuck at the same point after seeming to complete installation and then never opens the main program MC 34.  I've tried manually killing MC processes in task manager and manually restarting MC 34, but that doesn't work, either. It just seems to idle in task manager.

On other hand, I can run MC33 normally.  However, if I then try to run MC34 again, it closes MC 33 (which I didn't expect) and never opens MC34.  Plus, fwiw, when I tried to reinstall g-force visualizer in MC 33, it installs normally, but crashes MC 33 immediately if I try to switch display to the visualizer.

Any suggestions or help most appreciated

[JimH]

Antivirus.

[Cinelder]

Antivirus.

Thanks for the response. I'm not sure what to do -- the system only has Windows Defender on it, and AFAIK the settings for inbound/outbound connections are identical to MC33, and the same as they were for MC 34.23 and previous builds of MC34 which all installed and opened normally.  I ran SFC which found errors, but retrying installation after SFC completed had the same results as before - MC 34 appears to install but never opens - just winds up idling in Task Manager.   FWIW, I think perhaps something went awry with the initial update process itself. 

[Awesome Donkey]

With each major version of Media Center you'll have to redo the Defender exclusions to point to the new Media Center 34 and the executables (Media Center 34.exe, JRWeb.exe, JRWorker.exe, etc).

[Cinelder]

With each major version of Media Center you'll have to redo the Defender exclusions to point to the new Media Center 34 and the executables (Media Center 34.exe, JRWeb.exe, JRWorker.exe, etc).

As before after installing with earlier versions of MC and MC 34, Windows Defender popped automatically - and asked about exclusions for 34. 

However if there's something not ticked or that should be unticked in Defender to fix the issue, I can't find it - all the Defender exclusions look the same in Defender/Firewall as before, both in previous MC 34 builds and earlier versions of MC (33, 32, 31, 30, 29., 28) and seem to point to MC 34. 

I know this is a single user issue, but I really liked 34 and would like to be able to open it again.

[Awesome Donkey]

Manually add the Media Center 34 folder and executable exclusions. Defender itself doesn't update those from existing ones, at least for the antivirus side, you have to manually add the exclusions.

[Cinelder]

Manually add the Media Center 34 folder and executable exclusions. Defender itself doesn't update those from existing ones, at least for the antivirus side, you have to manually add the exclusions.

Thanks for the response.  I've tried the Defender exclusions manually, but get results with the same problem.  After the update, Task Manager reports MC 34 is running, but it just won't complete the last step after update and reopen the default MC window.  Instead, the exact same thing happens as before.  Task Manger thinks MC 34 is running, though I can't see the MC window and switch focus to it by alt-tab.  I  have to manually kill the process in Task Manager to try re-installation. 

It's very frustrating - I"d been updating all the latest releases from the initial build of MC 34 to MC 34.0.23 without issue.  In particular, MC 34.0.23 was running fine before the MC.34.0.24 update with no Defender issues.  Something seemed to go wrong during the initial go at the update process. Coud it have left some lingering problem that isn't fixable by uninstalling MC and trying to reinstall?  I'm talking off the top of my head, but could it be some conflicting registry entry or file that got corrupted when the initial update malfunctioned and that isn't handled by normal uninstallation/re-installation? 

I can certainly continue to get by with MC 33, but it sure would be nice to be able to see that MC 34 window open again...

[Awesome Donkey]

Usually when Media Center 34 is running in the background and not appearing on a new install, that means Windows Defender is in the background sending Media Center's executables and DLL files to Microsoft's servers for additional scanning. If you wait awhile, it *should* finally appear once it's done.

It's annoying that Defender does that, considering most of Media Center's files are signed with an extended validation certificate, but for whatever reason they don't seem to take it into consideration. This tends to happen right after a major version of Media Center is released to the public.

I really should update the Defender thread with updated screenshots and recommendations. Some users exclude the Media Center 34 folder and don't seem to have issues, but in my own experiences that's not enough. You'd need to exclude the install folder, each .exe file in the main install directory and even exclude the J River/Media Center 34 folder in %APPDATA% to stop it completely from messing with Media Center. I even exclude the Media Center 34.exe process in Defender as well.

[Awesome Donkey]

Here's the full list of Media Center's folders, files and processes I exclude in Windows Defender.

Folders To Exclude:

C:\Program Files\J River
C:\Program Files\J River\Media Center 34
C:\Users\YOURUSERNAME\AppData\Roaming\J River
C:\Users\YOURUSERNAME\AppData\Roaming\J River\Media Center 34

NOTE: Replace YOURUSERNAME with the name of your Windows account used, or use %APPDATA% in File Explorer to access the folder.


Executables To Exclude:

C:\Program Files\J River\Media Center 34\Media Editor.exe
C:\Program Files\J River\Media Center 34\PackageInstaller.exe
C:\Program Files\J River\Media Center 34\JRCrashHandler.exe
C:\Program Files\J River\Media Center 34\JRMediaUninstall.exe
C:\Program Files\J River\Media Center 34\JRService.exe
C:\Program Files\J River\Media Center 34\JRWeb.exe
C:\Program Files\J River\Media Center 34\JRWorker.exe
C:\Program Files\J River\Media Center 34\MC34.exe
C:\Program Files\J River\Media Center 34\Media Center 34.exe
C:\Windows\System32\MC34.exe
C:\Windows\SysWOW64\MC34.exe


Processes To Exclude:

Media Center 34.exe


Yes, it's all overkill, but it's my way to properly ensuring that Windows Defender can't mess with Media Center. And for me on my main PC and MC server PC Media Center 34 opens near instantaneously on Windows 11.

[Cinelder]

Here's the full list of Media Center's folders, files and processes I exclude in Windows Defender.

Folders To Exclude:

...

Very much appreciated!  Your full list of Defender exclusions did the trick - whatever it was must have been addressed by an exclusion on the full list.  If it fits there, I'd suggest adding your full Defender list of exclusions to the Thread of Wisdom (https://yabb.jriver.com/interact/index.php/topic,140570.0.html) or some other easy to find place on Interact.

After I excluded the full list you kindly provided, and tried re-installation, after a couple of anxious minutes monitoring Task Manager, MC 34 opened normally.  And, FWIW, the G-force visualizer now installs and works normally again.

Back to normal programming...

Thanks again, AD!