title: Web scraping script issue after updating to Windows 10
body: <p>I upgraded to Windows 10 a few days ago and I have not been able to get one of my scripts to work. This simple stand-alone script demonstrates the problem:</p>
  
  <pre><code>$erroractionpreference = "Continue"   
  $ie = New-Object -ComObject InternetExplorer.Application
  $ie.visible = $True
  
  $url = "http://gtr1.backtest.org/2013/?sp500.a:et1"
  
  $ie.Navigate($url)
  while ($ie.busy) {Start-Sleep 1}
  $backtest = $ie.document.getElementsByName("submit") |
              Where-Object {$_.value -eq "Run Backtest"}
  $backtest.click()  #shows SP500 backtest results
  while ($ie.busy) {Start-Sleep 1}
  $screener = $ie.document.getElementsByName("submit") |
              Where-Object {$_.value -eq "Run Screener"}
  $screener.click()  #shows list of SP500 stocks
  while ($ie.busy) {Start-Sleep 1}
  </code></pre>
  
  <p>The program navigates to a stock backtesting website with a simple screen, clicks on the "run backtest" button, and this part works fine; I can watch the progress in the visible IE session. What SHOULD happen is that the "run screener" button is then clicked and a list of SP500 stocks is shown.</p>
  
  <p>But the updated (after the first click) website information does not come back to the script, apparently. Once or twice I saw an RPC DISCONNECTED type error but I can't reproduce it. This is the usual error message:</p>
  
  <pre>Exception from HRESULT: 0x800A138A
  At C:\Users\MD\OneDrive\Documents\Mechanical Investing\GTR1\Daily Runs\Temp1.ps1:12 char:1
  + $screener = $ie.document.getElementsByName("submit") | Where-Object { ...
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : OperationStopped: (:) [], COMException
      + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException</pre>
  
  <p>So the initial navigation to the website, and first button click work fine, but the second one doesn't. It doesn't matter whether I'm running as Administrator or not, and it doesn't work at the command prompt. I had a similar script to this running for quite a long time on Windows 7 with no issues. I did add PowerShell as an allowed app in the firewall settings but that didn't help.</p>
  
  <p>Any ideas?</p>