Why official iso are still at 2026-03-27 and not 2026-07-23?
Because we were/are having issues with auto login - partially solved.
You do realise that you donāt need a new ISO to keep your system up-to-date, right?
You do realise that everything is done by volunteers, right?
yes
You do realise that everything is done by volunteers, right?
yes, but I thought they would be scrip to update automatically
There is, but until the problem is fixed it automatically produces iso with bugs.
So right now a slightly older but working iso is on the site, instead of newer but somewhat broken.
You could look at Manjaro Linux - Browse Files at SourceForge.net.
Or you could use one of the downloaders provided in the repo
- manjaro-get-iso
- manjaro-iso-downloader
Manjaro Team released a preview ISO with latest packages 3 days ago
Manjaro 26.1 Bian-May - Preview released
Bian-May 26.1.0-rc3 (2026-07-23)
Iāve split this into a dedicated topic. 
There are one or two other threads on here regarding this; Iāll see if i can find it/them. I am, of course, aware of how āwellā the forum search works. 
One of the topics
Is there a reason why is it not on: Download x86 ā Manjaro ???
Manjaro 26.1 ISOs should be available soon
As youāve been told multiple times, the new ISO version still has bugs that they are working to fix before releasing them officially.
And if you want to contribute instead of just complaining, download the latest from the troubleshooting topic and report if it boots correctly and on what machine, what usb, what DE, etc.
Exactly. We need testers, as is the case in any development scenario.
There seems to be a misunderstanding, so letās recap how I understand it.
You go to Download x86 ā Manjaro
burn an iso and install from there manjaro.
Since the iso dates back 2026-03-27, updates will be present, which latest is currently 2026-07-23
My question was why there is no iso 2026-07-23 to readily download the latest?
Now, Iām puzzled, it appears to me by these discussions, that install from iso 2026-03-07 and then update to 2026-07-23 would not lead to the same system than a new iso2026-07-23 because there are some unsolved issues(āBecause we were/are having issues with auto login - partially solved.ā)??
In that case it would mean that the nb of apps or the apps are not the same(different hash).
So when asked āYou do realise that you donāt need a new ISO to keep your system up-to-date, right?ā I wouldnāt get the same system, according to the iso I picked, in this is a surprise to me.
No, the issue with the new ISOs is related to how the ISO itself boots in live mode. It has nothing to do with the installed system, even if you install from those new ISOs.
Thanks, didnāt know iso needed extra stuff which are not installed
In the past it was on the same date: when the stable branch got updates, a new āstableā/final ISOs became available.
Looks cool, yeah? But itās not as good as could be for new installations. Why? Letās dive in.
Manjaro team designed their OS to have three branches of updates. So the stable branch got 2 lines/levels of potential bugs prevention based on earlier users bug reports.
When unstable branch users got updates, they reports: āHey! In my case I got ā¦ possible cause suspected in the ā¦ I was need to do the ā¦ and looks like I fix itā. Manjaro team gets involved into the process and analyses what it was and why and after investigation they issue package updates. In sophisticated cases it could be several updates, say even 4.
After team verified that users get it worked or no new issues was reported during some period of time, they pass that fixed packages state into the next line: the testing branch.
The same procedure goes there: testing branch users installs updated packages, uses them and reports their cases.
Cause an average user have about 1.2k-1.3k packages installed and Manjaro repos contains somewhere about say 15k-20k packages, all users have their specifics: exact packages run environments: software and hardware, different usage profiles and settings, so all users becomes important to report their possibly unique bugs they met to prevent shared cases of the same error for other users after they start to use it the near same way (under sort of the same execution environment).
So if a package joins testing it is not a 100% bug free version. After testing branch users have no other bug reports, then at some point Manjaro team could decide to move the new packages versions state into the stable branch.
Thatās where the question point is: āThe stable got updates. Hello! Hello!!! Philipā¦ Fredeā¦ Markā¦ could youā¦ Excuse me, can I knowā¦ where the hell new final ISO images? Why are they always late like a weather forecast or even a New Year in a spring?ā.
Some time ago (perhaps the ISO release discussion - #2 by alven suggestion) made influence on Manjaro team and later the team introduces new un-synced behaviour:
- the
stablebranch got massive update. - users report bugs they met.
stablebranch get several iterations of bug fixes.- if there are no severe bug reports or they was fixed already, the team could decide to compose a new āstableā/final ISO with maximised reliability of three levels bugs prevention.
So at some historical point of the ManjaroOS project, the stable branch updates was made as additional line, as the last line of defence against bugs before the new upcoming ISOs in order to minimise bugs inside the fresh āstrengthenedā ISOs shared via manjaro.org.
If not to postpone ISOs directly after the stable has been updated with huge amount of packages (during when Philip, Mark, Frede, other team members were running in the halls to read and investigate users issues), then it could lead to possible situation that new users installations from such early-made ISOs could be disappointed with Manjaro OS stability, reliability.
So, fresh āstableā/final ISOs are usually postponed by design, globally saying, to provide smoother user experience with maximum important severity bugs to be fixed even after the stable branch got massive amount of newer packages versions and to wait some time to settle down bug-fixes activity in the stable line of defence against packages bugs until it get important fixes and the state of thing in the stable branch could be ālabelledā/āmarkedā as mainly free of known severe bugs.
Cause of that new installations could be more reliable.
I hope now you got better understanding why.
Manjaro 26.1 official ISOs are due for release to forum and Download x86 ā Manjaro soon
If you want an up to date ISO now, 26.1 Release Candidate ISO can be downloaded from forum only
Each stable update may link to ISOs having this update. Sometimes they donāt have updated ISOs due to reasons ā¦