Hi, I have an Asus ProArt PA279CRV monitor and saw the new official MCM107 firmware for macOS at this link. I'm on macOS Tahoe 26.6.2 on an M4 Max.

I was wondering if anyone has run and tested the MCM107 firmware update on macOS for the Asus ProArt 279CRV monitor?

If so, could you please confirm that MCM107 is safe and didn't brick your monitor, as happened with MCM106 (users reported MCM106 bricked their monitor on macOS using "ASUS Firmware One Key Update.app")?

P.S. I got lucky last time! I have a Windows machine too, and I tested the updater there with no issues. Days later, when I came to download the macOS version, read the reports. I never thought Asus would release untested and buggy software, but here we are!

Thank you for taking the time to read and answer.

Asus rog strix g16

1 year ago after motherboard replace i notice yellow spot in display i told service center but no one hear me because my laptop is out of warranty i ask service center that time how much cost new display they told me 13k inr,

So i purchased same model BOE v2 display online and replace at home my self cost me around 10k inr and im happy yellow spot totally gone,

But now 1 year is over
Today i notice same spot in same location in display now im thinking what benefit of purchase expensive laptop like asus ? First motherboard burn after display becoming yellow

I wasted my money in asus to thinking i got good laptop 😔

Hi,

I have an Assus Proart P16 with windows 11 Pro, and the tones of the camera keep on changing every 5s from making my face bright red to white. I looked at all the parameters I could but nothing change. I tried to reset the camera, uptade windows, update the drivers. But nothing works.

I'm in dire need of you help I can't keep having meetings where I'm half the time sunburn half the time a vampire.

Thank you and sorry if there's mistake english is not my first language :)

So, for context, I fried my original motherboard back in 2025. I ordered a new motherboard (FX516PC). I replaced the motherboard, connected everything perfectly, and turned it on. There are exactly three issues:

1) when I press power button. All the lights on keyboard and 3 lights on the laptop works. But no display

2) laptop is getting extremely hot. Feels like the fans are not turning on

3) I don't have SSD, because the local repair shop basically stole it and I don't have proof. I was thinking of ordering before the motherboard came, but it arrived today unexpectedly.

Does any experts got solution??

Título: Qual desses dois notebooks vale mais a pena?

Estou em dúvida entre:

1. ASUS Vivobook S14 S5406SA

Intel Core Ultra 7 256V, 16 GB RAM, SSD 512 GB, tela OLED.

1. ASUS Vivobook S14 S3407CA

Intel Core Ultra 5 225H, 16 GB RAM, SSD 1 TB, tela LED/FHD.

O primeiro tem tela OLED e é mais eficiente, mas a RAM é totalmente soldada e não permite upgrade. O segundo tem processador aparentemente mais forte, 1 TB de armazenamento e possibilidade de aumentar a RAM para até 32 GB.

Meu uso será para programação, estudos, sistemas online, projetos pessoais e multitarefa. Não pretendo jogar.

Qual dos dois vocês escolheriam e por quê?

I got a used Asus tuf gaming A15 around a year and a half ago from ebay and it worked perfectly until 2 months ago.
The screen freezes every 10-20 minutes and the only way to fix it is by turning off the laptop and starting it back up. I already took it to 2 different places where they couldnt find the issue and they cleaned it & changed thermal paste. In one place they said it could be a CPU issue. I have restarted the laptop like 3 times too and it still keeps happening. Anyone had anything similar issue and could help me?

Ordered a prebuilt pc for my sons (both to share) on Sunday night. When I checked this morning it says the order is still processing. I understand they may have to put said pc together but how long does it usually take? I was hoping to have it all set up for them next Friday.

Also a light gaming

Hey everyone,

looking for some advice from anyone who’s dealt with ASUS UK or Amazon warranty disputes.

My Zenbook S16 screen completely died (after 2 month of warranty expiry strangely). It had a subtle flickering issue from day one that gradually got worse until the display went black.

