There are a whole host of runtime errors that can plague the computer at any time. The very fact that we live in a dynamic world where all sorts of programming and software can exist within the operating system environment will inevitably lead to many incarnations of programming and registry problems. Runtime error 372 is associated with the Microsoft Visual Basics environment and when it loads an Image List control, conflicts and problems with the software might make you receive a host of error messages that include (and somewhere along the lines of) - the program failing to load the control image list from a file that is called mscomctl.ocx. One of the common problems is that Windows will say that the version of this file is either outdated or missing.



The problem could be attributed to problems of colour depth within the desktop or icons or an application is running a conflicting colour depth. The other problem might be that there is a problem within the registry, invalid program entries that are associated with the Visual Basics Runtime environment can cause Windows to choke when it tries to load the specific program. At the end of the day, it all boils down to the registry. Runtime Error 372 is just one of the problems that is associated with the registry - an all too familiar signal that there is something wrong with how you use the PC. Don't be alarmed, every one of us is unknowingly slowly but surely decaying the registry because our daily lives require us to consistently add and remove programs, change system files or add components to the computer. We live in a philosophy of change and this mantra has translated itself to the computer. While change is good, change when it comes to the computer, change can cause some bad side effects. Bad uninstalls of programs (which happens all the time) can cause problems like program entries still existing for those which have been deleted, or orphan keys associated with the same problems.

Also, viruses, Trojans and malware also infiltrate the registry and add lines of information and code onto the registry which cause many problems within the OS. All these problems add up to a registry that doesn't work as it should and when this happens, you get familiar runtime errors, active X runtime errors and even major and drastic computer slowdowns. The solution has always been a registry cleaner and finding one is as simple as getting a tray of eggs from the local supermarket. Point and click, enter the words in a search engine and you will get a whole host of options. Of course in this case you should always compare the many available online and do a little research to figure out which registry cleaners are the better ones, floating atop the rabble below.

Spend a little time (and in some cases a little money) to get a really good one. When it comes to the computer, which has become the extension of the human being in this day and age, you cannot make any rushed decisions.