Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

error 1935 while installing Office 2007 on Vista Business

Featured Replies

Hi all, I'm trying to install Office 2007 on a machine running Windows Vista Business edition, and I keep getting "Error 1935. An error occurred during the installation of assembly component". Some googling has said to reinstall .Net 2.0 on the system, but I can't seem to find where I can do this on Vista. Downloading and attempting to install the Vista version of the .Net 2.0 software yielded nothing (says that I have a newer version) and the same is said of .Net 3.0. Any suggestions?


  • Author

Nope, still "Error 1935. An error occurred during the installation of assembly component {stuff goes in here}. HRESULT: 0x8007054F."

Hmmm - that status code is ERROR_INTERNAL_ERROR. Do you have the msi logs of the installation?

  • Author

Unfortunately I don't. The computer belonged to a student and he needed it back.

  • 2 weeks later...

I got the same error installing office XP, on Ultimate x64. After a long night of troubleshooting I found that is was a rights issue.

For some reason the Trusteruser (which I could not find anywhere) did not have rights to a few folders under the windows directory. (sorry for the vague description becasue this happend about a month ago and I dont remember the folder structure)

UAC was not disabled. so I figured I would try the install using the Administer account. I created a password for it and enabled the account.

I still got the errors. I then decided to try winblows update. There was 2 different patches that would not load because winblows didnt have right to some file under the /windows directory.

So after another reboot. and logging in as Administrator I took controll of the directory, then added rights for administrator and my normal user account.

Once that was done, update without a hitch, and Office XP installed and patched correctly.

The irony here is that I had this exact problem a long time ago with Winblows 2000. I was trying to install some ODBC componet, and got a message that the Administrator account didnt have access to the MSI folder.

Hmmm - that status code is ERROR_INTERNAL_ERROR. Do you have the msi logs of the installation?

"ERROR_INTERNAL_ERROR" likely means hardware issues.

I suggest that you get Memtest86 and Prime95.

Edited by RJARRRPCGP

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.