Microsoft Edge has come a long way since Microsoft introduced it nearly two years ago, and while the browser hasn’t caught up with Firefox or Chrome in terms of extensions or market share, MS has been adding features and capabilities in its major OS releases.
As BleepingComputer reports, however, Edge has a major printer bug that could cause significant headaches for anyone who uses the browser. The problem is compounded by the fact that Edge is set to be the default PDF handler in Windows 10. Microsoft has already confirmed the bug exists, and its recommendation for how to deal with the problem at this point is rather amusing. After acknowledging that the printed content looked different from the displayed PDF, Microsoft notes:
“Possible workaround: Copy the document after printing using a Xerox copier.”
Here are two example images that show the issue. The first image is the original image as saved to PDF, the second image is what Edge actually printed. Both images can be clicked on to expand them into a new window.
According to Microsoft, the formal name for this bug is “Edge displays “123456” in PDF but prints “114447.” But that doesn’t really seem to address the fact that there’s physical substitutions for letters as well. There’s also no explanation for why some fields are changed. In the top row, the second and third blocks should read “Vendor 1” and “Block 1,” but instead read “”Classifi” and “Tool” with some additional letters beneath those headings that I honestly can’t identify.
Scanned documents are not affected, but native and interactive PDFs are subject to the error. For now, users should look elsewhere for a PDF solution.
This is, I suspect, another example of how Microsoft’s new test procedures for Windows 10 create an environment where certain bugs can slip through the cracks. MS recommends testing the Fast Ring on hardware that isn’t your daily driver. For many people, this means a VM, but how many people try to test print support when working in a virtual machine?
For now, we’d recommend Foxit, Adobe, or a freeware PDF app of your own choice to print documents. Any documents printed with Edge that weren’t just images should be carefully checked to ensure they weren’t altered in the process. BleepingComputer reports that the bug has been reproduced on Edge running both EdgeHTML engine 14.14393 and EdgeHTML 15.15063. Other users have reported no issues, so your mileage may vary.
Now read: Windows 10: The best hidden features, tips, and tricks