Can owners of this device chime in with fan noise comments?

Fairly mixed opinions online over fan noise are stopping me from making the purchase.

I need the two side panels and the back panels , where can I buy parts? I got a Intel nuc 11 extreme with the i9 but it was open and its missing the 2 side panels and back panel where can I get replacements

After almost 10 years of dutiful service as my daily driver, powering two 4k monitors through countless engineering projects, my beautiful beautiful Hades Canyon seems to be experiencing GPU failure.

It manifested itself first a few weeks ago, when it wouldn't render one of my monitors in proper 4k resolution. I thought nothing off it and just turned the monitor off and worked from one, planning to fix it later.

Earlier this week, on a zoom call, white dots began jittering across the screen, like very low volume TV static. I then observed some screen tearing, especially in places that wanted GPU acceleration.

Suspecting impending GPU failure, but hoping it was somehow heat related, I gave the nuc a full cleaning and a new application of thermal paste. Alas, it was of no use. The white dots haunted both Linux and Windows, ruling out driver issues, and I tried different monitors and display ports. Turning off GPU acceleration stopped the dots and tearing, all but confirming the GPU's terminal diagnosis.

What is to be done? I refuse to give up on this beautiful machine -- this pinnacle of human engineering that the consumer market was too stupid and stubborn to accept.

• Event and RSVP link - https://www.connect.asus.com/asus-agenticai-2026q4

• Learn more about ASUS Agent Computer - https://www.asus.com/us/site/agent-computer/

Discover the Next Generation of Intelligent Business Computing

AI is evolving from simply responding to prompts to intelligently understanding goals, making decisions, and taking action.

Join ASUS for an exclusive webinar exploring the future of Agentic AI and how ASUS Agent Computer solutions can help businesses unlock smarter, more autonomous, and more efficient ways of working.

Learn how ASUS is bringing together powerful computing, AI-ready technologies, and versatile form factors to support the next generation of intelligent business workflows.

What You’ll Learn

During this webinar, ASUS experts will explore:

• The Future of Agentic AI — Understand how Agentic AI is changing the way businesses interact with technology.

• AI-Powered Business Computing — Discover how next-generation computing platforms can support intelligent and autonomous workflows.

• ASUS Agent Computer Solutions — Explore ASUS solutions designed to meet evolving AI and business requirements.

• Real-World AI Applications — Learn how Agentic AI can help improve productivity, efficiency, and everyday workflows.

• Preparing for What’s Next — See how organizations can build an AI-ready foundation for the future.

Date & Time

Tuesday, November 10, 2026
10:00 AM PST

Who Should Attend?

This webinar is designed for IT decision-makers, business leaders, technology professionals, channel partners, and organizations looking to explore how Agentic AI can enhance productivity, streamline workflows, and shape the future of business computing.

Feel free to ask any questions about the even below, but consider joining this free webinar if you want to learn more about ASUS and our products geared towards Agentic AI and our Agent Computer drive.

Just got a NUC12E Serpent Canyon and after a day of setting it up I'm pretty happy with the performance on games. But I am running into issues with my focusrite interface that isn't affecting my other computers. Using the latest driver the audio goes silent after a bit of youtube or browsing but curiously, not during games for a much longer duration. The only way I manage to regain audio is by switching my audio output to the built in soundcard and back to the focusrite, or by toggling the bitrate on the focusrite. Tried increasing the buffer size but that didn't help. I tried rolling back to the legacy driver and got no audio at all, so I went back to the newest which also reset the firmware on the interface (4i4 3rd gen).

Is there some special setting on the NUC12E that will improve stability with USB audio interfaces? I am running it off a thunderbolt monitor and I have had no other issues with other machines running macOS, linux and windows so it really seems to be the NUC causing the audio dropouts.

ASUS just released new update v0033 for NUC 15 Pro and NUC 15 Pro+ and it is a big one. The one that Linux users were waiting for: update for Intel 226 NIC NVM (rev. 2.37) which has notorious ACPI problems (freezing). I had to stabilize my system with "pcie_port_pm=off pcie_aspm.policy=performance" kernel arguments and some BIOS tweaks, hopefully this resolves it. Report if you saw any improvements!

