satstack icon indicating copy to clipboard operation
satstack copied to clipboard

Satstack won't open on Windows

Open raymonddurk opened this issue 3 years ago • 8 comments

It has been running fine for the last few weeks and then suddenly it has stopped working on all of the Windows devices I have access to. When I open the application, it appears then closes itself after a second tops. At first I thought I had updated something and broke it but I can no longer get it working on a personal Windows computer, Windows computer I have access to at work, and a family member's Widows device which all had it working fine. I don't have this issue on other operating systems at the moment.

Mixture of manufacturers, CPUs, GPUs, etc. which is why I believe this is a Windows problem.

raymonddurk avatar Mar 12 '21 16:03 raymonddurk

I am having the same issue on Windows 10 OS Build 19042.867

The only update that happened for me during this time was a Security Intelligence Definition Update for Microsoft Defender Antivirus - KB2267602 (Version 1.333.285.0) ... (That KB number has been reference for the last 4 updates and didn't provide me any insight)

cmofat avatar Mar 13 '21 19:03 cmofat

I tried updating one of our Windows computers with the Cumulative Update from last week with a ton of bug fixes (kb5003214) and it still does not stay open. It opens for a fraction of a second and them immediately closes from warm up. A second device was updated with kb2267602 it also opens and closes as described previously.

raymonddurk avatar May 30 '21 00:05 raymonddurk

The Windows OS is not the problem, please see my post very similar: https://github.com/LedgerHQ/satstack/issues/46#issuecomment-906760248

BushMasterSix-LA avatar Aug 26 '21 21:08 BushMasterSix-LA

Really, huh, nice. I ran it with multiple nodes and multiple computers and Windows was the only commonality. Glad to see some actual work diagnosing it in that thread but this has been not fixed since February and counting in that thread and March in mine.

raymonddurk avatar Aug 31 '21 03:08 raymonddurk

This error occurs when SLL.exe was not terminated properly. To fix the problem it is best to restart the node.

The next time you want to close the sll.exe you should click on the terminal (black window) and press CTRL+C to end the process correctly. If you simply close the window with the windows "X", the problem will occur again the next time.

IAMAngryDuck avatar Nov 30 '21 15:11 IAMAngryDuck

@raymonddurk do you still have this issue?

adrienlacombe avatar May 04 '22 13:05 adrienlacombe

@adrienlacombe-ledger I took my node offline but I'll resync it and report back with the new v15 that was released today.

raymonddurk avatar May 20 '22 21:05 raymonddurk

Thank you!

adrienlacombe avatar May 22 '22 18:05 adrienlacombe