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

Anonymous
2010-01-24T04:01:43+00:00

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!!!

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

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 No comments
Answer accepted by question author
Anonymous
2011-03-17T00:12:23+00:00

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.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2010-06-21T04:27:29+00:00

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.

Was this answer helpful?

80+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2010-02-09T14:17:07+00:00

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

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2010-09-03T00:15:06+00:00

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!

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Most helpful
  1. Anonymous
    2011-03-14T22:13:55+00:00

    I have the same problem, and a have tried a number of proposed 'solutions' to no avail. 

    It seems from other posts here that the root of the 1935 error is is a problem with windows updsate failing to apply win 7 sp 1.  This sp was released in the last few weeks, and to my understanding the update is failing because of a conflict of virus scanner and language packs.  The failure may corrupt your registry.

    To see if this may be you then try this at the command propmt as administrator:

    sfc /scannow

    This will check all the versions of your (file system) installed components.

    If this command fails with a 'Windows Resource Protection' error then its bad news. Further evidence of registry problems can be found by going into control panel/Programs and Feqatures  and open 'Turn ~Windows Features on or off' .  ~The dialog box that pops up and normally contqains internet explorer is instead blank. 

    To pinpoint the failing registry items take a look at the log file at %windir%\Logs\CBS\CBS.log.  Note this may be read only so copy it first.

    Let me know if the above helps.

    Was this answer helpful?

    0 comments No comments