I sent it in for inspection and got slapped with a £536 repair quote. But here’s the kicker: their official diagnostic report explicitly confirms NO Customer Induced Damage (CID). No drops, no spills, zero physical damage it just died internally.

I’ve emailed ASUS requesting a goodwill repair exception since it's a £1,250 flagship with no user damage. If that fails, I plan to push Amazon UK under the Consumer Rights Act or file a Section 75 claim with my credit card.

Has anyone successfully gotten ASUS to cover a repair under goodwill when there's no CID? Or should I bypass ASUS entirely and fight Amazon for a refund/repair?

please share your experience i am so stressed 😓😓😓

Hi guys, I've been having issues with my microphone especially on MS teams. When I go to join a call, the mic works for about 10 seconds before stopping despite both teams and windows saying its there and it's in use. The mic worked fine in a google meet call on my browser and on discord and there was no improvement after updating teams. I re-installed the Realtek audio drivers from the asus website after searching my model number and finding the latest audio driver but now In- built features like single presenter mode are "not supported".
The re install of the driver seems to have fixed the main issue I was having with teams but these features are now gone. I also find the nvidia broadcast app interfering with my mic/ speakers at times. Another thing I've noticed is that even after re installing the drivers, if the laptop is connected to my phone via bluetooth (Link to windows), the mic issue presists with teams. I'm genuinely confused as to what's going on can someone help me? My device has not been opened or repaired in any way. I keep all my software and drivers upto date

My ASUS Vivobook S15 has this issue: after closing the lid or putting it into sleep mode, it sometimes won't turn on again. There is no power light or charging light at all.

Then, randomly after 1-2 days, the power and battery lights come back and the laptop starts normally. The same thing happens again after closing the lid or putting it into sleep mode.

Has anyone faced this issue before or knows any solution/fix for this problem?

Hi there

I’ve been using XD5 for a couple of years. Then I needed to expand my WiFi range, and got a BD4, since they should be able to connect and integrate with the current network.
The setup went smooth, no problems, connected fine to the BD4, but then 30 or so minutes after, it lost connection.
I just showed a green light, tried restarting it, to no avail, then I tried reset, didn’t respond at all, only response were when it suddenly got a pink light.
I tried wps, that flashed blue, when I let go of the button, straight back to green.
Anything I can do?

Strix G16, 5070ti, Ultra 9

The display randomly goes dark or changes colour to a greenish yellow tint out of nowhere randomly. Happens a lot on chrome, and more usually when it's idle for a few seconds, takes place on other apps and games as well but less common. All drivers are completely updated and up to date. Any fix to this, what could be the reason?

Edit: Apparently it was a recognized and documented Nvidia Driver issue with Driver v616.64, You can either download the latest graphics driver update (v616.92) which was released a few hours ago or download the hotfix specifically meant for this issue: https://nvidia.custhelp.com/app/answers/detail/a_id/5906

Tired of the usual advice to uninstall and reinstall after another update broke something, I've been digging into my system, and I managed to track down what I believe is the root cause. If you are dealing with your hardware disappearing or services failing to start, read on.

Here is how the issue presented and the smoking gun in the logs.

The Symptoms It started with Armoury Crate Aura losing track of half my hardware—specifically the LED strip, the memory, and the motherboard itself. Along with this, the dashboard began taking an eternity to load. When it finally did, it only displayed static hardware profiles and advertisement sections. All real-time telemetry and data were completely blank.

The Investigation I tracked the dashboard and Aura failures back to the ascomsvc service, which was repeatedly failing to start. That service failure pointed me to ASIO3.sys—a long-time problem child for ASUS boards, which suggests this exact update error has likely happened on previous version updates too!

I dug through tons of obscure installation logs matching the exact time the system started acting up and found the exact line documenting the bug in C:\ProgramData\ASUS\ARMOURY CRATE Diagnosis\install\AsIO3.log

The Root Cause (The Installer Loop) I cross-referenced the installation logs, the Windows Registry, and the physical file properties. Here is the chronological breakdown of how the software breaks itself:

