[PCWorld]

Post your comments for Windows Takes Too Long to Boot here

[sickpup]

I prefer CCleaner to manage my startup applications. While these might affect windows boot time this has been an issue for since XP. The big issue is all the items Windows loads and how it prioritized resources. For example, I know there are lots of Windows services that need to start which are critical, not all need to be loaded before I can start using my desktop. They need to find a way to do a staged loading process (boot time, windows essentials after desktop loading, startup applications). With the use of multiple cores and RAM this should not be a problem to continue loading items while I begin using my PC.

[LeeChaql]

linix is faster to a working scenario and to be honest I don't know why. probably the main reason is there's no virus checking going on. another may be that the partition type is faster as well (thereby making disk access quicker). remember that there's a LOT of disk access at boot time regardless of what OS is loading. and finally as is mentioned here MS may have more threads running by default (and they may be slower as well). traditionally linux is "lean and mean" by default while windows represents "gloat and bloat" by default.

[xyberviri]

LeeChaql, on 16 April 2012 - 01:30 PM, said:

linix is faster to a working scenario and to be honest I don't know why. probably the main reason is there's no virus checking going on. another may be that the partition type is faster as well (thereby making disk access quicker). remember that there's a LOT of disk access at boot time regardless of what OS is loading. and finally as is mentioned here MS may have more threads running by default (and they may be slower as well). traditionally linux is "lean and mean" by default while windows represents "gloat and bloat" by default.

Windows 7 starts up in 30 seconds on most systems when its powder fresh, its all the crap that gets installed that insists on having a loader, adobe is notorious for this.

[kennyrosenyc]

Autobooting software can be a serious issue, particularly if you're using anything Adobe. I find that having more RAM trumps it though. If you have more than 8GB you can have Windows autoload almost anything so long as it fits into the extra RAM space. Windows 7 Ultimate can address up to 196GB of RAM so you can conceivably load everything on start up and it won't affect the speed of your computer as you have 8GB untouched. This is how I do it and my computer is still wicked fast. I should also point out that my computer also has 2 graphics cards and is kept absolutely immaculate at all times as well though.

[xImran]

kennyrosenyc, on 17 April 2012 - 05:56 AM, said:

Autobooting software can be a serious issue, particularly if you're using anything Adobe. I find that having more RAM trumps it though. If you have more than 8GB you can have Windows autoload almost anything so long as it fits into the extra RAM space. Windows 7 Ultimate can address up to 196GB of RAM so you can conceivably load everything on start up and it won't affect the speed of your computer as you have 8GB untouched. This is how I do it and my computer is still wicked fast. I should also point out that my computer also has 2 graphics cards and is kept absolutely immaculate at all times as well though.

Having more RAM is good but if you have too many programs auto starting when the windows load I doubt it will help much with start up time unless you have SSD.

At start-up the main bottleneck is HDD as all the programs need to be read from HDD and loaded into the memory.

[preferreduser]

using MS services works better than ms config.
"Once a service is installed, it can be managed by launching "Services" from the Windows Control Panel → Administrative Tools or typing "Services.msc" in the Run command on Start menu. In Windows Vista and later, it can be started or stopped in the Services tab in Windows Task Manager, where its process can also be found. The "Services" management console provides a brief description of the service functions and displays the path to the service executable, its current status, startup type, dependencies and the account under which the service is running. It enables users to:
Start, stop, pause or restart services.
Specify service parameters.
Change the startup type which includes Automatic, Manual and Disabled:
Automatic starts the services at system logon,
Manual starts a service as required or when called from an application (according to definition, but only some of the time in practice, depending on the service),
Disabled completely disables the service and prevents it and its dependencies from running.
Automatic (Delayed) is a new startup type introduced in Windows Vista, that starts the service a short while after the system has finished its booting and initial busy operations, so that the system boots up faster.
Change the account under which the service logs on.
Configure recovery options upon service failure.
Export the list of services as a text file or a CSV file.
In Windows XP Service Pack 3 and Windows Vista, besides the Services management console, users can manipulate services using MSConfig. The use of MSConfig to manage services, however, causes a prompt on the next startup. MSConfig can hide all operating system services for troubleshooting. Users can also use the SC command in the command prompt."- Wiki
http://en.wikipedia....Windows_service