Windows Vista Ultimate Edition ERROR

Regsvr32.exe is included with Microsoft Internet Explorer 3.0 or later versions, Windows 95 OEM Service Release 2 (OSR2) or later versions, and Windows NT 4.0 Service Pack 5 (SP5) or later versions. Regsvr32.exe is installed in the System (Windows Me/Windows 98/Windows 95) or System32 (Windows NT/Windows XP/Windows Vista/Windows 7) folder.

Note On a 64-bit version of a Windows operating system, there are two versions of the Regsv32.exe file:

• The 64-bit version is %systemroot%\System32\regsvr32.exe.
• The 32-bit version is %systemroot%\SysWoW64\regsvr32.exe.

Back to the top

Regsvr32.exe usage

RegSvr32.exe has the following command-line options:

Regsvr32 [/u] [/n] [/i[:cmdline]] dllname

/u - Unregister server
/i - Call DllInstall passing it an optional [cmdline]; when used with /u calls dll uninstall
/n - do not call DllRegisterServer; this option must be used with /i
/s – Silent; display no message boxes (added with Windows XP and Windows Vista)

When you use Regsvr32.exe, it attempts to load the component and call its DLLSelfRegister function. If this attempt is successful, Regsvr32.exe displays a dialog box that indicates success. If the attempt is unsuccessful, Regsvr32.exe returns an error message. This may include a Win32 error code. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

193625  WinInet error codes (12001 through 12156)

For example, to manually register a Sample.ocx ActiveX control, type the following command at command prompt:

c:\regsvr32.exe sample.ocx

Back to the top

Regsvr32.exe error messages in Windows Vista and later

The following list contains RegSvr32 error messages and possible causes.

The command-flag ""%1"" is not valid. Please review the command usage and try again.

An invalid combination of options was passed in the command line to regsvr32.exe.

This command is only valid if a Microsoft Visual Studio OLE Custom Control project is opened.

Regsvr32.exe was invoked by Visual Studio but no modules were specified in the command line.

To register a module, you must provide a binary name.

Regsvr32.exe was invoked without specifying any modules in the command line.

The command OleInitialize failed to run. Your computer might be low on memory. Close any open programs and then try again.

Regsvr32 must initialize the COM library before it can call needed COM library functions and uninitialize the library when it shuts down. These error messages occur if an attempt to initialize or uninitialize the COM library is unsuccessful.

The module ""%1"" failed to load.\n\n Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.\n\n%2.

There was an error in loading a module that was specified in the command line. The error text appears as part of the message.

The module ""%1"" was loaded but the entry-point %2 was not found.\n\nMake sure that ""%1"" is a valid DLL or OCX file and then try again

Regsvr32.exe was unable to find the required entrypoint in the module specified in the command line. This can occur if the entrypoints are not properly exported from the module or if the module is not a .DLL or .OCX file.

The module ""%1"" was loaded but the call to %2 failed with error code %3.\n\nFor more information about this problem, search online using the error code as a search term.

There was an error when regsvr32.exe invoked the entrypoint in the module specified in the command line. The error code appears as part of the message

The module ""%1"" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.

This error can happen, for example, if regsvr32.exe is run on an x86 machine and the module specified in the command line is a 64-bit module.

Back to the top

Regsvr32.exe error messages prior to Windows Vista

The following list contains RegSvr32 error messages and possible causes.

Unrecognized flag: /invalid_flag

You typed an invalid combination of flags or switches (refer to the "Regsvr32.exe Usage" section in this article).

No DLL name specified.

You did not include a .dll file name (refer to the "Regsvr32.exe Usage" section in this article).

Dllname was loaded, but the DllRegisterServer or DllUnregisterServer entry point was not found.

Dllname is not a .dll or .ocx file. For example, typing regsvr32 wjview.exe generates this error message.

Dllname is not an executable file and no registration helper is registered for this file type.

Dllname is not an executable file (.exe, .dll, or .ocx). For example, typing regsvr32 autoexec.bat generates this error message.

Dllname was loaded, but the DllRegisterServer or DllUnregisterServer entry point was not found.

Dllname may not be exported, or a corrupted version of Dllname may be in memory. Consider using Pview to detect the file and remove it.

Dllname is not self-registerable or a corrupted version is in memory.

For example, typing regsvr32 icwdial.dll returns this error message because the Icwdial.dll file is not self-registerable. If you suspect a corrupted version of Dllname is in memory, try restarting your computer or re-extract the original version of the file. If you are running Windows NT, you may need to use the Kill or Pview tool from the Microsoft Windows NT Server 4.0 Resource Kit. For additional information, click to view the following article in the Microsoft Knowledge Base:

197155  How to kill an orphaned process

OleInitialize failed (or OleUninitialize failed).

Regsvr32 must initialize the COM library before it can call needed COM library functions and uninitialize the library when it shuts down. These error messages occur if an attempt to initialize or uninitialize the COM library is unsuccessful. For example, the Ole32.dll file may be corrupted or may be the wrong version.

LoadLibrary("Dllname") failed. GetlastError returns 0x00000485

From Winerror.h, 0x00000485 = 1157 (ERROR_DLL_NOT_FOUND), which means "One of the library files needed to run this application cannot be found." For example, typing regsvr32 missing.dll returns this error message if the Missing.dll file is not found.

