tiff file displays correctly in Preview; gets cut off when opened in Bridge or Photoshop

Just wanted to jump in a with a "same problem here". Working on a large family photo project. Super annoyed.

Experiencing this as well. First bunch of scans were fine, last few are cutting off in the exact same place. Scanning from the Mac interface. Using a Canon MG6820. Surprised that Apple hasn't tried to fix this yet.

I think it's an Alpha channel problem.

Used the MacOS (Sierra 10.12.6) scanner software for an HP OfficeJet Pro 8500A Plus to scan a 2400dpi TIFF.

When opened directly in Photoshop (CC 2017.1.1) it showed the cut-off with transparency (25% off the right hand side).
Opened the TIFF in Preview, then immediately exported again as a TIFF, but without compression, and Alpha channel off.

Opened the exported TIFF in PS without any issues.

I just experienced the same thing. Scanning using the Mac OS Image Capture with a Canon Maxify MB5320. Sierra 10.12.5. The solution I found was to open it in Preview and save a copy, but I saved it as a TIFF! This allowed me to turn off alpha channels and any compression. The trick is to duplicate and then immediately save which brings up the Save dialog. When I renamed the file before saving it seems to revert to whatever default was set for the original and saves without the dialog-- and without fixing the problem.

Not any better of a solution, but I do believe this confirms that it is some sort of Alpha channel issue. Shooting mostly digital I rarely scan any more. I used to use Silverfast with a high end scanner and that never gave me a problem, however, this reminded me I originally bought Silverfast because I discovered that under some circumstances the software that came with the scanner made dogs meat of the Tiffs. Seems to me that this is an Apple software issue.

tiffinfo, part of the libtiff Open Source library. It's a command line tool.

Conceivably in fact a bug in the scanner driver, which returns junk Alpha channel info, and which Image Capture has started to use. If so, this will spread to other software in time.

This identifies the same bug, and notes it is a bug in Image Capture which, as of Sierra, is saving a TIFF with an alpha channel which is often wrong, requiring rescan. Is there a reason Image Capture Preview now loo... |Official Apple Support Communities

Well, some interesting results. Trying scan 11.tiff. Photoshop 7.01 also shows only the left of the image, followed by transparency. I believe Photoshop is correct, because the file has transparency. I believe the other apps which seem to show it correctly, just ignore the transparency.

Very different from the first one posted. Let's compare the TIFF structure.
First file:
Size: 50MB
TIFF Directory at offset 0x3073d92 (50806162)
  Image Width: 6739 Image Length: 4079
  Resolution: 1200, 1200 pixels/inch
  Bits/Sample: 8
  Sample Format: unsigned integer
  Compression Scheme: LZW
  Photometric Interpretation: RGB color
  Extra Samples: 1<assoc-alpha>
  Orientation: row 0 top, col 0 lhs
  Samples/Pixel: 4
  Rows/Strip: 4
  Planar Configuration: single image plane
  ICC Profile: <present>, 2020 bytes
  Predictor: horizontal differencing 2 (0x2)

Second file:
Size: 7MB
TIFF Directory at offset 0x6a3590 (6960528)
  Image Width: 5946 Image Length: 3671
  Resolution: 1200, 1200 pixels/inch
  Bits/Sample: 8
  Sample Format: unsigned integer
  Compression Scheme: JPEG
  Photometric Interpretation: RGB color
  Extra Samples: 1<assoc-alpha>
  YCbCr Subsampling: 2, 2
  Orientation: row 0 top, col 0 lhs
  Samples/Pixel: 4
  Rows/Strip: 8
  Planar Configuration: single image plane
  Model: EPSON ET-16500 Series
  Software: Apple Image Capture
  Tag 317: 0
  ICC Profile: <present>, 2020 bytes
  JPEG Tables: (289 bytes)

So, what do we see. The second file uses JPEG-format TIFF, which is really considered bad and obsolete. Not a good choice. BOTH files use RGBA format, so it is no surprise if we see transparency. However, it may be that the software has an error meaning it does not correctly fill in 100% alpha for the full width. We can see the second file was certainly made by Apple Image Capture but we cannot say what made the first one; maybe it was even resaved by Photoshop, there is just no indication. It is a much more normal LZW file, but still RGBA.

Image Capture might just decide to do this, but maybe there is an option that affects it.

Okay, this is weird.

Now, all of the sudden, scan 7.tiff can open normally in photoshop CS 2017...

Didn't open earlier today, hence my screenshots above...weird.

I even opened the original from the first folder location and that opened fine too (just in case the public Dropbox had been changed by one of you).

But I looked at one of the other ones that got cut off in the same way. That still shows up cut off.

I added scan 11.tiff to show you what I mean.

The one difference now is, the original, "scan 7.tiff" starts with the RAW image menu and I have to hit "OPEN" or whatever, but in RAW preview and when it actually opens, looks normal.

Scan 11.tiff on the other hand, just opens up into photoshop without the RAW menu. Why they would be different, I don't know. They were part of the same multi-image scan bed.

I still wonder if this is El Capitan, a certain Epson driver, an Adobe decoding problem or some cocktail of the above.

What OS is everyone using?

Thanks, I can confirm that does download a 50MB ZIP file containing one TIFF. Would be interesting now to hear from people about their success or otherwise with different versions of Photoshop. First, an ancient one: Photoshop 7.0.1 does open it in full.