Better to be safe than sorry!
2 Likes
I suppose using rim brakes on a disk brake wheel is more like the opposite of safe, but at least it is supposedly future-proof.
3 Likes
I am having exactly the same problem. I have been sending crash logs to Zwift, whi say it is a Mac issue and have closed my complaint!
My Zwift support ticket also got closed.
Even though Monterey is being pushed out as an upgrade, itās still in beta and therefore not supported by Zwift. Iāve turned off auto updates and wonāt update until there is an update on Zwift to say that itās officially supporting Monterey.
Itās driving me mad seeing ā1 updateā in system preferences. 
Since latest update it keeps losing BT signal. Switching between the Companion and PC for the BT helps sometimes. Happens on both laptop as well as PC. Continuous connection errors during some rides. Couldnāt add power control beginning of ride today. Finally got that but not Schoche HR monitor. But, waiting till my ride was over allowed me to add the HR monitor.
1 Like
Iām not sure what your problem was, but I have two Macs both on Monterey 12.1, the main Zwift machine is 12.1 beta 2 and the other the latest beta 4. Both run Zwift fine. Iām wondering if it is hardware differences? Both are Intel X5690 based macs with RX580 GPU.
Me too 
Monterey 12.1 Release Candidate is now available (21C51) - it might be worth trying that?
Your computer must be enrolled on the developer program.
The beta builds have been reliable for me on two different Macs (Intel based). Iām using both of these daily, the more powerful one is my work computer, the other one for Zwift. B2 has been faultless with Zwift for me.
I would not install development builds on my Zwift device. I would suggest waiting until Zwift had time to test it.
On one hand, this seems like solid advice. On the other hand, it doesnāt really seem like Zwift does much testing.
1 Like
Really? IMVHO all published versions are in development and we are testersā¦
2 Likes
Zwift 1.19.2 is working on macOS Monterey 12.1 released to the public today. Just tested it.
Mac Pro 5,1, Intel Xeon X5690 3.46ghz, 32gb RAM ECC, Sapphire Pulse Radeon RX580 8GB, 2TB Samsung 870 Evo. MacOS Monterey 12.1 with OpenCore 0.7.5
Others with different machines might experience different.
The āERROR # Z117 , FILE āPatcher.cppā, LINE 602ā error message at the logging screen is back again with this latest patch (December 16th). They made an update that had fixed the problem for the past 2-3 weeks, but it seems that error message wil be back at every single new game update. Thatās starting to become annoying, all the more if I have to wait 10 days again to be able to log inā¦
1 Like
haha - yeah, good one.
3 Likes
Yup, looks like the dreaded Z117 error is back for me too. Not sure what happened.
Tim
1 Like
OMG!! Finally got my Zwift working again by tethering my pc to my mobile and installing the update. I want to know:
- What variable has been changed in the update code that now breaks machines that fail to update?
- When is this variable going to be reinstated in the updates so we donāt need this workaround againā¦?
Itās been > 1 month trying to fix this. I want a creditā¦ so frustrating
1 Like
Hi @Tim_Chua, the Z117 error is back for me, too.
2 Likes
Sorry to hear that mate. Iāve alerted Tech Support of the issue a couple of hours ago, and will update hear once I hear back from them.
Tim
1 Like
Iāve alerted tech support again and they told me it had something to do with admin privileges or smth on my computer which isnāt true. When I got the Z117 for the first time ever, I changed nothing on my computer and thatās a later update from zwift which solved the issue. I hope they will eventually install the variable in future updates so we donāt need to go through all this again and again and wait for days before being able to zwift againā¦ Iāll let you know when I hear back from them.
Guys, this is the thread for the previous November update, not the December one 
2 Likes