Inspiring

Answered

Photoshop - Wacom - Latest Update Bug

Forum|Forum|7 years ago
April 11, 2018
44 replies
120765 views

So for me the program is unusable now.

Whenever I use any tool, instead of the tool doing what it should be doing it acts like the hand tool and moves around the canvas.

Things work fine when using a mouse, but without the ability to use the pressure sensitivity of my tablet I cannot accomplish my work.

This needs to be fixed now.

For now I'm going to have to use clip studio to do my work until the issue is resolved.

This topic has been closed for replies.

Correct answer davescm

I have Photoshop CC 2017, and I don't see this folder about photoshop setting, how do I fix this error?

Amanda

There should be no need for any workaround now that Microsoft have issued a further update to fix the issued caused in their earlier release. See here for details:

Cannot paint with stylus when zoomed in on image | Windows 10

Dave

Show previous replies

N

nicolel14332099

Participant

Will this work for a Surface 3?

N

nicolel14332099

Participant

I am having this problem too, but i am on a surface pro 3.... will this work for me?

T

terencec53414113

Participant

Wow thanks a lot, this worked like magic.

now, adobe, do you think it's kind of not user-friendly if the user needs to do a workaround?

davescm

Community Expert

Terence - the issue was caused by a deliberate change made by Microsoft in their Windows Ink APIs. It was not Adobe.

See here :

https://support.microsoft.com/en-us/help/4093112/windows-10-update-kb4093112

Dave

camik46434445

Participant

Okay so, I tried this. I have a Surface 3, and use Photoshop CC18. This didn’t fix the canvas problem, and I now don’t have pen pressure either. Fix?

P

PaulJManoogianJr

Participant

So, I tried everything that's here, and this is what I found worked on my Windows Surface Studio:

1. Run the Windows Registry edit (Must run command prompt with elevated permissions):
"reg add HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Pen /v LegacyPenInteractionModel /t REG_DWORD /d 1 /f"

Anytime you want to switch legacy applications back to the behavior introduced in the Windows 10 Fall Creator’s Update, execute this:
“reg add HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Pen /v LegacyPenInteractionModel /t REG_DWORD /d 0 /f”

Read more here: https://www.reddit.com/r/Windowsink/comments/8508fi/controlling_pen_behavior_in_windows_10/

2. DO NOT create the PSUserConfig.txt file. This actually REMOVED the ability to control pen pressure, and it slowed down the pen.

I will be curious to see if others using Windows Surface devices with Windows Pens have similar or different issues.

Good Luck, all!

Z

Zansky

Participating Frequently

Paul I removed the PSUserCOnfig and lost the brush pressure

P

PaulJManoogianJr

Participant

Interesting... On my system, when I had the file there it made me lose the pen pressure. But, the steps I have above are very specifically for my Windows Surface Studio system. If you're using Wacom or Huion or something like that, it might not work. Especially since I see that many folks who have those devices (and I used to) finally get the pressure support back when they add it.

Microsoft did a huge disservice to folks by changing the behavior of Windows Ink. It should have simply been a setting you could switch in terms of behavior, instead they made it a global change that cripples normal functionality that people are used to using.

M

meruba

Participant

I'm having the same problem! I can't draw anything like this! and it's been like this since the update. I tried the above but it doesn't work. When this issue is gonna be solved ?

Z

Zansky

Participating Frequently

I did all these commands to solve but after this is happen a brush lag. 15 -10 seconds to have any response when drawing!
If I delete the PSUserConfig.txt works fast but withou any pressure.
What is happening?!

P

pse2000

Participant

Thank you Thank you!

C

christopherl15086463

Participant

I just deleted the windows update, and no problem.