Follow this link to Microsoft Technet. It will describe all of the IKernel.exe problems and hopefully you will find the answer there
http://search.technet.microsoft.com...rand=technet&locale=&refinement=00&lang=en-gb
If you cannot access the site, which sounds as if you cannot here is a summary:
SYMPTOMS
When you try to install a program that uses InstallShield, you may receive the following error message:
The install Shield engine "ikernel.exe" could not be launched -Error loading type library /dll
Back to the top
CAUSE
This issue may occur if one or more of the following files are missing from the Windows\System32 folder: Stdole32.tlb
Stdole2.tlb
Stdole.tlb
Back to the top
RESOLUTION
To resolve this issue, expand the appropriate file from the Windows XP CD: 1. Click Start, click Run, and then type CMD. Click OK.
2. To change to the root folder of drive C, type cd\, and then press ENTER.
3. Insert the Windows XP CD, type Expand cd_drive_letter:\i386\filename.tl_ drive:\Windows\system32\filename.tlb, and then press ENTER, where filename is the name of the file that you want to expand and drive is the letter of the drive where Windows is installed.
For help with the Expand command, type EXPAND /? at a command prompt.
SYMPTOMS
You have a computer that is running Winternals Administrator's Pak. When you try to install a product that uses the InstallShield installer, you may receive the following error message:
The InstallShield Engine (Ikernel.exe) could not be launched. Error Loading Type Library/DLL patch
Additionally, you cannot continue with the installation.
Back to the top
CAUSE
This problem occurs when InstallShield components on the computer are corrupted or missing.
Back to the top
RESOLUTION
To resolve this problem, use the following methods. After you complete a method, run Setup. If Setup does not work, go to the next method.
Back to the top
Method 1
Delete the files that are in Temp directory.
Back to the top
Method 2
Delete the following folder:
C:\Program Files\Common Files\InstallShield\Engine
Back to the top
Method 3
Follow these steps: 1. Open the following folder:
C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32
2. In this folder, delete the folder that contains the IKernel.exe file.
3. Install and run the InstallShield installer. To do this, visit the following Web site:
http://consumer.installshield.com/kb.asp?id=Q108322 (
http://consumer.installshield.com/kb.asp?id=Q108322)
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
SYMPTOMS
Programs that use the InstallShield program may not start, and you may receive one of the following error messages:
Setup failed to launch installation engine: Access is denied.
or
Error installing Ikernel.exe, access is denied.
Back to the top
CAUSE
This behavior can occur if there are insufficient Component Object Model (COM) permissions.
Back to the top
RESOLUTION
To resolve this behavior, set the necessary permissions that are needed to successfully complete the installation: 1. At a command prompt, type: dcomcnfg.exe. The Distributed COM Configuration Properties dialog box is displayed.
2. Click the Default Security tab.
3. In the Default Access Permissions section, click Edit.
4. Ensure that you have "Allow Access" beside your name.
5. If you do not have "Allow Access" next to your name, either modify an existing profile or create a new profile that has the necessary permissions.
6. Apply all the changes and attempt to run Setup.
Back to the top
MORE INFORMATION
If installation or initialization errors, or denial of access errors occur, you may not have sufficient COM permissions on the workstation or server to successfully complete the installation.
This behavior can also be caused by a logon script, domain policies, or file system permissions. If this behavior persists, contact InstallShield Technical Support at either of the following InstallShield Web sites:
http://www.installshield.com/ (
http://www.installshield.com/)
http://support.installshield.com/ (
http://support.installshield.com/)
InstallShield Technical Support: (847) 240-9111
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
SUMMARY
If you try to install an application on a Microsoft Windows-based device, and the installation process requires Microsoft ActiveSync 3.6, you may receive one of the following error messages:
Message 1
The installShield Engine (iKernel.exe) could not be installed.
IKernel.exe could not be copied to 'C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32'.
Make sure that you have the appropriate privileges to copy files to this folder. (0x5)
Message 2
"Invalid Windows CE Setup Files: Application Manager cannot install this application on your mobile device due to an invalid setup file. Reinstall and try again."
MORE INFORMATION
To install any application on a Windows-based device, you must have Administrator rights because some files that can be changed or updated are system files. To change system files, you must have Administrator rights. Restricted rights and Standard rights are insufficient. Do not change the current applications to remove all the applications except ActiveSync. If you leave the other applications listed, searches may be more inclusive.
--------------------------------------------------------------------------------
APPLIES TO
Microsoft ActiveSync 3.6
Back to the top
Keywords: kbdswce2003swept kbinfo KB825676
Hope this helps mate. Microsoft Access rights over the Kernel part of the OS are notoriously difficult to resolve. You could try accessing the Virgin support line (there should be a telephone number somewhere in your documentation)
DG