How to Boost Windows Loading with New Reg Organizer 6.50
June 17, 2014 (updated 2 years ago) by Chemtable Software
In the brand new version of Reg Organizer 6.50, a system registry manager for Windows, we introduce a totally reworked tool to configure the boot up process of the operating system. “Program Autostart” has been segregated from “Crucial registry sections” to an individual instrument launched from the sidebar of Reg Organizer. It has become a completely new tool under the hood as well. Re-written from scratch, it offers convenient management of autostart programs and understandable display of the results in comparison with previous values.
Previously, you could get only a rough estimation of the effects of autostart boosting, or you had to use the “Applications and services log”. Both options were not too convenient or easy to use. The first way simply doesn’t have any visible parameters, and the second one is too complex to search and compare the data. So we decided to blend the simplicity and easiness of the autostart process depicting it as a diagram right in Reg Organizer. Now, in the completely new “Program Autostart” tool, you can instantly see the results of autostart manipulations and compare them with previous values acquired earlier.
Speeding the system up is usually done via disabling unnecessary autostart elements or removing them. But in Reg Organizer we decided to go beyond that and created one more possibility – creating delayed processes. This method allows you to begin work with the system faster and still run all necessary applications in the background while the system is already being utilized as usual. The best choice for delayed processes are necessary, but non-critical, processes.
When you delay processes, the timer automatically increments by the already selected period. So you can put an element into the autostart queue with merely one click, thus composing the program loading sequence you want on every startup of the computer.
When you disable unnecessary elements in other autostart managers, there is a possibility that these records will re-activate. This is caused by programs that often check if certain autostart registry records are still there, and restore them if they are lost. Fortunately, we foresaw this aspect in Reg Organizer too, so disabled elements won’t re-appear again; they will be automatically disabled even if another program eventually restores them.
And finally, how you can use this in your work? In particular, when you manage autostart elements (remove, disable, or delay starting programs), you need to restart the system and watch the diagram. If everything is done right, the new system loading times should be less than previous ones. If a bar on the diagram has become longer, the loading time has increased, and you should reconsider the order and the number of executed elements.
Since the loading time parameter is not constant and may fluctuate even with the same autostart parameters, you should monitor overall loading dynamics of few recent boot ups instead of just two consecutive loading times.