• PSA: What is voidtools Everything and is it any good?

    From Maria Sophia@mariasophia@comprehension.com to alt.comp.freeware,alt.comp.os.windows-10 on Thu Nov 5 02:35:36 2026
    From Newsgroup: alt.comp.os.windows-10

    PSA: What is voidtools Everything and is it any good?
    I generally don't search, but I ran into this & wondered if it's any good.

    https://www.voidtools.com/faq/#what_is_everything
    "Everything" is a search engine that locates files and folders
    by filename instantly for Windows.
    Unlike Windows search "Everything" initially displays every file
    and folder on your computer (hence the name "Everything").
    You type in a search filter to limit what files and folders
    are displayed."
    https://www.voidtools.com/downloads/
    Download Portable ZIP 64-bit https://www.voidtools.com/Everything-1.4.1.1032.x64.zip
    Name: Everything-1.4.1.1032.x64.zip
    Size: 1906504 bytes (1861 KiB)
    SHA256: 698DF475EC44E638F66F1B6A32D28FEA613CEC78D3B6310E6ABE53431EEB940C

    Everything parses the MFT records once at startup (takes maybe 2iV5 seconds
    on a modern drive). After that, the search is purely RAM-bound.

    It's matching against strings held in memory, not hitting the disk.
    That's why results appear "as we type".

    What it does NOT index by default:
    a. File contents (unless we enable content indexing)
    b. Files on non-NTFS volumes (FAT32/exFAT require crawling)
    c. Deleted or hidden system objects (unless we enable them)

    Name: everything.exe
    Size: 2272424 bytes (2219 KiB)
    SHA256: F191F756996A14A11E5445FA7103D302EFD510CF2FBF920E6C0C8ED51D512E36

    Name: Everything.lng
    Size: 1033107 bytes (1008 KiB)
    SHA256: 84E0AE09A9E268424CE85A85135C704C534FF60F92E150413B9DF05A88979BE7

    To test it, I ran it.
    I have 1,722,821 "objects" on Windows 10. Is that a lot?

    It's faster than superman.

    What's your experience with it?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Hank Rogers@Hank@nospam.invalid to alt.comp.freeware,alt.comp.os.windows-10 on Thu Nov 5 19:11:01 2026
    From Newsgroup: alt.comp.os.windows-10

    Maria Sophia wrote on 11/5/2026 12:35 AM:
    PSA: What is voidtools Everything and is it any good?
    I generally don't search, but I ran into this & wondered if it's any good.

    https://www.voidtools.com/faq/#what_is_everything
    "Everything" is a search engine that locates files and folders
    by filename instantly for Windows.
    Unlike Windows search "Everything" initially displays every file
    and folder on your computer (hence the name "Everything").
    You type in a search filter to limit what files and folders
    are displayed."
    https://www.voidtools.com/downloads/
    Download Portable ZIP 64-bit https://www.voidtools.com/Everything-1.4.1.1032.x64.zip
    Name: Everything-1.4.1.1032.x64.zip
    Size: 1906504 bytes (1861 KiB)
    SHA256: 698DF475EC44E638F66F1B6A32D28FEA613CEC78D3B6310E6ABE53431EEB940C

    Everything parses the MFT records once at startup (takes maybe 2N++V5 seconds on a modern drive). After that, the search is purely RAM-bound.

    It's matching against strings held in memory, not hitting the disk.
    That's why results appear "as we type".

    What it does NOT index by default:
    a. File contents (unless we enable content indexing)
    b. Files on non-NTFS volumes (FAT32/exFAT require crawling)
    c. Deleted or hidden system objects (unless we enable them)

    Name: everything.exe
    Size: 2272424 bytes (2219 KiB)
    SHA256: F191F756996A14A11E5445FA7103D302EFD510CF2FBF920E6C0C8ED51D512E36

    Name: Everything.lng
    Size: 1033107 bytes (1008 KiB)
    SHA256: 84E0AE09A9E268424CE85A85135C704C534FF60F92E150413B9DF05A88979BE7

    To test it, I ran it.
    I have 1,722,821 "objects" on Windows 10. Is that a lot?

    It's faster than superman.

    What's your experience with it?


    You tell us Arlen. Did it add value for you?

    Maybe you could compose a full tutorial on it?


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lumberdog@pup@play.dot to alt.comp.freeware,alt.comp.os.windows-10 on Thu Nov 5 22:59:59 2026
    From Newsgroup: alt.comp.os.windows-10

    On 11/5/26 17:11, Hank Rogers wrote:
    Maria Sophia wrote on 11/5/2026 12:35 AM:


    -a "Everything" is a search engine that locates files and folders
    -a-a by filename instantly for Windows.

    I have 1,722,821 "objects" on Windows 10. Is that a lot?

    It's faster than superman.

    What's your experience with it?


    You tell us Arlen.-a Did it add value for you?

    Maybe you could compose a full tutorial on it?

    And I think he should share that list of 1,722,821 "objects" with us.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.comp.freeware,alt.comp.os.windows-10 on Fri Nov 6 03:58:33 2026
    From Newsgroup: alt.comp.os.windows-10

    On Fri, 11/6/2026 1:59 AM, Lumberdog wrote:
    On 11/5/26 17:11, Hank Rogers wrote:
    Maria Sophia wrote on 11/5/2026 12:35 AM:


    -a "Everything" is a search engine that locates files and folders
    -a-a by filename instantly for Windows.

    I have 1,722,821 "objects" on Windows 10. Is that a lot?

    It's faster than superman.

    What's your experience with it?


    You tell us Arlen.-a Did it add value for you?

    Maybe you could compose a full tutorial on it?

    And I think he should share that list of 1,722,821 "objects" with us.

    They're all Python scripts.

    Just for a quick comparison...

    C: 391,327 (has a few VMs)
    H: 461,961 (has Visual Studio Community edition)
    S: 10,316 bigger files
    P: 191 bigger still files

    I'm going to have to start writing some Python scripts
    to catch up. That's not nearly enough files.

    *******

    I have a couple implementation demos of findnextfile. This one
    can list a million files per second (on my RAMDrive).

    https://learn.microsoft.com/en-us/windows/win32/fileio/listing-the-files-in-a-directory

    Whereas this one displays an absolute path, and runs at 1/3rd the rate.
    Just the execution of that number of printf statements, erodes the speed. That's why, if you want to win some races, you have to reduce the usage
    of printf.

    https://rosettacode.org/wiki/Walk_a_directory/Recursively#C

    I don't think the code I've written, to parse the $MFT goes nearly
    that fast. Neither does the nfi.exe that Microsoft made, read the $MFT that fast.

    # If you need some source code to inform your NTFS $MFT parser.
    # Not a complete implementation, so you still have work to do.

    https://handmade.network/forums/articles/t/7002-tutorial_parsing_the_mft

    the findnextfile code is one kick-ass piece of code in the Microsoft library. It seems to be (functionally) reading the $MFT at 4GB/sec (and it only selectively
    examines what it is hoovering in). I can know that, because I have
    a $MFT here that is over 60GB in size, for test :-) That's a pathological
    case, which is both good and bad. For example, using File Explorer (oink!)
    to count the files in the test object, that takes *two hours*
    on the RAMDrive. How you interface to your storage on the machine,
    there is quite a spread on performance.

    If I need real performance, I use TMPFS on Linux. Which is not good
    for long term usage (I would expect fragmentation slows it down as
    time passes), but if you want to do drag race runs, it's pretty good
    for those. When you run a Linux LiveUSB, half the RAM on the machine
    is set aside for a RAMdrive. The /tmp running that way, is hosted
    on RAM, and then you can do your benchmark run there.

    *******

    What slows down Everything.exe, is... progress.

    When the first release came out, I suspect it was just processing
    the $MFT and not gathering any details like "dates" for files.
    The $MFT phase might only take it a few seconds (much less than
    my parser).

    But when it wants to add dates to the database or file it is generating,
    that takes a stat() type process per file, and those are more expensive.
    It might take 15-20 seconds to backfill by doing that. So when the
    developer at Voidtools added the additional fields, that spoiled the
    really speedy first implementation.

    This is how you get Everything to make you a text file.

    everything.exe -create-filelist every_c.txt "C:"

    And that will seem to come back almost right away when
    your run it. Part of the run is in the background.
    You have to "monitor" the every_c.txt file and watch
    it until it stops growing, to determine the process is
    complete.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.freeware,alt.comp.os.windows-10 on Fri Nov 6 12:26:37 2026
    From Newsgroup: alt.comp.os.windows-10

    Paul wrote:
    They're all Python scripts.

    Just for a quick comparison...

    C: 391,327 (has a few VMs)
    H: 461,961 (has Visual Studio Community edition)
    S: 10,316 bigger files
    P: 191 bigger still files

    I'm going to have to start writing some Python scripts
    to catch up. That's not nearly enough files.

    *******

    I have a couple implementation demos of findnextfile. This one
    can list a million files per second (on my RAMDrive).

    https://learn.microsoft.com/en-us/windows/win32/fileio/listing-the-files-in-a-directory

    Whereas this one displays an absolute path, and runs at 1/3rd the rate.
    Just the execution of that number of printf statements, erodes the speed. That's why, if you want to win some races, you have to reduce the usage
    of printf.

    https://rosettacode.org/wiki/Walk_a_directory/Recursively#C

    I don't think the code I've written, to parse the $MFT goes nearly
    that fast. Neither does the nfi.exe that Microsoft made, read the $MFT that fast.

    # If you need some source code to inform your NTFS $MFT parser.
    # Not a complete implementation, so you still have work to do.

    https://handmade.network/forums/articles/t/7002-tutorial_parsing_the_mft

    the findnextfile code is one kick-ass piece of code in the Microsoft library. It seems to be (functionally) reading the $MFT at 4GB/sec (and it only selectively
    examines what it is hoovering in). I can know that, because I have
    a $MFT here that is over 60GB in size, for test :-) That's a pathological case, which is both good and bad. For example, using File Explorer (oink!)
    to count the files in the test object, that takes *two hours*
    on the RAMDrive. How you interface to your storage on the machine,
    there is quite a spread on performance.

    If I need real performance, I use TMPFS on Linux. Which is not good
    for long term usage (I would expect fragmentation slows it down as
    time passes), but if you want to do drag race runs, it's pretty good
    for those. When you run a Linux LiveUSB, half the RAM on the machine
    is set aside for a RAMdrive. The /tmp running that way, is hosted
    on RAM, and then you can do your benchmark run there.

    *******

    What slows down Everything.exe, is... progress.

    When the first release came out, I suspect it was just processing
    the $MFT and not gathering any details like "dates" for files.
    The $MFT phase might only take it a few seconds (much less than
    my parser).

    But when it wants to add dates to the database or file it is generating,
    that takes a stat() type process per file, and those are more expensive.
    It might take 15-20 seconds to backfill by doing that. So when the
    developer at Voidtools added the additional fields, that spoiled the
    really speedy first implementation.

    This is how you get Everything to make you a text file.

    everything.exe -create-filelist every_c.txt "C:"

    And that will seem to come back almost right away when
    your run it. Part of the run is in the background.
    You have to "monitor" the every_c.txt file and watch
    it until it stops growing, to determine the process is
    complete.

    Hi Paul,

    I love your humor. While I'm not on Usenet for my amusement, nor for
    that of the uneducated trolls, I do very much smile when I read your
    sardonic sarcastic responses, all the while knowing you are kind hearted.

    While I'll never comprehend why the uneducated trolls (Hank Rogers,
    Lumberdog) are desperate to post when they clearly understand nothing,
    we appreciate you tested this tool, which, I must say, is incredibly fast.

    In all my decades of working with computers, I've never seen anything
    run a search so fast, & yes, I pioneered fastfind on Solaris long ago.

    We appreciate that you *tested* this amazingly blazingly fast tool.
    Your comparisons and the -create-filelist example add useful context.

    Like you have, I had been using my own scripts for decades, to enumerate
    files on my system, where the salonb batch script below lists all files to create an archive I can go back to if/when there is a missing key file.

    But until your post, I hadn't much thought about how much the way a program enumerates and displays results can affect a file-count benchmark.

    My salonb.bat script turns a scan into an auditable, comparable record over time, while "Everything" makes a large live file collection searchable.

    While my original post was meant as a quick introduction, not a performance test, I was amazed at how blazingly fast "Everything" seemed to be, so I'm happy that you tested it more thoroughly, for the team, than I had done.

    I had just found 'Everything' while looking into filename search
    improvements for my salonb.bat script, and as far as I can tell
    we haven't discussed 'Everything" on this group before (AFAICR).

    That means this thread accomplishes the goal of adding value that wasn't
    there before, so that, as always, everyone benefits from our interaction.

    The practical appeal seems to be that "Everything" can search filenames
    across a large NTFS volume almost instantly after building its index.

    Your helpful examples also make it clear that listing or exporting every result is a different job from searching that index. Thanks for adding the programming and benchmarking angle.

    For the record, here is my salonb.txt, admittedly a rather simple script.
    :: -------------------------------------------------------------------------
    :: salonb.bat
    :: Creates a dated list of all files found on all normally-mounted drives.
    :: -------------------------------------------------------------------------
    :: v1p7 20260904 Added an error log file using an ERRFILE variable
    :: v1p6 20260904 Added gvim edit of the output file (which can be huge)
    :: v1p5 20260904 Added ready-drive filter to prevent empty-drive errors
    :: v1p4 20260904 Added visual-progress indicators as "/on" slows output
    :: v1p3 20260904 Put back "dir /s/a/l/on/b" that PowerShell can't replicate
    :: v1p2 20260904 Added a more robust powershell Get-ChildItem as dir hangs
    :: v1p1 20260904 Automatically finds and scans normally-mounted drives
    :: v1p0 20260904 Scans the C drive only (used only when seeking an inventory)
    :: -------------------------------------------------------------------------
    :: This script creates an easily maintained historical record of all visible
    :: files on all drives that are normally mounted (and ready) on a given PC.
    ::
    :: It automatically discovers the mounted drives before scanning them,
    :: so there's no need to manually specify the drive name (C:, D:, etc.).
    ::
    :: On purpose, the inventory is sorted, which makes each dated snapshot
    :: directly usable with the Microsoft CoreUtils grep, diff and comm.
    ::
    :: Two snapshots can therefore be easily compared as sets to identify files
    :: (or file types) that appeared or disappeared between the archived scans.
    ::
    :: The intent is to create a salonb archive (which can be used years later).
    :: Win+R > salonb {Enter} <=== that instantly opens up the salonb archive
    :: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\salonb.exe
    :: C:\data\sys\apppath\link\salonb.lnk whose TARGET=C:\data\sys\salonb\.
    :: -------------------------------------------------------------------------
    :: Comparing contents of two sorted files is easy when using MS CoreUtils
    :: NB: Normaly comm is better when we need to get a complete set, while
    :: diff is often better when we need to see everything that changed.
    ::
    :: Show a conventional line-by-line difference between two snapshots:
    :: C:\> diff salonb_20260901.txt salonb_20260904.txt
    ::
    :: Report all files that were removed between two snapshots:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt
    ::
    :: Report all files that were added between two snapshots:
    :: C:\> comm -13 salonb_20260901.txt salonb_20260904.txt
    ::
    :: Report all *.jpg files that were removed:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -i '\.jpg$'
    ::
    :: Report all *.jpg files that were added:
    :: C:\> comm -13 salonb_20260901.txt salonb_20260904.txt | grep -i '\.jpg$'
    ::
    :: Report all files removed from a particular directory:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -i 'thedir'
    ::
    :: Report all files added under a particular directory:
    :: C:\> comm -13 salonb_20260901.txt salonb_20260904.txt | grep -i 'thedir'
    ::
    :: Report all removed files matching a particular filename:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -i 'my\.docx$'
    ::
    :: Report all files that disappeared from a particular drive:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -i '^E:\\'
    ::
    :: Save the list of removed files for further investigation:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt > removed.txt
    ::
    :: Report all executable files that disappeared:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -Ei '\.(exe|dll|sys)$'
    ::
    :: Report all media files that disappeared:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -Ei '\.(jpg|jpeg|png|gif|mp4|mov)$'
    ::
    :: Report all document files that disappeared:
    :: C:\> comm -23 salonb_20260901.txt salonb_20260904.txt | grep -Ei '\.(doc|docx|xls|xlsx|pdf)$'
    :: -------------------------------------------------------------------------
    :: Note these are four separate switches: dir /s/a/l/on/b c:\*.*
    :: /s recurse through subdirectories
    :: /a include files with all attributes, including hidden/system
    :: /l use lowercase names (this has nothing to do with symbolic links)
    :: /on sort by name (useful for "comm" but it causes output to be delayed)
    :: /b bare format
    :: -------------------------------------------------------------------------

    @echo off
    setlocal

    :: Get current date
    for /f %%a in ('powershell -NoProfile -Command "Get-Date -Format
    yyyyMMdd"') do (
    set date_formatted=%%a
    )

    :: Configuration (Define editor, output location, and error log)
    set "VIEWER=gvim -R"
    set "OUTFILE=salonb_%date_formatted%.txt"
    set "ERRFILE=salonb_%date_formatted%_errors.txt"

    :: salonb scan loop
    for /f %%D in ('powershell -NoProfile -Command "[System.IO.DriveInfo]::GetDrives() | Where-Object { $_.IsReady } | ForEach-Object { $_.Name }"') do (
    echo [1/2] Scanning and sorting drive %%D... Please wait
    dir /s/a/l/on/b "%%D*.*" >> "%OUTFILE%" 2>> "%ERRFILE%"
    echo [2/2] Drive %%D complete.
    echo --------------------------------------------------
    )

    echo.
    echo Scan complete.
    echo Results: %OUTFILE%
    echo Errors: %ERRFILE%
    echo.
    pause

    %VIEWER% "%OUTFILE%"

    endlocal
    :: -------------------------------------------------------------------------
    :: end of salonb.bat
    :: ------------------------------------------------------------------------- --
    Posted out of the goodness of my heart to kindly help others do what I can.
    --- Synchronet 3.22a-Linux NewsLink 1.2