blocks|key|4114763|text|通过一些额外的努力，您可以使用标准++实现所需的行为，方法是使用自定义的、始终处于状态的电源方案，该是根据需要创建的，并在脚本运行期间暂时激活：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4114764|注意：|4114765|4114766|在下面查找评论#+YOUR+CODE+GOES+HERE+.|unordered-list-item|CODE|4114767|4114768|有关基于this+answer.的.NET+/+Windows的替代，请参阅|4114769|4114770|4114771|#+Define+the+properties+of+a+custom+power+scheme,+to+be+created+on+demand.
$schemeGuid+=+'e03c2dc5-fac9-4f5d-9948-0a2fb9009d67'+#+randomly+created+with+New-Guid
$schemeName+=+'Always+on'
$schemeDescr+=+'Custom+power+scheme+to+keep+the+system+awake+indefinitely.'

#+Helper+function+that+ensures+that+the+most+recent+powercfg.exe+call+succeeded.
function+assert-ok+{+if+($LASTEXITCODE+-ne+0)+{+throw+}+}

#+Determine+the+currently+active+power+scheme,+so+it+can+be+restored+at+the+end.
$prevGuid+=+(powercfg+-getactivescheme)+-replace+'%5E.%2B([-0-9a-f]{36}).%2B$',+'$1'
assert-ok

