ERROR 1935 When installing microsoft office 2007 on new comp with windows 7.

Anonymous

PLEASE help me before i lose my head...

I just purchased a new computer with windows 7 on it. I am trying to install Microsoft Office 2007 but I keep getting the "ERROR 1935 AN ERROR OCCURRED DURING INSTALLATION OF ASSEMBLY COMPONENT."

I read and attempted the microsoft .net framework fix. I tried to install it, but it says it's already installed as a part of the operating system-but when I go to control panel/programs, it isnt listed.

Why is this happening, and HOW can I fix it!!!

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Same Problem:

Upon Installation of Office 2007 on Windows 7 64 Bit Error 1935 with Assembly {63E949F6-03BC-5C40-A01F-C8B3B9A1E18E}. I tried almost everthing, repaired all DotNet Frameworks, Sfc /Scannnow , reinstalled all VC++ Redistributable Packages and even a Windows 7 inplace update didn't solve this problem.

But after all there was a solution:

I installed Microsoft .NET Framework SDK v2.0 (64bit)

http://download.microsoft.com/download/e/e/2/ee2042c3-20d3-4303-b67f-e9184085c58c/setup.exe

Now every thing works fine.

0 comments

Answer accepted by question author

Anonymous

I solved my problem by uninstalling two .Net framework 4 entries on the remove all programs pane. One was listed as "Microsoft .NET framework 4 extended" and the other was "Microsoft .NET framework 4 profile view" (or something similar).

I finally fixed my problem after looking around for days.

0 comments

Answer accepted by question author

Anonymous

Contact your computer manufacturer if Windows 7 came preinstalled for more help on repair for Windows or contact Microsoft Phone support for your region

All the best

ril_max

0 comments

Answer accepted by question author

Anonymous

I know this is well after the fact, but I thought you should know that your .Net Framwwork 4 solution worked perfectly to solve nearly the exact same problem we have been having for DAYS on a computer. We had gone through too many convolutions to describe here, but let's just say that uninistalling .Net was brilliant.

Many thanks!

0 comments

63 additional answers

Anonymous

2014-08-24T17:01:26+00:00

Does that make sense? In order to install a Microsoft application you have to REINSTALL the Microsoft operating system???? What's wrong with this picture? We might be missing something very basic here lads. This is a new computer. It has a trial of Office Home and Student already and you say you are installing another one. Uninstall all Office entries and try the new install again. A second version can cause huge problems of many different colours. Ron

You are right Ron, we are missing something very basic here, we are talking about Microsoft! To begin with if two different versions of Office are "causing huge problems of many different colours", why install allows that? Why it can't check for other versions, uninstall them and start clean installation of new version of Office? Or it is too logical or cost additional money to implement it? Microsoft and registries are the main issue here? **** stored in Windows registries of months of use gets out of control, and creates a mess after a while. In situations like one discussed here, you are stuck. You can't uninstall the old version of office as it prompts you to repair it first, and when you try to do so it ends up with an error 1935. Catch22 and it boils down to Microsoft's crappy and shoddy design and architecture.
Was this answer helpful?

0 comments No comments