We're using Extend 9.2 but have also tested with Extend 10.0, on Windows 10. We have a line in the config file set as PRINTER -Q DUMMY - in previous versions of Windows, we open file with name "PRINTER" for output, and print a report to it. The -Q line pointing to a non-existent print queue triggered Windows to pop a GUI box which allowed the user to select the printer they wish to use for the report.
On Windows 10, this no longer works. Rather, opening a file with the name "PRINTER" causes the runtime to lock up.
This had been a problem when Windows 7 was released, and was reported as incident 2513602, and was fixed in version 9.1 of the runtime, and I believe also released as ECN 3824 for version 8.0.
Is there a fix to make this work on Windows 10, or must we modify all the old legacy reports to make use of WIN$PRINTER?