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

Nyrna starts but never loads #180

Closed
TearOfTheStar opened this issue Aug 11, 2023 · 5 comments
Closed

Nyrna starts but never loads #180

TearOfTheStar opened this issue Aug 11, 2023 · 5 comments

Comments

@TearOfTheStar
Copy link

Hello!

Nyrna stopped running properly, it starts, i can enter settings and change things there, but main functionality doesn't work. It seems like something is missing in my system, but log isn't clear.

Last version that runs is 2.0 stable. After that this issue persists.

Win 10 x64 22h2 (19045.2846)

Installed on non system drive.

Log from 2.16.0 is attached.

nyrna_v2.16.0_log.txt

@Merrit
Copy link
Owner

Merrit commented Aug 11, 2023

Please try installing the latest version of PowerShell and see if that makes any difference.

@TearOfTheStar
Copy link
Author

Same effect. Installed and restarted. Here's the log.

Noticed interesting thing, several Process IDs are not present in my task manager, yet it looks for them. For example: GetProcessById(9064), there is no PID 9064 in my running processes.

nyrna_v2.16.0_PS7_log.txt

@Merrit
Copy link
Owner

Merrit commented Aug 11, 2023

That sounds very odd..

Please try running this in a terminal: where.exe powershell

Paste the output here.. from the logs it sounds like it can't find PowerShell.

@TearOfTheStar
Copy link
Author

TearOfTheStar commented Aug 11, 2023

Got it!

powershell (PS5) wasn't in the PATH, but pwsh (PS7) was. After manually adding the old powershell path it all works as it should.

Thank You!

edit: Close this issue if there is nothing to add.

@Merrit
Copy link
Owner

Merrit commented Aug 11, 2023

Interesting, never seen that not be on path before! Strange that they changed the executable name, but hey - glad you got it sorted! 🎉

Thanks for providing clear troubleshooting info :)

@Merrit Merrit closed this as completed Aug 11, 2023
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