Normal
Giday.Long time MediaPortal user here.When the final of MediaPortal 1.21 went release, I downloaded and upgraded my working 1.20 install.I ran Mediaportal, and it started normally and was greeted by the familiar GUI of the skin I use, which is 'Apollo'I later had to reboot my PC thru windows updates.The next time I ran MediaPortal 1.21, (which was working before restarting the PC) it starts, then seems to get into some weird startup loop, which I can not escape from, except by using task manager, and even then it is hard to select the mediaportal process and kill it, as it is constantly restarting.I retrograded back to MediaPortal 1.20, and everything works fine once more.When 1.22 pre-release dropped, I tried upgrading again from 1.20 to 1.22 pre-release, and the identical thing happens, and get stuck in infinite start loop, where Mediaportal fails to make it into it's GUI interface. If I retrograde back to 1.20, then it is fine again.Any idea what might be happening here?, I am gonna try choosing a different skin from the configuration utility, but this behavior is kinda weird.
Giday.
Long time MediaPortal user here.
When the final of MediaPortal 1.21 went release, I downloaded and upgraded my working 1.20 install.
I ran Mediaportal, and it started normally and was greeted by the familiar GUI of the skin I use, which is 'Apollo'
I later had to reboot my PC thru windows updates.
The next time I ran MediaPortal 1.21, (which was working before restarting the PC) it starts, then seems to get into some weird startup loop, which I can not escape from, except by using task manager, and even then it is hard to select the mediaportal process and kill it, as it is constantly restarting.
I retrograded back to MediaPortal 1.20, and everything works fine once more.
When 1.22 pre-release dropped, I tried upgrading again from 1.20 to 1.22 pre-release, and the identical thing happens, and get stuck in infinite start loop, where Mediaportal fails to make it into it's GUI interface. If I retrograde back to 1.20, then it is fine again.
Any idea what might be happening here?, I am gonna try choosing a different skin from the configuration utility, but this behavior is kinda weird.