Backup & Restore sync (Onedrive) issue with multiple computers and same (MSA) account

[Dr01dYallS33k]

Microsoft PowerToys version

0.64.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

General

Steps to reproduce

Initial save of backup (file) on a 2nd laptop (of same MSA user=me) creates a (Onedrive) folder sync (conflict) error at the C:\Users\xxx\OneDrive\Documents\PowerToys folder, as a folder with that name already exists when (initial) Backup was saved (to default Onedrive folder/library) on the 1st laptop.
To work around this required manually creating a new/diff folder at the PowerToys\ folder level (eg.: 'PowerToys_2') - creating a new/diff 'Backup' folder continued the sync error - and deleting the conflicting folders/files (on all OneDrive syncs).
It seems the implementation of the initial backup creation doesn't include a check/contingency for existing PowerToys folder, creating potential conflicts/issues including OneDrive syncing.
A possibly related issue saving Backup to non-C: drive locations might suggest these issues are library (and/or file type association default save location) related: #21645

✔️ Expected Behavior

On any of my laptops, when clicking the "Backup" button in the Backup & restore utility under the General tab, I expected the file to save without any errors.

❌ Actual Behavior

After successfully saving a Backup on my 1st laptop, when I clicked the "Backup" button on my 2nd laptop a sync error was triggered and the conflicting save folders/files were sent to Recycle Bin.

Other Software

Windows 11, fully updated; standard laptop, default Windows MSA config. (default OneDrive libraries and file type save locations, eg.: Documents, Pictures, Downloads, Desktop, Music)

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[crutkas]

sorry, i was wrong on closing this

[cinnamon-msft]

Are you still experiencing this issue? /needinfo

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.