Hi Ken,Couple of observations on testing the latest build.1. Phase 3a 'Forcing idle tasks to execute' doesn't appear to work on my system any more. With previous builds this Phase usually was completed within a few seconds but now the program seems to hang at this point. I have tried leaving it for 15-20 mins but it still fails to progress. Task manager reports that FSAutoStart is still running so perhaps I need to wait even longer. However, I can't believe that to be the case as I doubt whether any one would use this option.2. Can I suggest that instead of "Press any key to continue" it might be better to specify a key (say a function key) to reduce the chances of accidentally restarting all the programs and services before you have had a chance to start/switch to another program/game/application.Maybe the message should read something like: "Press to restart Programs and Services..."Regards,Mike

Hi:1) I didn't change anything here - I rarely use this option myself and it requires certain services to be running. The first time I ran it when I was testing it a while back, it ran for quite a long time. There should be a lot of hard drive activity while it runs. All it does is call one Win32 API function call - nothing complicated and nothing special that I came up with.2) Why didn't you say that before? ;-)

"1) I didn't change anything here".....this is very odd. I've tried repeatedly and always the same result. Left FSAutoStart running for 30 mins before checking back and it was still stuck at that line. After an initial brief period (few seconds only) of case light flickering there was little or no evidence of HD activity throughout the rest of this period and Task Manager confirmed FSAutoStart was still running at the end! This behaviour is definitely different to previous builds. Ah well, I guess I'll just have to switch that option off.It would be interesting for others to report on their experience in this particular area as it might turn out to be another of these things that is system specific. I'm pretty sure I didn't make any changes between using the previous build (yesterday) and build 7."2) Why didn't you say that before?".....sawrreee! Only occurred to me during testing after the release. Maybe I should apply to be on the next Beta team :)Best,Mike

Windows XP Home - it took about 2 seconds to get past FITtE.

"Windows XP Home - it took about 2 seconds to get past FITtE"....ditto re. o/s and that mirrors the behaviour in the past on my system.Mike

Well, I think I've isolated the cause - 'System Restore Service'I had it set to 'Stop and Restart' in my custom profiles.When I changed the setting to 'No Action' the behaviour of FSAutoStart returned to normal. The odd thing is on changing it back to 'Stop and Restart' the first test's behaviour was also normal!? Sadly this was short-lived and subsequent tests were as described in my original post.So, I guess the 'System Restore Service' should be left alone. I just don't understand why this different behaviour started now.While I was stopping and restarting this service I kept a check on the available number of restore points already created. This remained at 8 which surprised me as I was half expecting to see them all wiped out when the service was stopped. Can anyone explain this?Mike