#+Temporarily+activate+a+custom+always-on+power+scheme;+create+it+on+demand.
try+{

++#+Try+to+change+to+the+custom+scheme.
++powercfg+-setactive+$schemeGuid+2>$null
++if+($LASTEXITCODE+-ne+0)+{+#+Changing+failed+->+create+the+scheme+on+demand.
++++#+Clone+the+'High+performance'+scheme.
++++$null+=+powercfg+-duplicatescheme+SCHEME_MIN+$schemeGuid
++++assert-ok
++++#+Change+its+name+and+description.
++++$null+=+powercfg+-changename+$schemeGuid+$schemeName+$schemeDescr
++++#+Activate+it
++++$null+=+powercfg+-setactive+$schemeGuid
++++assert-ok
++++#+Change+all+settings+to+be+always+on.
++++#+Note:+
++++#+++*+Remove+'monitor-timeout-ac',+'monitor-timeout-dc'+if+it's+OK
++++#+++++for+the+*display*+to+go+to+sleep.
++++#+++*+If+you+make+changes+here,+you'll+have+to+run+powercfg+-delete+$schemeGuid+
++++#+++++or+delete+the+'Always+on'+scheme+via+the+GUI+for+changes+to+take+effect.
++++#+++*+On+an+AC-only+machine+(desktop,+server)+the+*-ac+settings+aren't+needed.
++++$settings+=+'monitor-timeout-ac',+'monitor-timeout-dc',+'disk-timeout-ac',+'disk-timeout-dc',+'standby-timeout-ac',+'standby-timeout-dc',+'hibernate-timeout-ac',+'hibernate-timeout-dc'
++++foreach+($setting+in+$settings)+{
++++++powercfg+-change+$setting+0+#+0+==+Never
++++++assert-ok
++++}
++}
++
++#+YOUR+CODE+GOES+HERE.
++#+In+this+sample,+wait+for+the+user+to+press+Enter+before+exiting.
++#+Before+that,+the+'Always+on'+power+scheme+should+remain+in
++#+effect,+and+the+machine+shouldn't+go+to+sleep.
++pause

}+finally+{+#+Executes+even+when+the+script+is+aborted+with+Ctrl-C.
++#+Reactivate+the+previously+active+power+scheme.
++powercfg+-setactive+$prevGuid
}|code-block|syntax|javascript|4114772|您可以从上面创建一个包装器脚本，将要执行的脚本的路径传递给该脚本。|4114773|4114774|如果您不介意修改当前活动的方案，可以使用Kerr's+answer中所示的方法，使用每个设置的powercfg+-change+<setting>+<value-in-minutes>调用(/x+/+-x是/change+/-change的别名)，在每个调用中使用以下d30名称；传递0作为<value-in-minutes>表示的<value-in-minutes>。|4114775|4114776|monitor-timeout-ac|4114777|monitor-timeout-dc|4114778|disk-timeout-ac|4114779|disk-timeout-dc|4114780|standby-timeout-ac|4114781|standby-timeout-dc|4114782|hibernate-timeout-ac|4114783|hibernate-timeout-dc|4114784|4114785|但是请注意，这样的更改是持久化的，因此可能希望稍后恢复原始值，这需要额外的努力。|4114786|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/powercfg-command-line-options|1|https://stackoverflow.com/a/65162017/45375|2|https://stackoverflow.com/users/3996028/kerr^0|F|2|W|G|I|1|0|0|0|0|7|L|0|0|H|H|4|B|1|0|0|0|0|0|X|0|0|0|55|1B|19|2N|2|2S|2|2V|7|34|7|3Q|1F|K|D|2|0|0|0|I|0|I|0|0|I|0|I|0|0|F|0|F|0|0|F|0|F|0|0|I|0|I|0|0|I|0|I|0|0|K|0|K|0|0|K|0|K|0|0|0|14|0|14|0^^$0|@$1|2|3|4|5|6|7|1X|8|@$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]]|D|@$9|22|A|23|1|24]]|E|$]]|$1|F|3|G|5|6|7|25|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|27|8|@$9|28|A|29|B|L]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|2A|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|2B|8|@$9|2C|A|2D|B|C]]|D|@$9|2E|A|2F|1|2G]]|E|$]]|$1|P|3|-4|5|K|7|2H|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|2I|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|2J|8|@]|D|@]|E|$U|V]]|$1|W|3|X|5|6|7|2K|8|@$9|2L|A|2M|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|2N|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2O|8|@$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|L]|$9|2T|A|2U|B|L]|$9|2V|A|2W|B|L]|$9|2X|A|2Y|B|L]|$9|2Z|A|30|B|L]|$9|31|A|32|B|L]]|D|@$9|33|A|34|1|35]]|E|$]]|$1|11|3|-4|5|6|7|36|8|@]|D|@]|E|$]]|$1|12|3|13|5|K|7|37|8|@$9|38|A|39|B|C]|$9|3A|A|3B|B|L]]|D|@]|E|$]]|$1|14|3|15|5|K|7|3C|8|@$9|3D|A|3E|B|C]|$9|3F|A|3G|B|L]]|D|@]|E|$]]|$1|16|3|17|5|K|7|3H|8|@$9|3I|A|3J|B|C]|$9|3K|A|3L|B|L]]|D|@]|E|$]]|$1|18|3|19|5|K|7|3M|8|@$9|3N|A|3O|B|C]|$9|3P|A|3Q|B|L]]|D|@]|E|$]]|$1|1A|3|1B|5|K|7|3R|8|@$9|3S|A|3T|B|C]|$9|3U|A|3V|B|L]]|D|@]|E|$]]|$1|1C|3|1D|5|K|7|3W|8|@$9|3X|A|3Y|B|C]|$9|3Z|A|40|B|L]]|D|@]|E|$]]|$1|1E|3|1F|5|K|7|41|8|@$9|42|A|43|B|C]|$9|44|A|45|B|L]]|D|@]|E|$]]|$1|1G|3|1H|5|K|7|46|8|@$9|47|A|48|B|C]|$9|49|A|4A|B|L]]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|4B|8|@]|D|@]|E|$]]|$1|1J|3|1K|5|6|7|4C|8|@$9|4D|A|4E|B|C]|$9|4F|A|4G|B|L]]|D|@]|E|$]]|$1|1L|3|-4|5|6|7|4H|8|@]|D|@]|E|$]]]|1M|$1N|$5|1O|1P|1Q|E|$1R|1S]]|1T|$5|1O|1P|1Q|E|$1R|1U]]|1V|$5|1O|1P|1Q|E|$1R|1W]]]]

With some extra effort, you can achieve the desired behavior with the standard <a href="https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/powercfg-command-line-options" rel="nofollow noreferrer"><code>powercfg.exe</code> utility</a>, by using a custom, always-on power scheme that is created on demand and temporarily activated for the duration of your script run:
Note:
<ul>
<li>Look for comment <code># YOUR CODE GOES HERE</code> below.
</li>
<li>For a .NET / Windows API-based alternative, see <a href="https://stackoverflow.com/a/65162017/45375">this answer</a>.
</li>
</ul>
<pre class="lang-sh prettyprint-override"><code># Define the properties of a custom power scheme, to be created on demand.
$schemeGuid = 'e03c2dc5-fac9-4f5d-9948-0a2fb9009d67' # randomly created with New-Guid
$schemeName = 'Always on'
$schemeDescr = 'Custom power scheme to keep the system awake indefinitely.'

