Status: read-only configuration inventory and inconclusive. Nothing was implemented or applied on the lab machine. No power plan, processor setting, Modern Standby state, hibernation, Fast Startup, Intel Dynamic Tuning, HP firmware, service, driver, task, policy, registry, security, update, recovery, or management setting changed.

The evidence question

Does the current Windows scheme, user power mode, processor policy, sleep-state, and Intel platform-policy inventory identify one supported change that improves startup or responsiveness on this exact ZBook?

No. The active base scheme is Balanced, while the Windows 11 user-configured mode is already Best performance on AC and Best power efficiency on battery. The processor policy exposes a 5 percent minimum and 100 percent maximum on both power sources.

Those values define configuration bounds. They do not measure current frequency, effective mode, sustained performance, readiness, responsiveness, energy, fan state, or temperature.

Exact observed power configuration

SurfacePlugged inOn batterySupport meaning
Base power schemeBalancedBalancedActive scheme reported by powercfg
User-configured Windows 11 modeBest performanceBest power efficiencyUser vote; other signals can override it
Minimum processor state5%5%Supported range: 0–100%
Maximum processor state100%100%Supported range: 0–100%
Effective runtime modeNot measuredNot measuredRequired at each accepted run boundary

The Windows APIs returned success for both user-configured modes. Microsoft describes that configured mode as a vote; thermal, firmware, battery, workload, and other platform signals can prevent it from becoming the effective runtime mode.

A second plan named My Custom Plan 1 exists but is inactive. Microsoft notes that a custom plan can make the Windows power-mode selector unavailable. Its presence is not a reason to delete or activate it.

The public alias inventory exposed minimum and maximum processor policy. A query for PERFEPP returned no setting record, even though powercfg exited successfully. No hidden energy-performance-preference value was invented.

Modern Standby and Fast Startup are different workflows

powercfg /a reported S0 Low Power Idle with network connectivity as the available standby state. S1 through S3 are unavailable under this platform's Modern Standby model. Forcing S3 with an undocumented registry workaround is outside the firmware support boundary.

Hibernation is disabled. That also makes Hibernate, Hybrid Sleep, and Fast Startup unavailable.

Microsoft documents Fast Startup as a hybrid shutdown: the user is logged off, but the kernel session is stored in a hibernation file. It is not a cold boot or Restart. Enabling it would create or resize hiberfil.sys, change available transitions, consume storage, and add driver, update, recovery, and rollback requirements.

A later experiment must measure cold boot, Fast Startup, Restart, Modern Standby resume, and hibernation resume separately. Calling all of them “startup” would hide which path changed.

Intel and HP platform boundary

The Intel Dynamic Tuning service was running with automatic start. Intel describes Dynamic Tuning as platform software that adapts power and performance using temperature and usage mode.

No DTT configuration, HP firmware power policy, adapter limit, fan state, CPU temperature, effective power mode, or platform power limit was read. Disabling or bypassing the service would remove part of the OEM thermal and power control system without evidence.

Microsoft's processor power-management guidance says its algorithms combine the performance-state engine, core parking, and platform-specific controls. It directs deeper tuning toward the silicon vendor. A copied “100% minimum processor” recipe is not model-specific guidance.

Evidence ledger

Documented facts

  • Windows 11 supports Best power efficiency, Balanced, and Best performance user modes.
  • The configured mode can be overridden by other system signals.
  • Processor minimum/maximum are policy percentages, not measured frequency.
  • Fast Startup stores the kernel session and differs from cold boot and Restart.

Lab measurements

One non-elevated configuration inventory was captured on AC at 99 percent charge. No startup, readiness, responsiveness, thermal, energy, effective-mode, or overhead measurement ran.

Hypotheses

Best performance may reduce some AC latency, battery efficiency may trade response for energy, and Fast Startup may reduce one hybrid-shutdown path. None is tested.

Unresolved questions

  • What effective mode is active at every run boundary?
  • What latency, energy, and thermal rule decides a winner?
  • What HP/Intel limits apply to this SKU and BIOS?
  • Was hibernation intentionally disabled, and can exact rollback be proven?

Compatibility and rollback status

The observation applies only to the recorded HP ZBook Firefly 14 inch G8 SKU, Windows 11 Pro build 26200, BIOS T76 01.24.02, AC/battery observation, schemes, configured modes, and current Intel DTT service state.

No configuration changed, so rollback is not applicable. A future power change still requires support detection, exact original-state capture, dry run, apply, state and workflow verification, structured logging, idempotence, exact rollback, rollback verification, and reboot-persistence testing.

A future comparison must separate AC and battery workflows and record charge, adapter, thermal readiness, ambient condition, active scheme, effective mode, DTT/HP platform state, workload reset, raw run order, medians, energy, and side effects.

Primary sources

All sources were retrieved July 27, 2026.

YouTube briefing

Presenter: This hour read the ZBook's supported power surfaces without changing them.

Balanced is the base plan, Best performance is already selected for AC, and Best power efficiency is selected for battery. That configured mode is a vote, not proof of the effective runtime state or a faster workflow.

Modern Standby is the supported sleep model. Hibernation is disabled, so Fast Startup is unavailable. Fast Startup is a hybrid shutdown, not a cold boot or Restart, and must be measured separately.

Intel Dynamic Tuning remained running. No power, sleep, firmware, service, or hidden setting changed. Layer 7 next investigates security and isolation overhead without reducing protection.

Read the complete source script

Source and next layer

The next hourly cycle position is layer 7: security and isolation overhead without reducing protection.

Back to all development updates