Ask These Guys

Microsoft Windows XP is a complex operating system and therefore has several different reasons why errors might be generated on it. Discussed here are three uncommon Windows errors and the methods you can use to resolve them.Code 10 Error

Code 10 error usually occurs when the driver of a hardware is missing, damaged or faulty and the driver file does not comprise the FailReasonString value defined in its hardware key. When a code 10 errors occurs, you will receive an error message similar to the one given below:

“This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)”

To resolve the code 10 error, you may either have to remove and then reinstall the faulty driver, update the existing driver, or rollback a recent driver update. You can do these tasks, by performing the following steps:

1. Open Control Panel.
2. Select Performance and Maintenance and then select System.
3. In the System Properties dialog box, open the Hardware tab, and then click Device Manager.
4. Here, select the faulty device.
5. In Driver status section on the General tab, you can view the details regarding the problems with the device driver.
6. Next, display the Driver tab and select the Update Driver, Roll Back Driver, or the Uninstall button to resolve the problem.

Note: When you uninstall a driver, it is recommended that you run a registry cleaner to scan and remove any left behind driver entries, before reinstalling the driver again.

Runtime Error 1706

Error 1706 is a runtime error, usually displayed when you install a program using InstallShield. When the error occurs, error messages similar to the ones given below may be displayed, and you may be asked to specify the path to the MSI package:

“Error -1706: No valid source could be found for product.”

“Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see <path to program that will provide you with the required help>.”

Error 1706 may occur, when one of the following conditions is true:

• Source files for the program you are trying to install are not available to Windows installer.
• The program you are trying to setup was earlier installed over a network share which is no longer available.
• Windows installer keeps prompting to specify the source of setup file, when you are trying to run the setup from a CD.
• Installer prompts to provide path the CD when you try to cancel the setup.
• You are trying to install software updates or patches.

• Your system is in Maintenance mode.
• There are caching problems with MSI package, which is cached in the C:\winnt\Installer directory.

To resolve the error, you need to ensure the following:

• You must be logged on to the system with user account that has administrative rights to your computer.
• If installing over a network, you must have full rights to the network share you are running the setup from.
• If the setup is unable to locate the setup source, try to use the Windows Search feature to look for the same.
• You may have to update the current InstallShield installation if the version existing on your computer is outdated.
• You may also use a good registry cleaner tool to scan the registry for conflicts and resolve cache-related problems.

Runtime Error 429

Runtime Error 429 is usually generated when you try to automate Microsoft Office programs, such as Microsoft Word or Microsoft Excel. The error usually occurs when the CreateObject function or New operator of Microsoft Visual Basic (VB) is used during the automation process to an Office program instance. When the error occurs, an error message similar to the one given below maybe displayed on the screen:

Run-time error ‘429?: ActiveX component can’t create object

You can resolve this error by re-registering the Office application causing the problem on your system. For example, if the error is generated from Excel, you need to open Start menu, select Run, type C:\Program Files\Microsoft Office\Office\Excel.exe /regserver and then press Enter.

The problem may also occur due to problems with the program registry entries. To repair these entries, you may use a reliable registry cleaner tool to locate the incorrect entry or entries and repair them.