Hi guys! I cannot manage to run nimble on Windows... and that's annoying because I cannot install dependencies.
Simply it does not show any output, it could be an antivirus related issue, but I guess I would receive some sort of notification (like I receive for nimgrep and other executables that are quarantined).
I have opened an issue (https://github.com/nim-lang/nimble/issues/1025), but after days I write here and I am sure I will get a quicker answer. I tried also to compile it from source, but still no output.
Do you have any idea about what could be or what to check and/or to fix this? Thanks
My System is Windows 10 Pro
Currently I tried with 3 version of the compiler package, with both cmd.exe and powershell I get no output from nimble.exe or nimble.exe --version or any other test I did:
Following version on nim which I tried to use nimble. As you can see nim works, the problem is only nimble.
Nim Compiler Version 1.4.4 [Windows: amd64] Compiled at 2021-02-23 Copyright (c) 2006-2020 by Andreas Rumpf >active boot switches: -d:release
Nim Compiler Version 1.6.6 [Windows: i386] Compiled at 2022-05-05 Copyright (c) 2006-2021 by Andreas Rumpf > active boot switches: -d:release
Nim Compiler Version 1.6.6 [Windows: amd64] Compiled at 2022-05-05 Copyright (c) 2006-2021 by Andreas Rumpf > active boot switches: -d:release
I also compiled nimble from source, but still no output.
Could be an antivirus issue, but would be strange because nimble was not quarantined and I have no messages from the antivirus.
Any suggestion about how to analyze better or how to perform more tests?
Thanks
You can try to install nim and nimble with choosenim.
https://github.com/dom96/choosenim
It downloads all binary files and handle PATH problems.
Your situation is very weird, could you give more details about the antivirus and the like that you use and sabotage you?
Unfortunately I cannot disable antivirus due to company restrictions.
But I have launched nimble inside a Visual Studio debugger to understand if I could have more clues about what was happening. The process terminates with:
Unhandled exception at 0x00007FFE305ABDA8 (InProcessClient64.dll) in nimble.exe: An invalid parameter was passed to a function that considers invalid parameters fatal.
Looking at the call stack I see:
InProcessClient64.dll!00007ffe305abda8() Unknown InProcessClient64.dll!00007ffe305abd3d() Unknown InProcessClient64.dll!00007ffe305abd59() Unknown InProcessClient64.dll!00007ffe305b2146() Unknown InProcessClient64.dll!00007ffe3054ef7b() Unknown InProcessClient64.dll!00007ffe305069df() Unknown InProcessClient64.dll!00007ffe30532d39() Unknown InProcessClient64.dll!00007ffe30506913() Unknown InProcessClient64.dll!00007ffe30506a98() Unknown InProcessClient64.dll!00007ffe30506881() Unknown nimble.exe!00007ff7dd5c6f05() Unknown nimble.exe!00007ff7dd60cc32() Unknown nimble.exe!00007ff7dd61b76e() Unknown nimble.exe!00007ff7dd61b789() Unknown nimble.exe!00007ff7dd626fad() Unknown nimble.exe!00007ff7dd581445() Unknown nimble.exe!00007ff7dd581146() Unknown kernel32.dll!00007ffe32637034() Unknown ntdll.dll!00007ffe331c2651() Unknown
So I searched for this InProcessClient64.dll and ... drums ... it is a process associated with SentinelOne Agent (my antivirus) that is apparently not simply blocking but crashing the process.
Here ends my investigation, I guess there is no fix for this kind of issue.
Anyway, If you think this is the case I am at disposition to go deeper with more tests.
It won't help you, @pp, but I can confirm I've had similar issues at work with SentinelOne and InProcessClient(32|64).dll a couple of years ago (Nim 1.2.x days). Nimble stopped working out of nowhere, as well as some Nim programs I'd written. The most obvious symptom was that "nimble -v" produced no output whatsoever, immediately returning to the command prompt. There would be errors in the Windows Event Viewer.
Luckily for me, I was able to convince the security guys to add exclusions for Nimble and a tool I'd written and they worked when SentinelOne was out of the picture. I've not seen this error in recent times so I'd hoped that SentinelOne has stepped up its game but it sounds like it's still troublesome to developers.
I was never able to pin down precisely what made SentinelOne break (I suspect it's not an intentional flag of software as a virus but simply SentinelOne being buggy - VirusTotal showed 0/74 matches for Nimble at the time) but I had a feeling that it was related to SSL: I had web sites that used Jester and SSL and they got flagged while other purely command line tools for CSV processing never triggered it.
I would first try to contact SentinelOne, though from what I've read they usually aren't very cooperative.
Perhaps the company you work for is willing to consider a hash based exclusion?