Gaussian Blur filter caused corruption in my Photoshop CC file.

  • 1
  • Problem
  • Updated 3 years ago
Was working with a file about 30 minutes ago and used Gaussian Blur on a normal layer that I had just used a brush to draw on. Not a Smart Object or anything like that, just a normal layer. The file was immediately messed up, so I restarted Photoshop and tried to reopen the file. It will open but it is completely corrupted, big chunks missing and some big chunky blocks added, and it corrupted ALL the layers so I have nothing to work with to save the file. Luckily it was a personal project, but it's still hours of work that are just gone now. I tried restarting the computer, everything, but the file is destroyed. It won't even open properly as a composite so there is nothing I can do.

There were less than 50 layers in the file, and it was an ~ 6000 x 6000 px file. Running Photoshop CC 20150722.r.168 x64 on OS X El Capitan 10.11.2. I tried to look up other people having this issue and I saw that it goes back to 2011 with CS5, but that was with Gaussian Blur and Smart things. Supposedly it was fixed in later versions, but I am fairly confident that this is not an issue with my computer/video driver/etc. Never had anything like this before.

Any help would be appreciated - and does anyone happen to know if a corrupted .PSD is at all salvageable??
Photo of Amy Phillips

Amy Phillips

  • 2 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Why haven't you installed the 2015.1.1 update?

The CS5 issue with smart filters was definitely fixed.
We haven't been able to reproduce any similar problems since then.
Photo of Amy Phillips

Amy Phillips

  • 2 Posts
  • 0 Reply Likes
I just checked for updates, and it looks like my account got disconnected at some point so I never knew there was an update! My internet can be a bit squirrelly, so there's no telling when that happened. It's installed now.


I appreciate the fast response - I wasn't sure if anything like this had been experienced since the fix for CS5. I definitely haven't ever seen anything like it, so hopefully it was just a one time fluke on my system! Thanks!
(Edited)