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.

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

0install overloads Windows 10 #180

Closed
que-vector opened this issue Nov 29, 2022 · 6 comments
Closed

0install overloads Windows 10 #180

que-vector opened this issue Nov 29, 2022 · 6 comments

Comments

@que-vector
Copy link

que-vector commented Nov 29, 2022

Hi,

since I do not know which software is using 0install I write this issue here. Out of nowhere 0install runs hundreds of processes on my windows machine and it seems that I am not the only one:
https://www.computerbase.de/forum/threads/0install-exe-muellt-ram-zu.2112206/

grafik

grafik

@bastianeicher
Copy link
Member

Sorry to hear you're having issues with Zero Install.

Could you look for the log file %temp%\0install-win %username% Log.txt and post it here (after removing personally identifiable information such as usernames)? This would help figuring out the cause of the problem.

@bastianeicher
Copy link
Member

Another helpful indicator could be, whether the InstallLocation value in the registry key HKEY_CURRENT_USER\SOFTWARE\Zero Install matches the directory where 0install-win.exe is located.

@que-vector
Copy link
Author

It seems that this won't help:

C:\Users\XXX>%temp%\0install-win %username% Log.txt
Der Befehl "C:\Users\XXX\AppData\Local\Temp\0install-win" is either misspelled or could not be found.

Do you mean this location?
grafik

if yes, then it seems to fit:
grafik

@bastianeicher
Copy link
Member

Yes, that's exactly the registry location I was looking for, thanks. :)

You may be able to fix the issue by simply changing the value in the registry to have an upper-case drive letter D: instead of d:.

Please note that this issue has already been fixed in a newer versions of Zero Install, so this shouldn't occur again if you reinstall on a new machine.

In case this does not solve the issue, you should be able to find the log file by adding apostrophes to the command-line:

"%temp%\0install-win %username% Log.txt"

@bastianeicher
Copy link
Member

Hi @que-vector,
just wanted to check in, whether changing the registry value solved the issue for you?
Regards, Bastian

@que-vector
Copy link
Author

Hi Bastian,
Yes, after the restart, everything worked as it should.
Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants