Configuration initialization failed during startup

[TingjiaInFuture]

Describe the bug
If connected to another VPN before startup, Windscribe will work properly after disconnecting from the other VPN. Conversely, directly opening Windscribe causes a connection failure regardless of the server chosen.

OS and app information:

• OS: Windows 11 23H2
• App version [2.11.6]

Expected behavior
If the configuration initialization succeeds during startup, Windscribe will connect to servers smoothly.

Additional context
This bug occurs in previous versions of the app.
In area with severe internet censorship.

[TingjiaInFuture]

Establishing an emergency connection before startup should resolve this issue, as provided during registration.

[bernerdad]

Hi. A couple questions:

• Do you have the 'Circumvent Censorship' setting enabled?
• Have you tried every protocol?

[TingjiaInFuture]

Of coz @bernerdad

[TingjiaInFuture]

It's the "windscribe service"!

[bernerdad]

It's the "windscribe service"!

Can you elaborate on this? Why do you feel the windscribe service is causing this issue?

[TingjiaInFuture]

Cuz it starts on boot by default. And restart after terminating it until VPN connect was set up helps.

[TingjiaInFuture]

Specifically, once a connection is successfully established with any node using any protocol, it is possible to switch to other nodes and connect successfully. Therefore, I suspect that the server configuration file was not successfully initialized before the connection. @bernerdad