I am using Windows 10 with Windows defender. After clicking on the downloaded installation file, I have got an error message indicating that there is a virus or a potentially dangerous file., and after that the downloaded file disappears. Iwill try yo desactivate Defender to install the software but will it still work if after installation i reactivate windows 10? Thanks a lot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately I have no way to know, but my guess is probably not. It's a problem with the antivirus software so I would either submit it as a false positive (if you want to go through the trouble -- I don't) or just exclude the path where you've install it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-05-21
I have the same issue - I have even tried downoading on a Windows 7 PC with no luck.
Perhaps the Developers should consider code-signing the installation binary.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the anti-virus issue is bothering you (and adding a folder exclusion is not an option):
If you're on a 64-bit system: Search for SwiftSearch64 to find the 64-bit version in your Temp folder, copy it somewhere, and use that instead.
If you're on a 32-bit system: Delete the embedded 64-bit binary with Resoure Hacker.
This should work for most anti-viruses, except a few (e.g. Kaspersky and ZoneAlarm seem to still get confused).
Last edit: - 2018-05-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-05-21
I do not want to 'hack' anything - I just want a tool that has worked fine before to simply work (download and run) since it has been 'improved'.
Unfortunately I do actually have better things to do with my time than trying to get something that should already work to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What do you propose I do? Honestly, the tool that is failing to run correctly here is your antivirus, not my program... it's weird to put the blame on me. The way to solve this once and for all is to just add an exclusion to your antivirus for the folder where you put this program. I could try to go out of my way and provide separate 32-bit and 64-bit binaries, but then I'd have to find a way to tell people to only download those if they have buggy antiviruses (how would I tell them? the download link on the front page goes straight to the download), and even then they might get flagged. Code-signing on my end require me to pay >$100/year which I don't think is a reasonable expectation for free software that I'm writing in my spare time...
Last edit: - 2018-05-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
in a temp directory. I copied it to somewhere else & renamed it to something without all those random numbers (I used SwiftSearch64 v7.0).
I then checked THAT file on VirusTotal and got 100% clean.
All is good and I'm using the latest version on Windows 10 with no problems.
Bottom Line - it is possible to work around the problem. However, given the prevelance of Windows 10 and 64-bit installations, the best solution probably is to package up the 32 & 64-bit versions seperately for downloading and avoid all this false positive business and its workarounds altogether.
Thanks - as usual it is a great program & I use it almost daily.
P.S. if you follow the Microsoft advice, don't forget to re-enable virus scanning on downloads!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-11
Isn't that program portable and consists in only one executable file which you run as SwiftSearch.exe?
What does it do/store in system temp folder? I supposed that SwiftSearch wouldn't extract anything to any location except RAM? And does it leave any leftover on system?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The program you download is 32-bit with a 64-bit version embedded. On a 64-bit system it extract and runs the 64-bit copy in the Temp folder, then deletes it when you close the program. It shouldn't leave any leftovers on your system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-12
Hi,
Based on the binary size i think i have version 6.0 and double-checked that it doesn't create any temporary file in %Temp% folder, and searching "SwiftSearch" keyword yields no results in any other location except current executable on my x64 machine. So is this specific to Windows 10 or version 7.x?
I have Windows 7 SP1 64-bit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This behavior isn't specific to any OS version. The 64-bit version should be in your Temp folder if you search for "SwiftSearch", unless for some reason it is failing to be extract the 64-bit version and continuing to run the 32-bit version instead. You can try to figure out what's happening with tools like ProcMon but I can't really explain how to do that here if you're not familiar with it already.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-12
ProcMon couldn't show any clue about the failure related to SwiftSearch. Actually it's hard to track as numerous I/O cycles happen at the same time system-wide, so filtering is useless, too. I just launch it approving UAC prompt, and that's it all. It just stays alone and runs from the location where it's located on my Win7 x64 with version 6.0. I don't know why, and it's not an issue, just a thingy i noticed based on your previous comments sir.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-12
By the way i am looking into "C:\ Users\<user>\AppData\Local\Temp" which is identical with %temp% you know. Maybe version 6 has this problem. Thanks.</user>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This isn't specific to any program version. That's strange. Could you check in Task Manager to see if there is a 64-bit copy running or if it's just 32-bit?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-13
I double-checked again and it runs in 32-bit mode as Task Manager shows SwiftSearch *32 on Win7 SP1 x64, and i do not have issues running other 64-bit apps including browsers. Maybe something is missing or incompatible within the program itself. You might review the code in your spare time sir.
Again it is v6.0 based on binary size. I wish version info was provided somewhere though such as title bar.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-13
By the way, is there any inconvenience or disadvantage while running in 32 bit mode other than performance/search speed? As it is blazing fast even with 32 bit mode on 64 bit system :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see. I'm not sure to be honest. I don't believe I changed the extraction behavior much recently. One possibility I now realized though is that your system isn't English (United States) and the program is unable to find a 64-bit executable for that language? If that's not the case then I'm not sure what else it might be.
The disadvantages to using the 32-bit version are somwhat minor. One is that it won't be able to use more than ~2 GB of RAM, although most people will not need anywhere near as much. Another issue is that right-clicking will show the 32-bit context menus rather than the 64-bit ones, so entries you see may be different from what you expect. The last issue I'm aware of is I'm not really sure that right-clicking files under a folder like System32 would work correctly. It might end up accessing the files under SysWOW64 instead. (Similarly, it would probably load their icons instead.) But I don't think there are any majors issues.
BTW, can I ask if there's a particular reason you're not using the latest version? I've only tried to make improvements, and I don't think I've removed any useful features. If you notice any problems with more recent versions, please let me know. They also do show you the build date to help you identify how recent your copy is (which performs the same function as what your desired version numbers would do).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Windows 10 with Windows defender. After clicking on the downloaded installation file, I have got an error message indicating that there is a virus or a potentially dangerous file., and after that the downloaded file disappears. Iwill try yo desactivate Defender to install the software but will it still work if after installation i reactivate windows 10? Thanks a lot.
Unfortunately I have no way to know, but my guess is probably not. It's a problem with the antivirus software so I would either submit it as a false positive (if you want to go through the trouble -- I don't) or just exclude the path where you've install it.
I have the same issue - I have even tried downoading on a Windows 7 PC with no luck.
Perhaps the Developers should consider code-signing the installation binary.
There's only one developer ;) I believe that requires money?
If the anti-virus issue is bothering you (and adding a folder exclusion is not an option):
If you're on a 64-bit system: Search for
SwiftSearch64to find the 64-bit version in your Temp folder, copy it somewhere, and use that instead.If you're on a 32-bit system: Delete the embedded 64-bit binary with Resoure Hacker.
This should work for most anti-viruses, except a few (e.g. Kaspersky and ZoneAlarm seem to still get confused).
Last edit: - 2018-05-21
I do not want to 'hack' anything - I just want a tool that has worked fine before to simply work (download and run) since it has been 'improved'.
Unfortunately I do actually have better things to do with my time than trying to get something that should already work to work.
What do you propose I do? Honestly, the tool that is failing to run correctly here is your antivirus, not my program... it's weird to put the blame on me. The way to solve this once and for all is to just add an exclusion to your antivirus for the folder where you put this program. I could try to go out of my way and provide separate 32-bit and 64-bit binaries, but then I'd have to find a way to tell people to only download those if they have buggy antiviruses (how would I tell them? the download link on the front page goes straight to the download), and even then they might get flagged. Code-signing on my end require me to pay >$100/year which I don't think is a reasonable expectation for free software that I'm writing in my spare time...
Last edit: - 2018-05-21
I just want you to know that this is the utility that I use most,
enjoy using, save time with -- and have recommended in my column.
Thank you for such a useful tool!
Jack Peckham
newscenter@rcn.com
==================================
At 08:15 PM 05/21/18 +0000, you wrote:
Thank you! Happy to hear :)
FYI, I resolved the virus scan problem by following this advice from Microsoft.
For grins, I checked it on VirusTotal and got 20 positives (and 45 clean).
When I then tried running the program, I got Windows Defender Screening error - I told it to run it anyway.
Then I followed the advice to search for SwiftSearch64 (using SwiftSearch, itself) and found the file:
in a temp directory. I copied it to somewhere else & renamed it to something without all those random numbers (I used SwiftSearch64 v7.0).
I then checked THAT file on VirusTotal and got 100% clean.
All is good and I'm using the latest version on Windows 10 with no problems.
Bottom Line - it is possible to work around the problem. However, given the prevelance of Windows 10 and 64-bit installations, the best solution probably is to package up the 32 & 64-bit versions seperately for downloading and avoid all this false positive business and its workarounds altogether.
Thanks - as usual it is a great program & I use it almost daily.
P.S. if you follow the Microsoft advice, don't forget to re-enable virus scanning on downloads!
Awesome, thanks for reporting back!
sorry - forgot to sign in. This was by me.
Haha cool! :)
Isn't that program portable and consists in only one executable file which you run as SwiftSearch.exe?
What does it do/store in system temp folder? I supposed that SwiftSearch wouldn't extract anything to any location except RAM? And does it leave any leftover on system?
The program you download is 32-bit with a 64-bit version embedded. On a 64-bit system it extract and runs the 64-bit copy in the Temp folder, then deletes it when you close the program. It shouldn't leave any leftovers on your system.
Hi,
Based on the binary size i think i have version 6.0 and double-checked that it doesn't create any temporary file in %Temp% folder, and searching "SwiftSearch" keyword yields no results in any other location except current executable on my x64 machine. So is this specific to Windows 10 or version 7.x?
I have Windows 7 SP1 64-bit.
This behavior isn't specific to any OS version. The 64-bit version should be in your Temp folder if you search for "SwiftSearch", unless for some reason it is failing to be extract the 64-bit version and continuing to run the 32-bit version instead. You can try to figure out what's happening with tools like ProcMon but I can't really explain how to do that here if you're not familiar with it already.
ProcMon couldn't show any clue about the failure related to SwiftSearch. Actually it's hard to track as numerous I/O cycles happen at the same time system-wide, so filtering is useless, too. I just launch it approving UAC prompt, and that's it all. It just stays alone and runs from the location where it's located on my Win7 x64 with version 6.0. I don't know why, and it's not an issue, just a thingy i noticed based on your previous comments sir.
Thanks!
By the way i am looking into "C:\ Users\<user>\AppData\Local\Temp" which is identical with %temp% you know. Maybe version 6 has this problem. Thanks.</user>
This isn't specific to any program version. That's strange. Could you check in Task Manager to see if there is a 64-bit copy running or if it's just 32-bit?
I double-checked again and it runs in 32-bit mode as Task Manager shows SwiftSearch *32 on Win7 SP1 x64, and i do not have issues running other 64-bit apps including browsers. Maybe something is missing or incompatible within the program itself. You might review the code in your spare time sir.
Again it is v6.0 based on binary size. I wish version info was provided somewhere though such as title bar.
Thanks!
By the way, is there any inconvenience or disadvantage while running in 32 bit mode other than performance/search speed? As it is blazing fast even with 32 bit mode on 64 bit system :)
I see. I'm not sure to be honest. I don't believe I changed the extraction behavior much recently. One possibility I now realized though is that your system isn't English (United States) and the program is unable to find a 64-bit executable for that language? If that's not the case then I'm not sure what else it might be.
The disadvantages to using the 32-bit version are somwhat minor. One is that it won't be able to use more than ~2 GB of RAM, although most people will not need anywhere near as much. Another issue is that right-clicking will show the 32-bit context menus rather than the 64-bit ones, so entries you see may be different from what you expect. The last issue I'm aware of is I'm not really sure that right-clicking files under a folder like System32 would work correctly. It might end up accessing the files under SysWOW64 instead. (Similarly, it would probably load their icons instead.) But I don't think there are any majors issues.
BTW, can I ask if there's a particular reason you're not using the latest version? I've only tried to make improvements, and I don't think I've removed any useful features. If you notice any problems with more recent versions, please let me know. They also do show you the build date to help you identify how recent your copy is (which performs the same function as what your desired version numbers would do).