Beta

[lifu]

Honestly, I feel like Everything 1.5 has left the sphere of alpha quality software a while ago. It's far faster and more stable than Everything 1.4 which is considered production-level.

Have you considered redesignating 1.5 to beta instead of alpha at the very least?

[void]

Just localization left to do now.

I will have a beta soon..

Sorry for the wait.

[rpnfan]

I never tried the alpha version, because the name implies it is far from being recommended to be used for daily tasks/ serious work.

From what I understood from another thread as soon 1.5 becomes beta, one has to decide if you want to use 1.4 or 1.5 and they do not run together without tricks. But then 1.5 can be seen as the recommended version, right? If it is only the multi language version missing I would make the jump now. I use the US/ English version anyways.

Anything one should consider when upgrading/ changing to the latest 1.5 release from 1.4?

[NotNull]

Anything one should consider when upgrading/ changing to the latest 1.5 release from 1.4?

Yes!

• Consider facepalming yourself for not installing 1.5 years ago.
• Consider thanking @void for creating this piece of art.
• Consider donating to further express this feeling.

Other than that: just install it.
(and let us know how long it took before you stopped using 1.4 altogether)


More seriously: there are may threads on this forum from people that think thought the same way.
They are happy 1.5 users now.


If you run other applications that have Everything integrated (here is a list), you might need to take some extra steps. Search the forum for details.

[rpnfan]

Thanks for the reply. I am a long time user of Everything and said thanks and also donated. I advertise it often to others as well.

I do not face-palm for not using an alpha labelled software. I prefer a stable system. I have been beta/ alpha testing lots of software, but I am not a power user of Everything so I left that for others. I kept coming back to look at the state of the coming release, but it stayed alpha for forever. I did not research why or what that means, so I just skipped, assuming that the progress is very slow and/ or the software not reliable enough. If the software was in reality in beta state for years it is a pity not to name it accordingly.

I will install 1.5 now and see which new features can be useful for me. Thanks for the encouragement.

EDIT: Will have to skip 1.5 for now. I see there is no ARM64 version yet.

[Herkules97]

More seriously: there are may threads on this forum from people that think thought the same way.

I am one, I thought 1.5 would be unstable and cause more problems than using 1.4x.
But 1.5x from what I've seen is better in every way.
Even if it would've been unstable and break a lot, I never actually tried it to find out back when it first came out. If someone wonders, you can always run it portable alongside 1.4x. I don't know if there are any noticeable bugs with portable usage, rarely there will be a file that is corrupted in some instances. My monolithic instance has maybe 24 bugged files out 180 million. Also one of the HDDs have maybe 30% full-indexed files. The rest only have the basic properties found under the "Indexes" tab in the options. But not anything under "Properties" tab like size on disk.
The single-device instance for that same device has everything, so it's possible it's a bug with larger instances and not from running them portable.

When did 1.5x come out..2021? It took me until 2024-01 to switch.

Here is some extra fluff
However I used to use EBV in an installed way. A lot of what I do nowadays comes from 2023-2024.
Not using recycle bin, using programs portable whenever possible, multi-audio-track recording in OBSS for realsies (tried before but I never updated OBSS and it was broken until a 2023 or 2024 update and I hadn't updated since 2022. As in if you try to run a recording it will never save to file, replay buffer either doesn't save anything or there's a massive delay. I used EBV to confirm that there was a file made with 2022 OBSS, but then under 500 milliseconds later removed).
It wasn't until 2024-12, on a new system install, that I fully switched to portable usage though. Where possible I now do this. It's also useful for Windows system resets because it doesn't touch user-made root folders! My system was broken probably by me using NTLite and had to system reset..I could run almost everything immediately as it was all under an untouched root folder.

I mention what I do because it can give others ideas for doing the same. Also some programs have to be installed, but can then be moved portable. For example with RTSS+MSI Afterburner or the other way around, I copied the program folders to my own root folder. Then deleted the originals, ran the program, it errored I think, ran it again and it has worked portable ever since. There can be other programs that works this way.

"Portable" means self-contained folders really. There is no such thing as true portable, typical programs require at the least an installed OS it was built for. Some programs can run from anywhere, but use profile data in appdata. Fortunately appdata is also kept on a system reset. ProgramData isn't. For me the only program that uses that I think is AJC Active Backup. Maybe they can add customisation for that if asked..

[NotNull]

180 million

That must be the "highscore" so far (IIRC, the previous "record" was 65 million files/folders).
Without extra properties and content indexed, Everything uses roughly 100 bytes per file/ folder, which in your case translates to 18 GB RAM usage!!

Just curious: How do regular searches perform?

[void]

=> High CPU usage on empty search

[void]

Everything 1.5 Alpha ARM/ARM64