Sign in to follow this  
Followers 2
Mythblood

14.2 Forge won't install - process failed, invalid outputs

By Mythblood, in Support & Bug Reports

Recommended Posts

Mythblood    0

Mythblood
Posted

After running the forge installer (the Jar file), it gets to the end and pops this up:

 

Process Failed, Invalid Outputs

 

I have completely uninstalled, and manually deleted the .minecraft folder twice, but still get this.

I'm on windows 7, JAVA edition.

 

The installation log just has the same:

Quote

 

Data version.json
Processor failed, invalid outputs:
C:\Users\gardner\AppData\Roaming.minecraft\libraries\net\minecraft\client\1
.14.2\client-1.14.2-extra.jar
Expected: 8e7c4fa876381116984795af4a43aee35906a227
Actual: 307e5ac271dbd6651ca599059e41b657bbfbb916
C:\Users\gardner\AppData\Roaming.minecraft\libraries\net\minecraft\client\1
.14.2\client-1.14.2-slim.jar
Expected: d784ffb5343e4750c5f61f63f94d26bc032c2c48
Actual: a7491a8df4b9f5c8b3bfe646f8d7cd1efa737fc0

 

 

Forge version: 26.0.12

Also tried Forge version: 26.0.13

 

I also gave up, and tried to downgrade to minecraft 13.2, but ran into the same issue (with diff hashes).

 

I don't know what to do next, any thoughts?

Share this post

Link to post
Share on other sites

DaemonUmbra    380

DaemonUmbra
Posted

I'm not getting this error, try deleting the files it mentions so the installer will re-download them

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://hastebin.com/: 400KB

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://gist.github.com/: 100MB Requires member (Free)

https://paste.gg/: 15MB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

Forge Version 1.12.2-14.23.2.2629 and newer:

Post debug.log

Older versions:

Please update...

 

Where to get it:

Mojang Launcher: When using the Mojang launcher both of these files are found in .minecraft\logs.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. 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
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Share this post

Link to post
Share on other sites

Mythblood    0

Mythblood
Posted

I've done that, still get the same error. I delete the entire .minecraft folder, relaunch the launcher let it download. Close and run the forge installer ...exact same error message with those exact same hashes.

 

I've uninstalled the launcher and deleted the .minecraft folder.

 

I get the launcher from: https://my.minecraft.net/en-us/store/minecraft/#owned

(followed the download link on logged in account)

 

Just get the same error. 

 

 

Share this post

Link to post
Share on other sites

DaemonUmbra    380

DaemonUmbra
Posted

Have you tried deleting the Forge installer and getting a fresh one?

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://hastebin.com/: 400KB

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://gist.github.com/: 100MB Requires member (Free)

https://paste.gg/: 15MB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

Forge Version 1.12.2-14.23.2.2629 and newer:

Post debug.log

Older versions:

Please update...

 

Where to get it:

Mojang Launcher: When using the Mojang launcher both of these files are found in .minecraft\logs.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. 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
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Share this post

Link to post
Share on other sites

Mythblood    0

Mythblood
Posted (edited)

forge-1.14.2-26.0.16-installer.jar.log

 

Fresh forge file, same error.

 

I guess if no one else is having an issue something is different about my system... so why am I getting different JAR files from the minecraft launcher? what has function is forge using? is it SHA1 or something? Is it worth verifying the hash of those files manually?

Edited by Mythblood

Share this post

Link to post
Share on other sites

Mythblood    0

Mythblood
Posted

My launcher version is (found by clicking on the number in bottom left of the launcher):

Launcher
2.1.3674 
Tue, 23 Apr 2019 08:35:33 GMT 
fafa322bd04a73d6e9d87f418eb59d929720d720
 
 

Share this post

Link to post
Share on other sites

Mythblood    0

Mythblood
Posted

I can see from the github this is an SH1 hash .... does this mean I'm getting a different download? from where? seriously could use some help on this. What do I do?

 

 

Share this post

Link to post
Share on other sites

LexManos    1543

LexManos
Posted

It means that something you're doing is producing a wrong output.

However, your input hashes are correct in the log.

So something else is wrong.

What version of java are you running?

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Patreon: http://www.patreon.com/lexmanos
Paypal: http://paypal.me/LexManos

BitCoin: 1Q8rWvUNMM2T1ZfDaFeeYQyVXtYoeT6tTn

Merch: http://forgedev.flocker.tv

Share this post

Link to post
Share on other sites

Mythblood    0

Mythblood
Posted (edited)

At this point I've just given up. This is beyond frustrating... still get the same error with 1.14.3-27.0.24

 

Is there nothing that can be done? can I get the download of forge from someplace else rather than a installer that generates the output? 

Edited by Mythblood

Share this post

Link to post
Share on other sites

DaemonUmbra    380

DaemonUmbra
Posted

No, you must use the installer.

Try updating to the latest Java 8.

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://hastebin.com/: 400KB

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://gist.github.com/: 100MB Requires member (Free)

https://paste.gg/: 15MB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

Forge Version 1.12.2-14.23.2.2629 and newer:

Post debug.log

Older versions:

Please update...

 

Where to get it:

Mojang Launcher: When using the Mojang launcher both of these files are found in .minecraft\logs.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. 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
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Share this post

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 2
Go To Topic Listing