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-12-14T22:29:07+00:00

Just sharing my experience - I got a persistent 1935 when trying to reinstall after a motherboard

swap. I spent several days researching and applying everything I could find on the web (including this thread) with no success. I finally called office support and explained what I had been doing. The guy was very polite and professional, and started a remote session to investigate and try to resolve the problem.

For the next 5 hours, I watched off and on as he repeatedly uninstalled .NET, cleaned the registry, and reinstalled incremented versions. At hour 3, he enlisted an additional person and they began using different download versions from Microsoft and Digital River images. At the stroke of 5 o'clock, they

both left, without any resolution, leaving the remote session open and quiet.

My assumption at that point was there must be a .NET corruption in my system that was not being uninstalled/cleaned by the programs we used. So, this morning I backed up the C drive, formatted it,

and installed W7 clean. My very next action was to install Office 2007, and it went to normal termination.

If you've tried the methods listed to this point without any success, it's worth considering.
Was this answer helpful?

0 comments No comments