# Helper function that ensures that the most recent powercfg.exe call succeeded.
function assert-ok { if ($LASTEXITCODE -ne 0) { throw } }

# Determine the currently active power scheme, so it can be restored at the end.
$prevGuid = (powercfg -getactivescheme) -replace '^.+([-0-9a-f]{36}).+$', '$1'
assert-ok

# Temporarily activate a custom always-on power scheme; create it on demand.
try {

 # Try to change to the custom scheme.
 powercfg -setactive $schemeGuid 2&gt;$null
 if ($LASTEXITCODE -ne 0) { # Changing failed -&gt; create the scheme on demand.
 # Clone the 'High performance' scheme.
 $null = powercfg -duplicatescheme SCHEME_MIN $schemeGuid
 assert-ok
 # Change its name and description.
 $null = powercfg -changename $schemeGuid $schemeName $schemeDescr
 # Activate it
 $null = powercfg -setactive $schemeGuid
 assert-ok
 # Change all settings to be always on.
 # Note: 
 # * Remove 'monitor-timeout-ac', 'monitor-timeout-dc' if it's OK
 # for the *display* to go to sleep.
 # * If you make changes here, you'll have to run powercfg -delete $schemeGuid 
 # or delete the 'Always on' scheme via the GUI for changes to take effect.
 # * On an AC-only machine (desktop, server) the *-ac settings aren't needed.
 $settings = 'monitor-timeout-ac', 'monitor-timeout-dc', 'disk-timeout-ac', 'disk-timeout-dc', 'standby-timeout-ac', 'standby-timeout-dc', 'hibernate-timeout-ac', 'hibernate-timeout-dc'
 foreach ($setting in $settings) {
 powercfg -change $setting 0 # 0 == Never
 assert-ok
 }
 }
 
 # YOUR CODE GOES HERE.
 # In this sample, wait for the user to press Enter before exiting.
 # Before that, the 'Always on' power scheme should remain in
 # effect, and the machine shouldn't go to sleep.
 pause

} finally { # Executes even when the script is aborted with Ctrl-C.
 # Reactivate the previously active power scheme.
 powercfg -setactive $prevGuid
}
</code></pre>
You could create a wrapper script from the above, to which you pass the path of the script to execute.
<hr />
If you don't mind modifying the currently active scheme, you can use the approach shown in <a href="https://stackoverflow.com/users/3996028/kerr">Kerr's answer</a>, using per-setting <code>powercfg -change &lt;setting&gt; &lt;value-in-minutes&gt;</code> calls (<code>/x</code> / <code>-x</code> is an alias of <code>/change</code> / <code>-change</code>), using one of the following <code>&lt;setting&gt;</code> names in each call; passing <code>0</code> as <code>&lt;value-in-minutes&gt;</code> represents never:
<ul>
<li><code>monitor-timeout-ac</code></li>
<li><code>monitor-timeout-dc</code></li>
<li><code>disk-timeout-ac</code></li>
<li><code>disk-timeout-dc</code></li>
<li><code>standby-timeout-ac</code></li>
<li><code>standby-timeout-dc</code></li>
<li><code>hibernate-timeout-ac</code></li>
<li><code>hibernate-timeout-dc</code></li>
</ul>
Note, however, that such changes are persistent, so you may want to restore the original values later, which takes extra effort.

blocks|key|2728177|text|提供基于.NET+/+Windows的替代以替代powercfg.exe-based+solution|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2728178|注意：|2728179|2728180|解决方案使用Add-Type按需编译C#代码，这将在当前会话中首次调用代码时造成性能损失。|unordered-list-item|2728181|2728182|2728183|在同一会话中调用::StayAwake($false)是非常重要的，以便清除所发出的电源请求。|2728184|2728185|2728186|在下面查找评论#+YOUR+CODE+GOES+HERE+.|2728187|2728188|这个解决方案是由MarkusEgle.从this+C#+answer中改编的。|2728189|Add-Type+-ErrorAction+Stop+-Name+PowerUtil+-Namespace+Windows+-MemberDefinition+@'

