Working with a 2020 MacBook Pro 4TB on Sequoia 15.6. In the past I have edited EDID override plist files to get custom resolutions and HiDPI on external QHD displays. I have also used BetterDummy/BetterDisplay to achieve this, but that app no longer works with Intel Macs (according to the developer, at least not for getting HiDPI resolutions). In the past (not sure which macOS version it changed on) you could edit display overrides in /System/Library/Displays/Contents/Resources/Overrides. It is no longer possible to do this, even with SIP disabled as /System is now read only. A workaround was to place a custom override in the folder: /Library/Displays/Contents/Resources/Overrides However, it seems that overrides in this location are no longer read by macOS. I am trying to get HiDPI (at 1980 x 1080 or 1600 x 900) on DELL P2418D and BENQ PD2500Q QHD displays. Both have worked in this was the past, with modified EDID and/or BetterDummy/BetterDisplay. Is there any way of forcing EDID override on Intel Macs running Sequoia now?

Which version should work on this machine? I've tried 10.1.3 and 13.5.2 and both refuse to work. There is a prompt saying I have an unsupported CPU on both versions. On 13.5.2 when I try starting up the VM it just says "failed to power on virtual machine" and so on, without any logs anywhere. On 10.1.3 it says "Unable to retrieve kernel symbols. Failed to initialise monitor device." I ran first help on my tom and there were no mistakes. What should I do? I need to run Windows XP on this machine by any means, I have another thread in which I describe my issues with Virtualbox which was working fine (6.1 version) on this very machine with Sonoma installed. Now that I've upgraded to Sequoia I can't seem to make any VM to work for me. Although, I haven't tried VMware Fusion on the Sonoma because I thought it's tied to Metal rendering only (which it isn't) The chip belongs to the Penryn family as far as I understand, doesn't it mean that 10.x versions should work on it?

Apple is currently providing macOS versions for both Intel and ARM/Apple Silicon. With Intel hardware getting old, how long will Apple still provide Intel macOS versions?

