Asus ptp driver there is a problem with this windows installer package

We need to know the root cause in order to find a final solution for this issue.

A user with this installer problem contacted me and he tried many of the previous solutions and ideas. Thanks Mark for the feedback and the screenshots! By the way, the workaround of using ELAN drivers worked in his case.

We enabled Windows Installer logging with this Microsoft tool: Enable | Disable. Then, a log file is created on the Windows temp folder %temp% when you run the installer. The file name is like “MSI___.LOG“. There it can be analyzed what is causing the error.

The ASUS Smart Gesture installer log contains this error:

This is the complete action with the error, until it starts the rollback:

MSI (s) (E8:3C) [22:11:20:759]: Executing op: ActionStart(Name=_7BC62223_8712_481D_BAE1_B05E6CF21272,,)
Action 22:11:20: _7BC62223_8712_481D_BAE1_B05E6CF21272.
MSI (s) (E8:3C) [22:11:20:760]: Executing op: CustomActionSchedule(Action=_7BC62223_8712_481D_BAE1_B05E6CF21272,ActionType=3090,Source=C:\Program Files (x86)\ASUS\ASUS Smart Gesture\install\x86\BatchCaller.exe,Target=/Install "C:\Program Files (x86)\ASUS\ASUS Smart Gesture\\",)
CustomAction _7BC62223_8712_481D_BAE1_B05E6CF21272 returned actual error code -1 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (E8:3C) [22:11:23:009]: Note: 1: 1722 2: _7BC62223_8712_481D_BAE1_B05E6CF21272 3: C:\Program Files (x86)\ASUS\ASUS Smart Gesture\install\x86\BatchCaller.exe 4: /Install "C:\Program Files (x86)\ASUS\ASUS Smart Gesture\\"
MSI (s) (E8:3C) [22:11:23:009]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (F4:A0) [22:11:23:013]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _7BC62223_8712_481D_BAE1_B05E6CF21272, location: C:\Program Files (x86)\ASUS\ASUS Smart Gesture\install\x86\BatchCaller.exe, command: /Install "C:\Program Files (x86)\ASUS\ASUS Smart Gesture\\"
MSI (s) (E8:3C) [22:11:25:502]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (E8:3C) [22:11:25:502]: Product: ASUS Smart Gesture -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _7BC62223_8712_481D_BAE1_B05E6CF21272, location: C:\Program Files (x86)\ASUS\ASUS Smart Gesture\install\x86\BatchCaller.exe, command: /Install "C:\Program Files (x86)\ASUS\ASUS Smart Gesture\\"Action ended 22:11:25: InstallExecute. Return value 3.
MSI (s) (E8:3C) [22:11:25:517]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (E8:3C) [22:11:25:518]: User policy value 'DisableRollback' is 0
MSI (s) (E8:3C) [22:11:25:518]: Machine policy value 'DisableRollback' is 0
MSI (s) (E8:3C) [22:11:25:527]: Executing op: Header(Signature=1397708873, Version=500, Timestamp=1215738216, LangId=1033, Platform=0, ScriptType=2, ScriptMajorVersion=21, ScriptMinorVersion=4, ScriptAttributes=1)
MSI (s) (E8:3C) [22:11:25:527]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (E8:3C) [22:11:25:527]: Executing op: DialogInfo(Type=1,Argument=ASUS Smart Gesture)
MSI (s) (E8:3C) [22:11:25:527]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 22:11:25: Rollback. Rolling back action:
Rollback: _7BC62223_8712_481D_BAE1_B05E6CF21272

Also, I found that another log is created on C:\Windows\Logs\ASUSSmartGesture.log but it didn’t have information related to the error.

Finally, if you were able to fix this problem, please share your findings. Also, if any of the solutions presented worked for you, leave a comment with your ASUS model and the solution.

ASUS touchpad driver ASUS PTP Driver installation fails Solution

tags: bios  driver

Intelligent Recommendation

More Recommendation

Sometimes, you can encounter the “There is a problem with this Windows Installer package” error while trying to install an application through an MSI installer. This error occurs if your system can’t run a script, program, or DLL file necessary for such operations. You will also encounter corresponding error messages in each case:

• Error 1720: There is a problem with this Windows Installer package. A script required for this install to complete could not be run.
• Error 1721: There is a problem with this Windows Installer package. A program required for this install to complete could not be run.
• Error 1722: There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.
• Error 1723: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run.

Even if they are different errors, you need similar solutions to resolve all of them. First, make sure to log in with an admin account and run the program as an administrator. Some installers require admin privileges to run properly. Also, make sure that there is enough space to install the application.

Re-register Windows Installer

Windows uses the MSIExec engine to run the MSI installer. If the registration of this engine becomes corrupt, you can’t run such installers. To resolve this issue, you need to unregister and then re-register the engine.

1. Open Run.
2. Type cmd and press Ctrl + Shift + Enter to open the Elevated Command Prompt.
3. Enter the following commands:
   • MSIExec /unregister
   • MSIExec /regserver
     

Restart Windows Installer Service

