Windows: Unable to configure ASIO device (major bug)

**Describe the bug**

If (a new) ASIO device is added to the system which is not yet configured correctly and this device is selected in Jamulus Jamulus will show an error message and revert to the previous device. This makes it impossible to access the ASIO settings of the new device, so you can't set the correct settings.
**To Reproduce**

Install a ASIO device (Like Focusrite 2i2) and configure it for Jamulus and make Shure it works in Jamulus.
Now install a new ASIO4ALL Beta version (which has no offline settings).
Now try to use ASIO4ALL in Jamulus.
Most likely you will get the error message. Jamulus will revert to the previous driver and you won't be able to configure ASIO4ALL.
(Same goes for a lot of other ASIO drivers where i.e. the sample rate is set in the drivers ASIO config.)

**Expected behavior**

Jamulus should NEVER change any device and/or in-/output settings on it's own!
Just show an error message and let the user solve the problem or revert to the other driver.

**Screenshots**


**Operating system**

Windows10, any version.

**Version of Jamulus**

v3.8.1

**Additional context**

Same problem occurs when a user forgets to plug in (or accidentally unplugs) their interface or USB device. You get an error and Jamulus changes settings, So after plugging in the device and restarting Jamulus it still doesn't work since Jamulus changed the device settings. (very annoying and confusing for a lot of users)

Start by reproducing the Windows ASIO device-selection failure with an unconfigured or disconnected device, using the steps in the issue. Trace the error path that reverts the previous device and verify the expected behavior: show the error without changing device or input/output settings, then confirm the device can be configured and selected after recovery.

Written by the indexing model from the issue text.