HaveSumPatience Posted May 26, 2020 Share Posted May 26, 2020 (edited) After running the installer for client, I get an error message "These Libraries failed to download. Try again." I have already looked through other solutions like running it through command prompt, updating Java to the latest version, firewall settings and restarted my computer. Yet, it still doesn't work. This is for 1.15.2. Here are the contents of the log file. Spoiler JVM info: Oracle Corporation - 1.8.0_251 - 25.251-b08 java.net.preferIPv4Stack=true Found java version 1.8.0_251 Extracting json Considering minecraft client jar Downloading libraries Considering library net.minecraftforge:forge:1.15.2-31.2.0 File exists: Checksum validated. Considering library org.ow2.asm:asm:7.2 File exists: Checksum validated. Considering library org.ow2.asm:asm-commons:7.2 File exists: Checksum validated. Considering library org.ow2.asm:asm-tree:7.2 File exists: Checksum validated. Considering library cpw.mods:modlauncher:5.1.0 File exists: Checksum validated. Considering library cpw.mods:grossjava9hacks:1.3.0 File exists: Checksum validated. Considering library net.minecraftforge:accesstransformers:2.1.1-shadowed File exists: Checksum validated. Considering library net.minecraftforge:eventbus:2.2.0-service File exists: Checksum validated. Considering library net.minecraftforge:forgespi:2.1.2 File exists: Checksum validated. Considering library net.minecraftforge:coremods:2.0.3 File exists: Checksum validated. Considering library net.minecraftforge:unsafe:0.2.0 File exists: Checksum validated. Considering library com.electronwill.night-config:core:3.6.2 File exists: Checksum validated. Considering library com.electronwill.night-config:toml:3.6.2 File exists: Checksum validated. Considering library org.jline:jline:3.12.1 File exists: Checksum validated. Considering library org.apache.maven:maven-artifact:3.6.0 File exists: Checksum validated. Considering library net.jodah:typetools:0.8.1 File exists: Checksum validated. Considering library org.apache.logging.log4j:log4j-api:2.11.2 File exists: Checksum validated. Considering library org.apache.logging.log4j:log4j-core:2.11.2 File exists: Checksum validated. Considering library net.minecrell:terminalconsoleappender:1.2.0 File exists: Checksum validated. Considering library net.sf.jopt-simple:jopt-simple:5.0.4 File exists: Checksum validated. Considering library com.github.jponge:lzma-java:1.3 File exists: Checksum validated. Considering library com.google.code.findbugs:jsr305:3.0.2 File exists: Checksum validated. Considering library com.google.code.gson:gson:2.8.0 File exists: Checksum validated. Considering library com.google.errorprone:error_prone_annotations:2.1.3 File exists: Checksum validated. Considering library com.google.guava:guava:20.0 File exists: Checksum validated. Considering library com.google.guava:guava:25.1-jre File exists: Checksum validated. Considering library com.google.j2objc:j2objc-annotations:1.1 File exists: Checksum validated. Considering library com.nothome:javaxdelta:2.0.1 File exists: Checksum validated. Considering library commons-io:commons-io:2.4 File exists: Checksum validated. Considering library de.oceanlabs.mcp:mcp_config:1.15.2-20200515.085601@zip File exists: Checksum validated. Considering library net.md-5:SpecialSource:1.8.5 File exists: Checksum validated. Considering library net.minecraftforge:binarypatcher:1.0.12 File exists: Checksum validated. Considering library net.minecraftforge:forge:1.15.2-31.2.0:universal File exists: Checksum validated. Considering library net.minecraftforge:installertools:1.1.4 Downloading library from https://files.minecraftforge.net/maven/net/minecraftforge/installertools/1.1.4/installertools-1.1.4.jar java.nio.file.NoSuchFileException: C:\Users\Asus\AppData\Roaming\.minecraft\libraries\net\minecraftforge\installertools\1.1.4\installertools-1.1.4.jar at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.Files.readAllBytes(Unknown Source) at net.minecraftforge.installer.DownloadUtils.getSha1(DownloadUtils.java:172) at net.minecraftforge.installer.DownloadUtils.download(DownloadUtils.java:149) at net.minecraftforge.installer.DownloadUtils.download(DownloadUtils.java:134) at net.minecraftforge.installer.DownloadUtils.downloadLibrary(DownloadUtils.java:123) at net.minecraftforge.installer.actions.Action.downloadLibraries(Action.java:79) at net.minecraftforge.installer.actions.ClientInstall.run(ClientInstall.java:108) at net.minecraftforge.installer.InstallerPanel.run(InstallerPanel.java:428) at net.minecraftforge.installer.SimpleInstaller.launchGui(SimpleInstaller.java:170) at net.minecraftforge.installer.SimpleInstaller.main(SimpleInstaller.java:143) Download failed: Checksum invalid, deleting file: Expected: ce2a64d84365374fc797f829e60321874d48145f Actual: null Failed to delete file, aborting. Considering library net.minecraftforge:jarsplitter:1.1.2 File exists: Checksum validated. Considering library net.sf.jopt-simple:jopt-simple:4.9 File exists: Checksum validated. Considering library net.sf.jopt-simple:jopt-simple:5.0.4 File exists: Checksum validated. Considering library net.sf.opencsv:opencsv:2.3 File exists: Checksum validated. Considering library org.checkerframework:checker-qual:2.0.0 File exists: Checksum validated. Considering library org.codehaus.mojo:animal-sniffer-annotations:1.14 File exists: Checksum validated. Considering library org.ow2.asm:asm-analysis:6.1.1 File exists: Checksum validated. Considering library org.ow2.asm:asm-commons:6.1.1 File exists: Checksum validated. Considering library org.ow2.asm:asm-tree:6.1.1 File exists: Checksum validated. Considering library org.ow2.asm:asm:6.1.1 File exists: Checksum validated. Considering library trove:trove:1.0.2 File exists: Checksum validated. These libraries failed to download. Try again. net.minecraftforge:installertools:1.1.4 Edited May 26, 2020 by HaveSumPatience Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted May 26, 2020 Share Posted May 26, 2020 Try deleting this folder: C:\Users\Asus\AppData\Roaming\.minecraft\libraries\net\minecraftforge\installertools\1.1.4\ and trying again Quote This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore] Link to comment Share on other sites More sharing options...
HaveSumPatience Posted May 26, 2020 Author Share Posted May 26, 2020 (edited) Tried it. Doesn't work, gives the same message as before. Although the folder for the forge version has been created in the versions folder. Should I try deleting all forge related folders and try again? Or maybe a clean reinstall of minecraft? Any other solutions? Edited May 26, 2020 by HaveSumPatience Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted May 26, 2020 Share Posted May 26, 2020 This solution is a bit nuclear, but try deleting your libraries folder Quote This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore] Link to comment Share on other sites More sharing options...
HaveSumPatience Posted May 28, 2020 Author Share Posted May 28, 2020 I have tried deleting my libraries folder as well as reinstalled minecraft. Looks like I gotta play without mods. Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted May 28, 2020 Share Posted May 28, 2020 I suppose you could try deleting the entirey of .minecraft if you REALLY want to go nuclear... the reason I keep going on about this is it feels like a file permissions issue Quote This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore] Link to comment Share on other sites More sharing options...
HaveSumPatience Posted May 28, 2020 Author Share Posted May 28, 2020 I did delete the the entirety of .minecraft after uninstalling it but it still doesn't work. I get exactly the same error. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.