You could have two powershell scripts each of which enables one interface and disables the other, there is a very good article here that describes how to do this.
You can test this out by opening a PowerShell as Administrator they using Get-NetAdapter
to get a list of your current network interfaces.
You can then enable them and disable them individually with:
- Disable:
Get-NetAdapter
wildcard that matches that one interface | Disable-NetAdapter -Confirm:$false
- Ensable:
Get-NetAdapter
wildcard that matches that one interface | Enable-NetAdapter -Confirm:$false
Example
Using VMWare as my test targets

Once you have your commands tested you can copy them to a couple of .ps1 files and set up shortcuts to them on your desktop, (don't forget to set them to run as Administrator), and you have direct commands to switch to either network.
This should work on Windows versions Windows 8 and above.
You could also write a PowerShell script to toggle between the two networks with something like: Get-NetAdapter Ether* | ? status -ne disabled | Disable-NetAdapter
and Get-NetAdapter Ether* | ? status -eq disabled | Disable-NetAdapter
This has the advantage of not costing anything as it uses the built in PowerShell.
Creating Shortcut
From OPs Experience
a straight shortcut to PS1 file had run as admin greyed out so you
have to instead make a shortcut to powershell.exe with the ps1 file as
argument. Then I found out that executing script was disabled so I had
to add bypass option in the shortcut target. In the end I had to use
the following in shortcut target:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy ByPass -File "D:\Tools\NetTool\BSNL.PS1"
Looks complex but works like a charm