Everything stops updating index

[Scoox]

Windows 10 Pro 64-bit v21H2 (OS Build 22000.2057)
Everything 1.4.1.1024 (x64) running as service

Hi, I've been using Everything for over 10 years and this started happening recently. When I create a file, rename an existing one or download a file from the Internet Everything is usually able to find them, but sooner or later it stops updating its index. The Force Rebuild button and a restart of Everything takes care of things, but I don't know what I'm doing wrong because I've been using the same configuration for years without problems.

Here's an example of me trying to rename a file in Everything, when I'm doing typing I hit Enter and the old name remains. If I try to open the file Everything says it can't find it (obviously).

TEST 2023-07-08-001905 Everything.gif (184.88 KiB) Viewed 2947 times

Otherwise the program has always been rock-solid and this is the first time I encounter a problem in years. Thanks!

[void]

Please make sure Everything is installed correctly and running as a standard user:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Store settings and data in %APPDATA%\Everything.
• Uncheck Run as administrator.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.
• Exit Everything (right click the Everything tray icon and click Exit).
• Restart Everything.

Please try forcing a rebuild:

• In Everything, from the Tools menu, click Options.
• Click the Indexes tab on the left.
• Click Force Rebuild.
• Click OK.

Please let me know if the issue persists.

[Scoox]

Hi Void, my settings were already exactly as you instruct, the only setting that is not the same is Store settings and data in %APPDATA%\Everything. which I didn't check because I run Everything as a portable app. Please note the folder containing Everything.exe is not a system-protected location. This is how I've always used Everything and it was never a problem. If I remember correctly, when this happens the service has stopped running for some reason. I will confirm this detail the next time it happens. Is there any reason why the service would stop?

[void]

The Everything Service should never be in the stopped state.

Please check the event viewer for any crash reports:

• From the Start menu, click run.
• Type in the following and press ENTER:
  eventvwr
• In the Event Viewer, navigate to:
• Windows Logs -> System
• On the right, click Filter Current Log...
• Check Error and click OK.
• Are there any error reports generated for the Everything Service?

[Scoox]

I went through the whole list and found no error events related to Everything. I haven't touch the following service recovery settings, I imagine Everything sets this as needed when the service is installed?

Service Recovery.png (17.36 KiB) Viewed 2933 times

[void]

Thank you for the information.

It sounds like the Service is running OK and is not stopping unexpectedly.

Everything will set those options in your screenshot.
These are the default settings.



There might be another process stopping the Everything Service.
Hard to tell which one.
Please check your antivirus software.
Please check any stuck or pending Windows updates.



To see if the Everything service is running:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Everything Service will be tick-checked if the Everything Service is running.
• Everything Service will be square-checked if the Everything Service is install and not running.

Please let me know if you see the Everything Service square-checked.

[Scoox]

I'm don't use any antivirus software (instead I use Sandboxie and scan any files that need scanning using VirusTotal), and the run as service option is tick-checked. Everything seems to be in order. If at the moment you can't think of anything else I'll check the error logs and the status of the service. I might try an earlier version to see if it still happens.

[Scoox]

It just happened again. It actually happened last night (2:26 AM) but of course it's easy for it to go unnoticed because I only notice when Everything continues to display files and folders that no longer exist, which is what just happened.

The service is not running. I've searched for related errors in the Event log and found this:

Code: Select all

Log Name:      System
Source:        Service Control Manager
Date:          12/07/2023 02:26:37
Event ID:      7034
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Supernova
Description:
[b]The Everything service terminated unexpectedly.  It has done this 1 time(s).[/b]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7034</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2023-07-12T00:26:37.6969732Z" />
    <EventRecordID>37459</EventRecordID>
    <Correlation />
    <Execution ProcessID="856" ThreadID="4812" />
    <Channel>System</Channel>
    <Computer>Supernova</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Everything</Data>
    <Data Name="param2">1</Data>
    <Binary>450076006500720079007400680069006E0067000000</Binary>
  </EventData>