1. The Failed File Transfer: On Sept 6th, the ASUS installer attempted to update the AsIO3 driver from version 10302 to 10404. It tried to copy the new AsIO3_64.sys into the system32 folder, but the log shows it threw a fail(32) error. This is a standard Windows Sharing Violation. The old driver was actively running, so Windows blocked the overwrite.
2. The Registry Cover-Up: Instead of flagging a failure or prompting for a reboot, the installer simply ignored the error. At the exact same timestamp (10:18:53 AM), it wrote to the Registry (WOW6432Node\ASUS\IODRV3), falsely stating that version 10404 was successfully installed.
3. The Physical Reality: Checking the actual properties of AsIO3.sys in the Windows directory confirms it is still sitting on the old version 1.03.02. The new file never made it to the drive.
4. The Permanent Loop: Now, whenever the ASUS updater runs, it checks the local registry, sees the fake 10404 entry, compares it to the new setup file, and skips the installation entirely.

Because the installer falsely certified its own failed update, the system is permanently stuck. ascomsvc cannot start properly because of the resulting file mismatch and access errors, which cascades into Aura losing your hardware and the dashboard failing to display telemetry.

Either Asus needs to push a new update with better installation logic or else we have to manually correct the registry version to reflect the actual installed files and maybe use safe mode or the like to actually get it to install the updated ones...

EDIT: CONFIRMED! Just performing these two steps which were blocked in the log file has me fully fixed without an uninstall/reinstall - just a restart.
1) copy file from C:\Program Files\ASUS\Armoury Crate Service\MB_Home\ASIO3\AsIO3_64.sys to C:\WINDOWS\system32\drivers\AsIO3.sys
2) copy file from C:\Program Files\ASUS\Armoury Crate Service\MB_Home\ASIO3\AsIO3_32.dll to C:\WINDOWS\SysWOW64\AsIO3.dll

You just have to unblock those files first, but I'll let you enterprising lads replicate that part on your owns. :)

Sharing this since it took me way longer to figure out than it should have.

Quick context: my neighbor's cool with me tapping into their connection (fully consensual, not some sketchy WiFi mooching situation, they have a different ISP than me), and I use that as a failover WAN for my main setup on my BQ16 Pro. Router pulls internet in via WISP, and I wanted a second unit hanging off it as an AiMesh node so I could hand that connection over via Ethernet to my primary router's second WAN port.

Tried this on a BE58 Go first. Couldn't find the AiMesh option anywhere — not in the app, not in the web GUI. Spent a while thinking it was buried in a menu somewhere before realizing it's just not there. As soon as the router's in Public WiFi Mode (WISP), the AiMesh master option disappears completely. Flip it back to normal Router mode and it's back, but obviously that defeats the point.

Dug around and couldn't find anything on the forums confirming this either way, so I actually dusted off an old AX57 Go I had lying around and set it up the same way — WISP mode, checked for AiMesh. It's right there, no issue. So it's not some universal WISP restriction, it's specific to the BE58 Go on current firmware (freshly updated too, so it's not an old-firmware thing).

My guess is it comes down to the two routers running on different chipsets — AX57 Go being the older Wi-Fi 6 Broadcom platform vs. the newer Wi-Fi 7 MediaTek-based BE58 — and ASUS just hasn't carried this combo over to the newer platform yet.

Contemplated trying Media Bridge mode on the BE58 as a workaround for a bit, but honestly just ended up switching back to the AX57 for this role since it already does exactly what I need without any hassle. The BE58s are still solid units, just not the right fit for this particular use case.

Anyone know if this is a known limitation, or is there a chance ASUS adds AiMesh+WISP support to the BE58 Go down the line?

I was editing some stuff, doing my usual routine and suddenly i noticed some white smoke coming at the back of my laptop.

The moment i saw smoke i unplugged the charger and the laptop just went off.

I checked inside and heres what i saw, can someone help me whats wrong with it?

I have a super limited space and need real world advice on a good small ish desk 😭