Well Charlotte Buff, I and many other MC players will disagree with you. See, it worked just fine FOR YEARS until the update caused it to not work anymore. Since it was changes by Mojang that caused the loading process to fail, Mojang was in fact the source of the problem.
Llibrary, which quite a few mods rely upon, is no longer being updated (see attached).
The only workaround is to disconnect from the internet, forcing the launcher to play offline. Then our beloved game works just fine.
https://www.minecraftforum.net/forums/support/java-edition-support/3198821-llibrary-mod-crashing-and-i-dont-know-why is where I found the solution to disconnect from the internet...and yes, that works.
So don't say that "There is literally nothing they could have done to resolve this issue." MOJANG IS THE SOURCE OF THIS ISSUE. You guys don't need to make your loader screw with previous versions. You should really fix this before some vindictive person talks to a lawyer who sees dollar $igns in a class action.
Some of us love this game because there is literally nothing like it, especially the older modded versions.
Dear Violine1101,
Thank you for reviewing the crash log and pointing me in a direction for resolution. It is frustrating to have a game that I have enjoyed for literal years suddenly stop working because of an update. Issue the "even though it's something we did, too bad we won't help you" standard response and compound that anger.
Again, thank you.
Your response is appreciated.
I paid for my game. I've played my game, my way, for years. YOUR UPDATE SCREWED IT UP, SO FIX IT.
This one is back.
@@unknown We also see that, it settles after a minute or two.
You can't expect the code to become less bloated, they will throw more copper meaningless features on the fire until the whole house comes crashing down.
You might want to give people access to the files the launcher installer fails to download instead fo causing all this fuzz/delay which is unprofessional.
I have zipped the files here: http://move.rupy.se/file/launcher.zip
That way people with Windows 7 can play the snapshot releases and hopefully the newer releases switch to resources.download.minecraft.net which has TLS 1.2 enabled.
An alternative is to recommend they install updates, I don't know which ones that made it work for me but probably one of these: kb4474419, kb4490628, kb4534310, kb4536952
Be professional and help your customers without delay?
Edit: Also the MinecraftLauncher.msi version has a memory leak (took 5 days to crash), great idea to switch to some web based solution instead of the 2 previous Java ones.
This now works again for the latest snapshot, they rolled back to TLS 1.2 on all servers for that release, 19, 19.1 and 19.2 are still unplayable on Windows 7 though.
This was also a bug because you fixed it. Now it's 3/3 that you marked invalid and I proved as valid.
@Moesh Then you need to remove the Windows 7/8 (alternative) .exe from this page too: https://www.minecraft.net/en-us/download/alternative
Because it has the same problem.
Yes, and since I cannot log in with the new Microsoft account on these launchers it's a permanent problem you have until you either:
1) Declare Windows 7 and the old launchers dead = you need to refund ANYONE that wants a refund.
2) You fix the bug 4 months after I reported it!
It's 3+ million customers!
In the broader scope it should be illegal for companies to force platform upgrades, they need to release responsible products always and support them forever since computers are not improving.
The forced deprecation that is happening now is desperate, TLS 1.3 is a joke. You cannot force anyone to use less good tools. It's immoral, you are wasting our time.
Edit: Plausible, lol you guys are fantastic.
Whoever agreed to this account migration is not a technical person.
So an update about the accounts system: the new Microsoft accounts do not work on the old .jar or .exe launchers. So the only way to play older Minecraft releases on Windows 7 is to have an old Mojang account.
We cannot play 1.19+
Mojang either needs to remove Windows 7 support from their pages and refund us OR fix the bugs.
Edit: All 3 bugs are now confirmed valid.
How come nobody is assigned to this bug yet?
I reported this 1 month ago... still nothing.
And the bug for the old/newer launchers was reported 4 months ago:
Ok so this bug happens with both old and newer (Minecraft.exe for Windows 7) launchers! Are you even looking at these reports?
4 months and zero assignements?
The (.exe) launcher from this page still works: https://www.minecraft.net/en-us/download/alternative
BUT then the same bug as the original launcher happens: MC-252904
I also reported this bug and it was solved as invalid: https://bugs.mojang.com/browse/MCL-22346
Obviously this bug is VALID.
So 3 of my invalid bugs are valid.
As I said I had to group them because they have a common denominator which makes them serious when combined.
Each one separately does not make a high priority.
I have two accounts that I paid for and I cannot play the latest version, I tried getting support from 2nd line and they are unfortunately not able to help.
3,2 million old or more importantly potential new customers have the same problem.
Well this is a company wide defect: with 2.6% of steam users still on Windows 7 that is 3,2 million customers.
These are bugs, the software has defects in it that creates problems.
Support is non existent, I have tried.
I needed to group them to explain the wider problem and be able to communicate the broader effect of the bugs = Mojang are ignoring customers.
The launcher does not work on Windows 7.
It IS a bug.
Windows 7 does not support TLS 1.3
Why are you wasting resources encrypting patch data?
Go back to using HTTP!
This still fails in the rc1 of 1.19.1!
Edit: 2 weeks later rc2 also fails: I tried moving natives to another folder and launch with half command but it just fails silently.
Edit 2: Running with jdb I get: Exception in thread "main" java.lang.NoSuchMethodError: 'com.mojang.datafixers.DataFixer com.mojang.datafixers.DataFixerBuilder.buildOptimized(java.util.concurrent.Executor)'
How does Minecraft load the DataFixerUpper jar? With a dynamic classloader?
I have the same problem. We are 5 friends playing and the 2 who entered the game previously do not have the error and can see the online skins, me (that I downloaded the game yesterday) and other two friends that purchased the game yesterday can’t see online skins. Its not a problem with the link between the skin and the account, because we can see it the game launcher. Basically the game can’t get online skins from the Minecraft servers. And no software, firewall or antivirus are in the middle.