A laptop and monitor display Windows power settings, sleep-state commands, and firmware options on a tidy desk.
Star Labs’ StarFighter Ultra earns an enthusiastic verdict from OSnews reviewer Thom Holwerda, who praises its construction, haptic trackpad and Linux experience. For Windows users, however, the more consequential finding is that Windows 11 works—but drivers, firmware settings and sleep behavior require attention.

A laptop and monitor display Windows power settings, sleep-state commands, and firmware options on a tidy desk. Premium hardware, with some everyday compromises​

Holwerda tested the Ultra configuration with an Intel Core Ultra 9 285H, Arc 140T integrated graphics, 64GB of soldered LPDDR5X memory and a 16-inch, 3840 × 2400 matte display running at up to 120Hz. The range also includes Standard Intel and AMD configurations.

His strongest praise goes to the rigid magnesium chassis and glass haptic trackpad. Less impressive were unstable-feeling keys, occasional missed off-center keystrokes and thin-sounding speakers. The detachable magnetic webcam provides an unusual physical privacy feature, although its image quality was merely adequate in his assessment.

These are useful hands-on observations, not controlled performance or reliability measurements. The distinction matters: an excellent trackpad can make a laptop delightful, but it cannot answer questions about sustained workloads or long-term durability.

Firmware is part of the ownership experience​

Star Labs’ documentation establishes an important strength beyond the review: Linux firmware updates are signed and delivered through LVFS, with unauthorized updates rejected before flashing. The company also publishes firmware source and build configurations.

The firmware exposes controls for charging, fan behavior, power limits and haptic-trackpad feel. Secure Boot, Measured Boot and a discrete TPM 2.0 are supported, but support should not be confused with an enabled security policy: Star Labs says Secure Boot is disabled by default. Intel Management Engine is likewise disabled, rather than removed, on Intel models.

The practical takeaway is straightforward: treat firmware configuration as part of deployment, not as a forgotten screen behind the boot logo.

Star Labs’ public release history reinforces that point. Version 26.08 introduced an interim option to retain older audio device IDs for Windows driver compatibility. Earlier notes document Windows audio and Device Manager fixes, alongside changes to suspend and hibernation behavior. These establish that compatibility has evolved; they do not prove that every reported problem is resolved on every configuration.

Windows sleep needs a more careful diagnosis​

Holwerda reports needing manufacturer drivers, elevated driver-install batch files, updated firmware and a Legacy audio setting. Windows sleep depleted his battery in under a day and did not automatically progress to hibernation. His Linux experience did not show the same drain.

There is an important qualification to the review’s apparent lack of Connected Standby support. Star Labs explicitly documents a Modern Standby (S0ix) firmware control, says it requires Intel ME to be enabled, and identifies ACPI S3 as the alternative when disabled. It also recommends disabling the Intel audio DSP when booting Windows. These settings are platform-dependent, so Intel instructions should not be generalized to AMD models.

Consequently, the evidence does not establish either that Modern Standby is universally unavailable or that Windows alone caused the drain. The useful conclusion is narrower: validate the exact firmware, drivers and power configuration before trusting unattended sleep.

A practical Windows 11 validation checklist​

Microsoft provides a direct way to inspect what Windows actually sees.

  1. Open Command Prompt as administrator.
  2. Check available sleep states:
    powercfg /a
    Microsoft documents this command as reporting supported states and attempting to explain why others are unavailable. Record the output before changing firmware settings.
  3. Enable hibernation if needed:
    powercfg /hibernate on
    Microsoft’s troubleshooting guidance specifies running this from an elevated command prompt.
  4. If Windows reports a reduced hibernation file, switch to a full one:
    powercfg /h /type full
    Microsoft distinguishes reduced files, which support Fast Startup, from full files, which also support hibernation. Run powercfg /a again to confirm availability.

As a validation exercise, save your work, test hibernation and resume, and compare battery levels after a known interval. Repeat after relevant firmware or driver changes rather than assuming an earlier result still applies.

The bottom line​

The StarFighter’s appeal is its Linux-first design and unusually accessible firmware controls. Its Windows path deserves evaluation on those terms—not an assumption that installation automatically means trouble-free mobile operation.

For a mixed-OS deployment, the deciding test is less glamorous than the display or chassis: does the exact configuration reliably suspend, hibernate and resume? A premium laptop should earn that trust before it disappears into a work bag.

 

References

  1. Finally, a truly premium Linux laptop: Star Labs’ StarFighter Ultra – OSnews osnews.com
  2. StarFighter Firmware & Security – Star Labs® sk.starlabs.systems
  3. Powercfg command-line options | Microsoft Learn learn.microsoft.com