Please check following things:

• Are Offline folders in use? Are the latest version of F-Secure products in use? If not, has the relevant hotfixes for products been applied?
• Check the programs that run on startup, if there is for example some indexing programs that scans folders on Windows startup. If this 3rd party program opens up all files alphabetically in certain folders, F-Secure Anti-Virus has also to scan all these opened files. This shows up as process Fssm32.exe (F-Secure Scanner Manager) taking all available CPU time, and real slow startup.

This can happen also if you have WFP (Windows File Protection) enabled. This might cause System File Checker (sfc.exe) to go through certain DLL and EXE files at startup. More information about this and also how to disable WFP can be found from Microsoft KB articles below:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;222193
http://support.microsoft.com/default.aspx?scid=kb;EN-US;310747
http://support.microsoft.com/default.aspx?scid=kb;EN-US;222471