Microsoft releases Epson dot matrix fix for Win10 1703, KB 4051033, and teases at a fix for 1709, KB 4051963

Topic

New Reply

Win10 1703 has a new, lengthy, cumulative update, November 22, 2017—KB4055254 (OS Build 15063.729), which mentions fixing the Epson dot matrix printer
[See the full post at: Microsoft releases Epson dot matrix fix for Win10 1703, KB 4051033, and teases at a fix for 1709, KB 4051963]

Reply | Quote

Replies

Don’t know where to post this, but just had someone on Home version updated to 1709. Unlike other feature upgrades, this one didn’t prevent the Brother printer from printing and thus needing a reinstall.

However, the person changed his router so used the printer on wifi instead of Ethernet like before. Since the setup was a static IP for stability, of course it stopped working so he called me. At first, I thought it was the same issue as usual, so I uninstalled the Brother driver, but when I wanted to reinstall it, oh horror, none of their setup programs worked on 1709 no more. I double-click, it asks for admin approval, fine I click then nothing.

Since this computer had EMET before (now uninstalled automatically by 1709 to be replaced by Windows Defender Exploit Guard), I thought maybe Windows didn’t transition well from EMET to WDEG, so I go in WDEG, set everything to disable, try to run the software again after restarting the computer. Doesn’t work. Set everything back to default. I thought I would have to reinstall the whole computer because I thought something was probably irremediably broken. Then I had the idea to use the troubleshooting compatibility option and it told me to use Windows 8 compatibility mode, which I did and the installer ran fine, maybe bypassing the latest security improvements of FCU, I don’t know. What I know is on previous feature upgrades, the unupdated driver from Brother would reinstall just fine and it would fix the printer is broken after feature update issue.

After seeing WDEG, I can confirm what I suspected about it vs EMET. It is certainly not a direct replacement. WDEG seems to only target the system-wide settings of EMET from the GUI while EMET had lots of other protections on a per-application basis. Maybe they are integrated somewhere system-wide, but I doubt it. I am not sure how they did WDEG, but from the quick glance I had at it, they seemed to have replaced a fine product with a subset of it integrated on Windows 10. And with the latest “by design” bug, it seems all they wanted to do is brag about new security for newer apps while making sure compatibility is not broken by not really activating the more secure options on old apps (which don’t really benefit that much from it to be fair in the real world, probably).

I still don’t know if updating from 1703 with EMET to 1709 messed up something related, but I would be cautious and suggest to people running EMET to restore the default system-wide settings and uninstall EMET before updating to 1709, just in case. Please note uninstalling EMET without resetting the default system-wide settings doesn’t restore them to defaults. EMET is just a GUI to trigger those settings, so uninstalling it is like removing the control panel for those settings without actually changing the settings.

 

Reply | Quote

Does anybody have a Brother printer and tried reinstalling the driver on 1709? I am wondering if it is just an issue with 1709 or the fact it has been upgraded and maybe didn’t properly update and adjust some security policies from EMET when it uninstalled it.

Reply | Quote

Now KB405963 is no longer “place-held” on the Windows 10 update history page

Reply | Quote

edit: KB4051963

Reply | Quote