64-bit ifilttst.exe broken in Windows 7.0/7.1 SDKs

[Schaaf@discussions.microsoft.com Rainer Schaaf]

I'm posting here first because I'm not sure about how to report a bug in the
Windows SDK.

Starting with Windows SDK 7.0 the IFilter test program ifilttst.exe is
available as a 64-bit binary. The 64-bit ifilttst.exe provided in the Windows
7.0 and 7.1 SDKs has a bug that
it does not read property GUIDs and property names correctly from an INI
file. This
is reproducible easily with an INI file that comes with the Windows SDK.

Steps to reproduce on a 64-bit Windows platform:

1) Create a .txt file (e.g. "filtertest.txt") with a few lines of text

2) Run the 64-bit ifilttst.exe program for the .txt file with the INI file
that
also comes with the Windows SDK:

"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\x64\ifilttst.exe" /i
filtertest.txt /ini "C:\Program Files\Microsoft
SDKs\Windows\v7.1\Bin\x64\IFiltTst.ini" /l /d

3) Look at the generated file "filtertest.txt.log" and search for "Section
name":

...

1440.4796 : +TEST+INFO **** New configuration ****
1440.4796 : +TEST+INFO Section name : Test3
1440.4796 : +TEST+INFO grfFlags : 3
1440.4796 : +TEST+INFO cAttributes : 1
1440.4796 : +TEST+INFO Attribute 1:
1440.4796 : +TEST+INFO GUID : 00000000-0000-0000-0000-000000000000
1440.4796 : +TEST+INFO PROPID : 0x00000013
...
1440.4796 : +TEST+INFO **** New configuration ****
1440.4796 : +TEST+INFO Section name : Test6
1440.4796 : +TEST+INFO grfFlags : 0
1440.4796 : +TEST+INFO cAttributes : 1
1440.4796 : +TEST+INFO Attribute 1:
1440.4796 : +TEST+INFO GUID : 00000000-0000-0000-0000-000000000000
1440.4796 : +TEST+INFO LPWSTR : GENERATO

Note the GUIDs that are all zero, and the name of the Test6 property
"GENERATO", where the last character is missing. Compare that to the
corresponding entries in the IFiltTst.ini file:

[Test3]
Flags = IFILTER_INIT_CANON_PARAGRAPHS IFILTER_INIT_HARD_LINE_BREAKS
cAttributes = 1
aAttributes1 = b725f130-47ef-101a-a5f1-02608c9eebac 13

[Test6]
Flags =
cAttributes = 1
aAttributes1 = D1B5D3F0-C0B3-11CF-9A92-00A0C908DBF1 "GENERATOR"

How should such a problem be reported so it can be fixed in the Windows SDK?