after installation its shows error

Question

the setup controller has encountered a problem during install. please review the log files for further information on the error. what we need to do.

Answer 1

Do you see an entry for Office (or Microsoft 365) in the list of Installed Apps in Windows Settings? In that case, I would try repairing the installation; for instructions, have a look at https://support.microsoft.com/en-us/office/repair-an-office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b .

If you don't see your Office product or if the repair fails, remove the broken installation manually (see https://support.microsoft.com/en-us/office/manually-uninstall-office-4e2904ea-25c8-4544-99ee-17696bb3027b) and then start fresh with a new install.

Answer 2

The best first option is to perform a full repair of your Office installation.

Open the Settings App.

Go to Apps, then scroll down to find Microsoft Office

Select that and choose Modify - Online Repair

That should fix any issues with your Office Installation.

Answer 3

Follow these steps to find the cause of the error and decide what to do next:

1. Locate the Office setup log
   • Office Setup writes a log that includes the command line used, checks it performs, and the return code.
   • The log will show if Setup.exe failed itself or if Windows Installer (Msiexec) failed.
2. Check the Setup.exe log for obvious issues
   • Open the Setup log file and look for:
     • The exact command line used to start setup. Verify all properties and switches are correct. For example, if a transform is used, the correct property is:
       • Transforms=<path>\<transform file name>.mst
       • Using Transform= (missing the final “s”) will silently prevent the transform from being applied.
     • Confirmation that the correct OS, service pack, and Msi.dll version were detected.
     • Messages about creating the local installation source (MSOCACHE) and disk space checks.
3. Look for the return code in the Setup.exe log
   • Scroll to the end of the Setup.exe log and find the final return code. For example:

          Chained install return code: 1603
          Shutting down chained setup processing.
          ***** Setup exits
          (return = 1603)
     

   • A return code like 1603 indicates the Windows Installer portion failed. In that case, continue with the Windows Installer logs.
4. Review the Windows Installer log
   • Open the Windows Installer log for the Office installation (this file is much larger than the Setup.exe log).
   • If an error message was shown during setup, search the log for that error number (for example, search for 1327 if you saw “Error 1327”).
   • The log will show the detailed context around the failure, such as invalid drives, missing files, or configuration issues.
5. Fix the issue indicated in the logs and rerun setup
   • Based on the specific error in the Windows Installer log (for example, invalid drive, missing path, or configuration problem), correct that condition.
   • After fixing, rerun the Office setup and verify that the new run completes without errors.

If the controller/setup error persists, always re-check the latest log files after each attempt to confirm whether the failure point or error code has changed.

---

References:

• How to use a setup log to troubleshoot setup problems in Office