Hey, thanks for reading the thread. Upon attempting to start up Minecraft in versions 1.5.2 and anything below it for Release minecraft versions (1.6 and up works fine), it immediately provides me with a crash error log after the "Minecraft" logo. The crash report is as follows:
---- Minecraft Crash Report ----
// You're mean.
Time: 8/29/16 9:05 PM
Description: Failed to start game
A detailed walkthrough of the error, its code path and all known details is as follows:
-- System Details --
Minecraft Version: 1.5.2
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 45230664 bytes (43 MB) / 127139840 bytes (121 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
OpenGL: Intel(R) HD Graphics 5500 GL version 4.3.0 - Build 10.18.15.4248, Intel
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
I have no mods installed for Minecraft, though the report seems to insist I do, which I find odd. I use a Windows 10 computer. Again, thank you for reading.
If the game thinks that it is modded but it is not then the 1.5.2 jar may be corrupted, and while the launcher normally verifies the integrity of files and redownloads any that do not match the hash on Mojang's servers it may not be doing so or think it is fine for some reason (this could happen if you rename the files and edit the json to delete the downloads for the jar, which includes the hash, but you would only do this to install jar mods). You may want to try deleting the 1.5.2 folder within the versions folder (%appdata%\.minecraft\versions), which will force the launcher to redownload it.
It should not matter if you have anything inside the mods folder since you would have to mod the game by installing a modloader in order to load any mods from there (even with just Forge the game will think it is modded because it is).
Also, if you are going to use multiple versions and/or mods I very highly suggest that you make a separate profile with a separate game directory (e.g. add \1.5.2 to the end of the default directory), which ensures that they use their own settings (for example, setting render distance to above 16 in 1.8 then trying to load 1.7.x will cause a crash due to 1.7 reading in an invalid render distance. 1.6.4, and probably 1.5.2, appear to just reset invalid settings to defaults but they are not guaranteed to be immune to future changes and in any case you have to change the settings back every time you switch versions); this also helps avoid loading worlds in the wrong versions and corrupting them.