by rivorson » Tue Apr 21, 2015 3:47 pm
Running as administrator doesn't use a different user account, though that function does exist and has a similar name. It is necessary if you want MM to maintain file associations.
It is possible that the MediaMonkey.ini file has somehow come to require admin permission to read, in which case MM without admin rights might either fall back on default settings or create another MediaMonkey.ini in a folder with write permission. This scenario is unlikely but it's the only explanation I can think of.
When you run as administrator and MM opens with the Metro skin, are your database and settings all intact and correct? And does MM run Metro skin every time you run as administrator?
Running as administrator doesn't use a different user account, though that function does exist and has a similar name. It is necessary if you want MM to maintain file associations.
It is possible that the MediaMonkey.ini file has somehow come to require admin permission to read, in which case MM without admin rights might either fall back on default settings or create another MediaMonkey.ini in a folder with write permission. This scenario is unlikely but it's the only explanation I can think of.
When you run as administrator and MM opens with the Metro skin, are your database and settings all intact and correct? And does MM run Metro skin every time you run as administrator?