++++//+Member+variables.
++++static+IntPtr+_powerRequest;
++++static+bool+_mustResetDisplayRequestToo;

++++//+P/Invoke+function+declarations.
++++[DllImport("kernel32.dll")]
++++static+extern+IntPtr+PowerCreateRequest(ref+POWER_REQUEST_CONTEXT+Context);

++++[DllImport("kernel32.dll")]
++++static+extern+bool+PowerSetRequest(IntPtr+PowerRequestHandle,+PowerRequestType+RequestType);

++++[DllImport("kernel32.dll")]
++++static+extern+bool+PowerClearRequest(IntPtr+PowerRequestHandle,+PowerRequestType+RequestType);

++++[DllImport("kernel32.dll",+CharSet+=+CharSet.Auto,+SetLastError+=+true,+ExactSpelling+=+true)]
++++static+extern+int+CloseHandle(IntPtr+hObject);

++++//+Availablity+Request+Enumerations+and+Constants
++++enum+PowerRequestType
++++{
++++++++PowerRequestDisplayRequired+=+0,
++++++++PowerRequestSystemRequired,
++++++++PowerRequestAwayModeRequired,
++++++++PowerRequestMaximum
++++}

++++const+int+POWER_REQUEST_CONTEXT_VERSION+=+0;
++++const+int+POWER_REQUEST_CONTEXT_SIMPLE_STRING+=+0x1;

++++//+Availablity+Request+Structures
++++//+Note:++Windows+defines+the+POWER_REQUEST_CONTEXT+structure+with+an
++++//+internal+union+of+SimpleReasonString+and+Detailed+information.
++++//+To+avoid+runtime+interop+issues,+this+version+of+
++++//+POWER_REQUEST_CONTEXT+only+supports+SimpleReasonString.++
++++//+To+use+the+detailed+information,
++++//+define+the+PowerCreateRequest+function+with+the+first+
++++//+parameter+of+type+POWER_REQUEST_CONTEXT_DETAILED.
++++[StructLayout(LayoutKind.Sequential,+CharSet+=+CharSet.Unicode)]
++++struct+POWER_REQUEST_CONTEXT
++++{
++++++++public+UInt32+Version;
++++++++public+UInt32+Flags;
++++++++[MarshalAs(UnmanagedType.LPWStr)]
++++++++public+string+SimpleReasonString;
++++}

++++///+<summary>
++++///+Prevents+the+system+from+going+to+sleep,+by+default+including+the+display.
++++///+</summary>
++++///+<param+name="enable">
++++///+++True+to+turn+on,+False+to+turn+off.+Passing+True+must+be+paired+with+a+later+call+passing+False.
++++///+++If+you+pass+True+repeatedly,+subsequent+invocations+take+no+actions+and+ignore+the+parameters.
++++///+++If+you+pass+False,+the+remaining+paramters+are+ignored.
++++//++++If+you+pass+False+without+having+passed+True+earlier,+no+action+is+performed.
++++////+</param>
++++///+<param+name="includeDisplay">True+to+also+keep+the+display+awake;+defaults+to+True.</param>
++++///+<param+name="reasonString">
++++///+++A+string+describing+why+the+system+is+being+kept+awake;+defaults+to+the+current+process'+command+line.
++++///+++This+will+show+in+the+output+from+`powercfg+-requests`+(requires+elevation).
++++///+</param>
++++public+static+void+StayAwake(bool+enable,+bool+includeDisplay+=+true,+string+reasonString+=+null)
++++{
++++++
++++++if+(enable)
++++++{

++++++++//+Already+enabled:+quietly+do+nothing.
++++++++if+(_powerRequest+!=+IntPtr.Zero)+{+return;+}

++++++++//+Configure+the+reason+string.
++++++++POWER_REQUEST_CONTEXT+powerRequestContext;
++++++++powerRequestContext.Version+=+POWER_REQUEST_CONTEXT_VERSION;
++++++++powerRequestContext.Flags+=+POWER_REQUEST_CONTEXT_SIMPLE_STRING;
++++++++powerRequestContext.SimpleReasonString+=+reasonString+??+System.Environment.CommandLine;+//+The+reason+for+making+the+power+request.

++++++++//+Create+the+request+(returns+a+handle).
++++++++_powerRequest+=+PowerCreateRequest(ref+powerRequestContext);

++++++++//+Set+the+request(s).
++++++++PowerSetRequest(_powerRequest,+PowerRequestType.PowerRequestSystemRequired);
++++++++if+(includeDisplay)+{+PowerSetRequest(_powerRequest,+PowerRequestType.PowerRequestDisplayRequired);+}
++++++++_mustResetDisplayRequestToo+=+includeDisplay;

++++++}
++++++else
++++++{

++++++++//+Not+previously+enabled:+quietly+do+nothing.
++++++++if+(_powerRequest+==+IntPtr.Zero)+{+return;+}

++++++++//+Clear+the+request
++++++++PowerClearRequest(_powerRequest,+PowerRequestType.PowerRequestSystemRequired);
++++++++if+(_mustResetDisplayRequestToo)+{+PowerClearRequest(_powerRequest,+PowerRequestType.PowerRequestDisplayRequired);+}
++++++++CloseHandle(_powerRequest);
++++++++_powerRequest+=+IntPtr.Zero;

++++++}
++}

