anto77562
Comments
final update, i was able to find that this is a duplicate of another bug report, and I'm sorry for wasting everyone's time. Im not sure how to close this ticket as a duplicate, but there is a more detailed and earlier submitted version of this bug here:
MCL-24212
ok, another update:
TL;DR its 1000% not a permissions issue or an issue with that specific file being open.
i renamed the "launcher_profiles.json" file to "launcher_profiles.BAK", and the launcher created a new launcher profiles .json and I tried launching the latest snapshot (it defaults to latest release, so theoretically the launcher should remember that I chose latest release most recently) and I launched it, opened a world, exited the world, closed Minecraft, and opened the launcher again. it did not remember it again. i haven't opened the new launcher profiles .json file that was created by the launcher, and this 1000% rules out that its opened in another program, and also rules out any permissions issue with the Minecraft directory.
Long story short, the Minecraft Launcher CAN modify the "launcher_profiles.json" file, but it refuses to modify the "lastused" property of Minecraft installations inside that file.
I've verified that no programs had the file open and that the launcher CAN modify the file, and the issue persists.
TL;DR this still affects the minecraft windows legacy launcher version 3.1.13, bootstrap 2.0.16 UI 3.1.13
i just spent the last 45 minutes creating a bug report for this exact thing, since I missed this bug report while searching to make sure I didn't create a duplicate (I accidentally made a duplicate anyways... sorry...) this problem still effects the most recent versions of the Minecraft launcher as of October 2nd 2024, and its extremely annoying.