Who can explain this : error 16 only under certain circumstances ?

  • 1
  • Problem
  • Updated 1 year ago
  • (Edited)
Hi,

Until I upgraded to Windows 10 Creators, I had to run both Photoshop and Lightroom in administrator mode, otherwise I always got the infamous error 16. I never could fix that. After the upgrade, both programs appeared to behave normally, although I had unchecked the "Run as an administrator" option in the Properties of each .exe file.

Then, in Lightroom,  I tried to "Edit in..." Photoshop from Lightroom. And PS emitted the error 16 again. But if I launch PS or LR directly, there's no error.

Now to the fun part : If I want to get rid of this error message, I need to set the "Run as an administrator" option for either Photoshop OR Lightroom. Not necessarily for both. Once one of these programs has its "Run as an administrator" option checked, there's no longer any problem.

Now if someone from the development staff could explain this oddity, I would appreciate (you can get technical, I'm a former developer and system engineer). I have multiple times checked all the permissions that are described in the various documents explaining how to fix this annoying and boring "configuration error - error 16" bug. To no avail.

I'm running Windows 10 Creators, PS and LR CC latest version. My TMP and TEMP variables point to a non system drive.

I have monitored the photoshop.exe process and I observed a problem when photoshop.exe tries to access C:\Program Files (x86)\Common Files\Adobe\SLCache\QUNDRVNTX0NIRUNL.slc in read/write mode. Just before this event, I can see that the file is accessed in read mode multiple times without any problem. See log file here (look for "access denied") :

https://www.dropbox.com/s/x9h7zkhojyn2vub/error16.log?dl=0

I have checked the permissions for this folder and for the file itself : all users including Everyone have full control for this folder and for this file.
Photo of Patrick Philippot

Patrick Philippot

  • 367 Posts
  • 67 Reply Likes
  • frustrated

Posted 1 year ago

  • 1
Photo of Patrick Philippot

Patrick Philippot

  • 367 Posts
  • 67 Reply Likes
Now even more fun about this issue...

Giving some thought to what could be different when I launch PS from Lightroom and when I launch it directly, I came to the only possible conclusion : when launched from LR, the path to the file to be handled in PS is passed along as an argument on the command line (unless LR is using OLE Automation) and the photoshop.exe process is launched from another process, not directly from Explorer.

So I tried to run photoshop.exe from the command line, passing it the path to a TIFF file as an argument (between quotes), and guess what ? Error 16.

Then I removed the filepath argument and tried again to launch photoshop.exe  from the command line : error 16 again.

Then I opened a new command line window (cmd.exe) but I ran cmd.exe as an administrator and tried again : no error.

I then checked what happened when launching PS from the Start menu or from the icon pinned to the taskbar (not in administrator mode) : no problem.

So the same command (photoshop.Exe) can fail or not depending on the way it is run (from the Start menu, from its desktop or taskbar icon or from the command line) ? Never seen this.

What on earth is doing this code ?
Photo of Todd Shaner

Todd Shaner, Champion

  • 1091 Posts
  • 352 Reply Likes
See if this helps. Try setting the permissions for both the Adobe PCD and SLStore folders to Read and Write:

https://helpx.adobe.com/creative-cloud/kb/configuration-error.html
Photo of Patrick Philippot

Patrick Philippot

  • 367 Posts
  • 67 Reply Likes
I have already tried to setup 2 clean accounts, one admin and one standard user. This doesn't change anything.

Also, as mentioned in my OP, I can see, when monitoring the photoshop.exe process, that it has problems accessing a given file in SLCache in write mode. However, this shouldn't happen since the current user has Full Control on this file and folder.

I'm beginning to suspect that photoshop.exe is switching to some special account during these operations (i.e. that it is using the impersonation technique in developer parlance). Otherwise, I can't explain why it is getting an ACCESS DENIED when trying to access this file.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1091 Posts
  • 352 Reply Likes
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 367 Posts
  • 67 Reply Likes
I already did that :-( .

Now I'm back to an old issue that I have already reported last year :

https://feedback.photoshop.com/photoshop_family/topics/error-16-in-ps-related-to-wia-device-manager?...
Photo of Todd Shaner

Todd Shaner, Champion

  • 1091 Posts
  • 352 Reply Likes
The only thing left is to uninstall ALL Adobe apps including the Creative Cloud app and run the CC Cleaner as outlined here.

https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

If that doesn't work you may need to reformat the drive and reinstall everything. IMHO this is a MS Windows 10 update issue. The last two major updates (Anniversary and Creator's) had numerous bugs causing many issues with Adobe and other developers applications. You can't really blame that on Adobe as it's still unclear why some people like yourself have issues with these Windows 10 updates.....and others don't. This is the primary reason why I am still on Windows 7. I've had exactly ZERO (0) issues with ANY apps due to Windows updates. With Microsoft now focused on phones I don't expect things to get any better for desktop users. There have been similar issues with OS X updates, but Apple seems to be better about rolling out bug fixes.

http://www.computerworld.com/article/3107238/microsoft-windows/more-win-10-anniversary-update-problems-and-what-to-do-about-them.html

https://www.theregister.co.uk/2017/04/26/stop_downloading_win10_creators_update/
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 367 Posts
  • 67 Reply Likes
Todd,

Please note that the problem didn't come with the Windows 10 Creators update. I just thought the Creators update had fixed the issue but this was not the case. I always had to run PS CC as an administrator, even under Win7. The Anniversary update was never installed on this system.

As mentioned above, I was fooled by the fact that the start menu and taskbar shortcuts for PS had their "run as an administrator" option enabled. So even if photoshop.exe didn't have this option checked, the program was run as an administrator anyway if launched from the Start menu or the taskbar or the desktop icon. This is just when I launched PS from LR that I discovered that the problem was still there.

Formatting my disk and re-installing everything would be overkill and could take at least a week. Not an option. Removing all the Adobe stuff was already done last year when I had the same problem and when I was unable to update Adobe CC Desktop.

I can live with PS running as an administrator. Just, as a former developer, I don't like situations where something is wrong on my system and I don't know what and why.

Lightroom runs normally on my system without having to launch it as an administrator. Since it also accesses the SLCache and SLStore folders, it's probably not the problem. I guess I'm on the right track with this WIA Device Manager anomaly but I'm unable to fix it.

Thanks anyway for your time.