Web Driver for Microsoft Edge version 18

Issue #22091761 • Assigned to Zachariah L.

Details

Author
Pratik V.
Created
Jun 11, 2019
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

My default Edge not working with WebDriver :
Microsoft Edge 44.17763.1.0 , Microsoft EdgeHTML 18.17763
I also tried to update default webdriver via command:
C:\WINDOWS\system32>DISM.exe /Online /Add-Capability /CapabilityName:Microsoft.WebDriver~~~~0.0.1.0

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.475

[==========================100.0%==========================]

Error: 0x80244022

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

DISM command failed so I downloaded Dev Edge Version : 76.0.159.0.
Please let me know which WebDriver Version is compatible with Dev Edge ?

Thank you,
Pratik

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Zachariah L.”

  • Hi Pratik!

    Thank you for contacting us about this issue! The version of the webdriver that will work for 76.0.159.0
    can be found on the webdriver page: https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/ .

    Zach

  • I have tried using the version 76.0.174.0 but still I can not run my Script.

  • Hi Pratik!

    Could you provide me with a simplified reproduction?

    Thanks,

    Zach

  • I am trying to add Microsoft WebDriver from “Add an Optional Feature” to run my scripts on Edge browser for automation. This is the version I am using:
    Microsoft Edge 44.17763.1.0 , Microsoft EdgeHTML 18.17763

    I also tried to update default webdriver via cmd run as administrator:
    DISM.exe /Online /Add-Capability/CapabilityName:Microsoft.WebDriver~~~~0.0.1.0

    I am getting error in this case as well and i have attached dism.log file.

  • Hi Pratik!

    You are confusing me a bit. Are you trying to automate Edge Dev or the current Microsoft Edge? This is important because they use two different webdrivers. The current Edge Dev is 76.0.174.0 whereas Microsoft Edge 44.17763.1.0  Microsoft EdgeHTML 18.17763 is the current Microsoft Edge that comes preinstalled with Windows 10. You mention both of these.

    I’m looking though your attached DISM file and you appear to have ran the command to install the webdriver a few times and those look like they were installed correctly. I see that your last run produced the error: DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950.

    This DISM command is currently for installing the webdriver for the in-market version of Microsoft Edge (Microsoft Edge 44.17763.1.0 , Microsoft EdgeHTML 18.17763

    1. and not Edge dev. If you are wanting the webdriver for Edge dev, I provided a link in a prior message to where is could be downloaded. However, if you are trying to automate the in market version of Microsoft Edge, it looks like a prior run of this command may have succeeded. If it has then the webdriver should already be on your system. The default location for the webdriver installation is C:\Windows\SysWOW64\MicrosoftWebDriver.exe. Please check to see if this is saved there, if so, then pass the location of your webdriver programmatically in your code.

    If the webdriver is not there and you are trying to automate the in-market version of Microsoft Edge then your DISM module may be corrupted. Here is a good resourse that discusses how this issue can be solved: https://windowsreport.com/dism-failed-windows-10/

    Please let me know if you need any additional information,
    Zach

  • I am talking about the Microsoft Edge 44.17763.1.0 Microsoft EdgeHTML 18.17763 which comes preinstalled, but you gave the suggestion to try with the Edge Dev 76.0.174.0 that i tried as well but didn’t worked.
    All the runs using command “DISM.exe /Online /Add-Capability/CapabilityName:Microsoft.WebDriver~~~~0.0.1.0” has been failed.
    I looked for the MicrosoftWebDriver.exe location but its not at C:\Windows\SysWOW64. I tried steps to fix corrupted DISM but still can not find MicrosoftWebDriver in C:\Windows\SysWOW64.

  • Hi Pratik!

    Thank you for clarifying! I apologize for the miscommunication. 

    A DISM failure is honestly outside the scope of this portal. If you can provide me with the test code that you are trying to automate Microsoft Edge with then I will investigate this further. If I cannot find a resolution to this issue, I will get you in touch with someone more knowledgeable on the subject.

    Please email me at v-zaleon@microsoft.com.

    Thanks,
    Zach 

  • Hi Pratik!

    So after some research, this DISM failure may be because your system is unable to access the Windows Update server. This is most likely the issue if you are on a domain-joined machine which is configured to download updates from a WSUS server. 

    To temporarily bypass the WSUS server, use the following registry edit (requires administrator privileges).

    Right-click Start, and click Run
    Type regedit.exe and click OK
    Go to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
    In the right-panel, if the value named UseWUServer exists, set its data to 0
    Exit the Registry Editor
    Restart Windows
    After the restart, run the following command in an elevated command prompt: DISM.exe /Online /Add-Capability /CapabilityName:Microsoft.WebDriver~~~~0.0.1.0

    Please let me know if this resolves the issue.

    Thanks,

    Zach

  • Hi Zach,

    I have followed your steps and result is still the same, can not find web driver. I can not share the test code as it is a huge project that I am working on.

  • Hi Pratik!

    Do you have another Windows machine that is running the same version? If you do, you can download the MicrosoftWebdriver and copy the exe to your main testing system. This would be more of a work around because it seems that there is an underlying issue that we would not be resolving. Regardless, this would allow you to carry on with your testing.

    Thanks,

    Zach

You need to sign in to your Microsoft account to add a comment.

Sign in