You will also get this error if the Windows Installer service is not running properly or another instance of the installer engine is already running. We recommend checking for both issues at the same time.

1. Open Run by pressing Win + R.
2. Type msconfig and press Enter to launch the System Configuration.
3. Go to the Services tab and search for Windows Installer.
4. Make sure the box next to it is checked and press OK.
   
5. Now, press Ctrl + Shift + Esc to open the Task Manager.
6. Go to the Details tab.
7. Look for msiexec.exe. If it’s there, select it and click End Task.
   
8. Then, open Run again.
9. Type services.msc and press Enter to open Window Services.
10. Look for Windows Installer and check its Startup Type.
    
11. If it shows Disabled, double-click on it and set the Startup type drop-down list to Manual. 
12. Click on Start if the Service status indicates Stopped. Otherwise, click Stop and then Start to restart the service.
    

Restart your computer and check if the issue persists.

Re-register Some DLL Files

Like with the MSIExec engine, your system uses many DLL files while running the MSI installers. You can similarly re-register them to resolve any potential registration issues.

1. Open the Elevated Command Prompt.
2. Enter the following commands:
   • regsvr32 Actxprxy.dll
   • regsvr32 Browseui.dll
   • regsvr32 Mshtml.dll
   • regsvr32 ole32.dll
   • regsvr32 Oleaut32.dll
   • regsvr32 Scrrun.dll
   • regsvr32 Shdocvw.dll
   • regsvr32 Shell32.dll
   • regsvr32 urlmon.dll
     
3. Don’t worry if you get a “The module was loaded but the entry point DllRegisterServer was not found” error, simply move on to the next command.

Troubleshoot Compatibility

If the error has the code 1721, it might be because the installer is for a previous version of Windows and therefore is not compatible with your current system. In such cases, you need to troubleshoot for program compatibility.

1. Right-click on the installer and select Troubleshoot Compatibility or Show more options > Troubleshoot Compatibility.
   
2. Select Try Recommended Settings.
3. Then, click on Test the program.
   
4. If the error doesn’t occur this time, go back to the Troubleshooter and select Next > Yes, save these settings for this program.

Install Necessary Windows Features and Updates

The installation of several programs on your system requires certain supporting software components and features. We recommend installing all such programs to prevent suffering from different installation errors. Even if you already have these components, they might have become corrupt, so it’s worth reinstalling them.

• All available Microsoft Visual C++ Runtime Packages
• Windows Management Framework
• Latest .NET Framework

You should also make sure to have the latest version of your Operating System. The newer applications require the most updated OS versions to be able to provide better features.

1. Open Run.
2. Type ms-settings:windowsupdate and press Enter to open Windows Update Settings.
3. Click on Check for Updates to scan for and download available updates or Install now if your computer has already downloaded them.
   

Re-download the Installer

It is also possible that the installer you downloaded or transferred is not complete. You can check for such issues by checking its properties.

Select the installer and press Alt + Enter to open its Properties and compare the Size and Size on the disk from the General tab. If the Size on disk is much lower than the Size, the file is not complete.

In such cases, you need to download it again. Also, we recommend you ensure that the installer you download matches the system architecture of your computer while doing so.

Take Ownership of the Temp Folder

Many programs including installers make use of the Temp folder inside AppData to store temporary files. By default, each user accounts have the ownership and permissions of the Temp folder for that account. However, if this setting gets changed somehow, you will encounter many issues, including the above.

In such a scenario, you should see the error code 1723 in the error message, so it’s easier to recognize. You need to take ownership and provide permissions to this folder to resolve the issue.

1. Open the Elevated Command Prompt.
2. Enter the following commands:
   • takeown /F %Temp%
   • icacls %Temp% /Grant %userdomain%\%username%:F
     

Uninstall Application Before Reinstalling

Sometimes the previous software of an application can also interfere with the new installation. In such cases, you need to uninstall the previous application first.

1. Open Run.
2. Type appwiz.cpl and press Enter to open Programs and Features.
3. Look for and select your application. 
4. Click on Uninstall or Uninstall/Change > Uninstall.
   
5. Confirm with Yes and follow the on-screen instructions.

Then, update/reinstall the app again by launching a complete installer. If you can’t uninstall the applications, there may be some app-specific reasons causing such errors. You need to check official websites for what to do in such scenarios.

Remove Pending Installations Using Registry Editor

You will also get this error if you try running an installer when another one is already running on your system. Windows will usually warn you if something like this happens, but it can’t do so if the previous instance of installers is stuck. In such a case, you need to remove all pending installations first.

1. Open Run.
2. Type regedit and press Enter to open the Registry Editor.
3. Navigate to Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer
   
4. If the InProgress key is present, delete all the entries inside it.
5. Then go to Computer HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager
6. If PendingFileRenameOperations is there, delete all of its entries as well.

Install a Different Version of Application

Sometimes, the latest version of the application or its installer may have some bugs that are responsible for such issues. In such cases, you will only encounter the above error while trying to install one application but can successfully install other programs through MSI installers. You need to try installing a previous or different version of the app instead to resolve the issue.