The names involved were short, so it should not have triggered that.

On 3/29/2012 1:01 AM, Mehrdad wrote:
> Is it really a bug, or is it this feature (NTFS tunneling)?
>
> http://blogs.msdn.com/b/oldnewthing/archive/2005/07/15/439261.aspx
>
> "Walter Bright" wrote in message news:jkmceb$r5f$1@digitalmars.com...
> On 3/24/2012 2:55 PM, Andrej Mitrovic wrote:
>> I can't reproduce this on Win7 x86. I've tried numerous times but it
>> never failed. It seems it's x64-related (or just a Win7 x64 bug).
>
> I submitted a bug report to Microsoft.

On 3/28/2012 12:10 AM, Don wrote:
> On 27.03.2012 00:42, Andrej Mitrovic wrote:
>> On 3/26/12, Walter Bright<newshound2@digitalmars.com> wrote:
>>> On 3/25/2012 2:50 PM, Kagamin wrote:
>>>> Microsoft has antivirus bundled with windows. Go to security center and
>>>> see
>>>> whether Windows Defender is working.
>>>
>>> Well, I'll be hornswoggled. That did the trick!
>>
>> I really don't think that's the bottom issue. I've had defender off,
>> and I can still reproduce the issue but it seems to happen in random
>> phases. Several hundred runs it's ok, and then it's not ok.
>
> Can't reproduce. I've run it more than a thousand times with no failures.
> Just looks like a bug in Windows Defender.

Also, it only happened with .exe files, another arrow that points at Defender, because Defender only mucks with .exe's.

This behavior of linker caused by a protection suit with sandbox or similiar technology. Affected systems are win xp, win 7. With a standard antivirus is all ok.