++//+Overload+that+allows+passing+a+reason+string+while+defaulting+to+keeping+the+display+awake+too.
++public+static+void+StayAwake(bool+enable,+string+reasonString)
++{
++++StayAwake(enable,+false,+reasonString);
++}

'@

try+{

++#+Create+power+request(s)+that+keep+the+system+awake.
++#+Pass+$false+as+the+2nd+argument+to+allow+the+display+to+go+to+sleep.
++#+The+reason+string+is+visible+when+you+run+`powercfg.exe+-requests`+to+show+current+requests
++#+(requires+elevation).
++#+Defaults:+keep+the+display+awake+too,+use+the+current+process'+command+line+as+the+reason+string.
++[Windows.PowerUtil]::StayAwake($true,+$true,+"Running+long-running+script+$PSCommandPath.")

++#+YOUR+CODE+GOES+HERE.
++#+In+this+sample,+wait+for+the+user+to+press+Enter+before+exiting.
++#+Before+that,+the+system+should+stay+awake+indefinitely.
++pause

}+finally+{+#+This+ensures+that+the+previous+scheme+is+restored+even+when+the+script+is+aborted+with+Ctrl-C.

++#+Clear+the+power+requests.
++[Windows.PowerUtil]::StayAwake($false)

}|code-block|syntax|javascript|2728190|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/65161413/45375|1|https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/add-type|2|https://stackoverflow.com/users/3090544/markusegle|3|https://stackoverflow.com/a/20996135/45375^0|4|H|O|C|O|R|0|0|0|0|6|8|6|8|1|0|0|0|8|J|0|0|0|7|L|0|0|8|A|2|K|E|3|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|D]]|E|@$9|1L|A|1M|1|1N]]|F|$]]|$1|G|3|H|5|6|7|1O|8|@]|E|@]|F|$]]|$1|I|3|-4|5|6|7|1P|8|@]|E|@]|F|$]]|$1|J|3|K|5|L|7|1Q|8|@$9|1R|A|1S|B|D]]|E|@$9|1T|A|1U|1|1V]]|F|$]]|$1|M|3|-4|5|6|7|1W|8|@]|E|@]|F|$]]|$1|N|3|-4|5|6|7|1X|8|@]|E|@]|F|$]]|$1|O|3|P|5|L|7|1Y|8|@$9|1Z|A|20|B|D]]|E|@]|F|$]]|$1|Q|3|-4|5|6|7|21|8|@]|E|@]|F|$]]|$1|R|3|-4|5|6|7|22|8|@]|E|@]|F|$]]|$1|S|3|T|5|L|7|23|8|@$9|24|A|25|B|D]]|E|@]|F|$]]|$1|U|3|-4|5|6|7|26|8|@]|E|@]|F|$]]|$1|V|3|W|5|6|7|27|8|@]|E|@$9|28|A|29|1|2A]|$9|2B|A|2C|1|2D]]|F|$]]|$1|X|3|Y|5|Z|7|2E|8|@]|E|@]|F|$10|11]]|$1|12|3|-4|5|6|7|2F|8|@]|E|@]|F|$]]]|13|$14|$5|15|16|17|F|$18|19]]|1A|$5|15|16|17|F|$18|1B]]|1C|$5|15|16|17|F|$18|1D]]|1E|$5|15|16|17|F|$18|1F]]]]

To offer a .NET / Windows API-based alternative to the <a href="https://stackoverflow.com/a/65161413/45375"><code>powercfg.exe</code>-based solution</a>:
Note:
<ul>
<li>The solution uses <a href="https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/add-type" rel="nofollow noreferrer"><code>Add-Type</code></a> to compile C# code on demand, which incurs a performance penalty the first time the code is called in the current session.
</li>
<li>It is important to call <code>::StayAwake($false)</code> in the same session in order to clear the power requests made.
</li>
<li>Look for comment <code># YOUR CODE GOES HERE</code> below.
</li>
<li>This solution was adapted from <a href="https://stackoverflow.com/a/20996135/45375">this C# answer</a> by <a href="https://stackoverflow.com/users/3090544/markusegle">MarkusEgle</a>.
</li>
</ul>
<pre><code>Add-Type -ErrorAction Stop -Name PowerUtil -Namespace Windows -MemberDefinition @'

 // Member variables.
 static IntPtr _powerRequest;
 static bool _mustResetDisplayRequestToo;

 // P/Invoke function declarations.
 [DllImport(&quot;kernel32.dll&quot;)]
 static extern IntPtr PowerCreateRequest(ref POWER_REQUEST_CONTEXT Context);

 [DllImport(&quot;kernel32.dll&quot;)]
 static extern bool PowerSetRequest(IntPtr PowerRequestHandle, PowerRequestType RequestType);

 [DllImport(&quot;kernel32.dll&quot;)]
 static extern bool PowerClearRequest(IntPtr PowerRequestHandle, PowerRequestType RequestType);

 [DllImport(&quot;kernel32.dll&quot;, CharSet = CharSet.Auto, SetLastError = true, ExactSpelling = true)]
 static extern int CloseHandle(IntPtr hObject);

 // Availablity Request Enumerations and Constants
 enum PowerRequestType
 {
 PowerRequestDisplayRequired = 0,
 PowerRequestSystemRequired,
 PowerRequestAwayModeRequired,
 PowerRequestMaximum
 }

 const int POWER_REQUEST_CONTEXT_VERSION = 0;
 const int POWER_REQUEST_CONTEXT_SIMPLE_STRING = 0x1;

 // Availablity Request Structures
 // Note: Windows defines the POWER_REQUEST_CONTEXT structure with an
 // internal union of SimpleReasonString and Detailed information.
 // To avoid runtime interop issues, this version of 
 // POWER_REQUEST_CONTEXT only supports SimpleReasonString. 
 // To use the detailed information,
 // define the PowerCreateRequest function with the first 
 // parameter of type POWER_REQUEST_CONTEXT_DETAILED.
 [StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
 struct POWER_REQUEST_CONTEXT
 {
 public UInt32 Version;
 public UInt32 Flags;
 [MarshalAs(UnmanagedType.LPWStr)]
 public string SimpleReasonString;
 }

 /// &lt;summary&gt;
 /// Prevents the system from going to sleep, by default including the display.
 /// &lt;/summary&gt;
 /// &lt;param name=&quot;enable&quot;&gt;
 /// True to turn on, False to turn off. Passing True must be paired with a later call passing False.
 /// If you pass True repeatedly, subsequent invocations take no actions and ignore the parameters.
 /// If you pass False, the remaining paramters are ignored.
 // If you pass False without having passed True earlier, no action is performed.
 //// &lt;/param&gt;
 /// &lt;param name=&quot;includeDisplay&quot;&gt;True to also keep the display awake; defaults to True.&lt;/param&gt;
 /// &lt;param name=&quot;reasonString&quot;&gt;
 /// A string describing why the system is being kept awake; defaults to the current process' command line.
 /// This will show in the output from `powercfg -requests` (requires elevation).
 /// &lt;/param&gt;
 public static void StayAwake(bool enable, bool includeDisplay = true, string reasonString = null)
 {
 
 if (enable)
 {

 // Already enabled: quietly do nothing.
 if (_powerRequest != IntPtr.Zero) { return; }

 // Configure the reason string.
 POWER_REQUEST_CONTEXT powerRequestContext;
 powerRequestContext.Version = POWER_REQUEST_CONTEXT_VERSION;
 powerRequestContext.Flags = POWER_REQUEST_CONTEXT_SIMPLE_STRING;
 powerRequestContext.SimpleReasonString = reasonString ?? System.Environment.CommandLine; // The reason for making the power request.

 // Create the request (returns a handle).
 _powerRequest = PowerCreateRequest(ref powerRequestContext);

 // Set the request(s).
 PowerSetRequest(_powerRequest, PowerRequestType.PowerRequestSystemRequired);
 if (includeDisplay) { PowerSetRequest(_powerRequest, PowerRequestType.PowerRequestDisplayRequired); }
 _mustResetDisplayRequestToo = includeDisplay;

 }
 else
 {

 // Not previously enabled: quietly do nothing.
 if (_powerRequest == IntPtr.Zero) { return; }

 // Clear the request
 PowerClearRequest(_powerRequest, PowerRequestType.PowerRequestSystemRequired);
 if (_mustResetDisplayRequestToo) { PowerClearRequest(_powerRequest, PowerRequestType.PowerRequestDisplayRequired); }
 CloseHandle(_powerRequest);
 _powerRequest = IntPtr.Zero;

 }
 }

 // Overload that allows passing a reason string while defaulting to keeping the display awake too.
 public static void StayAwake(bool enable, string reasonString)
 {
 StayAwake(enable, false, reasonString);
 }

'@

try {

 # Create power request(s) that keep the system awake.
 # Pass $false as the 2nd argument to allow the display to go to sleep.
 # The reason string is visible when you run `powercfg.exe -requests` to show current requests
 # (requires elevation).
 # Defaults: keep the display awake too, use the current process' command line as the reason string.
 [Windows.PowerUtil]::StayAwake($true, $true, &quot;Running long-running script $PSCommandPath.&quot;)

 # YOUR CODE GOES HERE.
 # In this sample, wait for the user to press Enter before exiting.
 # Before that, the system should stay awake indefinitely.
 pause

} finally { # This ensures that the previous scheme is restored even when the script is aborted with Ctrl-C.

 # Clear the power requests.
 [Windows.PowerUtil]::StayAwake($false)

}
</code></pre>

blocks|key|2728245|text|我使用的简单的一层衬垫：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2728246|Powercfg+/x+-standby-timeout-ac+0|code-block|syntax|javascript|2728247|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Simple one-liner that I use:
<pre><code>Powercfg /x -standby-timeout-ac 0
</code></pre>

I have a powershell process that reads records from a remote server and copies them into a local database. When it runs, it might run for 8-12 hours.
How do I prevent the computer from shutting down (or going into sleep/hibernate mode) during this time? I know I can adjust the 'Power and sleep settings' to set the computer to never sleep, but that's not what I'm looking for - I do want it to go to sleep when the process isn't running.
I know that sleep/hibernate is suspended if a netflix or youtube video is running, I'd like the computer to do the same when a powershell process is running.
The powershell process runs in a command window on the desktop - I'm happy for the screen saver to activate, but what I don't want to happen is for me to wake the machine after 8 hours and discover that the process only ran for 10 minutes before the computer went to sleep!

How to stop a windows 10 machine from sleeping/hibernating down when running a powershell process?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个powershell进程，它从远程服务器读取记录并将它们复制到本地数据库中。当它运行时，它可能运行8-12小时。如何防止计算机在此期间关闭(或进入睡眠/休眠模式)？我知道我可以调整“电源和睡眠设置”，将电脑设置为永不休眠，但这不是我想要的--我确实希望它在进程不运行时进入睡眠状态。我知道如果netflix或yo...

问如何在运行powershell进程时阻止windows 10机器休眠/休眠？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在运行powershell进程时阻止windows 10机器休眠/休眠？EN