Torrent recheck every Windows startup + invisible tray icon

[supraspecies]

I know this has been brought up over and over, but has never been fixed. My system is Windows 7 x64, graceful shutdown is set to true. Nothing potentially interferes with uTorrent because I have this problem even after reformat. I believe I also have the same problem on my second Windows XP computer (along with invisible uTorrent tray icon in Windows XP in some builds of uTorrent).

So, is there any solution yet? Coz I REALLY don't wanna recheck ~50 gigabytes or more every Windows startup.

And yes, this problem has been up for months and months. I was waiting for a fix, but I am sick of waiting already, so I am creating a (yet another) thread.

And no, I don't want to shut down uTorrent manually or stop all my torrents before restarting/shutting down my computer. If uTorrent can't do the job, then I'm sure some other torrent client can. This should be fixed, not worked around. And I failed to find even workarounds for that problem.

[ciaobaby]

And no, I don't want to shut down uTorrent manually or stop all my torrents before restarting/shutting down my computer.

Tough!!! Because that IS the ONLY way to fix it.

It is NOT a uTorrent 'bug'

It is NOT a Windows problem.

It is PURELY and SIMPLY a USER problem.

then I'm sure some other torrent client can.

Off you pop then, try and find one that WILL let you shutdown Windows before the cached data is completely committed to disc by interupting the process, that will then simply start jobs without checking for corrupted data.

The forced re-check is a SAFETY measure against corrupted data, OR would you prefer that ALL the potentially corrupt data be deleted from the disc and the entire job start again from 0% every re-start?

[supraspecies]

Tough!!! Because that IS the ONLY way to fix it.

I'm afraid you misunderstand. That is, at best, a workaround. Fix, is something that developers actually fix. Why wasn't it the *only* way in uTorrent 2.2.1? Why was it working then? Please, do answer. I want to know why before it was not broken, now it is broken, and nobody is fixing it.

The approach you are telling me about sounds just like "don't want bugs - don't use the program". Thanks, but aren't bugs and broken features something that developers should fix?

It is NOT a uTorrent 'bug'

It is NOT a Windows problem.

It is PURELY and SIMPLY a USER problem.

If a user is a uTorrent developer, then of course.

Off you pop then

Or, or - and stay with me on this one - developers could fix the problem.

try and find one that WILL let you shutdown Windows before the cached data is completely committed to disc by interupting the process

Windows is waiting for every program to shut down properly. If uTorrent shuts down improvperly that is uTorrent's problem.

The forced re-check is a SAFETY measure against corrupted data, OR would you prefer that ALL the potentially corrupt data be deleted from the disc and the entire job start again from 0% every re-start?

I would prefer uTorrent properly saving data, so it wouldn't be corrupted, isn't that obvious?

[ciaobaby]

I would prefer uTorrent properly saving data, so it wouldn't be corrupted, isn't that obvious?

But it CANNOT do that after a Windows shutdown is initiated.

When Windows is shutting down it does NOT wait for applications to complete every process, it will simply force the application to abandon the process and yield to the close command, so data may only be partially written to disc.

Application that operate as MDI or SDI (Multiple and Single Document Interface) applications will signal that the data is "dirty" BUT if there is no response is received from the user to abort the shutdown the application WILL be force closed, and any unsaved data lost.

[rafi]

When Windows is shutting down it does NOT wait for applications to complete every process

1. I remember applications holding up the shutdown process FOREVER and asking me to save files being edited. Am I dreaming?... uT can do the same, or just save the current state properly at that point.

2. If the design of updating resume.dat was solid, there wouldn't be any need to get to "corrupted" files . As it is, nothing is being updated in it for a state-change. It is only being updated every x minutes. This way, when download is finished, and you auto-shutdown windows (for example) this is not being recorded in time, sometimes.

[ciaobaby]

1. I remember applications holding up the shutdown process FOREVER and asking me to save files being edited. Am I dreaming?...

Yep they do, but as I said that is ONLY for application that run as SDI or MDI apps where they have open documents that are flagged as 'dirty', the uTorrent downloading operation does NOT have documents that are open and 'dirty'.

Read the last sentence of post #4 regarding user input and aborting shutdown.

[SaNdMaN82]

Hello.

Don't take the following general and random thoughts I've about your issue in the bad way, ok?

1) I think you fail to understand the concept of "data integrity"

2) It's Window's fault

3) It's not Utorrent's fault if its not given enough time to close properly

4) It's not utorrent's fault if it's not closed correctly

5) Please start your search for another bittorrent client, please inform us what you find

6) Have you considered to get a windows script to shutdown utorrent normally first and then reboot?. You would have to reboot this way, not using "Start / Shutdown"

7) Why don't you want to manually close it?... I think the time you loose by closing utorrent manually is quite less than having to recheck the files at utorrent's startup.

Cheers from Argentina.