Error unable to create gui exiting kodi что это
kcarney
Member
So I just upgraded from 17.6 to 18.1 and the Error: Unable to create GUI. Exiting pops up when attempting to launch kodi via RDP. This is a VM running on ESXI 6.7 that I use solely for database maintenance and library updates to SQL.
If I connect to the VMConsole kodi will launch fine, any tweaks I can make to the VM hardware that might help?
u could try if next link has influence Enabling GPU rendering on Windows Server 2016 / Windows 10 RDP if u don’t like group objects, u could try next link Use hardware graphics adapters for all Remote Desktop Services sessions which shows the registry key for it.
Btw i checked my own pc’s registry for this key i don’t have it on my windows 10 machine (whom is acting as rdp server through rdp wrapper) so don’t really know if it will help.
Just found on a thread about acceleration:
«one thing you should keep in mind if your rdp settings are too low the acceleration is turned off.
in my experience if you want acceleration to work normally you need 32bit color (Depending on your app this could be lowered) and set the connection speed to LAN.». In my own setup i’ve it both on autodetect but effectivly it means i get highest display and bandwith settings, so it could matter.
Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2 might also contain some clues. As for example RemoteFX cannot be used and such.
Error unable to create gui exiting kodi что это
Новые темы необходимо создавать только в корневом разделе! В дальнейшем они будут обработаны модераторами.
Если Вы выложили новую версию программы, пожалуйста, сообщите об этом модератору нажав на вашем сообщении кнопку «Жалоба».
Последнее обновление программы в шапке: 11.10.2021
Краткое описание:
Кросс-платформенный медиацентр XBMC.
Бесплатный кроссплатформенный медиаплеер и программное обеспечение для организации HTPC с открытым исходным кодом. Графический интерфейс программы позволяет легко управлять видеофайлами, фотографиями и музыкой, находящимися на компьютере, оптическом диске, в интернете или в локальной сети. Может управляться с помощью ПДУ.
Android 4.2+:
версия: 16.1 Jarvis for Windows Kodi (Пост _SERGEYX_ #56018605)
версия: 16.0 Jarvis Kodi (Пост fack1900 #47300196)
версия: 16.0 Jarvis x86 Kodi (Пост ROMANFIONOV #47315630)
версия: 15.2 final Kodi (Пост grey684 #43824098)
версия: 15.2 + кэш Kodi (Пост fack1900 #44038040)
версия: 14.2 (x86) Stable 
kodi-14.2-Helix-x86.apk ( 61.12 МБ )
версия: 14.2 (windows) Stable 
kodi-14.2-Helix.exe ( 67.82 МБ )
версия: 15.1.1 Kodi (Пост grey684 #42405075)
версия: 15.1 + кэш Kodi (Пост fack1900 #42280136)
версия: 15 + кэш Kodi (Пост fack1900 #41793816)
версия: 15.0 + кэш KODI (XBMC) (Пост fack1900 #41260543)
версия: 14.2 (arm) Stable kodi-14.2-Helix-armeabi-v7a.apk ( 59.74 МБ )
версия: 13 Stable XBMC (Пост #31290789)
версия: 13 XBMC (Пост #31210770)
версия: 12.2 https://4pda.to/forum/dl/post/2915114/xbmc-12.2-Frodo-armeabi-v7a.apk
версия: 12.1 xbmc-12.1-Frodo-armeabi-v7a.apk
версия: 12.0 http://mirrors.xbmc.org/releases/android/x. armeabi-v7a.apk
NEON Devices (Nexus 7 / Tegra3 / Newer Samsung Devices): xbmcapp-armeabi-v7a-debug-08-22-full-neon.apk
Non-NEON Devices (Tegra2 / A500 / A100 / Thrive): xbmcapp-armeabi-v7a-debug-08-22-no-neon.apk
версия: n/axbmcapp_armeabi_v7a_debug_20120714.apk ( 39.01 МБ )
Error unable to create gui exiting kodi что это
Rockeily
Member
(2017-11-19, 17:09) RENATOLORETO Wrote: When I try to obtain updated video drivers systems says thzat I have the lates version of drivers.
tom886
Junior Member
(2017-12-21, 08:46) nickr Wrote: Make sure you get the drivers from the video card/motherboard manufacturer, not microsoft.
Or much better, directly from the Graphic card vendor, e.g. Intel, AMD, NVDIA
Theme by Mishar DESIGN, modded by Team Kodi
Copyright © 2017 XBMC Foundation
Quick Links
Sponsors
About Kodi
Kodi is a free and open source media player application developed by the XBMC Foundation, a non-profit technology consortium.
Kodi is available for multiple operating-systems and hardware platforms, featuring a 10-foot user interface for use with televisions and remote controls. It allows users to play and view most videos, music, podcasts, and other digital media files from local and network storage media and the internet.
Error unable to create gui exiting kodi что это
Derek
Posting Freak
Marco275
Member
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
k4sh1n
Posting Freak
AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
jmh2002
Posting Freak
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too 
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
Marco275
Member
If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
(2016-03-16, 09:57) Marco275 Wrote: If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
k4sh1n
Posting Freak
Can you remove profiles.xml from KODI userdata folder and re-start KODI
Win key + R key
Paste: %appdata%\Kodi\userdata\
Press OK
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
(2016-03-16, 09:57) Marco275 Wrote: If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
absolutely nothing has worked at all. but i appreciate the help
(2016-03-17, 05:13) k4sh1n Wrote: Can you remove profiles.xml from KODI userdata folder and re-start KODI
Win key + R key
Paste: %appdata%\Kodi\userdata\
Press OK
Error unable to create gui exiting kodi что это
gjwAudio
Senior Member
Please help steer a newbie down the right path. I am brand new to XBMC (. excited to get it running), and cannot get the program to start successfully. A search of the Windows Support forum does not yield answers to the issue (although there are hits on the text of the error message).
Launching the program results in this error message:
Thank you in advance for any and all suggestions.
Cheers,
Grant
baijuxavior
Posting Freak
Update the gpu driver and try.
gjwAudio
Senior Member
Thanks for your quick reply. I followed the link you supplied (thanks for that), and created the entry to enable debug logging.
I also updated my nVidia drivers to the current stable release from GeForce.com (ie: v320.18_WinXP WHQL [2013-05-23]).
All this done to say: I receive the same error when XBMC is launched.
Bennie
Newbie
gjwAudio
Senior Member
jhhoffma
Senior Member
I know WinXP doesn’t support hardware acceleration in XBMC’s internal video player, but you should still be able to start up the GUI.
Unless your DirectX install is borked.
gjwAudio
Senior Member
Heh-heh. in a vain and pointless attempt (so it seems), I re-ran «directx_Jun2010_v9.29.1974_redist.exe» to refresh any files that may have needed it. Can’t find an execution log to verify anything was actually changed. Onward.
Relaunched xbmc. Same error as before.
Thanks again for any and all help.
Cheers,
Grant
gjwAudio
Senior Member
Bennie
Newbie
gjwAudio
Senior Member
(2013-06-23, 15:33) Bennie Wrote: It seems the other people haven’t met such a problem. Til now I still cannot run XBMC.
gjwAudio
Senior Member
(2013-06-30, 00:58) teeedubb Wrote: Have you tried moving/deleting the xbmc userdata folder? If the pc is just going to be used as a htpc take a look at openelec.
Deleted «userdata» folder and launched xbmc. Same result (though the usderdata folder was recreated before the crash).
Without knowing what a «normal» execution log looks like, I cannot troubleshoot the messages being sent as the program crashes. Too bad for me the «Log Swamis» are busy elsewhere.
This installation (on my main desktop environment) was intended to familiarize myself with xbmc basics, prior to building a dedicated HTPC. A rather inauspicious start.
Thank you for any pointers.
Grant
gjwAudio
Senior Member
I presume the Install stick creates the executable environment (in this case, another USB stick) according to what hardware is present (ie: mobo resources, video & audio, network, etc), so there’s no way around that step, if I want the «simplicity» and «ease» of running xbmc via OpenELEC.
Seems like no xbmc for this boy. no matter what path I take 
