Windows 11 + Everything Portable not indexing

[DonVoidEver]

I used to be able to just unpack the Portable Zip 64-bit, select the bottom option related to NTFS indexing and there wasn’t any need for admin credentials that way.
Then after adding the Folders in Options  Indexes it will create the Index and it works.
This has worked for 2 years on several laptops.

However with new laptops, which are Windows 11 23H2, the index just keeps building. No search results ever appear. Using version 1.4.1.1026 .
Even with an installed version of Everything the same issues appear. I’ve tried installing the ‘service’ too , didn’t help either.

I've also tried 'force rebuild' but it's just not doing anything it seems

Any feedbaack or suggestions is appreciated, I really like the Portable option

[therube]

Aside from the actual issue, see if Everything 1.5 Alpha works?
ZIP is fine. Unzip & run & ... ?

[void]

Please try putting Everything in debug mode and watch the current folder being indexed:

• Type in the following search and press ENTER:
  /debug
• Type in the following search and press ENTER:
  /verbose
• The current folder being scanned is shown in Green text.

Is Everything making progress?
What folder is Everything getting stuck on?

[DonVoidEver]

Thanks so much for the replies

I've tried the /debug mode with the installed version of Everything and some sort of CMD screen popped up and it said it couldn't focus a field. Didn't really do anything I had the impression.


I've now put the 1.5 Alpha version portable on the problematic PC and added the mapped drives to tools --> options --> indexes --> folders and it says it's indexing.
At least now I have some feedback it's actually indexing, been at it for hours. Seems a more responsive version , good.

We'll see how it goes, I always had to add the mapped drives under tools --> options --> indexes --> 'folders' , perhaps it's now under 'mapped drives' , I've no idea yet

[therube]

and added the mapped drives

So it was only mapped drives that did not work in 1.4, local drives did?

Tell us about your mapped drives.

[therube]

/debug, should open a console window

/verbose, should then be displaying a scrolling list of "stuff", some of which would be green in color, & that green stuff meaning that stuff is happening

& I suppose if there were not scrolling, & not display of "greens" or if the greens stopped...


And a subsequent /verbose would disable verbose mode & leave standard debug, &/or a subsequent /debug would close that debug window.