FWIW the open source C# (which you can reasonably assume is mostly Windows) of this ocean of windows boxes as measured by github is marginally higher than OCaml.
So they know that “currency” too.
But if your initial user experience is not up to a certain level I wouldn’t expect hearing from them.
The OCaml environment is/was mostly unfriendly towards Windows. Expecting Windows devs to jump in and contribute to a project that’s basically Unix emulation, thus unfamiliar, is a bit much.
I don’t think Windows devs are to blame for the current state of OCaml on Windows.
If anything, the current state of OCaml on Windows is what’s preventing Windows devs to contribute.
I don’t think playing the blame game is helpful here (in either direction). In open source projects complicated cross-platform support never just works magically, there are always errors and mountains of work going on behind the scenes to fix them. This is same for Node.js, Python, Racket, and other platforms. What you are seeing in OCaml is just a small community without deep pockets, but willing to work slowly towards improving the situation.
Again, there’s no magical solution here, just perseverance. It’s not for everyone, but it’s also not gatekeeping or elitism, sorry.
The more interesting thing is that the cousin of both C# and OCaml, F# , which started on Windows, seems to offer a great experience on Linux and MacOS.
If one is looking for a complete cross platform OCaml right now, F# + dotnet works much better.
Indeed. Anedoctically I was in contact last year with someone who had prototyped an app in F# and was considering perhaps moving to OCaml. Given the setting in which they were operating (PLM systems), I prudently indicated that there would be quite a few tradeoffs to consider before doing so :–)
My Road to Erlang mention, referring to the state of things in 1998:
There was also the worry that Windows seemed to be a “barely there” platform in the eyes of all three language maintainers. The OCaml interpreter had a beautiful interactive shell under MacOS, but the Windows version was–or should have been–a great embarrassment to everyone involved.
However isn’t Windows an embarrassment in itself 
?
When I write this (with the help of an untrusty LLM) I don’t really feel well :–)
:: Update %PATH% in registry
reg load HKLM\Offline %MOUNT%\Windows\System32\config\SYSTEM
set key="HKLM\Offline\ControlSet001\Control\Session Manager\Environment"
for /f "tokens=2*" %%A in ('reg query %key% /v Path') do set value=%%B
:: Avoid %SystemRoot% expansion
setlocal enabledelayedexpansion
set value=!value!;%%systemroot%%\System32\powershell
reg add !key! /v Path /t REG_EXPAND_SZ /d "!value!" /f
endlocal
I’ve spent too much time trying to solve never ending troubles with Win/WSL/docker, etc.
I’m now using (again) only a well known linux/debian OCaml environment both on bare debian PCs and on Win laptop via VMware workstationPro that offers a fluid integration (simple and reliable shortcuts for switching between Win and a linus VM).
So I can focus on… writing programs in OCaml.
Mainly without dune, except when libraries or programs are delivered with a thoroughly tested dune files set that just requires ‘dune build’.
I stay open to using OCaml in Win. In order to avoid installing VMware wokstation on many PC.
But I’ll try it when fully tested&certified installation instructions will be delivered by “fullstack experts in Windows/docker or WSL/OCaml and main editors (VScode, Emacs, vim…)”.