LoadLibrary("Dllname") failed. GetLastError returns 0x00000002

From Winerror.h, 0x00000002 = 2 (ERROR_FILE_NOT_FOUND), which means "The system cannot find the file specified." In other words, a dependent DLL was not found. For example, typing regsvr32 icwdial.dll with Tapi32.dll (a dependency) missing, returns this error message.

LoadLibrary("dskmaint.dll") failed. GetLastError returns 0x000001f

From Winerror.h, 0x000001f = 31 (ERROR_GEN_FAILURE), which means "A device attached to the system is not functioning." This behavior can occur if you try to register a Win16 .dll file. For example, typing regsvr32 dskmaint.dll returns this error message.

DllRegisterServer (or DllUnregisterServer)in Dllname failed. Return code was: string

Search Winerror.h for string.   Source By http://support.microsoft.com

Most Common Windows Vista Problems and Solutions

Windows Vista, released some 4 years back is one of the most talked about OS from Microsoft™. Large number of support issue cropped after it was released based upon the performance, hardware support, usability etc. People often said that Vista has been released pre mature and not tested rigorously for various features and performance. After the release of SP1 (Service Pack), the OS became quite stable and compliant. But still some of the problems user face while using this OS as listed below.

Vista doesn’t supports my new hardware

This is one of the most common problems that users see when they buy new hardware for Vista. The hitch is that the new stuff doesn’t get recognized and doesn’t install automatically the way it should. Immediate solution to this type of problem is that one needs to install Service Pack 2 (SP2), which is the latest one. This pack contains driver support for various new released hardware and other system/security updates.

Solution

Make sure that you have SP1 installed before installing SP2. The best way to find out, which Service Pack is installed on your machine, is to go to Start – Computer and right click on it and select Properties. To install SP2 (or SP1) you need to enable Windows automatic updates and wait for the system to download and install them.

Slow speed or high response time

Windows Vista needs at least one GB free on the hard disk for file paging purpose. Make sure that you have that much amount of unused space on the hard disk. Installation and enabling of multiple Antivirus and malware detection tools could also be one of the reasons of Win Vista lousy performance. Enable only one Antivirus/Antispyware tool at a time (so that there is no redundancy) and system performs smoothly.

Resource Comparison Chart (courtesy Wikipedia)

Solution

If your PC is old and do not have latest hardware (memory, processor, etc) then Vista could run sluggish. Recommended hardware for this OS is at least 1GHz processor speed, 1 GB of RAM and 15GB of space available on the Hard Disk. More information about system requirements can be found here.
In the resource comparison chart above, it’s very clear that resource used is directly proportional to the time of release

Laptop battery draining fast

People often complain that after installing Vista on their Laptop, the battery life has reduced considerably. This is true to a large extent. Since Vista is a new OS, it has lots of new features and applications, which tend to take more system resources including memory, processor and even battery!

Solution

The best way to tackle this problem is to reduce any such features, which are not that useful and are cosmetic in nature. For example if user turns Aero Visual effects off, then battery consumption reduces considerable making it even equivalent to Win XP.

Software bloat

Software bloat is a condition wherein the size (or footprint) of the software under consideration is quite large compared to the feature set or utility it provides. It is true for Windows Vista and other Microsoft OS as well to a large extent. This is because today’s software is packed with large number of features all of which user may or may not use. Industry experts say that most of the users only utilize only 20% of the full capability of any OS, while rest 80% they never use at all!

Solution

Workaround for this problem is that instead of default (or express installation), go for custom installation and select only those components, which you really require (stand good for any kind of generic software installation). Even after installation, user can go to Add or Remove Programs (in control panel) and click on Add/Remove Windows Components to specifically select/deselect desired options 
There are more small and big problems related to Vista, which are listed on Microsoft Website. Apart from this some general precautions like keeping Antivirus and Windows Vista up to date by turning Automatic updates on. Also time to time do a system tune-up by running Windows Disk Defragmenter and Disk Cleanup utility provided under System Tools can really help in keeping problems at bay.

Source By  http://techproblems.org

Windows problems associated with registry errors

If the registry is full of errors and not checked regularly, then a lot of problems can arise. Even though the computer may be new and there are not any visible errors, there is still the need to check the registry because errors will ultimately accumulate and cause severe problems. Some of the most common errors that we face when we are using the computer are directly caused by having a lot of errors in the windows registry. One of the most common is that as time passes, the computer takes longer to start up. This is due to the fact that the computer has to access the windows registry on startup and thus if this is full then this will take longer. In the worst cases, there might even be the case where one cannot start Windows.
Constant crashes whilst using applications and numerous error messages are also two problems caused by the windows registry being full of errors. This may be caused by broken paths, missing links and obsolete start menu items. These occur because when something is deleted, it is never deleted to the full. Also, this may be caused by having outdated recent files list and invalid fonts.
In some extreme cases due to high fragmentation, the registry file size exceeds the registry size limit assigned by Windows, thus disallowing any modifications. Obsolete shared DLLs and folders, unused and unwanted drivers and file extension associations are also problems directly related to the windows registry.
Ultimately all of this will all result in slowness of the system operating speed and poor performance. Thus one can use Registry Booster 2009 by Uniblue, a leading registry repair software utility to defrag, clean and repair the registry. By using this software regularly it will dramatically improve the performance and stability.

 Source By  http://www.uniblue.com