Issues in Microsoft Edge versions 44.19041 and below
info
NOTE FOR MICROSOFT EDGE : Older versions of Microsoft Edge i.e versions 44.19041 and below have few limitations when automating with Sahi Pro. So it is recommended to use Microsoft Edge versions 79.0.309 and above.
info
NOTE FOR MICROSOFT EDGE VERSIONS 44.19041 AND BELOW : Parallel execution is not supported for such older Microsoft Edge versions. Also you need to close any running instance of Microsoft Edge before playback for these old Microsoft Edge versions.
If you want to perform any automation with Microsoft Edge versions 44.19041 and below then don't make Microsoft Edge as your system's default browser.
If you want to perform any automation with Microsoft Edge versions 44.19041 and below then don't make Microsoft Edge as your system's default browser.
Sahi Pro console Edge 'PIDs not available'
symptom
When launching Edge browser from the dashboard, we get an error in Sahi Pro console stating PIDs not available yet. Waiting for 1 sec
and consequently, proxy gets reverted.
and consequently, proxy gets reverted.
info
To observe this issue
- Open task manager and go to details tab. Then launch Edge browser window (with or without Sahi Pro), it will start a new process 'MicrosoftEdge.exe' with process id lets say '1234'.
- Now close the browser window. This will end the process with id '1234'. However on closing, Edge will launch another process 'MicrosoftEdge.exe' with id lets say '5678'. This process will be in suspended state.
- So when we launch Edge browser again for the second time, a new process will not be started but the process 'MicrosoftEdge.exe' with id '5678' will be resumed.
- Sahi Pro collects the process IDs which were created after we launch the browser. Since in this case, no new process is created Sahi will assume that the browser was not launched. Thus Sahi will revert the proxy.
cause
- This is due to an update in Microsoft Edge. With this feature, Microsoft Edge will be pre-launched each time it is closed.
This feature has been introduced since Windows 10 build 17713.
resolution
This feature of Microsoft Edge needs to be disabled to fix this issue.
There are two ways to do it.
There are two ways to do it.
- For Windows 10 Pro and Enterprise editions :
- Open Local Group Policy Editor.
- Start by clicking on the Windows start bar (bottom-left corner) or press the Windows key.
- Then, type Local Group Policy to make use of the search function. Next, click on Edit group policy.
- In the left pane of Local Group Policy Editor, navigate to the location
Computer Configuration\Administrative Templates\Windows Components\Microsoft Edge
. - In the right pane of Microsoft Edge in Local Group Policy Editor, double click on the Allow Microsoft Edge to pre-launch at Windows startup, when the system is idle, and each time Microsoft Edge is closed policy to edit it.
- Select radio button for Enabled, and configure pre-launch setting by selecting dropdown value Prevent pre-launching . Click on 'OK' button.
- Restart your system.
- Open Local Group Policy Editor.
- For Windows 10 Home or other Windows 10 editions which do not have local group policy editor:
- Launch Registry Editor.
- Start by clicking on the Windows start bar (bottom-left corner) or press the Windows key.
- Then, type Registry Editor to make use of the search function. Next, click on Registry Editor.
- Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\MicrosoftEdge\Main
. If such a key does not exist, it needs to be created. - Right click on Main and select
New > Dword (32-bit) Value
. Name itAllowPrelaunch
and ensure the value is set to 0 (it is the default value). - Restart your system.
- Launch Registry Editor.