[Bug]: Installer needs exclusive access on files used by other applications

### ⚠️ 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

Installation is failing, as Client needs access to some files, which are in use by all kinds of applications, eg Firefox or Thunderbird.
Is this meant to be this way?


With this NVIDIA GeForce Overlay especially I have no luck closing it, all the Nvidia Tasks will always restart themselves.

### Steps to reproduce

Have Nvidia Overlay installed
Install Nextcloud 3.13.1.

### Expected behavior

It should be installed

### Which files are affected by this bug

None, it is about installation

### Operating system

Windows

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

Windows 11

### Package

Other

### Nextcloud Server version

Nextcloud Hub 8 (29.0.3)

### Nextcloud Desktop Client version

3.13.1

### 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 Disabled

### 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_

Start by reproducing the update from Nextcloud Desktop Client 3.13.1 on Windows 11 with the NVIDIA GeForce Overlay and other applications holding files open. The issue names no affected files, tests, or installer entry point, so first identify which installer operation fails and which process holds the file. Done means the client installs successfully in this scenario.

Written by the indexing model from the issue text.