With Beta 6 on a MacMini M1, Outlook works now perfectly but pdf printing still not working. Only Jpeg printing works with an HP printer.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Monterey Working/Not Working Apps
- Thread starter bradhs
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
My friend, any update since this post? Are you able to say me if Cisco VPN works with latest beta?
thanks
Bartender now works in Monterey, and there was an update today indicating preliminary support.
VMWare Fusion Version 12.1.2 (17964953) does not boot up any VM regardless of client OS - receive Transport (VMDB) error -14: Pipe connection has been broken. Regardless of existing VM or new creation, same error.
I have removed Fusion and reinstalled, no effect.
Last edited:
You may need to ask on the VMware Community forum. My limited understanding is that your problem is not related to Monterey specifically and it should be fixed by a complete uninstall of Fusion and reinstall. By a complete uninstall I mean more than just removing the Fusion app. You might need to search for how to uninstall.
I followed the following, https://kb.vmware.com/s/article/1017838. Reinstalled and still got the broken pipe error - Transport (VMDB) error -14: Pipe connection has been broken
Did you open up permissions on any folders perhaps?
No. For me it just continued to work after I upgrade from BS to Monterey beta 2 and later. I think there is more to remove than in that old article referring to Fusion 10. For example, stuff in ~/Library/Application Saved State and in /private/var. An app like App Cleaner and Uninstaller PRO can help you find everything.
After complete sanitization of *vmware* files in ~/Library, /private/var, etc. (ran AppCleaner prior), reinstalling 12.1.2 I still received the nefarious broken pipe error. Pondering through the crash log, I noticed references to "metal" and while not conclusive, I decided to put my rMBP into discrete graphics mode (as changing the Display settings in the Fusion VM config did not help). Instead of receiving the BP error, this time I received "Unable to start VM" error. Thinking more on this (perhaps slight improvement over the BP error), I decided to roll back the post OCLP patch for my graphics card. I also dropped the hardware version in Fusion for the VM from "18" to "17" and just like that my VM was able to start. Granted I would not want to run my VM with full discrete graphics with this setting too long as the fans and battery life are impacted, at least I now have my VMs operational albeit a small sacrifice until VMware fixes incompatibilities in the latest version to be released.
After tinkering around, I found out I can achieve operation by forcing Discrete Graphics using gfxCardStatus. Reinstalled the post patch with OCLP and updated the VM hardware version back to "18". Apparently Monterey patched with Intel HD4000 is asking for trouble in some cases.😉
Last edited:
Good news that you have a way forward. Though you risk rather brusque replies, I think it is worth making a thread in the VMware community forum to see how others with your hardware are managing.
I don't know why version 17/18 makes a difference - that probably reflects my level of understanding.
My testing is with a 2016 MacBook which has pretty basic Intel HD Graphics 515 - very different from your rMBP. (I am keeping my main VMware iMac with BS until release date).
Switched to MacOS in November last year I never had any experience upgrading my system. It was Big Sur from the start.
Is there a "safe time" so to speak when all the software has been compliant or likewise?
I don't see any reason upgrading day one so to speak, I can wait a couple of months if that's what it takes.
Is there a "safe time" so to speak when all the software has been compliant or likewise?
I don't see any reason upgrading day one so to speak, I can wait a couple of months if that's what it takes.
I have a couple of "complicated" machines. Lots of peripherals, lots of network connections, lots of software, and I can just say that Monterey looks stable and good to go. I know there are a few softwares that still have issues, but I only have one package that does not work, and that is Onyx (which is very OS version specific.)
I typically wait until v 2 or 3 to get bugs out and make sure all my software is compatible.
i never understand that; betas don't simply progress in a linear fashion; some things get better, some things get broken. it's never a straight line from pre-release beta 1 to the final release (and then, again, with the betas after that)...
I wasn't referring to betas, I was referring to releases. I agree entirely re: betas which is why I keep them off my Mac.
then why are you here discussing an OS that is only in beta? confusing.
also, fwiw, official point releases still contain bugs, surprises, bug fixes, etc. there really is never a finite point where an OS is ready, done. it's always a work-in-progress...
I was writing in reference to the post above from @Dockland which didn’t ask about the beta. Sorry if this was confusing.
I agree with you 100% re releases - I was just saying that in my experience waiting for a few releases has been a trouble free approach.
Grateful for the answer(s)
I know an OS (and apps) are somewhat organical and keeps updating. It was more if any software wouldn't be ready so to speak, the day of the release. Like Virtual Box and so on.
Now I know. I'll wait a couple of weeks or a month, or is Big Sur going to stop from working if I don't upgrade before a certain time?
Outlook 16.54 updated this morning is crashing again on Monterey beta 6 !!!!!!!!!! I installed 16.52 and its now working.....and I stopped the automatic upgrades as 16.54 looks like a beta also.