The title says it all. How can I create a bootable Mac OS thumb drive for an older Intel Mac Mini (A1347) from my current Mac Mini (MMFJ3LL/A)? I've found instructions from Apple's web site (Create a bootable installer for macOS ) for when you have a .app bundle installer. However, the download links from How to download and install macOS all either get me a .pkg file or link me to the app store. The app store punts me over to system update. (For context, why am I doing this? I'm trying to get HDMI audio working on the A1347 under Ubuntu and want to rule out bad hardware. Ideally I want to install any version of Mac OS on a thumb drive per Install macOS on an external storage device and use it as a startup disk simply to test audio over HDMI. See my other question question for reference.)

I have an 2019 Intel iMac on which I tried to install Windows 11 following instructions from this page . These instructions include disabling the TPM check. I used a (Dutch) Windows 11 ISO, which was downloaded from the Microsoft page . I did let BootCamp create a 128GB partition. Installation started well, but after a while, at the stage of copying Windows files, the installation stopped showing an error. What is going wrong here?

### Environment ### - Apple MBA 2020 MacBook Air9,1 / Intel / x86_64 machine - Host OS: macOS Big Sur 11.6.2 - Host OS Build: 20G314 - SW: VirtualBox 6.1.32 r149290 (also tried on VirtualBox 6.1.30 r148432) - Guest OS: macOS Monterey 12.1 (21C52) ### Purpose ### - Upgrade VM from Big Sur 11.6.2 (fully functional with VB 6.1.32) to Monterey 12.1.
OR - Installation from scratch a Monterey VM. Both have same final result: instability. After the first boot with Monterey, the VM suddenly HANGS AND REBOOTED BY ITSELF, reporting "This system was automatically rebooted after panic". It seems it enters in a "reboot loop" because after some time, even doing nothing, a reboot still happen again and again, like in an infinite loop. ### How to reproduce ### 1. Open VB 6.1.32 2a. Start a VM upgraded to Monterey
OR
2b. Start a VM installed from scratch with Monterey
OR
2.c Start a VM with "Install macOS Monterey ISO" as only Storage added to VM (NO other Hardisk present) 3. Just wait some time...
==> You'll see in 0-15 min Guest OS HANGS AND SUDDENLY REBOOTS by itself.
==> Then the console message is: "This system was automatically rebooted after panic" ### Logs and info ### I unfortunately continue to note the instability of Monterey as Guest with VB 6.1.32, even on Apple Hardware! All config data, and a video are at disposal to have an idea, as well as VB Logs (see attachments). - VirtualBox 6.1.32 Logs: - Monterey (VB 6.1.32) reboot loop video: ### Questions ### I asked to VirtualBox forum here [topic 104998](https://forums.virtualbox.org/viewtopic.php?f=22&t=104998) with hope of receiving helpful feedback, which has not been the case as yet. I'm primarily interested in sharing to the community and finding other user experiences. Does the same or similar behaviour happens to someone else?
Has anyone perhaps applied a workaround or found a fix?
Has anyone ever gotten a really stable and usable Monterey guest installation (on Mac HW) with VirtualBox? ---------- Added later... ==============
I just came back a few days later, just for a minor update on this topic. I was wandering if something changed with Monterey (Host), perhaps hardware resources are managed differently in Monterey, or that more generally something has changed. So I just repeated the tasks with the same VM, so VirtualBox 6.1.32 with Monterey (Guest) on Monterey (Host on Apple hardware) ### Environment (revised) ### - Apple MBA 2020 MakBookAir9,1 / Intel / x86_64 machine - **Host OS: macOS Monterey 12.1** - **Host OS Build: 21C52** - SW: VirtualBox 6.1.32 r149290 - Guest OS: macOS Monterey 12.1 (21C52) I unfortunately note that the result is still the same: VM do a reboot loop and kernel panic.

Intel-based Macbook Pro. Did OpenCore upgrade to Sequoia (hooray!). Then shrank the drive and created a new partition (with Disk Utility, while logged in normally) for Linux; booted Linux from a thumbdrive and installed it on that partition (mount point /). Now it will only boot into the Linux partition. Hitting "escape" at startup gets me to a grub command screen. Any way to restore the boot sequence so I can see both OSes as options on boot? Or do I need to start all over, delete everything, and this time use rEFInd?

I've got an old mid-2013 MacBook Air (A1465 EMC 2631) that's has no internal storage. Only external HD/SSD via USB. I have an M1 MacBook Air with macOS Sequoia to assist in this effort. I used the old Air for years so I’m confident it will still work but I don't currently have the media with the OS on it and it's been in storage for a couple of years. I now want to use it for the occasional Windows experiment. (Probably Windows 10) Can I install Windows directly onto it from its current blank state? Or is it only possible via Bootcamp? (Some drivers not available for instance?) Or is it the case that I can install Windows directly onto it but need to install macOS first, or need to install Windows via BootCamp first? (I specifically mention the lack of the original internal SSD because this causes issues for macOS. From memory I could do each upgrade from Mountain Lion to Sierra, but not High Sierra or newer. So this could also conceivably be a problem for installing Windows.)

I have different machines running OSX 10.12 and 10.13, which use different processors. I am trying to get from terminal, a string that can show me which CPU instructions are supported by that machine; so I can use the appropriate software (some of the software require specific instructions to be present on the CPU, and if that CPU does not support them, the software will either work incorrectly or crash). I did check querying the system profiler via terminal but I can get only the CPU type and model, not the CPU instruction set that it support; and if I would do this by hand, getting every CPU model and checking online, it would take hours. * CPU instructions are these set of instructions like MMX, AVX, SSE; that allow your CPU to operate in a certain way. With years, they are added to the base CPU instruction set, so modern CPU these days support more than 15 different instruction types.

Whenever I connect my Intel MacBook Pro to an external 4K-display and playback video on YouTube or on a video call, for example, CPU usage on kernel_task gradually increases until all 8 cores are at almost 100% and the whole system slows down. The video becomes choppy and I am forced to terminate whatever video-playback is running or disconnect the external display. This seems to be independent of the video resolution of what I am playing. The only difference seems to be that when I connect my external display, the graphics changes to use the AMD-chip, when I disconnect the display it falls back to the Intel-chip. So when using the more powerful graphics-chip the video playback capabilities are worse than when using the less powerful one. Is there anybody with the same problem? Is there any way to fix this behaviour? **2019 Intel MacBook Pro 16"** - Graphics: AMD Radeon Pro 5500M 8GB and Intel UHD Graphics 630 1536 MB - RAM: 32GB - CPU: 2,3 GHz 8-Core Intel Core i9 **Details** - Connected via USB-C to a display that also charges the Mac. - Mac is not in low-power mode.

My MacBook Pro 13" (Mid 2012) is struggling hard with what I'd like it to do (many many open Browser-Tabs, Microsoft Office, Signal Messenger and some more open applications) and I want to test, if Linux might be the better choice for the old machine. Configuration: MacBook Pro 13" Mid 2012 * 2,9 GHz Dual-Core Intel i7 * 16 GB RAM * SSD 870 QVO 1 TB * Intel HD Graphics 4000 1536 MB * Mac OS X 10.15.7 I would like to install Linux (e. g. Debian) for testing without compromising my still running OS X system, so I think I need a Dual Boot solution, right? I don't have experience with the hardware and software topics - bootloader, ... With OS X it was always very easy to boot from another partition or external Firewire HD. **Is there any risk to break my existing OS X system when trying to install Linux (bootloader, ...)?** Usually I would create a disk image of the current system (and data) partition of my OS X on an external hard disk which I could use for a backup later. But I wonder if that is enough. **Do I need to save any other partition or information to get back to the original state in case of failure?** ## EDIT: Storage hardware configuration: *diskutil list internal*

% diskutil list internal                                            
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         500.0 GB   disk0s2
   3:                 Apple_APFS Container disk1         500.0 GB   disk0s3
 
/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s3
   1:                APFS Volume Daten                   441.5 GB   disk1s1
 
/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume Ohne Titel - Daten      458.1 GB   disk2s1
   2:                APFS Volume MBP                     11.3 GB    disk2s2
   3:                APFS Volume Preboot                 26.2 MB    disk2s3
   4:                APFS Volume Recovery                526.8 MB   disk2s4
   5:                APFS Volume VM                      5.4 GB     disk2s5

## EDIT 2 - core of my question: p. s. I think my most important question is: could the setup for a Linux+OSX dual boot installation damage something so hard that I would not be able to just boot from an OS X firewire HD, partition the internal SSD and restore a clone (backup) of my working (slow) previous OS X? (It is crucial for me to stay "productive" with this machine and due to a very difficult personal situation I do not have time to fix and repair for some days (and during this time not be able to work with my old OS X, as long as there is no new working system set up.)

After running low on HD space, I decided to purge local copies of iCloud files by simply unticking the option in 'settings - iCloud' Now in Finder I cannot see the files, only a dialog with an option to change the settings. However, there has been no increase in HD free space at all! I have rebooted multiple times, I have even deleted quite a few files just in case it needed space for deletion purposes. Nope, didn't change a thing. This is Mojave btw, so the advice to 'right click undownload' does not exist hence having to take this action. N.B. the files still exist in icloud (which is what I want) I just don't want all the files that I have downloaded over time and for some reason it isn't doing any housekeeping to remove older ones (and yes 'optimise my mac' was also ticked)

Why does the DeepL desktop application consume a lot of energy? Even more than Chrome. How can I diagnose it? MacBook Pro 15-inch, 2019 (Intel chip)

I am helping a friend install MacOS onto her MacbookPro14,1 2017. She purchased it new and it has had no modifications. The disk has been reformatted and from the Disk Utility in Recovery Mode looks fine. I have attempted to install from (Cmd+R) Recovery Mode via internet and an install USB. Both processes start as per normal and then proceed to what I guess is copying resources to the local drive, which takes about 10 minutes, but fails at the end with the below:

storeassetd: SUAppStoreUpdateController: XPC error in __77-[SUAppStoreUpdateController _queryForAvailableUpdatesWithCompletionHandler:]_block_invoke (error domain=NZCocoaErrorDomain code=4999 "The connection to service named com.apple.softwareupdated was invalidated)...
...
osinstallersetupd: No native mechanism to verify InstallESD.dmg
osinstallersetupd: Operation queue succeeded 
osinstallersetupd: Couldn't mount base system dmg! (error code: 110)
osinstallersetupd: IATOOL: Failed to mount outer DMG

Any help would be much appreciated.

I updated to El Capitan yesterday (on MacBook Air 2014). I then decided to install Kali Linux 2.0, and boy it's been one problem after another, so far nothing has gone the way it's supposed to. Without going too much into details, some of which include (problems downloading rEFInd, burning the iso image onto the thumb drive and etc.). I think I managed to do that. So now I try to reboot my Mac, after the rEFInd boot screen shows up I plug-in the usb and I get only one volume (the legacy OS one) and the guide for installing Linux says try installing rEFInd and try again, but I already have rEFInd (you need to have 3 volumes as it shows here ). If I try to boot the legacy folder it says: >Starting the Legacy Loader >Using Load Options USB >Error: Not Found while loading legacy loader > >Make sure u have the latest firmware update installed >*Hit any key to continue* Any help is appreciated :) I'm really getting frustrated trying to install Kali, first time though. P.S. There is a very high probability I've messed up somewhere before, because as I said, I've been running into almost every problem out there, googling, and trying to go around it, most of the time not even sure what I am doing, so... I may have messed smth up on the way. BTW my laptop can't read my USB, which is to be expected, but I will be able to turn into readable later, won't I? More Details: rEFIdn used - 0.9.2 How I configured it: Iunzipped it, I had to turn my security settings off in the recovery mode, and I think that worked for me after I ran it as it's is supposed to be ran, as said in the link. Long process, I don't remember all of it.

I have three Intel Macs which have Windows 10 Pro installed. Windows is activated with a digital license linked to my Microsoft account. All three Macs also have macOS High Sierra or newer installed. This means the firmware in each Mac is capable of UEFI booting from ExFAT formatted volumes on GPT or MBR partitioned drives. Some additional relevant specifications for these Macs is given in the table below. |Specification|iMac (21.5-inch, Mid 2011)1|iMac (21.5-inch, Late 2013)|Mac mini (Late 2018)| |-|-|-|-| |Model Identifier|iMac12,1|iMac14,3|Macmini8,1| |Memory|16 GB 1333 MHz DDR3|16 GB 1600 MHz DDR3|8 GB 2666 MHz DDR4| |Windows Boot Method|64 bit BIOS|64 bit UEFI|64 bit UEFI| |Type of Partitioning|GPT/MBR Hybrid|GPT|GPT| |Internal Drive|500 GB SATA HDD|1 TB SATA HDD|256 GB PCIe SSD| |Processor2|"Second Generation" 2.5 GHz Intel Core i5 "Sandy Bridge" (I5-2400S)|"Fourth Generation" 2.9 GHz Intel Core i5 "Haswell" (I5-4570S)|"8th Generation" 3.0 GHz Intel Mobile Core i5 "Coffee Lake" (I5-8500B)| |Cores|4|4|6| |T2 Security Chip3|No|No|Yes| |Graphics Card|DirectX 12 Compatible with WDDM 1.0 Driver|DirectX 12 Compatible with WDDM 1.3 Driver|DirectX 12 Compatible with WDDM 2.0 Driver|| |Display4|1920x1280 (1080p)|1920x1280 (1080p)|1920x1280 (1080p)| |Keyboard|Wired Apple A1048|Wireless Apple A1314|Wired Apple A1048| |Mouse|Wired Logitech M110|Wireless Apple A1296|Wired Logitech M110| 1 Windows 10 Pro was installed using this answer . 2 Only the Mac mini (Late 2018) has a Windows 11 compatible processor. 3 A T2 security chip implies secure boot. No Intel Mac models have a TPM. 4 All displays are assumed to be at least 9” diagonally and have at least 8 bits per color channel. None of these Macs meet all of the Windows 11 minimum system requirements given below. |Hardware/Software|Minimum System Requirement| |-|-|-| |Processor|1 GHz or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC).| |RAM|4 GB.| |Storage|64 GB or larger storage device. |System firmware|UEFI, Secure Boot capable.| |TPM|Trusted Platform Module (TPM) version 2.0.| |Graphics card|Compatible with DirectX 12 or later with WDDM 2.0 driver.| |Display|High definition (720p) display that is greater than 9” diagonally, 8 bits per color channel.| Microsoft has publish the article Ways to install Windows 11 . Under the heading "Other ways to install Windows 11 (not recommended)" there is a method which is repeated below. >**Create an image install** > >Use DISM or 3rd party tools to directly apply an existing Windows 11 image to the disk. > > >**Important:** An image install of Windows 11 will not check for the following requirements: TPM 2.0 (at least TPM 1.2 is required) and CPU family and model. I have the following related questions: - Is it possible to do a clean install of the current Windows 11 Pro release (Version 22H2) on any of these Macs by using the method above? In other words, reformat the Windows 10 volume and install Windows 11 Pro. - Will Windows 11 be automatically activated for free? - Can the install be done with only tools provide by Microsoft and Apple? In other words, without the use of any other 3rd party tools from URLs that are not Microsoft or Apple. - Does the WDDM driver for Windows 11 (Version 22H2) have to be at least 2.0? - Does the Mac have to have a Windows 11 (Version 22H2) compatible 64-bit processor ? - Can the latest release of the Windows Support Software (Boot Camp Support Software) provided by Apple for each Mac be used?

