No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

any ideas? it's from an elevated prompt. it's always worked before. in a browser the cert is fine.

```PS C:\&gt; [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
PS C:\&gt; powershell -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient)
.DownloadString('<https://get.pulumi.com/install.ps1>'))"```

We recently upgraded <http://get.pulumi.com|get.pulumi.com> to only support TLS 1.2, which PowerShell doesn't support out of the box by default.  You can force it to use TLS 1.2 by doing `[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12`.  We updated `<http://docs.pulumi.com|docs.pulumi.com>` to reflect this as part of our giant copy and paste command for installing on Windows.

i've had that issue before with github so just thought to try it

Yeah, they make it hard to know these days :slightly_smiling_face:.

Let me boot back into my Windows 10 Pro Up To Date/Stable system and see if I can hit this as well.

I did a bunch of testing here against our staging site and it was all working for me.

```powershell -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; iex ((New-Object System.Net.WebClient).DownloadString('<https://get.pulumi.com/install.ps1>'))"```

i should read the command before i run it

presumably the powershell cmd creates a new context of sorts

I did not notice at first that you were invoking powershell from within powershell itself!

Yeah.  Or maybe just support it out of the box ;-)

Sorry for the trouble, and thanks for figuring it out ;-)

yeah or that. .10 is noticeably quicker! worth it :smile:

BTW: This made me realize the message the CLI prints on windows when it is out of date doesn't include this little dance, and I opened a PR for that here: <https://github.com/pulumi/pulumi/pull/2362>

thats where i copied it from yeah. good fix

JFYI, we ended up just relaxing the restriction on <http://get.pulumi.com|get.pulumi.com>, so it should just work out of the box with powershell again.