Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fail to run on win10-1903 #51

Open
the-liquid-metal opened this issue Aug 24, 2019 · 22 comments
Open

fail to run on win10-1903 #51

the-liquid-metal opened this issue Aug 24, 2019 · 22 comments
Assignees
@dfs-minded
Labels
bug

Comments

@the-liquid-metal
Copy link

the window does not appears at all.
@Stateford
Copy link
Contributor

Was this the binary or did you build it yourself? Any errors?

I think #37 could be related.

@the-liquid-metal
Copy link
Author

the-liquid-metal commented Aug 24, 2019 •
edited
Loading

The binary, from https://indexer-plus-plus.com/?smd_process_download=1&download_id=351.
I don't no how to catch the error. As i say before: the window does not appears at all.
There is already "UserSettings.xml".
The only change which i made is the installation directory (E:\Downloads\Indexer++ Beta).

@Stateford
Copy link
Contributor

I just tried that URL and I could not seem to reproduce the error. Are there any messages in event viewer?

I'm on 1903 as well. Unfortunately I do not have multiple drives to test this issue, but could you possibly try the following?

  1. Reinstall the application on the same drive
  2. Reinstall to your main drive.

@the-liquid-metal
Copy link
Author

the-liquid-metal commented Aug 25, 2019 •
edited
Loading 

1. Reinstall the application on the same drive
2. Reinstall to your main drive.

nothings happens

Do i have to install specific VCR or .net?

@Stateford
Copy link
Contributor

The readme says this:

Sources can be built using Visual Studio 17, .NET Framework 4.0. Suggested target platform is x86.

I would assume you would see an error when launching if you didn't have the correct run times installed.

I cannot seem to reproduce this error.

@dfs-minded dfs-minded added the bug label Oct 13, 2019
@dfs-minded dfs-minded self-assigned this Oct 13, 2019
@dfs-minded
Copy link
Owner

Hi Hendra! Thanks for reporting this issue.
As Dimitri has mentioned it really looks like some libraries are missing, most probably .NET. First what you can do is install a .NET. It is a 4.8 version, but Microsoft claims it should be compatible with all 4.x versions (so with 4.0 as well).

If it still does not help, I have compiled a debug version of Indexer++ with enabled logging, so we may find out what exactly is the error if it is cached and logged.

@the-liquid-metal
Copy link
Author

Sources can be built using Visual Studio 17, .NET Framework 4.0. Suggested target platform is x86.

is it critical? my own is x64.

If it still does not help, I have compiled a debug version of Indexer++ with enabled logging, so we may find out what exactly is the error if it is cached and logged.

still, nothings happens.

@dfs-minded
Copy link
Owner

No, x64 should also work.
That is expected, the only difference is that there is a "Logs" folder inside the folder where you have I stalled Indexer. Could you please send the files generated there? Keep fingers crossed they contain the error message)) If not, well, just several iterations may be needed as I will add more debug information.

@the-liquid-metal
Copy link
Author

the-liquid-metal commented Oct 17, 2019 •
edited
Loading

surprisingly, there is no folder named "logs" inside installation dir (E:\Downloads\Indexer++ Beta).
is there any effect if i disable win sercive named "Windows Search" (Control Panel > All Control Panel Items > Administrative Tools > Services => Windows Search) ?

@graphixillusion
Copy link

graphixillusion commented Nov 23, 2019 •
edited
Loading

I can confirm the bug under Windows 10 1909. The application starts in the tray icons but crash immediately after. Here's the error in the event viewer:

Origin: Application Error
ID EVENT: 1000

Name of the app: Indexer++ Beta.exe, versione: 1.0.0.0, timestamp: 0x5a7b0a3b
Name of the module: CLIInterop.dll, versione: 0.0.0.0, timestamp: 0x5a7b0a34
Exception Code: 0xc0000005
Offset error 0x00054ee9
ID process error: 0x1d0c
Application Path: C:\Program Files (x86)\Indexer++ Beta\Indexer++ Beta.exe
Module Path: C:\Program Files (x86)\Indexer++ Beta\CLIInterop.dll
Report ID: ea9a4d2b-fea9-4461-93b8-074318a820c6

Origin: .NET Runtime
ID EVENT: 1026

