Windows Photo Viewer error with BleachBit

Submitted by pbr on Fri, 12/26/2014 - 13:59
Forums: 
Support
Forum tags: 
windows
bug

After running BleachBit I get the "Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large" error. Reboot and Photo Viewer works again. Am I the only one? Windows 7 Pro 64-bit SP 1 and BB 1.6 (PortableApps version).

andrew

Fri, 12/26/2014 - 14:03

Does it happen with all photos?

It would help if you can isolate this to one, specific option or one set of files that was deleted. One way to do this is to left click on each option and click delete in the context menu. (This avoids the need to check each box.)

---
Andrew, lead developer

pbr

Fri, 12/26/2014 - 14:48

It happens with all graphic files that Viewer supports.

I was hoping there'd be a way to figure out which option might be the culprit without going through all of them one by one. I'll get back...

pbr

Fri, 12/26/2014 - 15:09

I think we have a winner:
System > Temporary files

It produced this error in the list of things cleaned:
[Errno 2] No such file or directory: 'C:\\Users\\PBR\\Local Settings\\Temp\\AdobeIPCBroker.log'

I have Adobe CreativeCloud installed.

pbr

Fri, 12/26/2014 - 16:48

A fwiw to I think we have a winner (and I clicked the wrong reply button above, sorry) —

I think the path BleachBit is showing for the error is wrong. It should be C:\Users\PBR\AppData\Local\Temp\AdobeIPCBroker.log , which is where the thing is actually located, no?

ROCKNROLLKID's picture

ROCKNROLLKID

Fri, 12/26/2014 - 17:48

Do you use Winapp2 at all? If so, I poked around and couldn't find any entries that are written incorrectly, however, I did notice this:

[Windows Photo Viewer*]
LangSecRef=3025
DetectFile=%AppData%\Microsoft\Windows Photo Viewer
FileKey1=%AppData%\Microsoft\Windows Photo Viewer|*.*

It is set to delete everything in that directory. I don't use Windows Photo Viewer so I have no idea what is in that folder.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

pbr

Fri, 12/26/2014 - 18:51

No, I don't use Winapp2. I also don't find a Windows Photo Viewer folder at %AppData%\Microsoft\ .

andrew

Fri, 12/26/2014 - 20:47

Hmm, I think this may not be the cause of the Windows Photo Viewer error for two reasons

1. The error "no such file or directory" means BleachBit did not delete this file. It seems the file was deleted by another process very quickly after BleachBit scanned that folder.

2. The AdobeIPCBroker probably affects only Adobe products, and I think Microsoft made the Windows Photo Viewer.

You can confirm whether AdobeIPCBroker.log causes the error using this procedure: close BleachBit, delete AdobeIPCBroker.log using Windows File Explorer, and then try Windows Photo Viewer again.

If it does not cause the error, try this one-at-a-time diagnostic procedure:

  1. In BleachBit, delete just one section (like System)
  2. Try Windows Photo Viewer
  3. If there is no error, go to #1 and delete a different section
  4. If there is an error, repeat #1 deleting each option (like System - Temporary Files) one at a time.

---
Andrew, lead developer

pbr

Sat, 12/27/2014 - 07:56

I moved AdobeIPCBroker.log (which has something to do with CreativeCloud, see https://forums.adobe.com/message/6315981 ) to another folder and ran BB for just System > Temporary files. BB didn't throw any errors but I did get the "Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large" error immediately after running BB. It's the only option that produces the problem. Truthfully, I don't think AdobeIPCBroker.log has anything to do with the problem; however, there is a definite if-one-then-the-other correlation between cleaning System > Temporary files and getting the Photo Viewer error. The workaround seems to be NOT cleaning System > Temporary files.

ROCKNROLLKID's picture

ROCKNROLLKID

Sat, 12/27/2014 - 11:41

Since you said you aren't using Winapp2 with BleachBit, I do not see any any CleanerML entries (the entries BleachBit uses for itself) for Windows Photo Viewer and the only Adobe one there is is for Adobe Reader.

When you say System > Temp, do you mean the Temp folder located in Windows folder or the one located in Users folder? Does the program require Temp files in order to run? If so, I would recommend creating a whitelist path for those files it requires. You can do this in BleachBit - Edit - Preferences - Whitelist tab.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

pbr

Sat, 12/27/2014 - 19:11

I mean System > Temporary files as listed in the left panel of BB — whatever files ticking that category may cover.

ROCKNROLLKID's picture

ROCKNROLLKID

Sat, 12/27/2014 - 22:33

Have you tried white listing the files the program makes in that directory with the instructions I gave in my previous post?

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

pbr

Sun, 12/28/2014 - 08:38

It does not create any temporary files anywhere. I've checked before, during and after using Viewer. Does Viewer require temporary files to operate? Beats me. So, no, I've haven't whitelisted anything because there isn't anything to whitelist.

Fwiw, I've done searches on the "Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large" error. Most of the results indicate the presence of malware, but this is different. In all the instances cited, the users could not get Viewer to work no matter what they did. In my case, it only happens when I use one particular BB option and it corrects itself after rebooting the pc.

Yes, it's odd. I suspect it's something particular to my system. What I'm going to do is download an older copy of BB and see if it still happens. Beyond that, I don't think we're going to get any further with this...unless you'd like to come over to my house and rummage through my system. :-)

pbr

Sun, 07/05/2015 - 05:13

Fwiw, version 1.8 eliminates the problem.

ROCKNROLLKID's picture

ROCKNROLLKID

Sun, 07/05/2015 - 09:07

Glad your issue was fixed. Let us know if you need anything else.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).