[7.12.1] Download directory suddenly reverted

[Radnozyp]

Describe the bug

All of a sudden my tribler download directory reverted to a year-old previous download folder.

Tribler 7.12.1
Windows 11

[xoriole]

@Radnozyp Thank you for reporting this bug. This is definitely not the expected behavior. To be able to diagnose the issue, we would need more information.

What was the last thing you have done before the issue occurred? Have you upgraded recently?

[synctext]

@Radnozyp We're trying to figure out your bug. Very strange!
Can you help us out and share more info?

All of a sudden my tribler download directory reverted

That means you where using Tribler normally? Was during startup or upgrade?

[Radnozyp]

Hey, sorry about the late response.

AFAIK I was using tribler normally when it happened, though I was away travelling so jumping between IP:s alot. I think it happened right after a tribler update.

[github-actions]

This issue has not seen activity for 60 days. It is now marked as stale. Please provide additional information or this issue may be closed in the future. We value your contribution and would love to hear more!

[qstokkink]

In the upcoming 8.0 release, the upgrade system is changed and this issue should no longer occur.

[Radnozyp]

I was just using it normally. Sent with [Proton Mail](https://proton.me/) secure email.

…

On Monday, November 20th, 2023 at 9:26 AM, Johan Pouwelse ***@***.***> wrote: ***@***.***(https://github.com/Radnozyp) We're trying to figure out your bug. Very strange! Can you help us out and share more info? > All of a sudden my tribler download directory reverted That means you where using Tribler normally? Was during startup or upgrade? — Reply to this email directly, [view it on GitHub](#7569 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BB4PB76BWMCZBMOKVM6K6K3YFMH2BAVCNFSM6AAAAAA3OPVQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYGQ2DEOBSGQ). You are receiving this because you were mentioned.Message ID: ***@***.***>

[qstokkink]

@Radnozyp that should be all you need to do. In the next release, just using it as normal should work again.