MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
WebPagetest Forums - [EC2 AMI] Edge is broken on Windows (wptagent) EC2 AMI

WebPagetest Forums

Full Version: [EC2 AMI] Edge is broken on Windows (wptagent) EC2 AMI
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
On the EC2 WPTAgent AMI, Microsoft Edge testing is not working properly. Edge is detected by the startup script [1], but if you attempt to run a check using Edge it throws an error [2] and fails the check with "The testing completed but failed."

@pmeenan let me know via DM if you need an assist on the EC2 AMI - I'm happy to contribute.

22:40:24.502 - Detected Browsers:
22:40:24.502 - Chrome: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
22:40:24.502 - Edge: C:\WebPageTest\wptagent\internal\support\edge\14\MicrosoftWebDriver.exe
22:40:24.502 - ie: C:\Program Files (x86)\Internet Explorer\iexplore.exe
22:40:24.516 - Microsoft Edge: C:\WebPageTest\wptagent\internal\support\edge\14\MicrosoftWebDriver.exe

22:47:28.289 - [{'record': True, 'command': 'navigate', 'target': u'http://<internalURL>'}]
22:47:28.289 - taskkill /F /T /IM MicrosoftEdge.exe
22:47:28.461 - taskkill /F /T /IM MicrosoftEdgeCP.exe
22:47:28.571 - taskkill /F /T /IM plugin-container.exe
22:47:28.680 - taskkill /F /T /IM browser_broker.exe
22:47:28.789 - taskkill /F /T /IM smartscreen.exe
22:47:28.898 - taskkill /F /T /IM dllhost.exe
22:47:29.023 - Terminating all instances of WerFault.exe
ERROR: The process "WerFault.exe" not found.
22:47:29.134 - Preparing browser
22:47:29.134 - Terminating all instances of MicrosoftWebDriver.exe
ERROR: The process "MicrosoftWebDriver.exe" not found.
22:47:29.226 - Flushing DNS
22:47:29.243 - ipconfig /flushdns
22:47:29.289 - Clearing profile C:\WebPageTest\wptagent\work\EC2AMAZ-CO5OM1I\browser.180507_PR_E.1
22:47:29.289 - Launching browser : C:\WebPageTest\wptagent\internal\support\edge\14\MicrosoftWebDriver.exe
22:47:29.289 - reg IMPORT "C:\WebPageTest\wptagent\internal\support\edge\keys.reg"
22:47:29.882 - POST http://localhost:51128/session {"capabilities": {"alwaysMatch": {"browserName": "MicrosoftEdge", "platformName": "windows"}, "firstMatch": [{}]}, "desiredCapabilities": {"platform": "WINDOWS", "browserName": "MicrosoftEdge", "version": "", "extensionPaths": ["C:\\Users\\Administrator\\AppData\\Local\\Packages\\Microsoft.MicrosoftEdge_8wek​yb3d8bbwe\\LocalState\\wptagent"]}}
22:47:29.882 - Finished Request Unknown error
22:47:32.898 - Stopping the browser...
22:47:32.898 - Stopping browser
22:47:33.289 - taskkill /F /T /IM MicrosoftEdge.exe
22:47:33.382 - taskkill /F /T /IM MicrosoftEdgeCP.exe
22:47:33.507 - taskkill /F /T /IM plugin-container.exe
22:47:33.618 - taskkill /F /T /IM browser_broker.exe
22:47:33.726 - taskkill /F /T /IM smartscreen.exe
22:47:33.835 - taskkill /F /T /IM dllhost.exe
22:47:33.960 - Test run time: 5.672 sec
22:47:33.960 - Uploading result
22:47:33.960 - Uploading result zip
Turns out Edge will not work on Windows Server 2016 because Microsoft doesn't support Edge on Server 2016 at all [1]. You can run the MicrosoftWebDriver.exe, but it will just throw that Unknown Error when you try to instantiate a session.

The only solution I can see is to switch the WPTAgent AMI from Windows Server 2016 to Windows 10, unless there's some other solution you're using on the Dulles, VA desktops, Patrick.

Bouncing back to top, as I've updated to the latest Windows Agent AMI and Edge still doesn't work.
Reference URL's