Install custom Power Plan .pow file

BadAtPowershell

New Member
Messages
5
Reaction score
1
Hello, I have a custom power plan that I was looking to import and was having some issues with it. Is the only way to do this through the Paid Version, or is there a work around for doing it in the Free Version?

I checked around on the forum and didn't see anything that was able to help me with this.
 
Thank you for the response.

This looks a bit different than your photo, is it still correct? I was concerned with the copy and C:\Intel\ at the front of the file.

1755710092392.png
 
Work too by exporting settings in registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power on current install and import it in loaded NTL registry as a reg file.
 
Thank you for the response.

This looks a bit different than your photo, is it still correct? I was concerned with the copy and C:\Intel\ at the front of the file.
The Post-Setup UI has changed since then and added more columns.

"Copy" is the action NTLite will take with the submitted file. The source path for the file is where NTLite is copying the added file from, so it's your path and not mine.
 
The Post-Setup UI has changed since then and added more columns.

"Copy" is the action NTLite will take with the submitted file. The source path for the file is where NTLite is copying the added file from, so it's your path and not mine.
Thank you very much. I saw that you mentioned in the post that it was for one time only. This power config is not going to stick around if I add another user to the computer, or reboot?
 
When a power plan is imported, it's config is added to the Registry. The original file is no longer needed, and NTLite creates a wrapper script to clean up temporary files when Post-Setup is done.

The imported plan will remain inside Windows, until you run "powercfg /d" or open the Control Panel to remove it. Making other unrelated changes won't disturb the current set of power plans.
 
U
When a power plan is imported, it's config is added to the Registry. The original file is no longer needed, and NTLite creates a wrapper script to clean up temporary files when Post-Setup is done.

The imported plan will remain inside Windows, until you run "powercfg /d" or open the Control Panel to remove it. Making other unrelated changes won't disturb the current set of power plans.
Understood, thank you for explaining this for me, really helped a lot.
 
When a power plan is imported, it's config is added to the Registry. The original file is no longer needed, and NTLite creates a wrapper script to clean up temporary files when Post-Setup is done.

The imported plan will remain inside Windows, until you run "powercfg /d" or open the Control Panel to remove it. Making other unrelated changes won't disturb the current set of power plans.
Seems that the power plan did not apply, had the .pow in there and the commands set to run it but it was still default when I installed the image.
 
I forgot the part where importing a power plan creates a random new GUID assigned to it.

To avoid this, you assign a fixed GUID when importing the plan. GUID's are pseudo-random numbers to avoid namespace collision (duplicate ID's). But since the range of possible numbers is staggering, it's completely rare to have it happen.

Code:
powercfg /import %SYSTEMROOT%\Setup\custom.pow 00000000-0000-0000-0000-000000001234
powercfg /setactive 00000000-0000-0000-0000-000000001234
 
Back
Top