Unable to start WAD during use

[Jermin2020]

2023-09-13 16:39:15:194 - [Appium] Welcome to Appium v2.0.1
2023-09-13 16:39:15:197 - [Appium] Non-default server args:
2023-09-13 16:39:15:198 - [Appium] {
2023-09-13 16:39:15:198 - [Appium] localTimezone: true,
2023-09-13 16:39:15:198 - [Appium] logTimestamp: true
2023-09-13 16:39:15:199 - [Appium] }
2023-09-13 16:39:15:199 - [Appium] Attempting to load driver uiautomator2...
2023-09-13 16:39:15:200 - [debug] [Appium] Requiring driver at C:\Users\zm-ye\node_modules\appium-uiautomator2-driver
2023-09-13 16:39:15:851 - [Appium] Attempting to load driver chromium...
2023-09-13 16:39:15:852 - [debug] [Appium] Requiring driver at C:\Users\zm-ye\node_modules\appium-chromium-driver
2023-09-13 16:39:15:892 - [Appium] Attempting to load driver windows...
2023-09-13 16:39:15:893 - [debug] [Appium] Requiring driver at C:\Users\zm-ye\node_modules\appium-windows-driver
2023-09-13 16:39:15:952 - [Appium] Appium REST http interface listener started on http://0.0.0.0:4723
2023-09-13 16:39:15:955 - [Appium] You can provide the following URLS in your client code to connect to this server:
2023-09-13 16:39:15:956 - [Appium] http://192.168.82.157:4723/
2023-09-13 16:39:15:956 - [Appium] http://127.0.0.1:4723/ (only accessible from the same host)
2023-09-13 16:39:15:956 - [Appium] Available drivers:
2023-09-13 16:39:15:957 - [Appium] - [email protected] (automationName 'UiAutomator2')
2023-09-13 16:39:15:957 - [Appium] - [email protected] (automationName 'Chromium')
2023-09-13 16:39:15:957 - [Appium] - [email protected] (automationName 'Windows')
2023-09-13 16:39:15:958 - [Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
2023-09-13 16:39:28:478 - [HTTP] --> POST /session
2023-09-13 16:39:28:479 - [HTTP] {"capabilities":{"alwaysMatch":{"platformName":"Windows","appium:automationName":"Windows","appium:app":"C:\\Windows\\System32\\notepad.exe","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},"firstMatch":[{}]},"desiredCapabilities":{"platformName":"Windows","appium:automationName":"Windows","appium:app":"C:\\Windows\\System32\\notepad.exe","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true}}
2023-09-13 16:39:28:483 - [debug] [AppiumDriver@5eba] Calling AppiumDriver.createSession() with args: [{"platformName":"Windows","appium:automationName":"Windows","appium:app":"C:\\Windows\\System32\\notepad.exe","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},null,{"alwaysMatch":{"platformName":"Windows","appium:automationName":"Windows","appium:app":"C:\\Windows\\System32\\notepad.exe","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},"firstMatch":[{}]}]
2023-09-13 16:39:28:485 - [debug] [AppiumDriver@5eba] Event 'newSessionRequested' logged at 1694594368485 (16:39:28 GMT+0800 (中国标准时间))
2023-09-13 16:39:28:490 - [Appium] Attempting to find matching driver for automationName 'Windows' and platformName 'Windows'
2023-09-13 16:39:28:491 - [Appium] The 'windows' driver was installed and matched caps.
2023-09-13 16:39:28:492 - [Appium] Will require it at C:\Users\zm-ye\node_modules\appium-windows-driver
2023-09-13 16:39:28:492 - [debug] [Appium] Requiring driver at C:\Users\zm-ye\node_modules\appium-windows-driver
2023-09-13 16:39:28:493 - [AppiumDriver@5eba] Appium v2.0.1 creating new WindowsDriver (v2.12.2) session
2023-09-13 16:39:28:494 - [AppiumDriver@5eba] Checking BaseDriver versions for Appium and WindowsDriver
2023-09-13 16:39:28:494 - [AppiumDriver@5eba] Appium's BaseDriver version is 9.3.16
2023-09-13 16:39:28:494 - [AppiumDriver@5eba] WindowsDriver's BaseDriver version is 9.3.16
2023-09-13 16:39:28:496 - [debug] [WindowsDriver@f034] Creating session with W3C capabilities: {
2023-09-13 16:39:28:496 - [debug] [WindowsDriver@f034] "alwaysMatch": {
2023-09-13 16:39:28:497 - [debug] [WindowsDriver@f034] "platformName": "Windows",
2023-09-13 16:39:28:497 - [debug] [WindowsDriver@f034] "appium:automationName": "Windows",
2023-09-13 16:39:28:497 - [debug] [WindowsDriver@f034] "appium:app": "C:\\Windows\\System32\\notepad.exe",
2023-09-13 16:39:28:497 - [debug] [WindowsDriver@f034] "appium:newCommandTimeout": 3600,
2023-09-13 16:39:28:497 - [debug] [WindowsDriver@f034] "appium:connectHardwareKeyboard": true
2023-09-13 16:39:28:498 - [debug] [WindowsDriver@f034] },
2023-09-13 16:39:28:498 - [debug] [WindowsDriver@f034] "firstMatch": [
2023-09-13 16:39:28:498 - [debug] [WindowsDriver@f034] {}
2023-09-13 16:39:28:498 - [debug] [WindowsDriver@f034] ]
2023-09-13 16:39:28:498 - [debug] [WindowsDriver@f034] }
2023-09-13 16:39:28:502 - [WindowsDriver@f034] The following capabilities were provided, but are not recognized by Appium:
2023-09-13 16:39:28:505 - [WindowsDriver@f034] connectHardwareKeyboard
2023-09-13 16:39:28:506 - [WindowsDriver@f034 (14a0cb95)] Session created with session id: 14a0cb95-428b-482f-b094-bb2f540be911
2023-09-13 16:39:28:513 - [WindowsDriver@f034 (14a0cb95)] Spawning 'C:\Program Files\Windows Application Driver\WinAppDriver.exe' with args: ["4724/wd/hub"]
2023-09-13 16:39:28:523 - [debug] [WindowsDriver@f034 (14a0cb95)] Matched '/status' to command name 'getStatus'
2023-09-13 16:39:28:525 - [debug] [WindowsDriver@f034 (14a0cb95)] Proxying [GET /status] to [GET http://127.0.0.1:4724/wd/hub/status] with no body
2023-09-13 16:39:28:537 - [WindowsDriver@f034 (14a0cb95)] connect ECONNREFUSED 127.0.0.1:4724
2023-09-13 16:39:28:629 - [debug] [WindowsDriver@f034 (14a0cb95)] Windows Application Driver listening for requests at: http://127.0.0.1:4724/wd/hub
2023-09-13 16:39:28:630 - [debug] [WindowsDriver@f034 (14a0cb95)] Press ENTER to exit.
2023-09-13 16:39:29:542 - [debug] [WindowsDriver@f034 (14a0cb95)] Matched '/status' to command name 'getStatus'
2023-09-13 16:39:29:542 - [debug] [WindowsDriver@f034 (14a0cb95)] Proxying [GET /status] to [GET http://127.0.0.1:4724/wd/hub/status] with no body
2023-09-13 16:39:29:546 - [debug] [WindowsDriver@f034 (14a0cb95)] ==========================================
2023-09-13 16:39:29:546 - [debug] [WindowsDriver@f034 (14a0cb95)] GET /wd/hub/status HTTP/1.1
2023-09-13 16:39:29:547 - [debug] [WindowsDriver@f034 (14a0cb95)] Accept: application/json, /
2023-09-13 16:39:29:547 - [debug] [WindowsDriver@f034 (14a0cb95)] Accept-Encoding: gzip, compress, deflate, br
2023-09-13 16:39:29:547 - [debug] [WindowsDriver@f034 (14a0cb95)] Connection: keep-alive
2023-09-13 16:39:29:547 - [debug] [WindowsDriver@f034 (14a0cb95)] Content-Type: application/json; charset=utf-8
2023-09-13 16:39:29:547 - [debug] [WindowsDriver@f034 (14a0cb95)] Host: 127.0.0.1:4724
2023-09-13 16:39:29:548 - [debug] [WindowsDriver@f034 (14a0cb95)] User-Agent: appium
2023-09-13 16:39:29:550 - [WindowsDriver@f034 (14a0cb95)] Got response with status 500: {"status":13,"value":{"error":"unknown error","message":"An unknown error occurred in the remote end while processing the command."}}

[mykola-mokhnach]

https://github.com/appium/appium-windows-driver#troubleshooting

[mike-optifino]

@Jermin2020 Hi! I faced the same problem when trying to run appium server as windows service (used nssm). Could you find the root cause and how to fix it? Thanks in advance

[a-einstein]

I also have this problem in WPF updating Appium.WebDriver from 4.4.5 to 5.0.0.
It forced me to use Appium Windows Driver as proxy (on port 4723), and explicitly use Appium.
I also had to adapt my code to the new API.
It took me a while to figure this all out.

Finally, at creating a WindowsDriver, Appium does the spawning (to port 4724), but fails to connect Windows Application Driver.
Essentially is seems to come down to "WinAppDriver server is not listening within 10000ms".

Is there anything I can do, or is this a bug?

It is disappointing to jump through so many hoops for something I assumed to be established, but apparently is not working.

I have to shelf my changes. This issue has already been open for 9 months.

[a-einstein]

This seems the same issue at WinAppDriver.
WinApp Driver not supporting Appium and Selenium upgrade in Java

Some hot topics there that speak volumes.
Update on WinAppDriver
Is WinAppDriver dead?

[liljohnak]

Just in case some can't get there work done due to this issue. My current C# code:

1. Start my application using WinAppDriver.
2. If there is no window within 10 seconds, I will get a failure with a ProcessId. I catch the message and extract the ProcessId.
3. Launch a root WinAppDriver session and search all top level windows for one with my ProcessId.

The code isn't pretty at all, but stably works for our tests.

[DharshiBalasubramaniyam]

I also have this problem in WPF updating Appium.WebDriver from 4.4.5 to 5.0.0. It forced me to use Appium Windows Driver as proxy (on port 4723), and explicitly use Appium. I also had to adapt my code to the new API. It took me a while to figure this all out.

Finally, at creating a WindowsDriver, Appium does the spawning (to port 4724), but fails to connect Windows Application Driver. Essentially is seems to come down to "WinAppDriver server is not listening within 10000ms".

Is there anything I can do, or is this a bug?

It is disappointing to jump through so many hoops for something I assumed to be established, but apparently is not working.

I have to shelf my changes. This issue has already been open for 9 months.

I also facing the same issue. Did you find any solutions? If yes, pls comment. It will be more useful!

[mykola-mokhnach]

Try https://www.advancedinstaller.com/prevent-smartscreen-from-appearing.html