Well into a big single file transfer I selected background transfer and wham, transfer ceased. Shit!

What version of WinSCP are you using? Can you reproduce this problem?

If I select background transfer I assumed I could then get to the menus and setting but no can do.

What prevents you from using the menus, while transferring the files on the background?

Okay, I'll start again. Free program and I always appreciate free. Still I saw this problem from last year. It's near August 2021 and seems this problem is still in WinSCP. But that background transfers ain't workin' is the least of my issues.
I'm running a fairly ordinary Windows 10 on an HP laptop. I only installed WinSCP this morning and it imported my server connection details for me. Brilliant. So I was off to a good start.
So onward I go. Well into a big single file transfer I selected background transfer and wham, transfer ceased. Shit!
I managed to get it to restart where it left off thankfully, but all incremental numbers were gone so it was adding to the existing file but telling me new download numbers as if it was first run.
There is no updating of file download size in the (classic) window and no access to the main interface anytime.
This is a trap for users in my circumstance; big file, invested gigabytes downloading with lots to go, cannot select ANY menu items as the small transfer window has complete precedence.
If I select background transfer I assumed I could then get to the menus and setting but no can do. The main issue FOR ME is, no menu item is accessible while it's transferring file/s, no updating of file size in the actual folders and I gotta ask, why have them there if they never update? Weird.
Thanks for reading guys and keep safe eh.
phil

@imhaggarwal: What version of WinSCP are you using?

Still experiencing it

I have added this bug to the tracker:
https://winscp.net/tracker/1983

Thanks for the details. Though I still cannot reproduce the problem.

I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

Thanks for your reply, I've attached the (modified to hide identifying information) log file. I also think I might have found more specific steps to reproduce the problem. I noticed that the problem doesn't occur when dragging files from within the left local directory window within the program to the right remote directory window to upload them, and then clicking the proceed in background button. The problem only occurs when the same steps are followed, but the files are dragged to the remote directory from a Windows Explorer window outside the program. Hopefully this information helps, thanks a lot for taking a look at this problem.

I never got any feedback from anyone regarding this (seemingly very rare) problem.
Can you post a session log file showing the problem (using the latest version of WinSCP)?

Sorry for the ambiguity, I meant the "Pressing "Proceed in background" terminates the transfer immediately in the latest version of WinSCP" problem.

@Jeroen45: What problem exactly? There are two different issues discussed here.

Hi there!

Sorry for bumping this topic, but this is the only reference to this problem I could find, and I'm still experiencing this problem with WinSCP 5.17.10. Is any fix known yet, apart from downgrading to older versions?
Thanks in advance for any update on this.

@radekzc: Thanks for your report.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Pressing "Proceed in background" terminates the transfer immediately in the latest version of WinSCP 5.17.2.

Sounds like you have hidden "Background transfers queue list" inadvertently:
https://winscp.net/eng/docs/ui_queue

You mean you can't see a use case where you would want to check on your background transfers. Maybe see how far they have come, maybe to cancel the operation altogether or maybe figure out if you can close the program and restart your pc already.

It shouldn't have been implemented without an undo function built in, that's just basic HCI.

It's not possible.
What is your use case for this?

This should be a simple task but for some reason I cannot find any option that allows me to bring the background transfer to the foreground.