Set a Windows Power Plan for an Exhibition PC

Set the exhibition PC's power policy to match its operating hours, display role and recovery requirements, then test the full idle and overnight workflow. Display timeout and system sleep are separate behaviors. A blanket maximum-performance setting is not evidence that a controller, USB adapter or display will remain usable under the venue's actual conditions.

Define the intended states

Write down whether the computer should remain running while the venue is open, whether its local screen may turn off, and what happens overnight. Include the controller's network and USB dependencies. An operator screen can be dark while the computer remains ready, or the whole system can sleep and stop processing scheduled work.

Microsoft's powercfg reference documents power scheme inspection and diagnostics. The system power states reference distinguishes operating, sleeping and shutdown states. Use the actual platform's supported states rather than assuming every desktop exposes the same options.

Capture the existing configuration

Before changing settings, record the active plan and available sleep states:

powercfg /getactivescheme
powercfg /query
powercfg /a

Store the results with the hardware inventory and note whether a domain or management policy controls the settings. A local change may be replaced later by centrally managed policy, so agree ownership with the venue's IT administrator.

Change the minimum necessary behavior

Use supported Windows settings or the organization's management tool to configure display and sleep periods. If the controller must process events throughout opening hours, verify that the system remains in an operational state for that interval. Do not assume a screen saver or full screen application prevents system sleep.

Avoid disabling every peripheral power feature as a precaution. Microsoft's USB selective suspend guidance recommends keeping that mechanism enabled. If a particular adapter fails after idle, investigate its driver, hub and resume behavior separately, with a supported comparison and rollback.

Test a realistic operating cycle

On portable hardware, repeat the relevant idle checks on both mains and battery because the active plan can specify different behavior. Record charging state with each result. If a USB dock also supplies power and networking, test removal only in a controlled exercise and account for all three dependencies.

• Start from a cold boot with the normal operator account.

• Exercise a safe control transaction and record application readiness.

• Leave the PC idle longer than each relevant timeout.

• Verify a status query and any required scheduled action after idle.

• Enter the approved overnight state and run the morning recovery sequence.

• Repeat with actual displays, hubs and network adapters connected.

Watch for display enumeration changes and application positioning when screens power down. Also verify that a tablet or remote operator can still reach the controller during local display sleep. These observations are more useful than accepting the plan solely because Windows reports a familiar scheme name.

Accept the configuration when the complete opening, idle and closing cycle works under the agreed requirements, and its power consumption and thermal behavior remain appropriate for the enclosure. Record any platform specific limitations and the procedure for restoring the plan after reinstallation.

Keep the accepted settings beside the opening and closing sequence, and use power-state WOL testing if the morning workflow depends on a wake packet.