_TLDR: I am aware that there are plenty of questions from people trying to migrate from Intel to Apple Silicon installations of homebrew; and many questions that speak of confusions from unwanted conflicts between those. This is not about that. This is about running two installations side by side and avoiding any mixing or involuntary confusion between the architectures._ ## Background I am setting up a brand new 2024 MBP, and so far all is going well. I am coming from an Intel MBP. I have installed brew (on the new machine) from scratch, fully native, with the evil "curl" method directly from https://brew.sh . I dumped my Brewfile on the old machine, and installed all the packages I had on the new, from that. This successfully pulled all the native versions of the packages and installed them in /opt/homebrew as advertised. I also used rbenv, installed via brew, to build some version of ruby that I need for a project. This also worked completely as expected with no hickups whatsoever, since all dependencies that rbenv or rbenv install needed were already in my Brewfile. _I have copied *nothing* from the previous MBP directly._ I am 100% certain that there is no confusion with some old architecture binary slipping onto the new machine. Nothing in /usr/local/bin has been copied. ~/.rbenv has not been copied. So far so good. Unfortunately, it turns out that a single gem that I need for that project, and which has a requirement on a closed-source binary from a vendor, is not yet available for Apple Silicon. I cannot get rid of that gem, but using it with the silicon version of ruby is just not on the table yet. ## Question While waiting for the issue to resolve itself, my thought is this: is it possible to install an Intel architecture version of brew (and subsequent tools like rbenv and the shims provided by it) in /usr/local/bin which is *completely* separate from the Apple Silicon version in /opt/homebrew, and which is by default also disabled (by virtue of the path not being in any environment variables)? Fortunately, I do not require rbenv or ruby to be available in both installations; I only use it for that single project. It would maybe be cleanest to have a script that I can source in a bash which sets a bunch of variables, and from then on, in that particular process, the /usr/local/bin environment would be active, and the /opt/homebrew environment would be hidden (i.e., maybe take /opt/homebrew out of all $PATH etc. variables). I am aware that the extended installation docs of brew describe how to install multiple versions in arbitrary directories. I could not find any mention of my usage scenario in the documentation or the brew github issues though. Am I setting myself up for disaster, or is this known to possibly work well (even if unsupported by brew, as stated clearly)? What would the required environment variables? Is it enough to just prefix any bash or other command I intend to run with the Intel versions with arch -x86_64 ... and make sure /opt/homebrew is not in any variable? If I start a bash with arch ..., does that architecture choice automatically get passed on to any subprocesses (i.e., when running brew, rbenv, and shims like ruby, cucumber etc.) or are there known cases where this setting somehow gets lost? The reason why I think it would be best to start with brew and not only arch'ify rbenv itself is that there are a few dependencies that rbenv needs to compile ruby, and *those* are easy to install with brew. Hence I could avoid having to completely manually install any dependencies of rbenv, ruby or some of the more "intense" gems. ## Bonus question As mentioned before, I would accept if the two brew environments are completely separate, and only one is ever "on" at any given time. Would there be a way to have them both active at the same time (i.e. both in the PATH), maybe making sure that the installation directory of the currently "active" brew is first in PATH and other variables? Or is this scenario definitely out, as being much to risky?

