What's confusing though is when the estimated time jumps between minutes, hours, days, and years for a process. Like it's not even vaguely accurate, it hasn't the faintest idea.,(reply>), Usually that kind of thing's because it's averaging the current rate of progress and using that for the estimate, but then that rate. Because, say, drive access speed has dropped because there's too many things accessing it now. Or your internet connection's just gone down, so your average download speed is heading towards 0 b/s (that's when the estimate starts to get into the years and decades - I mean it ain't wrong!)