Kodi Community Forum

Kodi Community Forum > Support > General Support > Windows > Win7 - Krypton 17.1 - Stuck on "Splash" screen
Full Version: Win7 - Krypton 17.1 - Stuck on "Splash" screen
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

ThaiWalker

2017-05-17, 04:53
Hi,
I'm trying to install and start Kodi (17.1) on a new Windows 7 install, very minimal so far.
Kodi starts but stays forever on that splash screen.

Don't exactly know how to get a detailled log - if possible - but the file kodi.log ends like this
Code:
...
09:39:06.692 T:4316  NOTICE: Additional mode: 1600x900@ 60.00 - Full Screen
09:39:06.692 T:4316  NOTICE: Previous line repeats 2 times.
09:39:06.692 T:4316  NOTICE: Additional mode: 1600x1024@ 60.00 - Full Screen
09:39:06.692 T:4316  NOTICE: Previous line repeats 2 times.
09:39:06.692 T:4316  NOTICE: Additional mode: 1680x1050@ 60.00 - Full Screen
09:39:06.692 T:4316  NOTICE: Previous line repeats 2 times.
09:39:06.692 T:4316  NOTICE: Additional mode: 1920x1080@ 60.00 - Full Screen
09:39:06.696 T:4316  NOTICE: Checking resolution 16
09:39:08.425 T:4340  NOTICE: Running database version Addons27
09:39:08.432 T:4340  NOTICE: Running database version ViewModes6
09:39:08.450 T:4340  NOTICE: Running database version Textures13
09:39:08.462 T:4340  NOTICE: Running database version MyMusic60
09:39:08.499 T:4340  NOTICE: Running database version MyVideos107
09:39:08.504 T:4340  NOTICE: Running database version TV29
09:39:08.505 T:4340  NOTICE: Running database version Epg11
09:39:08.558 T:4316 WARNING: CSkinInfo: failed to load skin settings
09:39:08.779 T:4316 WARNING: JSONRPC: Could not parse type "Setting.Details.SettingList"
09:39:08.888 T:4316  NOTICE: initialize done
09:39:09.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:14.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:16.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:21.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:24.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:29.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:31.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:36.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:39.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:44.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:46.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:51.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:39:54.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush
09:39:59.186 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::InitSink - failed to init
09:40:01.686 T:4344   ERROR: ActiveAE::ActiveAE::CActiveAE::FlushEngine - failed to flush

Any idea where to go from there?
Thanks

Karellen

2017-05-17, 04:59
Hello,

We will need two things...

1. The debug log. Follow this easier guide... http://forum.kodi.tv/showthread.php?tid=...pid2572642
2. Details of your hardware

ThaiWalker

2017-05-17, 05:17
First time discovering log feature :-)

Here is the log https://pastebin.com/FtADYzDV


And hardware details...
Win7 x64
on
Asus Strix Z270F & GTX 1050-2G

As far as I can say, drivers have been updated

Thanks for your help

Karellen

2017-05-17, 05:25
There are a few things that stand out, but I think they all come back to your install process.

You seem to have modified the install process. How and why have you done that? You have some unusual directory names and locations.

Code:
special://xbmc/ is mapped to: E:\Programs\Krypton
10:02:01.060 T:4544  NOTICE: special://xbmcbin/ is mapped to: E:\Programs\Krypton
10:02:01.060 T:4544  NOTICE: special://xbmcbinaddons/ is mapped to: E:\Programs\Krypton/addons
10:02:01.060 T:4544  NOTICE: special://masterprofile/ is mapped to: E:\Programs\Krypton\portable_data\userdata
10:02:01.060 T:4544  NOTICE: special://home/ is mapped to: E:\Programs\Krypton\portable_data\
10:02:01.060 T:4544  NOTICE: special://temp/ is mapped to: E:\Programs\Krypton\portable_data\cache
10:02:01.060 T:4544  NOTICE: special://logpath/ is mapped to: E:\Programs\Krypton\portable_data\
10:02:01.060 T:4544  NOTICE: The executable running is: E:\Programs\Krypton\kodi.exe
10:02:01.061 T:4544  NOTICE: Local hostname: Asus2017
10:02:01.061 T:4544  NOTICE: Log File is located: E:\Programs\Krypton\portable_data\/kodi.log

