Sometimes when I attempt to conduct a search for a folder or folders given or sharing a particular case-sensitive name or partial name, there is a semi-fatal error, semi-fatal in that it doesn't kill the program, but fails to actually carry out the command. A pop-up error is generated saying something about a Windows error. I don't remember what the exact message is, and I can't reproduce it upon command, as the application "decides" to generate the error "whenever it feels like it."
Now, to get the immediately-desired result, to find the directory or directories that I was looking for, I terminate the application, relaunch it, and then it automatically does what I wanted it to do before the error occurred.
This error started happening only after the latest update to the supported Windows 10x64 platform, 20H2. The OS is fully-updated, and doing a clean reinstall of Locate32 is impossible, as it technically isn't actually installed, only manually instantiated—and I am indeed using the latest version, 3.1 RC3m Build 11.7100.
I'll go ahead and file (publish) this, and the next time the error occurs, I'll capture a screenshot and upload it.
What mystifies me so deeply is that the programmers at Microsoft are evidently incapable of writing a version of File Explorer that does what Locate32 does so easily, and with such a small system footprint. Windows takes "forever" to conduct its searches, and when it's done, you cannot have faith in its results, unlike with Locate32. When Locate32 says it can't find any files matching the given parameters, you can believe it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is not so much options to debug the program as development is not continued, but maybe the error message gives some hints if something can be done.
Yes, no need to reinstall Locate32, but you can try to reset settings. There is settool.exe for that.
Bitty (?) Unsure how to parse. Anyway, since you were nice enough to make your contribution, I thought I should tell you how well your advice has served me: Greatly.
Since installing the version that you had recommended, I have not had any of the strange errors I was getting. I did get one error message, but I don't even remember what it was, only that it wasn't the one that was irritating the dickens out of me, and it did happen only once,
I can only figure that a Windows update screwed up something that the old version of Locate32 was dependent upon (it wasn't a virus; in the twelve years I've been buying Webroot, I've only had one threat slip past it, and that was seven years ago) because the newer version isn't "suffering" as the old one was.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The link above gives version 3.1.10.8220 and not as shown, please.
If I stop searching and stop it on my win8.1 x64 machine, it doesn't stop even end task from task manager can't close the process.
The program locate32.exe version 3.1.10.8220 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 464
Start Time: 01d7da2d1fb58ad4
Termination Time: 60000
Application Path: C:\locate32x64\locate32.exe
Report Id: 8c4b797d-4620-11ec-825e-e0d55e669f39
Faulting package full name:
Faulting package-relative application ID:
Log Name: Application
Source: Application Hang
Date: 15-11-2021 20:01:31
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: Win8SSD1P1
Description:
The program locate32.exe version 3.1.10.8220 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 464
Start Time: 01d7da2d1fb58ad4
Termination Time: 60000
Application Path: C:\locate32x64\locate32.exe
Report Id: 8c4b797d-4620-11ec-825e-e0d55e669f39
Faulting package full name:
Faulting package-relative application ID:
Sometimes when I attempt to conduct a search for a folder or folders given or sharing a particular case-sensitive name or partial name, there is a semi-fatal error, semi-fatal in that it doesn't kill the program, but fails to actually carry out the command. A pop-up error is generated saying something about a Windows error. I don't remember what the exact message is, and I can't reproduce it upon command, as the application "decides" to generate the error "whenever it feels like it."
Now, to get the immediately-desired result, to find the directory or directories that I was looking for, I terminate the application, relaunch it, and then it automatically does what I wanted it to do before the error occurred.
This error started happening only after the latest update to the supported Windows 10x64 platform, 20H2. The OS is fully-updated, and doing a clean reinstall of Locate32 is impossible, as it technically isn't actually installed, only manually instantiated—and I am indeed using the latest version, 3.1 RC3m Build 11.7100.
I'll go ahead and file (publish) this, and the next time the error occurs, I'll capture a screenshot and upload it.
What mystifies me so deeply is that the programmers at Microsoft are evidently incapable of writing a version of File Explorer that does what Locate32 does so easily, and with such a small system footprint. Windows takes "forever" to conduct its searches, and when it's done, you cannot have faith in its results, unlike with Locate32. When Locate32 says it can't find any files matching the given parameters, you can believe it.
That's bitty.
There is not so much options to debug the program as development is not continued, but maybe the error message gives some hints if something can be done.
Yes, no need to reinstall Locate32, but you can try to reset settings. There is settool.exe for that.
Have you tried this? It's the most recent version, but I am not completely sure if it's 64 bit
https://sourceforge.net/projects/locate32/files/locate32_3.1.11.8220a_fix.zip/download
Bitty (?) Unsure how to parse. Anyway, since you were nice enough to make your contribution, I thought I should tell you how well your advice has served me: Greatly.
Since installing the version that you had recommended, I have not had any of the strange errors I was getting. I did get one error message, but I don't even remember what it was, only that it wasn't the one that was irritating the dickens out of me, and it did happen only once,
I can only figure that a Windows update screwed up something that the old version of Locate32 was dependent upon (it wasn't a virus; in the twelve years I've been buying Webroot, I've only had one threat slip past it, and that was seven years ago) because the newer version isn't "suffering" as the old one was.
The link above gives version 3.1.10.8220 and not as shown, please.
If I stop searching and stop it on my win8.1 x64 machine, it doesn't stop even end task from task manager can't close the process.
The program locate32.exe version 3.1.10.8220 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 464
Start Time: 01d7da2d1fb58ad4
Termination Time: 60000
Application Path: C:\locate32x64\locate32.exe
Report Id: 8c4b797d-4620-11ec-825e-e0d55e669f39
Faulting package full name:
Faulting package-relative application ID:
Log Name: Application
Source: Application Hang
Date: 15-11-2021 20:01:31
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: Win8SSD1P1
Description:
The program locate32.exe version 3.1.10.8220 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 464
Start Time: 01d7da2d1fb58ad4
Termination Time: 60000
Application Path: C:\locate32x64\locate32.exe
Report Id: 8c4b797d-4620-11ec-825e-e0d55e669f39
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<system>
<provider name="Application Hang">
<eventid qualifiers="0">1002</eventid>
<level>2</level>
<task>101</task>
<keywords>0x80000000000000</keywords>
<timecreated systemtime="2021-11-15T14:31:31.000000000Z">
<eventrecordid>3391</eventrecordid>
<channel>Application</channel>
<computer>Win8SSD1P1</computer>
<security>
</security></timecreated></provider></system>
<eventdata>
<data>locate32.exe</data>
<data>3.1.10.8220</data>
<data>464</data>
<data>01d7da2d1fb58ad4</data>
<data>60000</data>
<data>C:\locate32x64\locate32.exe</data>
<data>8c4b797d-4620-11ec-825e-e0d55e669f39</data>
<data>
</data>
<data>
</data>
<binary>55006E006B006E006F0077006E0000000000</binary>
</eventdata>
</event>
Last edit: Daren Hoff 2021-11-15
See newer response above.
Last edit: William Kuns 2021-05-18