Oops! Bug is clearly reproduced on Windows Server 2003 R2 SP2 with "plain" ruby-1.9.3-p448 (just extracted from http://dl.bintray.com/oneclick/rubyinstaller/ruby-1.9.3-p448-i386-mingw32.7z?direct) c:\ruby-1.9.3-p448-i386-mingw32\bin>rub...zapped (Alexey Shumkin)