Application: Indexer++ Beta.exe
Framework Version: v4.0.30319
Description: the process was terminated becouse of an unhandled exception.
Exception information: exception code c0000005, exception address 69C54EE9

@diVineProportion
Copy link

diVineProportion commented Jan 22, 2020 •
edited
Loading

before I couldn't get the window to go past flashing. I think I'm on a new install of windows or at least a different version. I have .NET 4.8.
IndexerUILog_637152574449304181.txt
IndexerUILog_637152575148346977.txt
IndexerUILog_637152575427376086.txt
IndexerUILog_637152576290262294.txt
IndexerUILog_637152573095704693.txt

the 'IndexerUILog_637152574449304181' is the only one that seemed to fail, or rather produce anything resembling a crash log.

I freed up some memory after receiving the memory error and haven't had that message again, but still crash on start

@Stateford
Copy link
Contributor

@diVineProportion
I'll take another look when I have time.

Did you download the installer, or build from source?

Did you download from here, or from somewhere else?

@diVineProportion
Copy link

Downloaded the installer; wasn't able to build from source. Not sure if it had to do with v141_xp or something else, i'm playing around with it.

Do you have a nightly build or anything else I can try?

@diVineProportion
Copy link

One of the things i tried was disabling all the drives so that none were selected. Didn't help. Today after a restart I saw it sitting in the system tray and it had the C drive indexed.

The 2-3 times I tried to use indexer++ I uninstalled it before attempting a restart. Maybe other people have a similar experience.

Try leaving it installed and restart. lol

@Stateford
Copy link
Contributor

@diVineProportion I'm guessing it was open in the tray when you tried to launch it. Seems like that could be a possible bug and I'll see if I can reproduce it.

@Stateford
Copy link
Contributor

nvm, could not reproduce. I just installed it and ran it and did not have any issues with it crashing.

@diVineProportion
Copy link

and you didn't have to restart?

@Stateford
Copy link
Contributor

I did not have to restart, it just worked. I'm wondering if there's a C++ redist package missing, or possibly a .net version.

@the-liquid-metal
Copy link
Author

the-liquid-metal commented Jan 31, 2020 •
edited
Loading

Still nothings happens.
These are my config. Hopefully can help you:

Location: Control Panel\System and Security\Administrative Tools

  • Diagnostic Execution Service: disabled
  • Diagnostic Policy Service: disabled
  • Diagnostic Service Host: disabled
  • Diagnostic System Host: disabled
  • Server: disabled
  • Windows Error Reporting Service: disabled

Location: Control Panel\System and Security\Security and Maintenance\Change Security and Maintenance settings

  • internet security settings: uncheck
  • network firewall: uncheck
  • user account control: uncheck
  • virus protection: uncheck
  • Windows backup: uncheck
  • automatic maintenance: uncheck
  • drive status: uncheck
  • windows troubleshooting: uncheck
  • homegroup: uncheck
  • file history: uncheck
  • storage space: uncheck
  • work folders: uncheck

Location: settings\privacy\background apps:

  • let apps run in the background: off

Location: settings\privacy\app diagnostics:

  • let apps access diagnostic information: off

.net 3.5: console admin, then command:

  • dism /online /enable-feature /featurename:netfx3 /all /source:d:\sources\sxs /limitaccess

But please don't ask me to change those.
Thanks in advance.

@dfs-minded
Copy link
Owner

dfs-minded commented Jan 31, 2020 via email

@the-liquid-metal
Copy link
Author

the-liquid-metal commented Jan 31, 2020 •
edited
Loading

.net version is 3.5, but should be 4.0

Ah, i forgot to mention that i already installed .net 4.0.

FYI: i have been using app named "Everything" hosted at https://www.voidtools.com/ for several years. It is a lovely app. It works just what i need with minimum requirement. It is not open source, but it is fine to continue to work with.

As an open source enthusiast, i was very excited when i found this project and gave it a try. I hope this app has same minimum requirement which is very important to me. Once or two, I was faced with a difficult situation to install dependency/change config on my clients machine.

@diVineProportion
Copy link

Now that it runs without crashing (only my C drive in selected for indexing) I can mess with it a bit. First observation is that when indexing my 4TB external hard drive (mounted to A:) it will crash. Logs are no help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dfs-minded dfs-minded

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@the-liquid-metal @dfs-minded @Stateford @graphixillusion @diVineProportion