Probably is an issue, i install Crystal use scoop which following the official guides, after i uninstall Crystal use scoop, but crimson still warn me crystal was not uninstalled.(check following screenshot)
And, then, install crystal use crimson failed too.
But it install sucessful if run only crimson install without version.
I try this on Win10 in VirtualBox, this is a relatively clean system, only install Crystal use scoop several times.
That’s a system issue: it finds Crystal 1.8.1 before it reaches Crimson’s environment paths. Crimson wont remove existing Crystal versions on your system, it will only warn you about them.
I don’t know about CMD but with PowerShell you can do (Get-Command crystal).Source | Remove-Item then run crimson setup just to make sure everything is good.
Have you tried restarting your terminal? I know that symlinks don’t always play well with CMD/PowerShell. If you have refreshenv installed I’d advise giving that a try too.
Application cannot be initialized normally (0xc0000142). Please click OK and close the application.
It may be a dependency issue for Crystal 1.14.0, because 1.13.2 work well, but what ever i install Crystal 1.14.0 use scoop or crimson, still get same issue.
I have no idea what happen, it’s seem like 1.13.2 not work too. I swear this is almost an unused Windows 10 system in VirtualBox, except for previously installing and configuring Scoop and Crystal, didn’t change nothing.
I even download official installer and reinstall it again, still not work.
It might be an issue with missing dependencies about the vs_cpp_build_tools. You can download Crystal directly from Github, check if it works, and compare to confirm this.
I faced a similar issue with Crimson earlier this year: Crystal was unable to find the DLLs (0xC0000135). Its for this reason that Crimson forces you to run crimson setup before you can do anything else. However, 0xc0000142 indicates it’s finding the DLLs but it can’t load them for whatever reason.
There was a library change between 1.13.3 and 1.14.0, Crystal is now using iconv-2.dll instead of libiconv.dll. You can check if Crimson has properly linked it by running dir %LOCALAPPDATA%\Programs\Crystal, you should see iconv-2.dll is symlinked to the absolute path in the Crimson path.
Next up would be checking that the executable is properly linked to the DLL. You can do this by:
Opening the Visual Studio Developer Command Prompt (typing “developer” in the start menu should bring it up)
Assuming that’s all correct, we’ll have to go a bit deeper. Press Windows + R, type eventvwr and enter. We shouldn’t need to navigate it just yet. Keep it running in the background and run crystal.exe in command prompt. That should give you a direct error message window.
On a slightly unrelated note, I compared the properties between 1.13.3, 1.14.0 from Crimson and 1.14.0 from Scoop, I don’t know if there’s anything meaningful to deduce from this: