Print

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

[codecode]

I so I have a sub for MC and got MC27.

The problem is once the MC27 is closed, my pc thinks its on the wrong OS when I restart MC27 - I have to do a full reinstall.

Is this a known issue, how to fix it?

[EnglishTiger]

Sounds like your Desktop Shortcut for MC27 could be running the MC27 Installer and not "Media Center 27.exe"

[codecode]

No, I am certain that is not the case.
The program will run fine until it is closed, then the OS error pops up stating that MC27 was in the wrong OC, and requires reinstallation.

[wer]

Please provide screenshots.

[codecode]

"C:\Program Files\J River\Media Center 27\Media Center 27.exe" <- this is the path of my shortcut

[zybex]

Right-click the shortcut, select properties; go to the Compatibility tab and uncheck the "Compatibility mode" checkbox. Or just create another shortcut.

If that is unchecked, or if the same error happens when you execute the EXE file directly from that folder, then it means the Compatibility flags are set directly in the registry and need to be deleted. Check if there's something related to MC under these paths:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

[Awesome Donkey]

This also happens if you were using Windows 7 or Windows 8.1 and you upgraded to Windows 10. The only real fix for it is to do a library backup, then install Media Center 27 then uninstall it, then reinstall it again as a clean install then restore your library backup. I suppose you could also just copy/move the J River folder found in %APPDATA% to the desktop when doing this.

[codecode]

Right-click the shortcut, select properties; go to the Compatibility tab and uncheck the "Compatibility mode" checkbox. Or just create another shortcut.

If that is unchecked, or if the same error happens when you execute the EXE file directly from that folder, then it means the Compatibility flags are set directly in the registry and need to be deleted. Check if there's something related to MC under these paths:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

I checked, nothing in any of those.

[codecode]

This also happens if you were using Windows 7 or Windows 8.1 and you upgraded to Windows 10. The only real fix for it is to do a library backup, then install Media Center 27 then uninstall it, then reinstall it again as a clean install then restore your library backup. I suppose you could also just copy/move the J River folder found in %APPDATA% to the desktop when doing this.

I've had Win10 long before having MC.
My first action was to completely wipe all installed MC information and started from scratch. That said, I have only tried that way once after the issue persisting I did not go that way again, and have just been reinstalling without any data clearing.

[zybex]

I can reproduce that exact error by changing this value:
HKEY_LOCAL_MACHINE\SOFTWARE\JRiver\Media Core\Installations\Media Center 27\OS Version

For my Win10, the working value is 0x3F4. Anything else results in the same OS mismatch error.

[codecode]

Ugh. 'Now' he tells me...

Last night I went back to MC26. After to and fro-ing through that process the issue stopped.

Now... now I might get the gumption. But no harm no foul, I might just stay at MC26 for now since my machine needs some TLC elsewhere.

I will note your finding though as MC27 seems to have just the right 'umph' for my audiophilia.

[zybex]

You can just install MC27 without uninstalling MC26. They can coexist and will both work, using the same database. This way you can attempt to fix MC27 while still enjoying 26.

I think that the Reg key I mentioned would only get a wrong value if the MC installer itself was running in Compatible mode. Windows sometimes offers to enable compatible mode for a given EXE when it detects it had some problem running - sometimes just cancelling an installation triggers this behavior. If this were the case, you should see some reference to the MC installer on those AppCompatFlags registry keys.

[codecode]

Yes, I noticed they worked without much conflict.
However, I noted that in my task manager the running processes were jumping by plus or minus 1 - 3 at at time rather quickly.
That is where the 'to and fro-ing' comes from. It took a bit of 'smacking the top' to get that to stop by uninstalling MC27 - and the PC resisted me a bit too venerously. So the old TV reference, and finally settling with only MC26.

Note: I have not gone the regedit way as yet. I'm having heat drama with other operations atm.

Thanks for keeping tabs on this. I am sure others will benefit in the future as MC gains even more popularity.

[zybex]

MC starts JRWorker processes while doing many tasks, like importing or analyzing files. Windows itself frequently starts/stops processes for many scheduled tasks like autoupdates and .NET assembly compilation. It's a normal part of any OS and many applications.

If you're gonna get spooked by the changing process count you might as well switch to a Mac with OSX. It will still happen, but at least it will be hidden from you.

[codecode]

I dont agree. Flat out, nothing changes that fast and consistently on the same app. nothing.

[zybex]

I'm sorry to tell you, you don't know what you're talking about.