So basically, the problem is extreme slow start up?
I do (for testing) install (one after the other) each version of Lazarus. 32 and 64 bit versions. Unfortunately it does not happen on my PC. So I can't check the causes myself...
I can think of a few vaguely possible things, that might take some time during startup.
But those are just guesses. And they shouldn't normally add a big slowdown.... But otherwise I don't have any idea, sorry.
Potential
GUESSES are:
First of all, when an app is started for the very first time, Windows defender (and maybe other AV too) may send checksums to a microsoft server. But usually that adds a few seconds at the very worst. (This could also affect the search for the fpc below, as that also needs to execute the found compiler)
Second, When you start the IDE for the first time (when the config dir is empty), it searches for FPC. It does this because some people don't use the installer, and their fpc may be in a different location. But unless - really unlikely - you have many many files or folders witch fpc in the name, then that again should be a few seconds only.
Then there is
C:\Users\USERNAME\AppData\Local\Temp\0_LazarusMain01
a lockfile. (I forgot about that in my previous post)
That is used to make sure only one IDE is running. => E.g. double clicking an lpi file opens in the already running IDE, rather than opening a 2nd IDE.
If that file exists, and a dead/crashed/hanging (or maybe - not tested - no longer running at all) IDE created it, then I don't know how long an IDE will wait for it....
Also, IIRC by default you may be starting "startlazarus.exe" which then will find and run "lazarus.exe". I don't quite see how that would consume much time (other than disk and/or AV). But as far as guessing goes...
Some versions of Lazarus also searched for fppkg, not sure if 3.n still does...
There could be other issues, that I am not aware off.
If you can spent the time to further investigate....
Check you don't have C:\Users\USERNAME\AppData\Local\Temp\0_LazarusMain01
For you first start, (if you have an empty config, and the load will take longer: You can skip startlazarus.exe. Open the folder in which lazarus was installed, and start lazarus.exe directly from that folder. I doubt that will help, but anyway....
You can create a new file in the folder to which you installed. The same folder in which lazarus.exe is. (not the shortcut, but the real file). New file to be created:
lazarus.cfgThis file will exist, if you create a "2ndary install". => the file is a textfile.
You can add a line
into the file. (or give that to lazarus.exe on the command line.
This will skip the 0_LazarusMain01 lockfile, and a few other file searches..
So if that helps, it will afterwards have to be narrowed down.
If the IDE still takes long to start, you can open the taskmanager and on the "Details" tab check what is running.
- Anything with high CPU
- Any app from the following: startlazarus (if you used that), fpc, ppcx64, ppci386, fppkg.