nextcloud / nextcloud/desktop

[Bug]: Windows Desktop starts then disappears, might be quiting immediately. Cannot access GUI once sync is set.

Open
#6,323 5 comments 0 reactions 0 assignees View on GitHub
0. Needs triage os: :door: Windows
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 21h
Merged PRs (30d)
127

Description

### ⚠️ Before submitting, please verify the following: ⚠️

- [X] This is a **bug**, not a question or a configuration issue.
- [X] This issue is **not** already reported on Github (I've searched it).
- [X] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

Both windows nextcloud and unraid nextcloud are up to date. Nothing changed except turning off startup for windows but I tried turning it back on and nothing.

I was successful in gaining access to the gui by deleting local, roaming, and packages Nextcloud in appdata but once I chose my sync location I can't access it.

### Steps to reproduce

Every time I start the program it disappears. I am unsure what caused it.

### Expected behavior

I should be able to use gui and nextcloud.

### Which files are affected by this bug

All

### Operating system

Windows

### Which version of the operating system you are running.

Windows 10

### Package

Appimage

### Nextcloud Server version

28.0.1

### Nextcloud Desktop Client version

3.11.0

### Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

### Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

### Are you using an external user-backend?

- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Nextcloud Server logs

_No response_

### Additional info

_No response_

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Start by reproducing the exit on Windows 10 with Nextcloud Desktop 3.11.0 after selecting a sync location, then collect the relevant client logs; done means the GUI remains accessible after sync is configured.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.