Windows is more oriented UI usage rather than command-line usage, so by default we do not have any batch file invoked by default (as we can have on nix platform).
Based on that, it appears to be logical to set MODULESHOME as environment if we want to be able to use moduleinit.cmd or module.cmd batch files.
Until batch file are used, it is very simple to automatically define/update appropriate environment variables when moduleinit.cmd is invoked to ensure an easy usage of modules even on Windows platform