Well, if you disabled the ashServ.exe service, then it's possible that ashCmd.exe takes longer to start. The thing is that normally, the resident protection initializes the virus database in memory somehow - for its own scanning, but also for other scanning processes. So, when ashCmd.exe starts, it just uses the virus database from ashServ.exe's memory for the scan. When ashServ.exe is not running, however, it has to initialize the database itself (every time you start it, unless another instance of ashCmd.exe is already running) - which takes some time. 40 seconds is quite a lot though (I'd say it should be seconds, not tens of seconds)... unless the machine is really slow or loaded by other processes.
