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

cereberus said:

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.

OK. In that case, you can leave execution policy always as restricted and in PowerShell run scripts with following command, always bypassing current policy:

powershell.exe -executionpolicy bypass [ScriptPath\ScriptName.ps1]

This runs script regardless of current policy. In my case, variable $Scripts points to my scripts folder, I could for instance run my CreateUSB.ps1 script (tutorial) to create W10 USB install media with following command, even if my execution policy would be set to Restricted:



To make it even easier, I could run following command:

& [ScriptPath\ScriptName.ps1] -ExecutionPolicy Bypass



The difference is, the first command can be run from both Command Prompt, PowerShell and RUN dialog, whereas the latter needs to be run from PowerShell.

Kari

Update: Announcing Windows 10 Insider Preview Fast Build 17107 - Feb. 23 Insider - Windows 10 Forums

Thight as much but skippy started moving too:

Searched the OP and didn't see this mentioned anywhere. Not sure if it applies to both builds, as I only have build 17604 on both of my machines.

Task manager --> Startup tab shows all items as 0 Suspended, but I can still enable or disable them (just can't tell which is which without right-clicking on each item).



This is occurring on both laptop and desktop.

Anyone else seeing this?

EDIT: Added the following:

Reported to Feedback hub, and it is already there, and reports from both builds showing the same thing, so it looks like it affected both builds. The 17101 users upgrading to 17107 now may have this fixed. Here's to hoping us Skip Ahead folks get a new build soon.

johngalt said:

Searched the OP and didn't see this mentioned anywhere. Not sure if it applies to both builds, as I only have build 17604 on both of my machines.

Task manager --> Startup tab shows all items as 0 Suspended, but I can still enable or disable them (just can't tell which is which without right-clicking on each item).



This is occurring on both laptop and desktop.

Anyone else seeing this?

Now when you mentioned it, yes, 17604. Everything I allowed tor run is running.

Added more to my post above.

johngalt said:

Searched the OP and didn't see this mentioned anywhere. Not sure if it applies to both builds, as I only have build 17604 on both of my machines.

Task manager --> Startup tab shows all items as 0 Suspended, but I can still enable or disable them (just can't tell which is which without right-clicking on each item).



This is occurring on both laptop and desktop.

Anyone else seeing this?

EDIT: Added the following:

Reported to Feedback hub, and it is already there, and reports from both builds showing the same thing, so it looks like it affected both builds. The 17101 users upgrading to 17107 now may have this fixed. Here's to hoping us Skip Ahead folks get a new build soon.

It's at least one build old news. Suspended doesn't mean allowed to start, but suspended as process. It's in process tab too

Edit: it's fixed in 17107. Not showing suspened anymore in Start up tab, but enabled...

AndreTen said:

It's at least one build old news. Suspended doesn't mean allowed to start, but suspended as process. It's in process tab too

Edit: it's fixed in 17107. Not showing suspened anymore in Start up tab, but enabled...

I know what suspended means, but it is not supposed to show on the startup tab at all in the first place.

johngalt said:

I know what suspended means, but it is not supposed to show on the startup tab at all in the first place.

exactly, so I added, that it's fixed. It was there in previous Fast build too