I am a frequent user of the Vim editor on Linux and now I want to use it on Windows.
I downloaded Vim for Windows, which happens to be gVim. Several features of Vim doesn't work in gVim 7.4 like visual block, rx command, and several other key combinations.
I want the same/original Vim from Linux to be used on Windows. Is that version available for Windows too? Or, can I use settings similar to the Unix format?
When I have to work on Windows (which is more often than I would like), I use Cygwin to get a terminal a little less crappy than the original Windows command line. Cygwin provides an environment which tries to be close to a Bash console with standard Linux commands, and of course it is far from being flawless.
See the project page of Cygwin. During the installation you'll end on a window allowing you to choose which packages you want to install. The search bar allows to look for packages to install, among other useful stuff (like git, tmux, curl, wget, etc.) you can type vim and select packages like vim, vim-common, vim-doc, gvim. This will install a Vim editor pretty close to what you're used to on Linux.
Once everything is installed (which can sometimes be a little long) you'll be able to start Cygwin which will show a terminal, and you'll be able to start Vim as usual and use your Linux .vimrc and your usual plugin manager. The main drawback is the compatibility of colors which often needs to be tweaked and still look crappy.
Note that I use Cygwin out of habit, but other solutions (like cmder for example) exist. None of them are flawless, so you might want to try several and find your favorite.
Also note that mintty is a good way to make Cygwin a little less crappy.
C:\Program Files\Git\usr\bin or similar to your path.
As of Windows 10 Anniversary Update, you can use the Bash on Ubuntu terminal to run a Linux subsystem where you can apt install anything you're used to inside Ubuntu. Your Windows file system is mounted so you can use Vim inside the shell to edit your files.
As Roflo and Rich mentioned in their comment here and here, your problem with being unable to use visual block (I'm not sure what rx command is) is because the system-wide vimrc ($VIM\_vimrc) sources $VIMRUNTIME\mswin.vim which defines Windows-style mappings like Ctrl+v for paste, Ctrl+c for copy, Ctrl+x for cut.
The easiest way to get around this is to create a _vimrc files in your home directory (Note that Windows version of vim uses _vimrc instead of .vimrc). As you can see in :h vimrc, vim looks for vimrc in several locations and only uses the first one it finds while ignoring the rest. The one in the home directory is always searched/used first.
Minimal steps:
:e ~/_vimrc:wA further fairly small but no-less major update happened to Windows 10 for the 1803 build. They added 24-bit support for the console (cmd/powershell prompt). In Vim 8.1 (https://www.vim.org//download.php/#pc) they added support for termguicolors which means you can get the full 24-bit colour support inside the Vim console. I recently posted an answer of getting the colour support working.
But what it means is that there is pretty much full support for running Vim in the DOS prompt - so you don't need to install any Linux subsystem or any other dependencies beyond Vim itself to get pure Vim working. I find it still somewhat slow, but it's great to see the progress.
The fonts and colours render wonderfully inside Vim (Click on this screenshot to see it properly):
Things that work in Vim console (in Windows 10 build 1803+):
colortheme (e.g. vim-solarized8, tender)vimdiffThings that don't work / problems:
_vimrcfile for a line saying something likesource $VIMRUNTIME/mswin.vim. That file enables lots of config stuff to be MSWindows-friendly (including many mappings).ctrl-vkey-combo with a paste mapping. It's possible (likely?) that your other issues with Windows Vim stem from the same problem, although you don't mention what they all are so it's hard to say for certain.