Saturday , 22 September 2018
Home >> O >> Operating Systems >> Does moving your pen drag the canvas? Welcome to yet another bug in Win10 1709 patches

Does moving your pen drag the canvas? Welcome to yet another bug in Win10 1709 patches

A Windows Ink engineer has confirmed that there’s a bug in the third Win10 1709 March Cumulative Update, KB 4089848, that breaks common pen movements in Photoshop, Lightroom and CS Paint. Looks as if the same problem bedevils this month’s 1709 Cumulative Update, KB 4093112, as well. Microsoft, it seems, decided to break pen behavior in Win10 1709 without any notification or explanation.

Early this month, DavideV, on the Microsoft Answers forum, posted a rather strange observation:

I’m on a Surface Pro 4 and Photoshop CC used to work just fine for me but recently I’m experiencing the following problem: often in Brush mode the pen moves the canvas around instead of drawing. This is almost always the case when starting a vertical stroke, less so for horizontal ones.

This happens:

  • both with and without Photoshop gestures enabled
  • with both the new and old Surface pen
  • with and without hardware acceleration enabled in ps (note: without hardware acceleration, moving the canvas around is comically slow).

Please note that my Surface pen is working normally other than in this specific instance. All other drawing or writing applications work as usual. I therefore suspect this is a Photoshop specific problem, but I’m posting here just in case anyone else has seen the problem and/or knows of any obscure Windows Setting that could potentially affect this.

Ends up that DavideV hit a bug in the March 22 Cumulative Update to Win10 Fall Creators Update, version 1709. You’ll be forgiven if you’ve lost track of all the 1709 cumulative updates, but KB 4089848 is the third cumulative update for 1709 released in March. Microsoft hasn’t yet confirmed the bug, but it now looks as if the same bug also appears in this month’s (first) Win10 1709 cumulative update, KB 4093112.

On Wednesday, Microsoft MVP and community moderator Barb Bowman posted a detailed explanation of the bug, simply describing it thusly:

close
==[ Click Here 1X ] [ Close ]==