</Event>

The event before that is a warning which repeats multiple times over time, looks like I'm running low on memory. Indeed I have a heavy Firefox session going and one of my RAM sticks died a while back, so maybe this is related. I'm getting a new PC soon. If you can't find any clues in these event log reports, I'll keep an eye on this and make a note every time it happens once I get the new PC. If it doesn't happen I would guess low memory was the cause.

Code: Select all

Log Name:      System
Source:        Microsoft-Windows-Resource-Exhaustion-Detector
Date:          12/07/2023 02:25:29
Event ID:      2004
Task Category: [b]Resource Exhaustion Diagnosis Events[/b]
Level:         Warning
Keywords:      Events related to exhaustion of system commit limit (virtual memory).
User:          SYSTEM
Computer:      Supernova
Description:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: firefox.exe (9672) consumed 4196978688 bytes, firefox.exe (10808) consumed 2223521792 bytes, and firefox.exe (12644) consumed 1842434048 bytes.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748e-c2e8-4054-85f6-0c3e1cad2470}" />
    <EventID>2004</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>3</Task>
    <Opcode>33</Opcode>
    <Keywords>0x8000000020000000</Keywords>
    <TimeCreated SystemTime="2023-07-12T00:25:29.0883975Z" />
    <EventRecordID>37458</EventRecordID>
    <Correlation ActivityID="{55563bcf-4f6c-4779-9041-ac706fb7eb47}" />
    <Execution ProcessID="10052" ThreadID="19420" />
    <Channel>System</Channel>
    <Computer>Supernova</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">
      <SystemInfo>
        <SystemCommitLimit>33040412672</SystemCommitLimit>
        <SystemCommitCharge>33004290048</SystemCommitCharge>
        <ProcessCommitCharge>27156549632</ProcessCommitCharge>
        <PagedPoolUsage>547631104</PagedPoolUsage>
        <PhysicalMemorySize>17130635264</PhysicalMemorySize>
        <PhysicalMemoryUsage>14194061312</PhysicalMemoryUsage>
        <NonPagedPoolUsage>443006976</NonPagedPoolUsage>
        <Processes>261</Processes>
      </SystemInfo>
      <PagedPoolInfo>
        <Tag_1>
          <Name>MmSt</Name>
          <PoolUsed>42051968</PoolUsed>
        </Tag_1>
        <Tag_2>
          <Name>Vi54</Name>
          <PoolUsed>41910272</PoolUsed>
        </Tag_2>
        <Tag_3>
          <Name>Ntff</Name>
          <PoolUsed>34241152</PoolUsed>
        </Tag_3>
      </PagedPoolInfo>
      <NonPagedPoolInfo>
        <Tag_1>
          <Name>smNp</Name>
          <PoolUsed>53420032</PoolUsed>
        </Tag_1>
        <Tag_2>
          <Name>smCB</Name>
          <PoolUsed>34398208</PoolUsed>
        </Tag_2>
        <Tag_3>
          <Name>smBt</Name>
          <PoolUsed>31096832</PoolUsed>
        </Tag_3>
      </NonPagedPoolInfo>
      <ProcessInfo>
        <Process_1>
          <Name>firefox.exe</Name>
          <ID>9672</ID>
          <CreationTime>2023-07-11T22:29:39.6916169Z</CreationTime>
          <CommitCharge>4196978688</CommitCharge>
          <HandleCount>1741</HandleCount>
          <Version>114.0.2.8570</Version>
          <TypeInfo>201</TypeInfo>
        </Process_1>
        <Process_2>
          <Name>firefox.exe</Name>
          <ID>10808</ID>
          <CreationTime>2023-07-08T14:26:23.4069631Z</CreationTime>
          <CommitCharge>2223521792</CommitCharge>
          <HandleCount>4357</HandleCount>
          <Version>114.0.2.8570</Version>
          <TypeInfo>210</TypeInfo>
        </Process_2>
        <Process_3>
          <Name>firefox.exe</Name>
          <ID>12644</ID>
          <CreationTime>2023-07-08T14:26:29.3083228Z</CreationTime>
          <CommitCharge>1842434048</CommitCharge>
          <HandleCount>452</HandleCount>
          <Version>114.0.2.8570</Version>
          <TypeInfo>219</TypeInfo>
        </Process_3>
        <Process_4>
          <Name>
          </Name>
          <ID>0</ID>
          <CreationTime>1601-01-01T00:00:00.0000000Z</CreationTime>
          <CommitCharge>0</CommitCharge>
          <HandleCount>0</HandleCount>
          <Version>0.0.0.0</Version>
          <TypeInfo>0</TypeInfo>
        </Process_4>
        <Process_5>
          <Name>
          </Name>
          <ID>0</ID>
          <CreationTime>1601-01-01T00:00:00.0000000Z</CreationTime>
          <CommitCharge>0</CommitCharge>
          <HandleCount>0</HandleCount>
          <Version>0.0.0.0</Version>
          <TypeInfo>0</TypeInfo>
        </Process_5>
        <Process_6>
          <Name>
          </Name>
          <ID>0</ID>
          <CreationTime>1601-01-01T00:00:00.0000000Z</CreationTime>
          <CommitCharge>0</CommitCharge>
          <HandleCount>0</HandleCount>
          <Version>0.0.0.0</Version>
          <TypeInfo>0</TypeInfo>
        </Process_6>
      </ProcessInfo>
      <ExhaustionEventInfo>
        <Time>2023-07-12T00:25:44.5983080Z</Time>
      </ExhaustionEventInfo>
    </MemoryExhaustionInfo>
  </UserData>
