Hi! I’d appreciate some help with a few installation issues I’ve encountered, especially with the newer version on Windows. I just post it also in github Q&A, put it also here: Windows When installing Sling via Scoop (as recommended), it seems that something in the installation process corrupts or interferes with DLL files related to MSYS2. This happened to me on two different machines. When running a simple Sling command, I get the following error: sling.exe – System Error The code execution cannot proceed because libgcc_s_seh-1.dll was not found. Reinstalling the program may fix this problem. On one machine, I managed to find a workaround, but it doesn’t address the root cause—it was just a temporary patch to make it work. I’d appreciate your thoughts on: Whether this is a known issue with the newer Windows version How to properly fix the problem on existing installations Linux On a Linux machine, I installed Sling as recommended and it works correctly. However, the sling command is not recognized unless I reference it using the full path (/path/to/slingexe/sling command). This feels like a classic PATH issue (although I’m still having trouble resolving), but on another Linux machine the behavior was different. So I wanted to clarify the expected behavior: Should Sling automatically be added to PATH? Do I need to manually add the Sling binary to PATH? Or is there another recommended approach? Python If I install Sling using pip install sling, will that installation also provide a fully functional sling CLI executable that works the same as the standalone native CLI? Or is it necessary to install the standalone Sling CLI binary (e.g., via Scoop / brew / curl) in addition to the Python package for full CLI functionality? I would appreciate any tips and thoughts, thanks!

hey @dek-inf , responded on https://github.com/slingdata-io/sling-cli/discussions/692