I found an offer online for a MacBook Pro 2020 with Intel i7 processor and without Touch Bar (that is, with physical Esc and F1-F12 keys). Did such a model ever exist? I have not heard about anything like it. I thought the Touch Bar was first removed with the M1 MacBooks.

Due the fact that Oracle has not released an ARM version (Apple Silicon) of their Instant Client (OCI8) I am forced to use the Intel version of MAMP with my MacBook Air (M2; 2023) so I can properly compile the OCI8 binary (based on the Intel version of the Instant Client) via Pecl. Okay, that should be no big deal. MAMP basically runs Apache, MySQL and PHP so there should not be a performance hit. Rosetta translation of Intel code should not significant or negatively impact the use of MAMP at all. But how I can I install the install the Intel version of the binary (MAMP_MAMP_PRO_6.9-Intel-x86.pkg) on my MacBook Air (M2; 2023)? I launch the installer and get this message that effectively blocks and install: > **x86_64 CPU required!** > > You need a x86 CPU (64 bit) to run MAMP or MAMP PRO. I guess I could hassle a co-worker to install in on an Intel-based Mac and then just copy the MAMP folder located at /Applications/MAMP to a USB flash drive and then install that on my MacBook Air? But is there any way to force the installer to ignore the CPU architecture mismatch so I can handle this on my own?

My old 2016 MacBook Pro is extremely slow all of the sudden, starting a program like finder can take several minutes, every click on a button will have the UI freeze for a few seconds, installing a new fresh macOS version took over 20 hours - it is basically unusable. What I tried so far: - Completely erased the SSD, partitions, encryption everything - Re-installed the newest Monterey version from a bootable usb drive (the installation from the recovery partition failed) - Resetting PRAM and NVRAM - Reset the SMC - Run the system diagnostics on boot up (no problems found) - Checked the CPU DIE temperature, it is at 40°C and the fans are running Is there anything else I could try, short of bringing the MacBook to the shop?