Windows 11 Optimization for Music Production: A Practical Setup

Why does Windows 11 need tweaking for music production?

Windows 11 ships tuned for battery life, background updates and general use, not for delivering audio in tiny, perfectly timed chunks. Focusrite's support team puts it plainly: Windows caters to many users and applications and is not configured for optimal audio performance by default.^[2]

The symptoms are familiar: pops and clicks during playback, crackles that appear only when you lower the buffer, an interface that disconnects mid-session, or a DAW that stutters when the browser is open. Most of these come from power saving, background software or a single misbehaving driver, and all three can be fixed without buying new hardware.

Work in order. Change one setting, test for a few minutes with a real project, and note the result. If you tweak ten things at once and the crackles stop, you will not know which change mattered, and you cannot undo the ones that did nothing. If you are still choosing a platform, Mac vs PC for music production covers that decision.

Which power settings should you change first?

Set Windows to its highest performance mode and stop it from throttling the CPU, USB ports and PCIe devices. Power saving that is invisible in a web browser can cause audible dropouts at low buffer sizes.

Ableton's Windows guide starts with the power mode: open Settings with Win + I, go to System, then Power & battery, and choose Best performance.^[1] Focusrite goes further and recommends a custom power plan based on High Performance, with deeper settings changed inside it.^[2]

1. Create a custom plan
   Search Start for Choose a power plan, click Create a power plan, pick High Performance and name it something like Audio Workstation. Set display off and sleep to Never.
2. Open advanced settings
   Click Change plan settings next to your new plan, then Change advanced power settings.
3. Disable USB selective suspend
   Expand USB settings, then USB selective suspend setting, and choose Disabled. On a laptop, set both On battery and Plugged in.
4. Disable PCIe power management
   Expand PCI Express, then Link State Power Management, and set it to Off or Disabled.
5. Lock the processor state
   Expand Processor power management and set both Minimum and Maximum processor state to 100 percent.
6. Test a real session
   Load a project that used to crackle, set your usual recording buffer and play it for several minutes before changing anything else.

These plan settings come straight from Focusrite's guide.^[2] On a laptop they cost battery life and raise fan noise, so switch back to a balanced plan when you are not making music.

How do you stop USB power saving from interrupting your interface?

Turn off the per-device power switch in Device Manager and connect the interface straight to the computer with a short cable. USB selective suspend in the power plan covers part of the problem; Device Manager holds a second setting that can still cut power to the port.

Focusrite's steps: right-click Start, open Device Manager, expand Universal Serial Bus controllers, open each device's Properties, go to the Power Management tab and untick Allow the computer to turn off this device to save power. Skip devices without that tab.^[2]

The same guide recommends a cable shorter than 2 meters (6 feet), no USB hubs or adapters, and testing every port, since performance can vary from port to port.^[2] On desktops, rear ports wired directly to the motherboard are usually the safest first test.

Which background apps and Windows features should you turn off?

Disable startup apps you do not need, uninstall bloatware, and close browsers and streaming apps while you record. Every process that wakes up in the background competes with your DAW for CPU time.

Ableton recommends reducing startup programs and even suggests a freshly installed operating system for the fewest extra processes.^[1] Focusrite specifically advises disabling Copilot or Cortana at startup because they can try to use your interface's inputs in the middle of a recording.^[2]

The system sounds, exclusive mode, processor scheduling and disk space items all come from Focusrite's Windows guide.^[2] Inside the DAW, CPU savings come from freezing and bouncing; CPU optimization for large FL Studio projects covers that side.

Which drivers and updates matter most?

Your audio interface driver comes first, then GPU, chipset and BIOS. Ableton lists Windows, the DAW, the graphics driver, interface software and firmware, MIDI controller drivers and third-party plugins as things to keep fully updated.^[1]

Use the manufacturer's own ASIO driver for your interface. If it will not load or keeps dropping out, work through the Windows ASIO driver troubleshooting guide rather than switching to a generic driver.

• GPU driver Focusrite notes that AMD and NVIDIA offer PRO and Studio driver branches aimed at professional applications, which may be more stable than gaming drivers.^[2]
• BIOS Focusrite has seen problems on systems running a BIOS that predates Windows 11 and recommends updating in that case. Follow your motherboard maker's instructions exactly.
• C-states CPU power-saving states can hurt audio performance on some systems. Disabling them is a BIOS change; if you are not comfortable in the BIOS, ask your PC maker or a technician.
• Device Manager Right-click each device and choose Update driver to catch anything Windows Update missed.

How do you check your PC with LatencyMon?

LatencyMon is a free-for-home-use tool from Resplendence that tells you whether your Windows system is suitable for real-time audio and which driver is to blame if it is not. It measures kernel timer latency, DPC and ISR execution times and hard pagefaults, then names the drivers and processes responsible.^[3]

DPCs and ISRs are short tasks that drivers ask the CPU to run immediately. If a network or graphics driver holds the CPU too long, your audio driver misses its deadline and you hear a click, even though overall CPU use looks low.

1. Close the DAW
   Run the first test with your normal background state: Wi-Fi, Bluetooth and anything else you usually leave on.
2. Start monitoring
   Open LatencyMon and click Start. Let it run for at least 10 minutes while you browse, stream a video or open files the way you normally would, then click Stop.
3. Read the verdict
   The Main tab gives a conclusion at the top. Resplendence rates a system suitable when all DPC and ISR routines stay below 2000 microseconds, doubtful between 2000 and 4000, and unsuitable above that, while noting those limits are chosen arbitrarily.^[7]
4. Find the responsible driver
   Open the Stats tab for the detailed report and note which driver has the highest execution time. Resplendence gives the example that tcpip.sys or ndis.sys usually points to a wireless network adapter.^[7]
5. Test one change
   Disable that device in Device Manager (for Wi-Fi, switch to an Ethernet cable) or update its driver, then run LatencyMon again. Keep the change only if the numbers improve. Another driver may still show up next.

Once LatencyMon is clean, go back to the DAW and find the lowest stable buffer. The numbers behind that setting are explained in latency and buffer size explained.

Should you add antivirus exclusions for your DAW?

Keep Windows Security running and add narrow exclusions only for folders full of trusted audio, such as sample libraries and project folders. Real-time scanning of thousands of samples can slow library loading, but switching protection off leaves the machine exposed.

Vendors differ on how far to go. Ableton suggests adding Live to the antivirus allow list,^[1] Focusrite warns that third-party antivirus can interfere with interface drivers and suggests Windows Security may be more stable,^[2] and Avid goes as far as recommending disabling antivirus before following its Windows optimization guides.^[6] Microsoft's own advice for slowdowns is to check the software vendor's knowledge base for known antivirus issues.^[5]

In Windows Security, go to Virus & threat protection, Manage settings, then Add or remove exclusions, where you can exclude a file, folder, file type or process. Microsoft warns that exclusions mean Defender no longer checks those files, which could leave your device vulnerable, and that they apply only to real-time scanning.^[4]

• Reasonable to exclude Sample library folders from official installers, your DAW project folder, and recording scratch folders.
• Do not exclude Downloads, whole drives, file types like .wav or .dll, and plugin folders that contain software you are not sure about. Know where your plugins live first: see where VST plugins are stored.
• Never Turn off protection to run cracked plugins or installers. They come from unknown sources with no accountability, and no latency gain is worth that risk.