Skip to main content
Participant
March 10, 2021
Answered

P: Pen Tool Not Working as it should

  • March 10, 2021
  • 338 replies
  • 23210 views

I have just updated Photoshop to v22.3 (10 March 2021). When I try to use the Pen Tool it puts the nodes in but doesn't create a linking line. I have closed everything and re-started my PC but the error still there. I've been trying to find a way to report this to Adobe but this is the only feedback area I can find. I have been using Photoshop for over 20 years and using the Pen Tool all that time. I need to complete a job but I'm now stuck as I need this tool.

 

Can I uninstall this update?

 

Anyone else having this problem?

 

Do Adobe monitor this feed?

Correct answer nikunj.m

Hi,

 

We're happy to announce the release of Photoshop 22.4 which should include the fix for this issue. To update Photoshop to the latest version, you can check: https://helpx.adobe.com/creative-cloud/help/creative-cloud-updates.html

 

For information on other issues fixed with this update, please check: https://helpx.adobe.com/photoshop/kb/fixed-issues.html

 

Regards,

Nikunj

338 replies

Inspiring
May 1, 2021

The workaround is to create a work path, and leave that work path in the path list. You can then create new paths with +, and name them what you like and work on them normally.

Inspiring
May 1, 2021

The workaround is to create a work path, and leave that work path in the path list. You can then create new paths with +, and name them what you like and work on them normally.

Inspiring
May 1, 2021

What seemed to be happening with me was that if I established a path first, the pen tool only created a series of points and didn't draw the path between. Just clicking on the pen tool seemed to work as usual. 

Inspiring
May 1, 2021

I was having the same problem today when establishing a path first, then making a selection. Just selecting the pen tool and clicking from point to point seemed to work as far as creating a functional path I could select or make into a clipping path, but if I created a path first, the tool didn't connect the points and just made a series of them so the application had no idea what to "select" when going to "select path." Definitely a bug that needs working out. I've been using PhotoShop since the days it was in "beta" so I knew something wasn't right!

Participating Frequently
April 30, 2021

And yet here we are nearly 2 months later and nothing has changed. Acknowledgement is great I suppose, but a fix is what we're all after.

Bottom line: clearly some additional motivation is needed. Hopefully more vocal and unhappy paying customers chiming in provides some additional incentive to get a move on, but who knows with Adobe anymore.

Known Participant
April 30, 2021

Still not working
Shame on you Adobe!!

Inspiring
April 29, 2021

If you look at the title heading of the post you can see that it is marked "Acknowledged".

zebra7228140
Inspiring
April 29, 2021

Same here to all the above.  This may be the worst and most problematic release of photoshop ever. No matter the fixes, there is always more misbehavior. I realize how difficult programing this software can be for so many operating systems, video cards etc., but why release such a problematic version? Honestly, I am sure most of us would be fine with the same version for two years or more before a new and stable release would come along (mark the word stable - stable is FAR more important to me than anything newly added)...Running a Mac with Big Sur using PS 22.3.1 and yet one more disappointment. (from saving error, to lagging radial tools in ACR to lagging brushes and now non-connecting path nodes - never mind the poor memory management aka leaks). Please fix ASAP please? And yes - I have moved back to the previous Photoshop (and Bridge) release to work on my projects. I am happy to get back with the Beta team to help this get worked out- just let me know). 

Participating Frequently
April 29, 2021

You know, when I deliver a final product with major flaws that a client notices, I do this weird thing where I either a) fix it immediately, or b) give them at least some of their money back.

I get that there's a workaround, but knowing a problem exists and actively choosing not to solve it with the next update is the issue here, not whether there's a band-aid solution during the intervening months. My post, this one, and all those like it are here to point out to Adobe that the problem persists and that we notice.

Participating Frequently
April 29, 2021

Yeah, I don't pay a subscription service for bugs, I pay (in theory) for functional software, or at least timely fixes to major issues (and no, 1-2 months+ isn't a timely fix, not that this has actually been resolved anyway...).

The point of bringing it up again in spite of any finger-in-the-dam solutions is simply to make the point to Adobe and their devs that this isn't acceptable and is precisely the sort of thing that makes me contemplate switching -- something I have zero problem doing when there's a better option that suits my needs available, as was/is the case with Capture One vs. Lightroom.

In any case @jq1969 hits the nail on the on head: wasting my working time with searching for workarounds and/or installing an update only to then re-installing multiple versions of Photoshop just to find the one that doesn't break crucial features I rely on costs me money. That's really all there is to it; I'm a freelancer and this is business, and I sincerely wish it wasn't just business-as-usual for Adobe to deliver software that's this flawed (and I'm thankful the competition is catching up, otherwise they'd continue to have zero incentive to improve).