</Event>

[void]

Thank you for the information Scoox,



Please try capturing a mini crash dump:

• Make sure Everything is not running (File -> Exit)
• Restart the Everything Service from the Task Manager -> Services -> Everything -> Right click -> Start Service.
• Download SysInternals ProcDump from Microsoft.
• From an admin command prompt, in the same directory as procdump, type in the following and press ENTER:
  procdump -mm -e Everything.exe
• Restart Everything.
• Wait for Everything to crash.
• A dmp file should be generated.
• Please check for an Everything dmp file in:
  C:\Users\Administrator\AppData\Local\CrashDumps
• Could you please send this mini crash dump to support@voidtools.com

Please try Everything 1.5.
The new service might be more stable.

[Scoox]

[*]Wait for Everything to crash.[/list]

Do you mean wait for the problem to happen? Or will ProcDump cause Everything to crash?

Please try Everything 1.5.
The new service might be more stable.

Downloading now, thanks for the heads-up.

[void]

What for the service to crash again.
It may take some time..
When the service crashes, ProcDump will create an Everything .dmp file.

The dmp file will contain the stack at the time of the crash which will help locate the issue.

[Scoox]

[18:04:19] Process Exit: PID 11332, Exit Code 0x00000001
[18:04:19] The process has exited.
[18:04:19] Dump count not reached.

That's all ProcDump spat out. I could find a file named "Everything.exe.7468.dmp" but I can't copy it out, I get an error message saying I don't have enough privileges. I've tried getting to it running Explorer as administrator but still didn't work.

[NotNull]

Explorer can't be run as administrator [1] (on Windows newer than XP), so if you try, Everything will still be running as a non-elevated user.
Alternative: Third party filemanagers can be run 'as administrator'. Use Everything to find the location of the file if needed.

[1] technically it is still possible, but very atypical

[Scoox]

I got to the file running Everything as admin but I'm not comfortable sharing this file as it's not human readable although there are bits that contain paths and stuff but I have no way to check what it contains so I'm probably just going to give up on this and assume the problem is I'm low on RAM. I sincerely appreciate your help!