Skip to main content
Participant
August 25, 2018
Answered

Error 156 when updating Lightroom Classic CC on Windows 10

  • August 25, 2018
  • 2 replies
  • 1045 views

i get an installation failed for both products.  I have uninstalled and tried to reinstall but when it gets to 91% it just hangs up.  Below is the error information.  Can someone please tell me what is going on.  i have a Microsoft surface book 2.

Exit Code: 156

-------------------------------------- Summary --------------------------------------

- 2 fatal error(s), 0 error(s), 1 warnings(s)

FATAL: Error (Code = 156) executing in command 'CreateSymlinkCommand' for package: 'AdobeLightroomCC-mul', version:1.5.0.201808071548

FATAL: Error occurred in install of package (Name: AdobeLightroomCC-mul Version: 1.5.0.201808071548). Error code: '156'

WARN: Unable to create symlink at "C:\Users\patek\Desktop\Lightroom CC.lnk"

-------------------------------------------------------------------------------------

This topic has been closed for replies.
Correct answer Treehugger81

I turned off the ransom ware portion of the windows defender updated/installed the apps then turned it back on again.  Rudimentary but it worked.  There is a way to give certain apps access but I am lazy and haven't figured it out yet. 

2 replies

MikeMac666
Participant
August 26, 2018

Can you explain which protected folders you had to modify please..

kglad
Community Expert
Community Expert
August 26, 2018

this is the key folder:

C:\Users\<your user name>\Desktop\

if you that's in your warning message.

Participant
August 27, 2018

the ransom ware portion of Window Defender will not let apps change anything in the desktop folder.  if you can tell me how to add apps to my trusted list in window defender would be helpful.

kglad
Community Expert
Community Expert
August 25, 2018

what os do you have and did you install the cc desktop app from here https://creative.adobe.com/products/creative-cloud and use it to install your adobe subscription and trial programs?

Participant
August 26, 2018

it was a problem with permission on my windows based machine. i modified the protected folders and it worked.