Serious command processor bug

This is definitely the weirdest bug I've seen in 12 years! We lost a full day just tracking down this issue.


We found that cmd.exe silently drops the 8191st char of a long enough command. Furthermore, this bug occurs in Windows 7 clients as well.


This simple batch echoes a sequence of zeroes and ones, clearly exposing this bug:

@echo 01010101010101010101
@pause > nul

Since I'm unable to post links or images until my account gets verified, these should suffice

Batch file: pastebin.com/7747wNJu

Screenshot: i.imgur.com/17EmcSk.png


Best regards,

George Weinburg

May 24th, 2015 8:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics