[Bug]: Application does not open

[CSsnap]

Guidelines

• [X] I have encountered this bug in the latest release of FreeTube.
• [X] I have encountered this bug in the official downloads of FreeTube.
• [X] I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.
• [X] This issue contains only one bug.

Describe the bug

When starting Freetube, the application does not open at all. It shows up in the task manager with 0% CPU usage and a few megs of ram usage, but not the screen or taskbar. This occurs no matter how the application is started.

Expected Behavior

The application opens and is ready for use.

Issue Labels

usability issue

FreeTube Version

0.20.0

Operating System Version

Windows 10 19045.4170

Installation Method

.exe

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

This issue was present in previous versions. This latest issue is from a fresh install.

Nightly Build

• [ ] I have encountered this bug in the latest nightly build.

[Bouch76]

Essentially I've the same issue with: "freetube-0.19.2-setup-x64" "freetube-0.20.0-setup-x64" Also tried extracting "freetube-0.20.0-win-x64-portable" to "C:\Program Files\FreeTube"

Note: I am nubile.

OS Build: 22631.3527
Ver: 23H2 Installed: 1/‎28/‎2023 Experience: Pack 1000.22700.1003.0

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Is this also present in v0.21.0?

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.