# ScanSnap and MacOS 27

**URL:** https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692
**Category:** Tips
**Created:** [September 22, 2026, 9:13am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692 "2026-09-22T09:13:54Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![NickLowe](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/nicklowe/32/38937_2.png) [@NickLowe](https://discourse.devontechnologies.com/u/NickLowe)
#### Post date: [September 22, 2026, 9:13am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/1 "2026-09-22T09:13:55Z")

</div>

Many using this combo will already be aware of this, but the current ScanSnap software doesn’t work with MacOS 27 Golden Gate (it get stuck processing the scan). There’s a beta version [here](https://scansnap-faq.pfu.ricoh.com/hc/en-us/articles/60891363718041-ScanSnap-Home-stays-on-the-Image-Processing-Screen-or-the-Book-Image-Correction-Screen-does-not-open-on-macOS-Tahoe-26-7-Golden-Gate-27) which solves the issue. It has to be manually installed as if it’s a fresh installation, but doesn’t overwrite your existing settings, and will scan to DT as normal.

---

<div class="post-metadata">

### Author: ![tinksquared](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/tinksquared/32/39350_2.png) [@tinksquared](https://discourse.devontechnologies.com/u/tinksquared)
#### Post date: [September 22, 2026, 11:20am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/2 "2026-09-22T11:20:25Z")

</div>

Yes the beta version works great, even with my old ix500!

---

<div class="post-metadata">

### Author: ![GACowboy](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/g/7ab992/32.png) [@GACowboy](https://discourse.devontechnologies.com/u/GACowboy)
#### Post date: [September 23, 2026, 1:23am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/3 "2026-09-23T01:23:25Z")

</div>

@NickLowe THANK YOU SO MUCH for this information. I bought a new scanner since I thought it was something with my ix500. Like @tinksquared said, it works with my old ix500 and the new one is going back!

---

<div class="post-metadata">

### Author: ![raluke](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/raluke/32/13583_2.png) [@raluke](https://discourse.devontechnologies.com/u/raluke)
#### Post date: [September 26, 2026, 2:28pm UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/4 "2026-09-26T14:28:19Z")

</div>

Thanks so much for this! And now that I know it works with tinksquared’s ix500, here’s hoping that my slightly less ancient ix1500 will also continue to be supported. 😀

---

<div class="post-metadata">

### Author: ![whirte](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/w/49beb7/32.png) [@whirte](https://discourse.devontechnologies.com/u/whirte)
#### Post date: [September 26, 2026, 2:44pm UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/5 "2026-09-26T14:44:00Z")

</div>

Thanks a lot. I have the same issue. It‘s the scansnap App which is not working. I was Award of the Beta. Thank you!

---

<div class="post-metadata">

### Author: ![GymW](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@GymW](https://discourse.devontechnologies.com/u/GymW)
#### Post date: [September 28, 2026, 3:59am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/6 "2026-09-28T03:59:49Z")

</div>

Just another example why I never upgrade to the initial release of a macOS major update. I am of the opinion that Apple OS releases are not dependent on adaquate testing to fix class 1 and serious class 2 bugs but on a calendar schedule. In the last 5-10 years I have not witnessed a major OS release that did not have serious issues left in it. I always wait for the AppleOS xx.1 release at minimum. I am fed up with being a volunteer beta tester for Apple and offering to report serious bugs without some form of compensation. When working for Apple decades ago I used to get paid for doing that stuff and I no longer are going to give them my experience and skills for free. I have found such things as a way to bypass the 28 digit recovery code and how to totally wipe out a Mac silicon internal SSD to its initial out of box state without a second computer or password without hacking, but I am not about to share it as they are security risks but are useful to me for recoverying data or corrupted drives. If I tell Apple they will likely disable them without creating tools for users to fix such issues themselves.

---

<div class="post-metadata">

### Author: ![tinksquared](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/tinksquared/32/39350_2.png) [@tinksquared](https://discourse.devontechnologies.com/u/tinksquared)
#### Post date: [September 28, 2026, 7:58am UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/7 "2026-09-28T07:58:07Z")

</div>

I may wrong, but wouldn’t it be on ScanSnap to make sure their software works on upcoming releases?

---

<div class="post-metadata">

### Author: ![heldersales](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/heldersales/32/38233_2.png) [@heldersales](https://discourse.devontechnologies.com/u/heldersales)
#### Post date: [September 28, 2026, 5:26pm UTC](https://discourse.devontechnologies.com/t/scansnap-and-macos-27/87692/8 "2026-09-28T17:26:04Z")

</div>

Great. Thanks. Will wait for the end of September for 4.1 release