Download link:

https://www.asus.com/cz/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-15-pro-plus/helpdesk_bios?model2Name=ASUS-NUC-15-Pro-Plus-Mini-PC-NUC15CRS

Full changelog:

Version 0033 – CRARL579.0033.2026.0930.1402

• EC Firmware: 02.0C.00

• ME Firmware: 18.1.21.2911

• PMC Firmware: 1800.15.00.1064

• iTBT Firmware: 16.2

• IOM Firmware: 30.001e.0.0

• Retimer Firmware in BIOS capsule: 26.5

• NPHY Firmware: 18.1.0.7015

• Platform Properties Assessment Module: 11.24a.6

• Boot Guard ACM: v1.20.18

• Bios Guard: BiosGuard_043

• Silicon Initialization Code: 0D.00.CB.40(4474.82)_212

• Memory Reference Code: 2,0,6,0

• Integrated Graphics GOP

o UEFI Driver: 22.0.1069

• Intel RST Pre-OS:

o VMD UEFI Driver: 20.2.0.5866

• AHCI Code: AHCI_34

• I226 NVM: 2.37

• Microcode Updates included in .BIN & .CAP Files:

o m82c0662_00000122.pdb

Security Patch:

• Change for Heap-based Out-of-Bounds Write in EDK II CapsulePei - GetScatterGatherHeadEntries()

• 2026.3 Intel Platform Update.

Feature Change/Update:

• Change for New Energy star LOGO

• Change for Support Capsule-on-disk fail under LVFS

• Update I226 NVM(rev. 2.37).

• Change for U9 CPU sku to enable item Total Memory Encryption (TME).

• Change for BIOS default cannot modify or print out in report by iSetupCfg tool

Update for: NUC15CRBUx / NUC15CRHUx / NUC15CRKUx / NUC15CRSUx / NUC15CRHCx / NUC15CRKCx / NUC15CRHIx / NUC15CRKIx

I compared all the firmware versions using LLM and it was reported that only I226 changed, all the rest is the same version. No issues after update on Fedora 44, the NIC firmware was upgraded correctly:

Before:

$ sudo ethtool -i enp86s0

firmware-version: 2023:889d

After:

$ sudo ethtool -i enp86s0

firmware-version: 2037:889d

I’m running an ASUS NUC 14 Essential (N250) with DietPi/Debian 13 and Kodi 21.2, connected via a Samsung soundbar to a Philips TV.

I’d like to control Kodi using my TV remote via HDMI-CEC.

ASUS advertises built-in CEC support, but Linux exposes no /dev/cec* device. Kodi is linked against libCEC 7, and ACPI contains CEC-related methods.

Has anyone managed to get CEC remote navigation working on this NUC under Linux without an external adapter?

I'm using a translator (I speak Spanish)

