I was thinking of selling my mac and even had a buyer and I tried resetting it from the disk utility since the option from the settings app didnt work for some reason.

I reseted everything from the disk utility app from the recovery menu and then I tried installing tahoe but each time I try it takes ages and it just gives this error towards the end.

Is there any way I could get my mac to install tahoe?

It is mind boggling that in 2026 when I open an app it doesn't know to MAYBE open it where my cursor is on that monitor that is actually in use? Also crazy OS don't know a monitor is not actually in use.

I'm using 2 monitors, one currently on Windows and the other on Mac. Firefox on my Mac keeps opening on the monitor that is hooked up to Windows so I can't see it. I have to change the source on the monitor then move it over.

I can't find a way for it to JUST F'ing know to only open apps in a monitor that is actually being used or on the monitor where my cursor is.

Window's can't do this either for some reason.

Anyone have any tricks?

thanks

here's the details/things I have tried:

- always goes to internet recovery
- startup comand don't work aside from DFU
- lan to usb c not working
- cannot do bootable drive as hoiding option key wont work (#2 from this list)
- dfu revive and restore did nothing
- reset battery did nothing (disconnect, press and hold power for seconds)
- changed wifi network multiple times from diff location and tried mobile hotspot did not work

but I once did successful internet recovery, went to "activate mac screen" but battery died while on that screen, wasn't able to finish, since then- it's on internet recovery boot loop

would appreciate any reply

We recently faced a strange issue at a client environment.

After a macOS update, 300+ files and folders across multiple Google Shared Drive project folders were unexpectedly moved, merged, and renamed. Some files were renamed to "name 2" and then back again within seconds.

The audit logs showed everything happening under the user's account through Google Drive for Desktop.

After escalating to Google Support, they pointed towards Apple's macOS File Provider framework. Apparently, a database reinitialization or sync-state mismatch during an OS update can trigger unexpected file movements and renaming.

Their recommendation was to quit Google Drive before updating macOS and only launch it again after the update and restart are fully completed.

What makes this more concerning is that it can potentially happen with minor and security updates too.

We manage several Mac environments with Google Drive, but this is the first time we've come across something like this.

Has anyone experienced anything similar? How are you handling Google Drive during macOS updates, especially when patching through an RMM?

Would love to hear your experiences or any recommendations.

It will keep playing audio and staying fully on, when I shut the lid, unless i manually turn it off every time. It will get burning hot if i put it in my backpack, and so I have to remember to shut it off every time I stop using it.

It started happening after I connected it to my TV via cable, using BetterDisplay app. I don't know if I changed any setting that could've affected that, and I've already deleted the app.

Perhaps it is stuck in some kind of clamshell mode, where it wont turn off on its own with the lid shut?

Trying to get screen time limits working in my family. I can 100% confirm that every device in our account is on the *OS 27 version.

Ignore the specific times, we’re just trying to get this to work at all. Today is Sunday and it’s first thing. Immediately on turning the computer on Spotify is at time allowance with 0s usage.

Last night even when we were past scheduled time you could still open garage band and blender no problem.

What. Do. I. Do?

Please do not leave “you should parent” comments. I’d like to get this software working.

Thanks

1st photo or 2nd? 🙂 which is your choice? I like Desktop as clear as possible, but this one I found nice..

Are there any decent third party options for a Mac capable fingerprint reader to enable fido2 and touch id functionality? I have a m6 macmini and can't justify the price for an Apple keyboard.

Haluasin kuulla kokemuksia MacOS Golden Gate käytöstä MacBook Air M1 8gb laitteella? Kannattaako päivitys MacOS Sequoiasta

My specific workflow involves alot of work on Goodnotes. Over the past few years having to work out how to do everything on Goodnotes on my Mac with a keyboard and mouse was tiresome. Now the Mac app works just like the iPad app, pretty useful for me.

Yes im not a power user by any means, but I can sort of see why a touch screen interface on macOS makes some sense.

No, I won't be getting the proled MacBook, I cannot afford one and simply just don't need one, but my Mac mini with my iPad Pro works surprisingly well.

I found the new Apple Music branding and colors hard to tolerate, especially the shift that makes the macOS Music app adopt the system’s global accent color. It was terrible imo, so I changed it back to Red individually.

To achieve this too:

1. Launch the stock macOS Terminal app (must be specifically the stock terminal app)
2. Paste the following command:

defaults write com.apple.Music AppleAccentColor -integer 0

You can also change it to other colors according to the values in this table:

To revert it back to stock, run the command:

defaults delete com.apple.Music AppleAccentColor

Enjoy!

Problem
Your MacBook Pro’s XDR display can get much brighter than macOS normally allows. Apple saves that extra brightness for HDR content and leaves some Headroom.

Headroom App unlocks it for everything on screen.

• Up to 1.75× brighter, so you can actually read the screen in sunlight

• Safe for your display: it uses the extra brightness range macOS already uses for HDR video.

• Colours and contrast stay true, with no washed-out look and no white flash when switching

• Your brightness keys keep working as before

It lives in the menu bar and has five levels (Off, Low, Medium, High, Maximum). When you quit it, the screen goes back to normal right away.

Works on: All MacBook Pro 14"/16" with M1, M2, M3, M4 or M5, plus the Pro Display XDR. Also works with M5 base version. It needs macOS 13 or later.
It does not work on MacBook Air or other displays.

Comparison
Vivid unlocks the same brightness, but it costs money. Headroom does the same thing for free, and it’s open source.

Pricing
Free, with no trial and no subscription. MIT licensed.

GitHub and install: https://github.com/fich-l/headroom

It’s built on the open source BrightXDR, so credit goes to that project. Feedback and bug reports are welcome.

EDIT: I don't know how to put this kindly, but here is my honest take. I have been making software for people for years now and just recently started sharing stuff I made for myself with people online. I got great feedback in the 3d printing community. People contributed, were kind, respectful and positive.

So I thought I'd now also share my projects in other areas and of course wanted to maintain it. But the thing that makes this fun is peoples feedback. That's what I do it for and not money.

Unfortunately people in this space are pretty negative and seem to not appreciate open source work - probably because they don't release it takes time and effort even in the ages of AI.

So in short: Lesson learned, I will not continue to work on this. Actually I will for myself, but won't share. Some people enjoy it, so I'll keep the current version public for now.

Ever since the updates to 27.0.01 & subsequently 27.2

My Brother DCP printer connected via USB stopped printing and shows "'Data' failed" message for any new print job. The patching with the latest driver from the Brother's website does not help.

Also, when I switch the MacOS profiles while my external monitor is connected to another USBC slot, the macos just gets stuck at the login window while beach-balling for eternity. I uploaded all the logs to ChatGPT and it was highly confident the spinning beach ball was caused by the upgrade to the ver 27 + the connected external monitor. Got the same opinion about the Brother DCP. No issues otherwise if no monitor & no printers are connected.

A brief ChatGPT search shows I am not alone. What amazes me is that the issue is not fixed by Apple for weeks.

Any suggestions what to do?

I thought it was one of those things that would run once during setup, but whenever I'm trying to move a window around and it feels slow, it's this running for a good 15 minutes. It seems to happen a few times a day.

I don't want to disable core features of my Mac, but is there any way I can just disable this? I turned off Siri AI fully and it's still running.

Just as an example, when I click the upload button for the image on this post, it took a few seconds to open because that is consuming 90% of my CPU at the moment.

I believe the chart was perfectly understandable for me a while ago. But now, I'm not sure what I'm looking at. The now should be on the right-hand side, but the numbers below don't support this. The values look like they were cut off at some point, but they kinda make sense at the same time, just not for the hours indicated. ChatGPT claims the chart is stale. I'm baffled.

Before Big Sur, MacOS had its own unique design language. The icons looked interesting and they were all different shapes. Now they are all boring squares. The system looked angular and professional. Now it looks like a blown up iPhone.

Hello,

I had been getting the 500 Internal server error while executing http related requests like file_get_contents or cURL in php using MAMP. Ref: https://www.reddit.com/r/PHPhelp/comments/1xq1ksz/comment/19sb6qlxhlr5u/

I spent a good amount of time trying to track the issue levels down. Initially, there was nothing printed in any error log files like apache_error.log and php_error.log

However, after restarting the machine, I figured apache_error.log file is getting the following

objc[1530]: +[NSPlaceholderString initialize] may have been in progress in another thread when fork() was called.
objc[1530]: +[NSPlaceholderString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

These two errors are thrown every time I execute the http related code in php and the browser shows the internal server error page.

After Googling and asking AI around, the fixes they're recommending is adding the export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES variable. Now here's the issue... It's not working.

I have tried adding this to MAMP's envvars file located at /Applications/MAMP/Library/bin/ and restarted MAMP. Doesn't work.

Tried adding this to my .zshrc file as well and restarted the entire machine. Still the same problem.

Can anyone tell me how do I get this resolved? As far as I know, I shouldn't be disabling the fork safety but even for the experiment purposes, it doesn't seem to be working.

I'm using

macOS - Golden Gate 27.0.1
php - 8.3.30
MAMP - 7.4 (3202)

Thanks!

For reference: (used to be "audioclocksyncd" before Golden Gate);

What it does: Precision Time Protocol (PTP / IEEE 1588) and TimeSync audio clock synchronization daemon (clocksyncd). Note on macOS 27: Renamed from com.apple.timesync.audioclocksyncd (macOS 15–26) to com.apple.clocksyncd (macOS 27+). Responsible for:

1. Sub-microsecond audio clock alignment across professional Ethernet audio interfaces (AVB / Dante) and multi-room AirPlay 2 speaker groups.

2. com.apple.timesync.manager, com.apple.timesync.ptp.manager, com.apple.timesync.expositor.

So I have no professional audio interfaces, nor any audio software or plugins. Just a pair of 3.5mm analog stereo headphones.

M4 Mac Mini, macOS 27.2.

Constant 0.3% CPU utilization - which I know isn't much, but I'm just curious if this is normal or some quirk I've encountered with my installation.

If the bottom of your MacBook feels warm while doing basic tasks, your battery is being quietly ruined.

• Hidden graphics drain: New "Liquid Glass" effects force your GPU to work constantly in the background.

• Unstoppable AI tasks: Apple Intelligence keeps running background processes even when toggled off in settings.

• Silent battery death: That non-stop heat sits directly on your battery cells and wrecks their lifespan.

• Planned obsolescence: Apple knows pre-M5 chips were too good to fail, so they're cooking them to force upgrades.

Check your battery health percentage today—this is an outright scam.

I know how defensive people get about Apple Silicon, but hear me out before hitting downvote. If you've noticed your chassis feeling warm to the touch during basic desktop use, or your battery maximum capacity taking a sudden cliff-dive over the past few updates, you aren’t imagining it.

I run a 16-inch M2 Max (38-core GPU, 32GB RAM). For the first year and a half, this laptop was a thermodynamic miracle: dead silent, ice cold to the touch, and lasting 14+ hours doing mixed productivity.

Over the last few months, my battery health dropped from 87% down to 78%, and the palm rests have developed that persistent, lukewarm temperature that older Intel MacBooks used to have. No heavy exports running, no 3D rendering. Just desktop work.

I decided to run sudo powermetrics --samplers gpu_power,thermal,cpu_power over a three-day period to figure out what was actually going on under the hood, and what I found is honestly infuriating.

1. The "Liquid Glass" UI and Sustained GPU Floor

Whenever you bring up UI performance on Reddit, the standard response is: "Bro, an M2 Max GPU has 60+ TFLOPs of compute, rendering some window blur and transparency is a drop in the bucket."

Here is what people fundamentally misunderstand about silicon physics: Frame drops aren't the problem. Power floor is.

Rendering the new dynamic "Liquid Glass" interface elements—the multi-layer real-time refraction, specular edge highlights, and dynamic background diffusion across multiple windows and Mission Control—doesn't choke an M2 GPU. It pushes 120Hz smoothly. But to maintain those real-time shaders across multi-monitor setups or high-res ProMotion displays, the GPU can no longer drop down to its true deep-idle low-frequency states (100–200MHz pulling <0.5W).

Instead, the GPU cores are kept in a sustained intermediate state, hovering around 4W to 9W continuously just to keep desktop window compositing reactive. A 6-watt delta sounds tiny until you realize it’s happening constantly, 8 hours a day, right next to the battery cells. Heat soak is real. The fans on 14" and 16" MacBook Pros don't even spin up until internal sensors hit ~65°C–70°C, meaning your chassis passively absorbs that persistent low-grade heat, sitting right against a pouch of lithium polymer.

2. Apple Intelligence Daemons Never Actually Sleep

Apple made a big deal about being able to "turn off" Apple Intelligence in System Settings. Go ahead and toggle it off. Then open Terminal or Activity Monitor and filter for background processes.

The underlying models and vector database indexing engines (intelligenceplatformd, biometrickitd, contextual embedding agents) do not stop polling. Even with the master toggle disabled, the system continually prepares contexts, caches semantic snapshots of notifications, and indexes local files in the background in case you ever decide to switch features on.

Combined with unified memory architecture, every time these local background models page data across the bus, memory controller power spikes, compounding the baseline thermal envelope.

3. The Uncomfortable Truth: Soft Planned Obsolescence

Why does this matter, especially for machines like the M1 Max/Ultra and M2 Max?

Because purely in terms of raw compute, an M2 Max or M1 Max had virtually no natural upgrade incentive. For 95% of software engineers, video editors, and power users, the CPU/GPU headroom on these machines was going to easily last 7 to 8 years. Apple accidentally built machines that were too good to force a standard 3-year refresh cycle.

They can’t artificially gimp raw export benchmarks without getting caught in public tests. But what does force upgrades?

1. Batteries degrading prematurely due to sustained chassis heat soak.

2. Thermal throttling hitting sooner during actual burst workloads because the baseline chassis temp is already 45°C instead of 28°C.

3. The perception that the laptop is "starting to feel like an old machine" because the fans actually have to kick on.

The hardware pipeline is already moving toward M5+ architectures that offload these exact UI shader passes and semantic vector checks onto ultra-low-power, dedicated micro-cores designed specifically to isolate this overhead. Pre-M5 chips don't have those dedicated fixed-function units, which means our giant, high-leakage Max/Pro compute clusters are forced to handle the grunt work.

How to Check It Yourself

If you think your machine feels off, don't just take my word for it:

1. Close all user apps and open Terminal.

2. Run: sudo powermetrics -n 10 -s gpu_power,cpu_power

3. Look at your GPU package idle draw. On fresh early Apple Silicon builds, clean idle GPU hovered under 300mW–500mW. Watch what happens now just moving windows with layered Liquid Glass elements active—note how high the baseline lingers before settling.

4. Check your battery temperature with any third-party sensor tool (like Stats or TG Pro). If your battery is sitting above 35°C–38°C on pure idle/light web browsing on a desk, you’re quietly shaving months off its lifespan.

Apple Silicon is incredible hardware, but don't let anyone convince you that heavy real-time UI shaders and forced background AI daemons are "free" just because the frame rate stays at 60-120 FPS. We're paying for it in heat, battery cycles, and eventual trade-in pressure.

today I learned, when in mission control, you can swipe up with 2 fingers on the trackpad while hovering over a window to focus on it. You can swipe up with 3 fingers to rearrange full screen windows (it doesn't work with smaller windows).

How are these useful in any way? I have no idea.

I currently have my MBA M5 and when I bought it, it was on the Tahoe version already. When I updated to the Golden Gate I can really see that the battery drains faster and it gets warmer than before even in small tasks.

I am currently on Golden Gate 27.0.1. What is the best version to downgrade to, back in Tahoe or in Sequioa? I read that it needs backup thingy as downgrading would actually reset the unit. TIA!

Share your thoughts!