![]() ![]() If if then works, you know it's a preference file of some kind. Reboot, and log back in and see if it happens. a full clone with carbon copy cloner), just so you can undo this if it messes something up.īoot in normal mode, then in ~/Library, move the entire preferences folder to the desktop. First, I strongly recommend making a reliable back (i.e. If it still doesn't work, there's a brute force step you can try. If it works, that means it's probably some kind of code that's interfering. Safe mode is tricky to get into on the M1 machines, follow the support doc steps very closely. Two ideas:įirst, startup the machine in safe mode, login to the user account with the issue, and see if it happens. So since it works in a new user account but not the old one, it's likely to be something in ~/Library more than any of the standard software. I did update VMware Tools in this VM just for good measure, but no joy. I don't have the problem in other Macs running Fusion, even the same Windows 10 VM. Perhaps someone else in Fusion-land can suggest a place to look.īTW, now that I can run Fusion on this Mac, albeit only in inconvenient logins, i notice that Unity mode won't engage with a " Display Topology update request could not be completed in guest" complaint. I'm at a loss to imagine which haystack to look for the needle. Not sure what glimmer had me try on accounts other than my original principal account but it did smoke out the login-specific nature of the Fusion problem. This confirms that Fusion's behavior is login-specific. I've created another account, also administrator, and Fusion works as well as it did in the Guest account. No 'root' password on machine I'm aware of. I don't think this is particular to Ventura as I've had the same behavior in previous MacOS releases. I've never updated the T2 firmware, so it's whatever shipped with the MBP. Your suggestion about the T2 chip's possible involvement is intriguing. That's why I asked if anyone with my model and configuration had succeeded then I could answer at least this last question. ![]() I've suspected there is something pathological about this MBP with respect to Fusion, but could never distinguish whether it was common to the entire MBP 16 line (perhaps my configuration) or peculiar to my specific machine. This was symptomatic of earlier unstable Fusion installations where VM crashes and corruptions occurred, so when I saw this behavior after bare installation, I stopped there and ripped the Fusion installation out by its roots. A Fusion thread was left consuming an entire CPU's worth of processing, never completing and persisting across reboots. On my most recent installation attempts on Big Sur and Monterey, I never got past installation. I believe the OS corruption I encountered was during that initial unstable period, where Fusion might not have been the root cause but could have exacerbated the already unstable Catalina environment.With this Catalina 15.4 release and henceforth, the general stability issues with the MBP subsided and it was now decently stable, EXCEPT for Fusion. When retracing my history, I remembered that it was Catalina on which I had my original problems with Fusion 12. A few months later, Catalina was up to 15.4 and I decided to try again. Catalina's first releases (at least through 15.2) were unusably unstable on the new MBP and after dozens of troubleshooting hours with L2 and 元 support, we declared it hopeless and i returned the MBP for full refund. It was designed to work with Catalina which was in its maiden release when the MBP was shipped. Yes, there very well may be something amiss in this MBP. Has anyone been successful installing Fusion 13 and running VMs on a MBP matching (or close to) my specs under Ventura? Some success here would bolster my courage to try again on my MBP. But given the downsides, including OS corruption, needless to say I'm hesitant to try. With the recent releases of MacOS Ventura and now Fusion 13, I've been hoping against hope that whatever led to these unsuccessful results on the MBP might have finally been corrected. I had given up on running Fusion on the MBP. All have failed, despite installing and running VMs successfully on other Macs such as Mac Mini with same software releases. The earliest combination I tried was an earlier Fusion 12 release on Big Sur, and the most recent was a later Fusion 12 on Monterey. From the inception of this MBP, any attempt to install and run Fusion on this combination has failed: incomplete installation, corrupted VMs, even once corrupted MacOS forcing a wipe-and-reinstall of MacOS. I have a maxed-out MacBook Pro 16 (2019, 2.4GHz I9, 64GB RAM, 8TB SSD, Radeon Pro 5500M) now running Ventura 13.0.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |