Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

Wynona said:

Nope, nope, nope! Hybernate presents too many problems in my estimation, so I never let it enable.

Odd how experiences differ. I've been routinely using 'shut the lid and hibernate' on my laptops without any problems - first in '95, then XP, Win7 and now Win10. All were Toshibas, which may be relevant. I have heard that some other brands could be 'problematic'.

Bree said:

Odd how experiences differ. I've been routinely using 'shut the lid and hibernate' on my laptops without any problems - first in '95, then XP, Win7 and now Win10. All were Toshibas, which may be relevant. I have heard that some other brands were 'problematic'.

My Surface Pro 3, also. Same thing. Fine on lappy.

I have hibernation enabled on both my laptop and my desktop.

I use Dell's High Performance power scheme for my laptop (with tweaks of my own in the various configuration, including disabling sleep (but lowering the monitor down) and enabling hibernation if AC power cuts off and ht battery gets to ~15%).

I've set the same settings in the High Perf scheme on my desktop - because my desktop is connected to an APC UPS with a USB cable connecting both as well, so the Windows 10 monitors what the battery is doing. It's a lot different than running PowerChute, but this far it was worked pretty well.

ThrashZone said:

Hi,
lol yeah my first action usually with cmd :)

Code:

Powercfg -h off

Same here. Usually followed by PS>set-executionpolicy unrestricted.

Something changed with updates in 17604 ?. First time it downloaded and installed update for AMD graphic drivers and screwed it up royally . AMD has own driver updater (optional) so I relied on it to announce new version and than I download it from their site.
Update really, but REALLY needs an option to refuse particular update. I always had it set to "Notify only" but that doesn't stop it from updating once is started. Now I had notification about 2 updates, one for WD and one for display driver and couuldn't stop former one and only install WD update.

martyfelker said:

ThrashZone said:

Hi,
lol yeah my first action usually with cmd :)

Code:

Powercfg -h off

Same here. Usually followed by PS>set-executionpolicy unrestricted.

Is it a good idea to set execution policy unrestricted permanently from a security view point?

cereberus said:

Is it a good idea to set execution policy unrestricted permanently from a security view point?

Running powercfg command in PowerShell does not require any execution policy be set, command can be run also when policy is Restricted (running scripts disabled). A command or cmdlet is not a script.

Anyway, running a command or a script, PowerShell execution policy can be bypassed. In this case the command would be:

powershell.exe -executionpolicy bypass [ScriptName.ps1 OR command with options]

When command is given like this, it can also be given simply from RUN (WIN + R) dialog:



This is just an example, all this being unnecessary. The powercfg command can of course be run, and is in fact easiest and fastest to run directly as standalone command from RUN:



No need to open Command Prompt or PowerShell for this.

Kari

cereberus said:

Is it a good idea to set execution policy unrestricted permanently from a security view point?

Possibly not. However I don't run remote powershell scripts.

A saying from Wanda the Fish while running Linux and VMware Server.

beta test, v:
To voluntarily entrust one's data, one's livelihood and one's
sanity to hardware or software intended to destroy all three.
In earlier days, virgins were often selected to beta test volcanos.

Kari said:

Running powercfg command in PowerShell does not require any execution policy be set, command can be run also when policy is Restricted (running scripts disabled). A command or cmdlet is not a script.

Anyway, running a command or a script, PowerShell execution policy can be bypassed. In this case the command would be:

powershell.exe -executionpolicy bypass [ScriptName.ps1 OR command with options]

When command is given like this, it can also be given simply from RUN (WIN + R) dialog:



This is just an example, all this being unnecessary. The powercfg command can of course be run, and is in fact easiest and fastest to run directly as standalone command from RUN:



No need to open Command Prompt or PowerShell for this.

Kari

I do not think OP meant he did the powershell execution policy change for powercfg but just as one of first things he does with a new installation which is why I queried if it is a good idea.