Windows 10: Powershell WebRequest to Microsoft.com shows Operation Timeout

I have created the following PowerShell script to test connectivity to a bunch of URLs. The below example is just the meat of the script (full script includes error handling)


$web1 = $null
[System.Net.ServicePointManager]:efaultConnectionLimit = 1024
[System.Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$web1 = [net.WebRequest]::Create("https://www.microsoft.com")
$web1.UserAgent = "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299"
$web1.Timeout = 10000
$web1.AllowAutoRedirect = 1
$web1.GetResponse()


When I run the above test, I always get the following error:

Exception calling "GetResponse" with "0" argument(s): "The operation has timed out"


When I change the url from www.Microsoft.com to www.bing.com or any other website (there are a few which have similar behavior), I get the proper output. Removing the timeout or TLS1.2 option yields the exact same result.

Running Edge with the www.Microsoft.com also works without any issue?


What is going on?


Mathew

:)

 

Windows 10 Powershell Invoke-WebRequest “Windows Security Warning ”


Alright this is one big problem in my opinion that Microsoft needs to address immediately. Steps to reproduce this:
powershell> Invoke-WebRequest "anywebsitewithcookies.com" (Let's do microsoft.com for example)
What happens is that you get the following warning:



Now this is just horrible. Why Microsoft thinks this is acceptable is beyond me, however in Windows 8.1 there was a workaround. If you went into:
Control Panel > Internet Options > Privacy



You could set cookies to be accepted all the time. This was the only way to get rid of this message and still retain DOM parsing functionality. -UseBasicParsing isn't a solution for me, because I want to use the functionality of what Invoke-WebRequest returns without basic parsing.
However now in Windows 10 Microsoft decided to get rid of this slider for whatever reason:



This problem can be reproduced on every Windows 10 machine and completely destroys how Invoke-WebRequest can be used in a silent scripting environment, because the script hangs and waits for the dialog to be answered. Is there a way to still set Cookies to be accepted for all like in 8.1? I tried every setting in Internet Options in Windows 10, but nothing holds the key. I believe they stopped using it and perhaps moved that setting elsewhere, but I can't find it. Microsoft Edge doesn't have many settings either, so none of them were helpful.
This is just infuriating. Any help would be highly appreciated, as this will create quite a chaos in many environments.

 

Windows 10 Internet Options ~ Powershell Invoke-WebRequest “Windows Security Warning”

Alright this is one big problem in my opinion that Microsoft needs to address immediately. Steps to reproduce this:

powershell> Invoke-WebRequest "anywebsitewithcookies.com" (Let's do microsoft.com for example)

What happens is that you get the following warning:



Now this is just horrible. Why Microsoft thinks this is acceptable is beyond me, however in
Windows 8.1 there was a workaround. If you went into:

Control Panel > Internet Options > Privacy



You could set cookies to be accepted all the time. This was the only way to get rid of this message and still retain DOM parsing functionality. -UseBasicParsing isn't a solution for me, because I want to use the functionality of what Invoke-WebRequest returns
without basic parsing.

However now in Windows 10 Microsoft decided to get rid of this slider for whatever reason:



This problem can be reproduced on every Windows 10 machine and completely destroys how Invoke-WebRequest can be used in a silent scripting environment, because the
script hangs and waits for the dialog to be answered. Is there a way to still set Cookies to be accepted for all like in 8.1? I tried every setting in Internet Options in Windows 10, but nothing holds the key. I believe they stopped using it
and perhaps moved that setting elsewhere, but I can't find it. Microsoft Edge doesn't have many settings either, so none of them were helpful.

This is just infuriating. Any help would be highly appreciated, as this will create quite a chaos in many environments.

 

How to change the Screen Timeout settings

Hello,

Welcome to the Microsoft Community.

I would suggest you to follow the below steps and check if it helps.

• 
  Right click on the desktop and click on Personalization.
  
• 
  Click on Lock screen
  
• 
  On the bottom of the screen click on Screen Timeout.
  
• 
  Under screen select the Time period accordingly.
  

Reply us back with the status of this issue. We will be glad to assist you.