I think the best thing to do is completely uninstall, and reinstall in the correct manner.

ThaiWalker

2017-05-17, 05:33
It's just the normal "portable" way, following the wiki instructions. Not my first time, even with Kodi 17.1 and it always worked perfectly.

Karellen

2017-05-17, 05:50
Ok. What are you trying to achieve?

ThaiWalker

2017-05-17, 06:03
I am not trying. I have been succeeding for some time now. Like a lot of people using portable software, I am trying to avoid re-installing again and again everything when I have to re-install again Windows, or move to a new machine. It worked and usually works.

My first try on this new machine was not with a bare Kodi of course. And I strongly believe my actual trouble has nothing to do with the path, but with my new hardware and drivers or Kodi code associated with it.

Thanks

PatK

2017-05-17, 15:01
In your case the best way to accomplish this, would be .. yet another portable install. Ensure it's operation (that would confirm your hardware) close Kodi. then inject the contents correct path Kodi\portable_data replacing the existing. Next launch you'll be at the right place with your previous settings. If you're still having issues another debug log at that point would be informative.

ThaiWalker

2017-05-17, 15:45
(2017-05-17, 15:01)PatK Wrote: [ -> ]In your case the best way to accomplish this, would be .. yet another portable install. Ensure it's operation (that would confirm your hardware) close Kodi. then inject the contents correct path Kodi\portable_data replacing the existing. Next launch you'll be at the right place with your previous settings. If you're still having issues another debug log at that point would be informative.

I am not sure what you mean exactly by "yet another portable install".

But to be clear
- I first simply copy my previously running installation,
- then did a fresh portable install,
- and again to be sure, a normal/classic installation,
- before I went back to my needed and favorite one...

They all/each and every one of them got stuck at the same "place" with the same messages. That's why I felt allowed to say that the trouble is not not coming from the type of installation.

Anyway, thanks for trying.
I do intend to restart everything from zero tomorrow :-)

PatK

2017-05-17, 17:20
Quote:I am not sure what you mean exactly by "yet another portable install".
Looking at the statement "I am trying to avoid re-installing again and again everything" Your solution is not quite in the order of things I laid out.

This:

I do intend to restart everything from zero tomorrow :-)

ThaiWalker

2017-05-17, 19:00
I'm glad to see how helpful and to the point you are, both of you.... which so explains this forum reputation.

ThaiWalker

2017-05-21, 05:41
By the way. it's now working perfectly... and not because of you!

And I can already tell you you're going to have more and more people with the same kind of trouble, portable or not! Good luck!

nickr

2017-05-21, 06:32
Thai Walker you come across as pretty rude. Warning coming.

Uberwolf

2017-05-23, 17:29
Well to be honest I'm a bit pissed off also because of this issue and it is an issue. Before I updated my perfectly working Kodi I checked on the forums that I could install ver 71.1 over 16.1 and keep my current installs settings, so all I did was install the new version, kodi-17.1-Krypton over my last install 16.1 and now I cannot access Kodi. I notice when I run Kodi within seconds the Windows Task manager shows Kodi "Not Responding". I really do not want to uninstall everything, I was comfortable with the setup I had prior to this and if I wanted to uninstall Kodi I would have done so from the start. Any idea why this is happening.

Karellen

2017-05-23, 21:15
(2017-05-23, 17:29)Uberwolf Wrote: [ -> ]Well to be honest I'm a bit pissed off also because of this issue and it is an issue. Before I updated my perfectly working Kodi I checked on the forums that I could install ver 71.1 over 16.1 and keep my current installs settings, so all I did was install the new version, kodi-17.1-Krypton over my last install 16.1 and now I cannot access Kodi. I notice when I run Kodi within seconds the Windows Task manager shows Kodi "Not Responding". I really do not want to uninstall everything, I was comfortable with the setup I had prior to this and if I wanted to uninstall Kodi I would have done so from the start. Any idea why this is happening.

Your issues is not the same as the issue in this post. Re-read the first post to understand why.

Now read Post #2, follow the directions and submit for review.
Kodi Community Forum > Support > General Support > Windows > Win7 - Krypton 17.1 - Stuck on "Splash" screen