Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, August 13, 2018 3:48 PM
Hello. I desperately need you guys' help. I've been suffering from office setup. I've done my best to solve the problem and I've been communicating at mssoft community but havent' got any proper answer.
I have used
o15 ctrremove program and, removed all document security programs might affect on ms office
and checked system file error on command prompt and there was no problem.
Also tried to remove .net framework but win10 already included it in itself so I wasnt able to remove it.
So.. here is my effort and the problem is.
EVERY SINGLE TIME when I try to setup the office , it fails and says
1: 1935 2: {91434829-10AB-4DB1-0C5C-73E0FC8B9BC8} ( the code in { } changes everytime when the folder name below changes) 3: 0x80131049 4:
lAssemblyCacheItem 5: Commit 6: Policy.12.0.office,(This folder name changes like.. policy.11.0~~blah ) fileVersion="15.0.4420.1017", version= "15.0.0.0000000", culture="neutral",
PublicKeyToken="71E9BCE111E9429C", processorArchitecture="MSIL"
For me it sounds like there is some file error on policy.11.0. ~ 12.0 office folders because in these folders, there are name of folder or file of 15.0.4420.1017 71e9bce111e9429c .... just the same as the part of the error message.
I found the SetupExe logs and copied some here, ( I cant upload any image here, i don't know why.) Please check it up. I'm looking for a job these days so I swear I reallllllly NEED Word for my resume , etc.... HELP ME...........
2018/08/04 16:06:58:128::[15176] MSI(INFO): '08/04/2018 16:06:58.128 [14712]: Assembly Install: Failing with hr=80131049 at CAssemblyCacheItem::LegacyCommit, line 1323
'
2018/08/04 16:06:58:129::[15176] MSI(INFO): '1: 1935 2: {91434829-10AB-4DB1-9C5C-73E0FC8B9BC8} 3: 0x80131049 4: IAssemblyCacheItem 5: Commit 6: Policy.12.0.office,version="15.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL" '
2018/08/07 01:46:55:099::[1500] MSI(INFO): '08/07/2018 01:46:55.099 [7724]: Assembly Install: Failing with hr=80131049 at CAssemblyCacheItem::LegacyCommit, line 1323
'
2018/08/07 01:46:55:101::[1500] MSI(INFO): '1: 1935 2: {91434829-10AB-4DB1-9C5C-73E0FC8B9BC8} 3: 0x80131049 4: IAssemblyCacheItem 5: Commit 6: Policy.12.0.office,fileVersion="15.0.4420.1017",version="15.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL" '
2018/08/04 02:05:33:200::[5072] MSI(ERROR): '1: 1712 '
These contents are what I found the most out of the exe logs have been made. As I said one time above, the folder name changes to also policy.11.0.office or policy.11.0.Vbr... etc.
And I found this message in the latest failed setup log
2018/08/07 01:46:55:131::[1500] Error: MsiEndTransaction failed. MsiEndTransaction ErrorCode: 1603(0x643).
which is not error 1935, but error 1603.
HELP ME PLEASE. SAVE me from this hell. THANKS
All replies (19)
Tuesday, August 14, 2018 10:28 AM
Hi,
Thank you for doing so many attempts.
Are you installing Office 2013? On this device, have you installed and uninstalled other Office products before?
I recommend that you install the Microsoft. NET Framework for Windows installation that meets the requirements for Office installation and operations. You can download and install Microsoft . NET Framework 4.7 from Microsoft website to see if the problem can be resolved.
To diagnose this problem for you better, can you post the complete installation log to me?
Please send the log file as an attachment to the following mailbox that we use to collect the information: **GBSD TN Office Information Collection **[email protected]
Please attach this link to the post in the subject of the email to help us differentiate messages. I will try to reproduce your problem in the test environment, for further analysis. I will continue to focus on this issue and look for a more appropriate solution.
If you have any question or update, please feel free to let me know.
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Thursday, August 16, 2018 1:16 AM
Hello,
Any update here? Have you solved the problem? Is my answer helpful to you?
I'm looking forward to your response. If you have any additions, or update, please feel free to let me know.
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Wednesday, August 22, 2018 1:06 AM
Hi,
This thread has been around for a long time.Please remember to mark the replies as answers if they helped.Please help us close the thread.
Thank you for understanding! If you have any question, or update, please feel free to let me know.
I wish you a happy life!
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Wednesday, August 22, 2018 6:32 PM
Hi team,
I too had a same issue on two different computers. This issue is faced by Laptop which has preinstalled Office application from windows store .. I have uninstalled the Microsoft desktop apps and able to install Office 2016, but not able to install visio 2016.
Regards,
Nandha
Nandha Kumar J Techincal Consultant Chennai, India
Monday, August 27, 2018 10:19 AM
Hi Nandha,
I am sorry that I did not respond to you in time. Have you solved your issue? If the problem persists, I advise you to open a new thread to ask question in TechNet Office Forums for help,you may get more appropriate advice according to your scenario.
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Friday, January 25, 2019 3:00 PM | 1 vote
what worked for me was deleting the following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Office
Friday, January 25, 2019 10:47 PM
This did not help at all. I removed that key, restarted and ran the setup file and still same error. Has anyone found a fix for this? I've installed this licensed Office on 5 previous computers without issue. This was open value license so they own this software and have plenty of licenses.
Lisa Veneri
Wednesday, February 27, 2019 9:59 PM
No help, still broken. Brand new computer, fresh install, Office 2013 Pro still fails 1935 error. .net framework repair does nothing, create new local admin user does nothing, compatibility mode does nothing! This is so stupid that Microsoft products will not even install on Microsoft Operating systems.
Thursday, April 4, 2019 4:13 PM | 5 votes
This is the key to delete.
HKLM\Software\Microsoft\AppModel
Be sure to backup your registry before altering..
Hope this helps..
James
Friday, April 19, 2019 10:39 PM
This worked for me on brand new Optiplex 7060 machines, thanks so much. I have been trying many of the 'older' solutions and nothing was working. I needed to get this straightened out before installing 8 new PC's at a law firm.
Tuesday, May 7, 2019 1:32 PM
Thank you!!! This worked like a charm!
Monday, May 20, 2019 9:37 AM | 1 vote
This is the key to delete.
HKLM\Software\Microsoft\AppModel
Be sure to backup your registry before altering..
Hope this helps..
James
Good afternoon!
Should I delete the folder AppModel?
Thanks for the answer
Thursday, May 30, 2019 6:22 PM
This worked for me. Must be something to do with the Trial Office that MS keeps insisting on installing! It also created a ton of other issues too but that's just what I can come up with as far as the possible cause.
.Net was already installed and the latest version.
Tuesday, June 11, 2019 2:54 PM
This is the key to delete.
HKLM\Software\Microsoft\AppModel
Be sure to backup your registry before altering..
Hope this helps..
James
Para los que tengan este problema al quitar el office preinstalado de fabrica en equipos, solo deben abrir REGEDIT y eliminar esa carpeta AppModel, después instalar office, no es necesario reiniciar. Me funcionó en equipos Lenovo con office precargado y despues instalar office 2016.
Friday, July 5, 2019 8:03 AM
This worked! after trying so many different solutions. weird issue and even weirder solution. Thank you for finding it and/or posting it here.
Sunday, August 18, 2019 3:19 PM
what worked for me was deleting the following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Office
where to find this registry key? can someone show steps by steps? i desperately need helps right now
thank you all!
Thursday, September 26, 2019 3:08 PM
Fantastic! It works! (With Office 2016 Professional x86). Thanks a lot.
Tuesday, November 12, 2019 4:52 PM
+1, saved me hours of trial/error.
Thanks a lot!!!
Saturday, December 7, 2019 8:04 PM
Thank you, this worked also for me.<style></style>