There seems to have been some change distributed. I've always done manual update installation. Somehow, CC got reset to auto-update. Sadly, Adobe has a long history of using their customers to trap code regressions. While performance has improved in recent years, there are still too many customer-found regressions. I've always taken the point of view to hold-off on any new release for at least a couple of weeks before deploying on my machines, hoping that the worst case regressions while have been found by that time.  I turned OFF auto-update in CC and will check to make sure it stays that way. ... View more

There seems to have been some change distributed. I've always done manual update installation. Somehow, CC got reset to auto-update. Sadly, Adobe has a long history of using their customers to trap code regressions. While performance has improved in recent years, there are still too many customer-found regressions. I've always taken the point of view to hold-off on any new release for at least a couple of weeks before deploying on my machines, hoping that the worst case regressions while have been found by that time.  I turned OFF auto-update in CC and will check to make sure it stays that way. ... View more

Quentin, you are the man! This has been bugging me for ages and yours is the ONLY correct solution. Shame on Adobe. ... View more

Today I was able to get support from Adobe and the problem did not recur on demand as anticipated.  I'd not wanted to open any images with Bridge > ACR > Photoshop in case of damage to the NEF files.  But after at least one reboot of the computer, it did not happen again.   So strange.  But fixed. ... View more