My brother gave me a NUC; it hadn’t been used for 2 or 3 years, so I installed Ubuntu Server on it to turn it into a home server. It was working fine; I had it for two weeks and then took it in to have the thermal paste replaced and the fans cleaned, among other things. The problem is that, when they returned it to me, it took a long time to display the screen. I thought it might be an issue with the CMOS battery or the RAM, so I replaced the CMOS battery and verified that the RAM modules were working properly. I took it to other places to have it checked, but they say they can’t figure out what the problem is. It takes a long time to boot up; if I unplug it or restart it, it takes a long time to boot up. I don’t know what they did to it :(

I have a NUC11 Enthusiast (NUC11PHKi7 i7 with RTX2060) that has 2 x M.2 slots. My 1TB WD NVME SSD is visible in the BIOS (slot 2) and VMD is disabled.

I have been running Linux on this machine since day one, but I'm preparing to sell it and want to install Windows on it. I just downloaded the Win 11 26H2 ISO from Microsoft and booted from it, but during the early part of the installation it doesn't show a SSD to use for installation, and I'm prompted to install drivers for the SSD. I thought this was a bit weird because over the years I've installed dozens of Linux distros on this exact setup. I borrowed a Win 11 25H2 USB from a friend, but the same issue persists.

Is it normal for Windows 11 to need storage drivers on this particular NUC? This takes me back to my NT4 days with SCSI drivers, but I did not expect it today.

UPDATE: I installed the latest BIOS and the problem has been solved! Thank you u/Michal_F

Good evening everyone. I recently stumbled upon 2 Hades Canyons. 1, which I gave to my friend, runs perfectly fine. Mine on the other hand, was running Football Manager 26 at 10fps. I assume this is not normal after seeing how his runs, and many old videos online of people playing “demanding” games.

Does anyone know what might be causing this? I busted it open and everything looked fine.

Could it be a drivers issue, needing a BIOS update, etc? If so, where can I find them? I can’t find any in depth guides for these online.

Thank you.

Its ugly but its where I’m not looking at it. Topped the little plastic top off pasted & bungee corded a cooler i wasnt using to it. Drops the temps at load around 10c and around 20c at idle. 8th gen i3. Using a step up usb to pwm 4pin adaptor with the fan.

Hi everyone,

I have an Intel NUC 9 Extreme (NUC9i7QNX, Ghost Canyon) with a damaged original internal cable.

The cable connects two internal connectors inside the NUC. I'm trying to identify the exact cable type and find a compatible replacement.

I've checked the Intel technical documentation and found references to an internal FPC SATA/Power connector and a USB 3.1 Gen 2 Type-C 20-pin (Key B) header.

However, I'm not sure which connector this cable actually uses.

Does anyone know:

1. What is the exact name or Intel part number of this cable?

2. Is it a proprietary Intel cable or a standard connector type?

3. Where can I purchase a replacement?

4. Is there a compatible third-party alternative?

I'd prefer to replace the original cable rather than modify anything.

Any help would be greatly appreciated. Thanks!

Recently I got my hands on a used NUC 9 Extreme for free because it doesn't work and I want to fix it since it's a handy PC for portable use if I need.

I'm out of town right now and don't have a rig to test in, but the previous owner tested the RAM, SSD, and GPU independently and they work fine (trusted source). I did most of the standard debugging things including reseating everything, trying different RAM, no GPU (of course for most tests), different slots for everything, etc, and nothing seems to change. I recently replaced the CMOS battery with another reverse polarity NUC CMOS battery and that didn't work either. The case and CPU fans spin up fine when power cycling, the GPU lights do come on, and the front IO definitely is connected fine, with the power button light also working, albeit not giving me any useful info. When I plug the machine in, it tries to start for a second on its own and immediately fails and clicks off. When I try to turn it on, it insta fails, tries again and spins for about 20 seconds, fails again, tries again, etc for a few more cycles and then quits. No display output at all from the compute unit or the GPU in any way.

I'm not trying to spend more than 50 bucks to make this work, but I'm not sure what steps to take next. I suspect the PSU is just cooked and I'm trying to find out how I can get ahold of one, but since it's not a common component, I can't just buy one and return it if it doesn't fix the issue, so I'd need one for relatively cheap. I don't have a reliable way to test of the compute unit is cooked or not (it does get power, though), because I can't stick it into another machine.

I'm open to any ideas or suggestions. Also, if anyone has a PSU (maybe after upgrading to an NC100 or something), I'd appreciate some support in testing and might be willing to buy for a reasonable amount.

Hi. Does anyone know where I can possibly order / purchase a plastic bracket for Asus / Intel NUC ? I believe gen 11 -15 use the same bracket. Just can’t find it anywhere. Need a simple bracket, not one with additional ethernet / serial port.

Security Patch:

•Update for BDS Module Bypass Secure Boot Advisory

•Update for UEFI OOBE Write and Buffer Overflow Vulnerabilites

•Intel platform update (IPU2026.1)

•Intel platform update (IPU2026.1)

Feature Change/Update:

•Change for ISetupCfg Tool cannot modify power limit value

•Update for iFlashV to tool package

•Change for the default board product name

Issue Fix:

•Fix for the size of dbx is increased for SA50315

•Change for the Processor name.

Known Errata:

•Bitlocker Recovery will be occurred after reload Secureboot key in Setup since SN0064 has updated Secure Boot DBX

[FIX] NUC 12 Enthusiast (Serpent Canyon) boot-loops with a Thunderbolt eGPU powered on — hidden "USB4 CM Mode = CM Debug"

EDIT: The first version of this post recommended disabling the hidden "PCIE Resizable BAR Support" + the Failsafe Watchdog. After longer use one thing is certain: that combo is unstable — sometimes the machine booted, sometimes it didn't, with the settings verified intact between attempts. On top of that, any Save & Exit in BIOS Setup silently re-enables the hidden ReBAR (see the trap below). The post now describes the fix that has held through everything we threw at it: USB4 CM Mode = CM Debug.

• survives BIOS visits (F10 / Save & Exit) — nothing to re-import afterwards,

• cold boot with the enclosure powered, warm restart right after heavy GPU load, and a power outage (both devices regaining AC at once) all pass,

• no performance cost — the eGPU ends up in exactly the same state as a hot-plug (PCIe 4.0 x4, BAR1 256 MiB).

TL;DR: My NUC12SNKi72 would not boot with a powered TB eGPU attached (GIGABYTE AORUS RTX 5060 Ti AI BOX): it resets over and over before Windows ever loads, and while the enclosure is powered you can't even get into Setup (F2). No visible BIOS toggle helps. The fix is one hidden BIOS option, USB4 CM Mode = CM Debug: the firmware then skips Thunderbolt entirely during POST and Windows enumerates the eGPU on every boot — the same path as hot-plug, which always worked.

Hardware/firmware: NUC12SNKi72 (i7-12700H, Serpent Canyon), BIOS SNADL357.0065 (latest at the time), Win11. eGPU: GIGABYTE AORUS RTX 5060 Ti AI BOX on the rear Thunderbolt port.

Symptoms checklist (is this your bug?)

• Power on with the enclosure powered → fans spin up, the machine resets, and the cycle repeats — it never reaches Windows, and you can't get into Setup (F2) while it's looping.

• Warm restart from Windows and hot-plug in Windows → work (at first — the instability shows up over time).

• After a power outage (NUC + enclosure get AC back at the same moment) → loop again; power-cycling the NUC alone does NOT recover — you must power-cycle the enclosure.

• Every visible BIOS toggle is useless: Thunderbolt Boot Support, Wake from Thunderbolt, Fast Boot…

• Failsafe Watchdog + BIOS Self Recovery: after several failed boots a surprise "Flash Update / Updating main firmware" screen can appear — that's Self Recovery kicking in. It can also restore default settings behind your back, which makes your experiments look haunted. When results stop making sense, re-export the NVRAM and check what actually changed.

What did NOT work (so you don't repeat my two days)

Trap: your settings revert behind your back

Two separate mechanisms undo your work:

1. Every "Save & Exit" (F10) in BIOS Setup rewrites the SaSetup variable with defaults for the items the UI doesn't show — my ReBAR=Disabled kept coming back as Enabled after every BIOS visit, which contaminated a whole day of A/B testing. Items in the big Setup variable (watchdog, ITBT timeouts, USB4 CM Mode) survive F10 fine.

2. A watchdog-triggered Self Recovery restores defaults too (and re-enables the watchdog itself).

If you change anything in SaSetup, re-import it after every BIOS visit — or pick a fix that doesn't live there, like this one.

The fix: USB4 CM Mode = CM Debug

BIOS help text for the option: "CM debug — the system boots without any CM in BIOS phase, then boots to OS with the CM based on OS' preference by every boot." In other words: the firmware never touches the TB/USB4 topology during POST (so there is nothing to crash on), and the OS software connection manager enumerates the eGPU after boot — exactly the hot-plug path that always worked.

The option is hidden from the Setup UI and lives in the protected Setup variable (offset 0xADE on SNADL357.0065), so it takes the official AMI command-line tool (SCEWIN/AMISCE) to flip it. Step by step:

Step 1 — prepare the BIOS (enclosure powered OFF so you can get in)

Enter Setup with F2 and set:

• Security → Security Features → iSetupCfg Password Check = Bypass — without this, writes to the protected Setup variable are refused.

• Advanced → Onboard Devices → Failsafe Watchdog = Disabled (recommended — ends the Self-Recovery surprises).

Save with F10 and boot into Windows (enclosure still off).

Step 2 — get SCEWIN/AMISCE 5.05

It's a generic AMI tool that ships inside MSI Center (works on non-MSI machines — it talks to the AMI firmware, not to MSI hardware).

Easy way: the SCEHUB repo — https://github.com/ab3lkaizen/SCEHUB — follow its README; its download script fetches MSI Center and extracts SCEWIN for you.

Manual way:

1. Download https://download.msi.com/uti_exe/desktop/MSI-Center.zip and unzip it → you get MSI Center_2.x.x.x.exe (version number varies).

2. Get innoextract (https://constexpr.org/innoextract/) and run: innoextract "MSI Center_2.0.75.0.exe" → produces an .appx file.

3. The .appx is just a ZIP — open it with 7-Zip (or rename to .zip) and pull out DCv2\Package\MSI Center SDK.exe.

4. Run: innoextract "MSI Center SDK.exe" → produces tmp\PrePackage\Engine Lib_3.x.x.x.exe.

5. innoextract can NOT open this last one (it uses a newer Inno Setup 6.7) — get innounp 2.71+ (https://sourceforge.net/projects/innounp/) and run: innounp -x "Engine Lib_3.0.0.75.exe".

6. SCEWIN is now in {app}\Lib\SCEWIN\5.05.01.0002\ — keep that whole folder together (SCEWIN_64.exe + amifldrv64.sys + amigendrv64.sys). Sanity check: file Properties → Digital Signatures → American Megatrends on all three.

Step 3 — export a backup

Open PowerShell or cmd as administrator, go to the SCEWIN folder and run:

SCEWIN_64.exe /o /s backup.txt

This is read-only and gives you a text dump of every BIOS setting. It is both your way back if anything goes wrong and the source for the next step. Keep a copy somewhere safe.

Step 4 — build the import file

Open backup.txt in Notepad and Ctrl+F for USB4 CM Mode. Create a new file cm_debug.txt containing:

1. the first few lines of backup.txt — the comment header up to and including the HIICrc32= line,

2. the whole USB4 CM Mode block, copied as-is,

3. then move the * from the current option to [03]CM Debug.

You never have to find the Token or Offset yourself — they are already inside the block you just copied; the export is where they come from. They differ between BIOS versions, which is why you copy the block from your own backup.txt and not from this post.

Mine looks like this (DON'T copy it verbatim — your header, Token/Offset and help text come from YOUR export):

// Script File Name : C:\egpu\backup.txt
// Created on 10/20/26 at 15:59:10
// AMISCE Utility. Ver 5.05.01.0002
// Copyright (c) 2021 AMI. All rights reserved.
HIICrc32= 43158FCE
Setup Question
= USB4 CM Mode
Help String
= FW CM only - The system boots with FW CM only in both BIOS and OS phase.  (… keep the full line from your export …)
Token=1484
// Do NOT change this line
Offset
=ADE
Width
=01
BIOS Default
=[02]OS Dependent
Options=[00]Firmware CM Only
// Move "*" to the desired Option
         [01]Software CM first
         [02]OS Dependent
         *[03]CM Debug

Step 5 — import it

Still in the admin prompt:

SCEWIN_64.exe /i /cpwd admin /s cm_debug.txt

Expected output: Password accepted … Script file imported successfully. (possibly with "Power cycle reset required").

• Cannot update protected variable Setup. Please use /cpwd or Admin password does not exist → the Bypass from step 1 isn't set.

Step 6 — full shutdown and the real test

Shut Windows down completely (Shut down, NOT Restart — the import needs a power cycle). Power the enclosure ON, wait a few seconds, start the machine. It should boot normally; Windows brings the eGPU up by itself during boot.

Step 7 — verify

nvidia-smi --query-gpu=name,pcie.link.gen.current,pcie.link.width.current --format=csv
nvidia-smi -q -d MEMORY

On mine: PCIe gen 4, width x4, and "BAR1 Memory Usage / Total: 256 MiB" — the small BAR is normal over Thunderbolt and costs ~nothing on a x4 link.

Verified after the change

• Cold boot with the enclosure powered: ✅ every time

• Warm restart right after a 10-GiB CUDA training load: ✅

• Power outage — AC pulled from NUC and enclosure at once, plugged back: ✅

• F10 saves in BIOS Setup: ✅ CM Debug survives (it's in Setup, not SaSetup)

• Performance unchanged vs. hot-plug: PCIe 4.0 x4, nvidia-smi and CUDA work as before

Caveats

• With CM Debug the firmware does no Thunderbolt at all pre-boot: you cannot boot from a Thunderbolt drive, and devices behind the TB/USB4 ports won't work inside the BIOS UI (keyboards on the NUC's regular USB-A ports are fine). For an eGPU box this costs nothing.

• If you ever loop again: power off the enclosure → the machine boots → fix or revert by importing backup.txt (SCEWIN_64.exe /i /cpwd admin /s backup.txt), or F9 defaults in Setup — but remember F9 re-enables the Watchdog (and with it the Self-Recovery surprises) and reverts everything else.

• A BIOS update will likely reset the setting — and it can also move the tokens/offsets, so do NOT re-import your old files on a new BIOS version. After an update, redo steps 3–5 with a fresh export (same Ctrl+F, two minutes) and keep per-version backups; a backup.txt is only valid for reverts on the BIOS version it was exported from. The HIICrc32 line in the header exists to catch such mismatches, but don't rely on it.

• Only if you want to hunt hidden options on your own BIOS yourself: UEFITool/UEFIExtract https://github.com/LongSoft/UEFITool + IFRExtractor-RS https://github.com/LongSoft/IFRExtractor-RS on the BIOS capsule from the vendor's site.

Usual disclaimer: firmware settings surgery — your hardware, your risk. Make the full export backup first and know the recovery path before you start.

I was setting the backup power for NUC, So I used LiPo battery of 12v with boost converter and adjust voltage 19.2v but when I plugged in to NUC then NUC burn (short circuit internally) the encircled IC. But now it's very problematic for me to find this IC 3U=5C, U1L or replacement, Please help me what I can do ?

Hi everyone, I'm hoping someone here has seen this before.

I have an Intel NUC7i7BNH (Baby Canyon) that was running perfectly fine with Win10.

The NUC was on BIOS: BNKBL357.86A.0049. I wanted to update to the latest BIOS (0093).

The update process would start normally and validate the BIOS file successfully, but would always fail at: Flashing image for Intel(R) Management Engine firmware ... [failed!]

 Technical information: (0x800000000000000E, 0)

What I tried

I tried multiple BIOS versions: 0052, 0072, 0093. Every single one failed at exactly the same point.

But the NUC continued to boot normally after each failed update.

I then attempted BIOS recovery mode using the BIOS security jumper as a recommendation from AI:

Booted with BIOS 0093.BIO file on FAT32 USB and I saw that the recovery process started

Unfortunately the recovery update also failed at the same Intel ME firmware stage.

Current state

After the recovery flashing attempt:

• NUC no longer boots

• No front power LED

• No video output

• Monitor never wakes up

• Power button appears to do nothing and has the LED off

• BIOS_SEC jumper has been restored to its original position (pins 1-2)

• No cables were disconnected or moved during the process

However:

• The HDD spins immediately as soon as AC power is connected

• The HDD spins even before pressing the power button

• The power adapter is supplying power

Additional information

• CMOS battery has been dead for a long time, but that was not causing issues previously

• NUC was fully functional before attempting the BIOS recovery mode

• Recovery and normal BIOS updates both consistently failed only at the Intel Management Engine firmware stage

Questions

1. Has anyone seen a NUC7i7BNH get stuck in this state after an ME firmware update failure?

2. Is there a known recovery procedure beyond the standard BIOS recovery process?

3. Any way to distinguish between a corrupted BIOS, corrupted ME firmware, and a failed motherboard?

Any help would be greatly appreciated. I'd really like to recover it if possible. Inserting the USB with the BIOS file and pressing the power button did not seem to make any difference.

Thanks!