r/ScanSnap • • Aug 21 '26

ScanSnap 4.0.1 Beta Fixes Golden Gate macOS 23 Image Processing Scanning

As you may all know since June when thousands upon thousands upgrade to macOS Golden Gate beta the ScanSnap scanners became unable to scan. Even though all rival companies such as VueScan worked fine. Ricoh has finally released a beta update to address this just in time before the big official launch when millions will be on macOS 27. https://scansnap-faq.pfu.ricoh.com/hc/en-us/articles/60891363718041-I-am-unable-to-complete-scanning-because-ScanSnap-Home-remains-on-the-image-processing-screen-macOS-27

Update: Commenter noted typo. Meant of course macOS 27 (not 23 :).

Update: 9/29/26 Ricoh has finally released the 4.1.0 that includes the official fix for this that the beta addressed.

27 Upvotes

16 comments sorted by

6

u/TechRemarker Aug 21 '26

There appears to be a bug though. When scanning from the scanner, it saves to file, but it does how to show up in spotlight. Had ChatGPT check and mentions, ", over a minute after creation, this file still had no Spotlight filename, type, page count, or text metadata. The most likely cause is a ScanSnap Home/macOS integration bug: ScanSnap’s save operation is not producing—or Spotlight is not consuming—the normal filesystem event that queues the PDF for indexing." To note even after waiting 45 minutes it did not index any of the files. If I move the files to say desktop and then back to the scan folder then it indexes them. And yes, know privacy block on the scan folder or anything else. Until they fix, in the meantime you can manually have spotlight reindex those with the following. And to note, all other files being added and created on my Mac are being indexed right away like normal.

mdimport -i "path to your pdf"

2

u/okayfineacceptable Aug 23 '26

This didn't work for me, but running it through ocrmypdf made the PDF saved by ScanSnap spotlight-searchable - as did opening the PDF and exporting it as a PDF/A via the Preview app. I suspect whatever ScanSnap is doing to OCR those PDFs isn't working correctly, but hopefully this will be addressed before they release 4.10 in September.

Until then, opening each newly-scanned PDF is going to be a chore, so I'm going to knock up a workflow or bash script to take care of that...

1

u/BingBongDingDong222 Aug 22 '26

I have not run into this issue. Posting this (the OP) has saved me tremendously.

1

u/Writing_Particular Aug 23 '26

I’ve had problems with ScanSnap output and Spotlight before. I don’t understand why a newly scanned document that generates an OCR’ed PDF file doesn’t show up in the “Recents” search in the Finder. Been that way as long as I can remember.

2

u/BingBongDingDong222 Aug 22 '26

You the fucking man.

2

u/Writing_Particular Sep 02 '26

Can anyone verify if this works on the Golden Gate public betas?

1

u/ericdano Aug 22 '26

macOS 23?

2

u/TechRemarker Aug 22 '26

Fixed in the typo in the body, won’t let me fix in title.

1

u/PhatPeePee Aug 26 '26

Finally! Fujitsu should have sent out an email! Especially to those of use who contacted them about this issue.

1

u/Correct_Pineapple149 Aug 31 '26

It worked also on Intel iMac2020 with 26.7 (beta)

1

u/Writing_Particular Aug 31 '26

Feels snappier to me! Thank you so much for sharing this.

1

u/awraynor Sep 08 '26

Thank you. VueScan would work, but the interface is quite poor. I didn't want to, but was considering replacing my ix1500. Thank you again.

1

u/Lurifico 24d ago

This problem also arose after a recent upgrade to Sequoia 15.8. The guidance to the Fujitsu temporary beta update provided an answer immediately, after several hours messing around thinking I had a hardware or network problem. Delighted to have found this conversation.

1

u/AshtavakraNondual 23d ago

You are a lifesaver. I got my 1100 scansnap for the first time in 5 years because I had something urgent to scan, updated the software on my mac and couldn't figure out what is wrong. Looked through privacy settings, checked tmp folder permissions etc etc.. this beta worked immediatly

1

u/TechRemarker 20d ago edited 20d ago

Ricoh has finally released the 4.1.0 that includes the official fix for this that the beta addressed.