This application requires a java runtime environment что делать
«Minecraft Java Runtime Environment Error 1.6.0» обычно называется формой «ошибки времени выполнения». Разработчики программного обеспечения, такие как Mojang, обычно принимают Minecraft через несколько уровней отладки, чтобы сорвать эти ошибки перед выпуском для общественности. К сожалению, некоторые критические проблемы, такие как ошибка 1.6.0, часто могут быть упущены из виду.
Пользователи Minecraft могут столкнуться с ошибкой 1.6.0, вызванной нормальным использованием приложения, которое также может читать как «Minecraft Java Runtime Environment Error 1.6.0». После возникновения ошибки 1.6.0 пользователь программного обеспечения имеет возможность сообщить разработчику об этой проблеме. Mojang может устранить обнаруженные проблемы, а затем загрузить измененный файл исходного кода, позволяя пользователям обновлять свою версию. Поэтому, когда вы сталкиваетесь с запросом на обновление Minecraft, это обычно связано с тем, что это решение для исправления ошибки 1.6.0 и других ошибок.
Что вызывает ошибку 1.6.0 во время выполнения?
«Minecraft Java Runtime Environment Error 1.6.0» чаще всего может возникать при загрузке Minecraft. Проанализируем некоторые из наиболее распространенных причин ошибок ошибки 1.6.0 во время выполнения:
Ошибка 1.6.0 Crash - это распространенная ошибка 1.6.0 во время выполнения ошибки, которая приводит к полному завершению работы программы. Как правило, это результат того, что Minecraft не понимает входные данные или не знает, что выводить в ответ.
Утечка памяти «Minecraft Java Runtime Environment Error 1.6.0» - когда происходит утечка памяти Minecraft, это приведет к вялой работе операционной системы из-за нехватки системных ресурсов. Есть некоторые потенциальные проблемы, которые могут быть причиной получения проблем во время выполнения, с неправильным кодированием, приводящим к бесконечным циклам.
Ошибка 1.6.0 Logic Error - логическая ошибка возникает, когда Minecraft производит неправильный вывод из правильного ввода. Это связано с ошибками в исходном коде Mojang, обрабатывающих ввод неправильно.
Как правило, ошибки Minecraft Java Runtime Environment Error 1.6.0 вызваны повреждением или отсутствием файла связанного Minecraft, а иногда — заражением вредоносным ПО. Большую часть проблем, связанных с данными файлами, можно решить посредством скачивания и установки последней версии файла Mojang. В качестве дополнительного шага по устранению неполадок мы настоятельно рекомендуем очистить все пути к неверным файлам и ссылки на расширения файлов Mojang, которые могут способствовать возникновению такого рода ошибок, связанных с Minecraft Java Runtime Environment Error 1.6.0.
Частичный список ошибок Minecraft Java Runtime Environment Error 1.6.0 Minecraft:
- "Ошибка приложения Minecraft Java Runtime Environment Error 1.6.0."
- «Ошибка программного обеспечения Win32: Minecraft Java Runtime Environment Error 1.6.0»
- «Minecraft Java Runtime Environment Error 1.6.0 должен быть закрыт. «
- «Minecraft Java Runtime Environment Error 1.6.0 не может быть найден. «
- "Minecraft Java Runtime Environment Error 1.6.0 не найден."
- «Ошибка запуска в приложении: Minecraft Java Runtime Environment Error 1.6.0. «
- «Minecraft Java Runtime Environment Error 1.6.0 не работает. «
- «Ошибка Minecraft Java Runtime Environment Error 1.6.0. «
- «Minecraft Java Runtime Environment Error 1.6.0: путь приложения является ошибкой. «
kaikramer commented Dec 19, 2020
@Bill-Stewart I really appreciate your efforts to improve KSE and at a later point in time I will certainly take a look at your Inno Setup installer.
However, a few comments above I have posted a pre-release version of the new KSE launcher. This is going to be the solution for the launcher issue for the next KSE release. It is not complete yet, but the next KSE release is still pretty far away.
As I have said earlier, the installer is not the right place to search for JREs. Updating or switching Java runtimes after the installation is obviously not handled. And I certainly don't want to reinstall all my Java applications just because I have switched to another JRE. So the code for locating the JRE should be in the launcher, not in the installer.
In addition to the new launcher there will be a second version of KSE for Windows coming with the next release that includes a custom Java runtime. Providing a self-contained version of KSE is probably the best solution and it might also help with some tickets describing issues that I just cannot reproduce.
lawrence-dol commented Dec 19, 2020 •
That would be more than adequate, though I'm surprised you didn't do the JVM location in the launcher rather than the installer, if the ini file is not present. Perhaps because the installer is Windows specific, but the launcher code is not?
But that said, anyone using the zip package likely has more than enough skill to be able to set the path manually.
kaikramer commented Nov 21, 2020 •
As the launch4j project seems to be pretty dead (no release for more than two years), I have replaced launch4j with my own Windows launcher that uses the JAVA_HOME environment variable.
Just replace kse.exe in your KSE installation with the file from the ZIP file.
The next release of KSE will include this new launcher.
hendrikebbers commented Jul 20, 2020
douph1 commented Jul 21, 2020
To write "Oracle Java Key" you must write to
HKLM only ( be root required )
The key path is based on :
- Major version (1.8 or later)
- JRE vs JDK
- know if you use Wow > Wow6432Node
But a key must not be overridden with an older key ( always pointed to the latest/newest Java )
As it depends of the version intended to be installed and already installed, just write reg key without the binary is useless and or/copy/paste reg key from one host to another is a bad idea.
.jar and .jnlp apply to HKMU (switches between hklm and hkcu depending on machine or user installation)
.jnlp apply only to Java 8
Adding/splitting the installer features in two groups will break actual feature level compatibility. So no
Bill-Stewart commented Dec 18, 2020
In thinking about this a bit more, I wrote a launcher executable that uses a kse.ini file (same directory as .exe file) that looks like this:
The launcher uses this path to launch a command line such as:
" java home path \bin\javaw.exe" -jar " kse install path \kse.jar" [. ]
The installer has a Select Java Runtime page where you specify the Java home directory (it does some auto-detect using JavaSoft registry values, JAVA_HOME and JRE_HOME environment variables, and it also searches the path). If you run a reinstall, it will rewrite the kse.ini file.
For anyone that wants to use KSE on Windows without the installer, you could provide a sample kse.ini file and a readme.txt that says you need to manually add the Java directory to it.
This would seem to be a simple and clean solution that provides a simple way to run KSE on Windows without needing symlinks, complicated searching in the executable, etc.
Bill-Stewart commented Mar 5, 2019 •
Is OpenJDK really relevant on Windows?
Now that Oracle is forcing corporate JRE users to a subscription model, yes it is.
I've tested the AdoptOpenJDK JRE 8 distribution and it seems that KSE works with it without any problems. (Launch4j doesn't support it yet, but that's a separate problem.)
aahlenst commented Jul 21, 2020
I'm not yet sure what the exact problem is. Therefore it is hard to recommend something and even more so to take action.
What do you want to achieve? Beyond applying "registry magic" to the ZIP files? Do you need multiple Java versions and an easy way to switch between them? Why is using an MSI not an option?
dhamann commented Jul 21, 2020 •
To write "Oracle Java Key" you must write to
[. ]
[. ]
.jnlp apply only to Java 8
@douph1 thank you for all the input!
Adding/splitting the installer features in two groups will break actual feature level compatibility. So no
snap, i liked the idea :)
yes, that is what i tried yesternight . i tried to use a tool called regshot, which produced a bit too much noise (many background regchanges also in delta result) . hmm .
would you maybe be able to suggest relevant reg-branches i should monitor for changes, @douph1 ? I currently built the following reg-file . and am trying now to switch the current version. But i probably have not grasped the picture well enough.
but what about [HKLM\SOFTWARE\WOW6432Node\JavaSoft]? Do i need both? (Win10 Pro x64)
I am starting to fear this rabbit hole.
A batch file supplied with the zip distro that sets the right entries is probably also too complicated?
//last edit: please excuse the edit-storm. it has ended now.
kaikramer commented Nov 21, 2020
@lawrence-dol Java 1.8 is the minimum version. KSE works perfectly fine with Java 15. You just have to check the option to create the registry entry when installing AdoptOpenJDK as described on the download page.
Bill-Stewart commented Jun 14, 2019
Caveat: The 32-bit Launch4j will not detect the Oracle registry entries added by the 64-bit AdoptOpenJDK installer (you would have to install the 32-bit version of the JDK/JRE). But again: This is not KSE's problem at all, but rather an issue with Launch4j. I have worked around this by creating a "launcher" script that uses the JAVA_HOME environment variable and launching javaw -jar kse.jar .
Bill-Stewart commented Apr 23, 2019
This is a new feature they have added to the AdoptOpenJDK MSI installer that didn't exist when I posted earlier. This is good to know - thanks.
hendrikebbers commented Jul 20, 2020
dhamann commented Jul 20, 2020
hi @aahlenst the supplied info in the deep link is probably just the tip of the iceberg, i suppose? would i not also need some kind of reg entry for the directory that this keys point to? orcl url sadly does not mention anything like that there
Could the installer maybe also create windows cmd / batch files that make it possible to re-execute that same registry-setting commands for the specific version? (although I just peeked into douph1@c79c7e8 and that seems rather complicated :) ) Thank you for putting your time into this solution there, btw. Seems really challenging to find "the right" solution!
lawrence-dol commented Dec 19, 2020
Providing a self-contained version of KSE is probably the best solution.
Hmmm. I'm not so sure. When it comes to cryptography, I want it to use the version I have installed. I think I'd be concerned if my keystore manager is using crypto from JSE 15, released, say in 2018, and it was 2025 and JSE 22 is the latest. Seems like bundling a JVM is just adding maintenance overhead.
Still, your project, your call.
Bill-Stewart commented Dec 16, 2020
My recommendation on this front is that the launcher should perform several searches for increased robustness.
Search HKLM\SOFTWARE\JavaSoft subkeys for highest version number and use JavaHome value.
Use value of JAVA_HOME environment variable.
Use value of JRE_HOME environment variable.
Search the path for javaw.exe and use parent of parent subdirectory name.
In addition, the installer could create a JRE symlink in the application directory to the correct path.
FWIW I built an Inno Setup (IS) installer for KSE that adds the above features. The IS installer compiles to a bit larger size than NSIS but it looks and acts better (IMO) and can be localized fairly easily. (Let me know if you're interested.)
Bill-Stewart commented Feb 20, 2019 •
On Windows, one possible solution is to create a directory link inside the KSE installation directory using the cmd.exe built-in mklink command (available in Vista/Server 2008 or newer); e.g.:
(change paths as appropriate, of course)
douph1 commented Jul 21, 2020
on systems running Windows 8 or later
..a new registry key was introduced and Windows now writes the user choice to
"UserChoice"
HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Both the "App Paths" and "Applications" registry subkeys are used to register and control the behavior of the system on behalf of applications. The App Paths subkey is the preferred location.
I'm even not sure if WIX/our usage of WIX installer use the new "App Paths" reg key
as I have already seen that .jar file association don't work always.
ghost commented Jan 28, 2019
Hi,
@chhe your version did not work for me, im running windows 10 Pro 64bit and i needed to change your workaround like so:
this works for me.
dhamann commented Jul 21, 2020
I tried to omit the FeatureMain option when calling the msi-installer . so for example:
could maybe have done everything except installing files to target dir. But that did not produce the envisioned result.
uh this is hard.
hendrikebbers commented Jul 20, 2020
Is scoop like home-brew for windows? The project has 11k stars on GitHub. Maybe we should think about providing a script for scoop?
kriegaex commented Nov 2, 2016
Истоки проблем Minecraft Java Runtime Environment Error 1.6.0
Заражение вредоносными программами, недопустимые записи реестра Minecraft или отсутствующие или поврежденные файлы Minecraft Java Runtime Environment Error 1.6.0 могут создать эти ошибки Minecraft Java Runtime Environment Error 1.6.0.
В основном, осложнения Minecraft Java Runtime Environment Error 1.6.0 связаны с:
I do not know where to address my question (am aware this repo is for the installer), please be kind if you think this is the wrong place. i am open to recreating this issue somewhere else seen better fitting. but as i found the personally most fitting issue in this repo that is handling technicalities concerning the openjdk windows registry stuff i thought i post this issue here.
If there currently is no way . could the functionality be transformed to a utility that could be distributed inside the zipped distribution?
The text was updated successfully, but these errors were encountered:
dhamann commented Jul 20, 2020
hi both of you, @aahlenst you are thinking in the right direction, @hendrikebbers you too!
. actually i would like to be able to do the stuff the installer does to the registry by running a utility that sets the values for the version that is distributed with the zip file.
running a jar via doubleclick is one use case, another would be running an executable file generated by launch4j
@aahlenst i probably would need to do the stuff you pointed me to . for every installed java version and for every next coming update again? how do other people using the zipped distribution handle this? (please point me to a better target for my question if the openjdk-installer repo is a not fitting place for this, i just do not know where to ask)
dhamann commented Sep 13, 2020 •
After some weeks of inactivity i just re-read the whole thread and with this issue still being open i feel a bit of "something to do left" . so i would like to mention the rather hidden question of "my opening post" and leave the action of closing or further working on/with something to you. (You could also ask me to close it if that is the way to go)
If you think that this (something executable that would be included in the zip distribution) would be something that might be creatable . should i create a new issue asking for relating to just that (and relating to this issue as documentation of the thought process)?
In my first post i asked
". is there a way to reproduce the things the installer does concerning creation of the the required registry entries?"
and in hindsight i might have clarified that i was not thinking of crafting the reproduction myself but that something like an executable script (or something similar) already might exist that would be included in each zip distribution.
@douph1 thank you especially for the last three thorough replies! Via your input i now have a better understanding of the windows client side peculiarities of the jre/jdk installation. Or the challenges applications have to find out about the configured java binaries to run with.
Thanks, too, to everyone who took the time to inspect this Issue. :)
douph1 commented Jul 21, 2020
but what about [HKLM\SOFTWARE\WOW6432Node\JavaSoft]? Do i need both? (Win10 Pro x64)
no. it is intended for Java 32 on Win 64
By default it look only onto JavaSoft
so you must look/create (depending of the java version)
"CurrentVersion" on
- HKEY_LOCAL_MACHINE\Software\JavaSoft\ JRE
or/and - HKEY_LOCAL_MACHINE\Software\JavaSoft\ Java Runtime Environment (for 1.8)
and/or - HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\ JDK and/or
- HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\ Java Development Kit (for 1.8)
Bill-Stewart commented Dec 19, 2020
I suppose this is one approach. My thought was that the work of finding the Java runtime feels more appropriate for install time rather than run time, and it's not hard to reinstall (or just manually edit the kse.ini file).
dhamann commented Jul 21, 2020 •
I'm not yet sure what the exact problem is. [. ]
Reproducing the windows registry settings that get set by the installer after having extracted (either by hand or by using a tool like scoop) the zip-distribution.
What do you want to achieve? [. ] Do you need multiple Java versions and an easy way to switch between them?
Why is using an MSI not an option?
it is an option. i can do it via the installer. i thought there might already exist a way to have every needed jdk installed and switch the windows registry settings separately.
michelecos commented Jun 14, 2019
I tried Bill Stewart's solution And it works OK with my OpenJDK 11 installation. I think it might be implemented in KeyStore Explorer's setup. Something like «where is yout Java installation?».
kaikramer commented Jun 15, 2019
I tried Bill Stewart's solution And it works OK with my OpenJDK 11 installation. I think it might be implemented in KeyStore Explorer's setup. Something like «where is yout Java installation?».
Then KSE won't start anymore when the JRE location changes. The right place for detecting the JRE is the launcher. There has already been a patch provided for launch4j which solves this problem, but we'll have to wait for the next release of launch4j.
Bill-Stewart commented Dec 20, 2020
And I certainly don't want to reinstall all my Java applications just because I have switched to another JRE. So the code for locating the JRE should be in the launcher, not in the installer.
This is a persuasive argument in favor of including this logic in the launcher rather than the installer; I agree with this assessment.
dhamann commented Jul 20, 2020
hmm . i just tried it with the current installer . and it is like i want everything except the root node :)
would it be possible to put all the sub-entries of the root node in a second node that just sets the configuration? It could use the path supplied like shown in the screenshot below (i just painted that as a suggestive idea, the current dialog is also shown BELOW for reference)
Idea for different Dialog (two root nodes):
Current Dialog (one root node):
kaikramer commented Nov 1, 2016
Okay, so I have checked the source code of launch4j and it searches the registry (not the file system) for entries from Oracle and IBM:
"SOFTWARE\JavaSoft\Java Runtime Environment"
"SOFTWARE\JavaSoft\Java Development Kit"
"SOFTWARE\IBM\Java2 Runtime Environment"
"SOFTWARE\IBM\Java Development Kit"
However, the Zulu installer creates the following registry entry:
"SOFTWARE\Azul Systems\Zulu"
It might help to comment on the feature request, so the author of launch4j notices that there is not only one user that wants this feature.
Also, as I have already mentioned, there is always the option to copy the jre folder into the KSE folder. KSE then uses this local runtime preferredly.
kaikramer commented Jun 15, 2019
Caveat: The 32-bit Launch4j will not detect the Oracle registry entries added by the 64-bit AdoptOpenJDK installer (you would have to install the 32-bit version of the JDK/JRE).
That's not true. Launch4j has a configuration option called "runtimeBits", which determines which registry paths are checked for JRE locations:
runtimeBits
Optional, defaults to 64/32; Allows to select between 64-bit and 32-bit runtimes.
For KSE it's the default, which means both 64 bit and 32 bit Java runtimes are found.
lawrence-dol commented Jul 14, 2020
Now, of course, it's requiring 1.8 in a day where OpenJDK 15 is released. Why don't you set a minimum version with no maximum, instead of a specific version?
aahlenst commented Sep 14, 2020
If you really want to, you can create a PowerShell or batch script that does the registry alterations. But why? If you want that kind of automation, the MSI has you covered and even provides multiple safeguards you had to re-implement in the script. With something like scoop in the mix, it gets really hairy because you need to remove/update those entries. This is something that has to be solved by the application that manages you JDK installations.
For the record: I don't think it makes sense for scoop or a similar tool to use the MSIs. VS Code does it and judging by the bug reports we get here, this wasn't the right choice. If your tool does version management of JDKs, let your tool handle the registry stuff.
When running the kse.exe on Windows as installed by your installer, I get a popup error message. Maybe the tool has problems finding the JRE because it specifically looks for Oracle JDK instead of OpenJDK, I have no idea. When running from the command line with java -jar kse.jar it works nicely.
The text was updated successfully, but these errors were encountered:
kaikramer commented Apr 23, 2019
The MSI installer of AdoptOpenJDK's Java 8 distribution has an option to add registry entries that are compatible with Oracle's JDK (under HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit ):
If this option is selected launch4j (kse.exe) finds the AdoptOpenJDK installation and starts KSE just fine.
lawrence-dol commented Nov 21, 2020
@lawrence-dol Java 1.8 is the minimum version. KSE works perfectly fine with Java 15. You just have to check the option to create the registry entry when installing AdoptOpenJDK as described on the download page.
Fair enough, though I already knew that from running it with JDK 15 using the -jar command line form. In my defense, I was believing the loader, which states, "This application requires a Java Runtime Environment 1.8.0", not "This application requires Java Runtime Environment 1.8.0 or later". The former is exact, the latter is a minimum.
For a while I was mistakenly under the impression that the loader was needed instead of being a mere convenience, and that the software require exactly that version. It would probably help the situation to include a basic command line in the "Running" section, along with a statement along the lines of "KSE can be run by simply launching the JAR or by using the Windows executable. blah blah blah".
Regardless, thanks for the program -- it's excellent and the loader issue is, in the end, a minor irritation at worst. I do appreciate your efforts and did not mean to sound ungrateful.
kriegaex commented Oct 17, 2016
Would you mind re-testing this issue and, if necessary, file an upstream ticket at launch4j? OpenJDK is a relevant platform, I guess.
Mart-Bogdan commented Nov 2, 2020
This is a problem. Becouse I have both 1.8 and 15 installed.
And if I click on JAR file it opens and works correctly with 15 AdoptOpenJDK
Bill-Stewart commented Dec 24, 2020
After thinking about this some more, it seems this problem would be nicely solved on Windows by using a DLL that can detect a Java installation using the aforementioned techniques and return information about it. I wrote a prototype that exports 4 functions:
IsJavaInstalled() - returns non-zero if Java is detected, or 0 if not detected
IsJava64Bit() - returns non-zero if the detected Java is 64-bit, or zero if not 64-bit
GetJavaHome() - returns a unicode string in an output parameter containing the Java home directory location
GetJavaVersion() - returns a unicode string in an output parameter containing the version number embedded in java.exe
I am doing some more testing, but it seems to me that this functionality would be useful not just to the KSE project but for anyone writing Java programs to be run on Windows.
This application requires Java Runtime Enviroment 1.6.0
- Out of the Water
- Join Date: 7/3/2013
- Posts: 3
- Member Details
This Application Requires Java Runtime Environment 1.6.0
This is what I get trying to run MC after 1.6 update for MC.
I did download and install Runtime (the new one) and I get this still.
The one on the error that sends you to download a different one don't fix it.
- Out of the Water
- Join Date: 1/18/2013
- Posts: 7
- Minecraft: deathkraft
- Member Details
- Out of the Water
- Join Date: 7/3/2013
- Posts: 3
- Member Details
- Stone Miner
- Join Date: 5/2/2012
- Posts: 10
- Member Details
Wonderful! That solution worked for me. Thank you very much, and, as we used to say, "Diamonds for you! "
- Mathematical Dessert
- Join Date: 5/15/2013
- Posts: 487
- Member Details
This Application Requires Java Runtime Environment 1.6.0
This is what I get trying to run MC after 1.6 update for MC.
I did download and install Runtime (the new one) and I get this still.
The one on the error that sends you to download a different one don't fix it.
What Java version do you have?
- Out of the Water
- Join Date: 1/3/2013
- Posts: 4
- Minecraft: SkyDaGuy
- PSN: SkyRockStar1
- Member Details
Thank YOU SO MUCH! IT WORKED! I JUST NEEDED TO UNINSTALL EVERY JAVA APPLICATION and BAM! Restarted my cp, and re-installed java, Thank you so much dood!
- Newly Spawned
- Join Date: 4/16/2014
- Posts: 1
- Member Details
I beleive that possibly this bug is occuring due to all the recent internet security problems and updates rushed out. I also simply had to un-install all versions of java and re-install the newest version. I think java is simply trying to wipe out all their old code that was affected by the heartbleed/heartbreak
Не запускается игра? На этой странице собраны наиболее распространённые ошибки.
Чаще всего проблема кроется в некорректной версии Java, либо недостаточном количестве оперативной памяти, либо в антивирусе.
Прежде всего, рекомендуется сделать следующие шаги:
1) Запустить лаунчер от имени администратора (ПКМ->Запуск от имени администратора)
2) Удалить старую Java и установить новую под разрядность своей операционной системы (Windows 64bit, Windows 32bit)
3) Отключить антивирус или добавить лаунчер в список исключения
4) В настройках лаунчера выделить 1,5 Гб оперативной памяти - этого должно хватить для комфортной игры. Если вы выделите памяти слишком много, вашему ПК может не хватить ресурсов для корректной работы приложения. Для версий 1.12.2 и 1.16.5 может потребоваться больше ОЗУ (пробуйте 2 Гб, 2,5 Гб и т.д.)
5) Перезапустить ПК
6) Если вы ранее играли на проекте и всё было нормально, попробуйте удалить полностью папку с игрой и заново скачать лаунчер с сайта и установить его с нуля
7) Если появляется "Оффлайн режим", то скорее всего нет соединения с сервером. Проверьте работоспособность своего интернета, отключите брандмауэр (он может блокировать подключения лаунчера), а также попробуйте включить или отключить VPN. Также такая ошибка может возникать если сервер перегружен или перезапускается, просто попробуйте зайти повторно через несколько секунд или позже.
8) Если вы живете в Украине или у вас Ростелеком может быть проблема с настройкой DNS, возможна проблема с подключением к сайту и "Оффлайн режим" лаунчера. Попробуйте изменить DNS с помощью этой программы (Fastest DNS -> . Test -> Apply DNS -> Закрыть окно -> Apply DNS): DnsJumper
Если указанные выше действия не помогли вам, то попробуйте включить режим отладки в лаунчере и/или найти свою ошибку в списке ниже и следовать рекомендациям.
Если вы не нашли свою ошибку, либо решение вам не помогло, создайте тикет в Дискорд в канале "поддержка", мы постараемся вам помочь
Причина возникновения: Такая ошибка возникает при отсутствии нормального соединения лаунчера с сервером
Возможные решения: 1) Если вы живете в Украине или у вас Ростелеком может быть проблема с настройкой DNS, возможна проблема с подключением к сайту и "Оффлайн режим" лаунчера. Попробуйте изменить DNS с помощью этой программы (Fastest DNS -> . Test -> Apply DNS -> Закрыть окно -> Apply DNS): DnsJumper
2) Если ранее такой проблемы не было, удалите полностью папку с игрой, скачайте заново лаунчер с сайта и запустите
3) Возможно соединение блокирует антивирус или брандмаур. Добавьте лаунчер в список исключений либо попробуйте отключить антивирус и брандмауэр
4) Плохое интернет соединение, проверьте свой интернет, попробуйте перезагрузить роутер, свой ПК
5) Ваша страна блокирует соединение, попробуйте включить VPN (в интернете полно инструкций). Либо наоборот, если вы используете VPN, лаунчер может блокировать выбранную страну из соображений безопасности, в этом случае попробуйте отключить VPN или изменить страну в VPN. Если используете Hamachi или Radmin, попробуйте отключить или удалить их.
6) Возможно лаунчер или веб-сайт просто перегружены или находятся в состоянии перезагрузки, попробуйте зайти через несколько секунд/минут
7) Если указанные действия не помогли вам, то создайте тикет в канале "поддержка" нашего Дискорд сервера
hendrikebbers commented Jul 20, 2020
I assume setting JAVA_HOME is not the part that was asked here. If I understand @dhamann correctly he wants to add the JAR mimetype to be executed by Java for example. Is that right?
douph1 commented Jul 21, 2020
kaikramer commented Oct 17, 2016
Is OpenJDK really relevant on Windows? There are no official builds for Windows, the Zulu builds are only 64bit and it's quite cumbersome to compile OpenJDK on Windows.
Anyway, I'll try to re-produce this issue and see what can be done about it.
kriegaex commented Oct 17, 2016 •
I am currently coaching a Scrum team in the German bank industry. Because OpenJDK is used in production on Linux, all developers also use OpenJDK (Zulu) on their Windows workstations. So much for relevance. But I admit, this is just one project, I cannot speak for the rest of the software development world. Feel free to do whatever seems appropriate. Thank you for your swift response and for kindly considering our situation.
chhe commented Dec 31, 2017 •
I know this is an old issue but since it is still relevant here is my solution:
Create a registry file with the following content and import it into your regsitry
Obviously change the JavaHome to your Zulu installation. So far this works quite well for me.
Bill-Stewart commented Jun 17, 2019
That's not true. Launch4j has a configuration option called "runtimeBits", which determines which registry paths are checked for JRE locations. For KSE it's the default, which means both 64 bit and 32 bit Java runtimes are found.
Oddly, on one system, the registry values weren't there even though the feature was selected in the installer. Repairing the AdoptOpenJDK JRE installation fixed the problem and indeed kse.exe works as needed even though only the 64-bit values are added. This is good. Thanks for the follow-up.
Читайте также: