You don't say whether the status says Uploading or still says Running. However, for me at least, the Elapsed time stops moving once the task is Uploading.

Some WCG projects do do a sort of consolidation or very short secondary simulation at the end of the main run, but I've always seen progress stick at fraction under 100%. You don't say which WCG projects this is happening for, or if it's all of them.

Have you checked to see if the task is still actually using CPU time (task manager, or similar)? Or is it just the case that BOINC isn't reporting properly?

But, all in all, this sounds very odd to me. I think my first course of action would be to reboot the machine. If that doesn't fix it, I would make sure you're running the latest supported WCG/BOINC version and, if so, then try resetting the project.

Good luck getting this sorted.

I understand what you're saying, and I can see why you might think that, but, even though I don't know the ins and outs of the BOINC system design, I don't completely agree with you. I know from my ancient Windows machine that there is communication between the active tasks and the manager -- and that that communication can be disrupted with unwanted results. That is why I suggested a re-boot to start things over. Unless you know something you haven't told us, or you do a lot of monitoring of what is going on, I think you are jumping to unfounded conclusions.

I've put the computer on Run Always and watched the individual tasks. While time to completion is an estimate, at least tasks that are actually performing actual work show both progress and something remaining in the Remaining field.

In this particular case, the task progresses normally until it reaches 100%. Then, instead of doing the expected upload to the server and placing the task in the Ready to Report status, it continues to sit at 100%, the Elapsed time continues to increase, and the Remaining field shows "----". If I don't do anything and leave it, a task in this condition will run for at least a day or so, and when I first noticed this bug, a couple tasks stuck in this condition had been running for several. As a task in this state continues to consume a slot and CPU cycles, I now abort it when I see this happening.

Up to now, nothing you've said tells me that you have independently verified what is happening. Just because the manager is reporting CPU time does not mean the the WU is using CPU time. Neither does the fact that the manager is not uploading the WU mean that the WU has not completed. It could simply mean that the message from the WU to the manager to tell the manager that it is ready to upload has gone AWOL.

If you're sure that the unit is still using CPU time (by observing the usage in a monitoring tool, not by checking the WU properties in BOINC) then, if and when it finishes, or you cancel it after allowing 100% more time than expected, I would take a look at the WU's log on the web site (or you can try reading it in real time in the appropriate slot directory). If there really is recorded activity once the unit has hit 100%, then I should report it using the contact procedure on the web site so that the techs can take a look at it.