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
Thursday, September 6, 2018 4:28 PM
Deploying Office 2013 SP1 to Windows 10 1803 on a new pc fails with error 1935. I've also tried installing by just running setup.
Brand new batch of Dell Optiplex 3060's.
Windows 10 1803. Updated today. Dell OEM version.
This has worked on 90 previous pc's. Most of which were Optiplex 3040 and 3050.
The Office trial stuff was on there and I removed it first.
The event log shows "Failed to end a Windows Installer transaction STANDARD. error 1603 occurred while ending the transaction."
All replies (35)
Tuesday, April 23, 2019 2:51 PM âś…Answered | 26 votes
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
Thursday, September 6, 2018 8:31 PM | 3 votes
Update:
The first thing I do on a new pc is remove all the bloatware. Like "My Office", "Candy Crush Saga","Microsoft Office Desktop Apps", etc...
Resetting the pc, which returned all the bloatware, including My Office and Microsoft Office Desktop Apps, allowed the install to finish.
Friday, September 7, 2018 1:45 AM
Hi Darron,
It looks the issue has been resolved now, am I correct? If so, could you help mark your reply as the answer, so that it could benefit other community members when they encounter a similar issue and come across this thread?
If I've misunderstood something, feel free to post back with more details.
Thank you for your understanding and support.
Regards,
Steve Fan
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.
Sunday, February 17, 2019 8:57 PM
Update:
The first thing I do on a new pc is remove all the bloatware. Like "My Office", "Candy Crush Saga","Microsoft Office Desktop Apps", etc...
Resetting the pc, which returned all the bloatware, including My Office and Microsoft Office Desktop Apps, allowed the install to finish.
I have experienced the same. In the past, and with very similar PCs (HP 15.6" laptops) I have had to remove the "trial" edition of the current offering of Office. On the first occasion, I did not realise a trial of Office had been pre-installed, and when I tried to install my own licensed copy (an older edition), some clash occurred and caused me a heap of issues and a support call with Microsoft late into the night.
With a brand new HP laptop running Windows 10, I did my best to remove the Office 365 trial installation, together with a new thing called Office Hub. It was odd this time, because the "Uninstall or change a program" list, found in Control Panel, did not list any Office applications. But they were there in the Start Menu. I uninstalled them using their own "Right-click sand Uninstall" feature and then tried to install my own Office 2013. This resulted in the error code under discussion.
I too have performed a reset - I tried different "levels" of reset. Eventually I had to do what appears to have been a factory reset, which re-installed Windows 10 and blitzed all the user setup. I ran through all that again and left the pre-installed Office icons where they were. Then I re-installed Office 20123 and this time the installation completed. Previously, it got so far, then rolled back complaining of a failure and then displayed the weird error "1935".
I have not used the Office suite yet, so maybe it is still hosed. But I wanted to share my common experience.
The crazy thing is that the rules have changed without any notification. On previous machines, not uninstalling the trial software caused problems with my Office 2013 installation. Now, removing the pre-installed gear causes a problem.
Thanks, Microsoft - you totally rock at wasting users' time.
Sunday, April 14, 2019 12:43 PM
uninstall OneDrive worked for me.
Monday, April 22, 2019 9:45 PM
Removing OneDrive and pre-installed tools on Microsoft Surface 2 does not solve the
1932 2:{559659F8-2117-4E3E-A4C2-828890E30B93} 3: 0x80131049 4:lAssemblyCacheltem 5:Commit 6: Policy.12.0.Microsoft.Office.Interop.Access.Dao, fileVersion="15.0.4420.1017", version="15.0.0.0000000", culture="neutral", publicKeyToken="71E9BCE111E9429C", processorArchitecture="MSlL"
error received when attempting to install Office Pro 2013.
Monday, April 29, 2019 2:00 AM | 1 vote
Darron, You the Man!
Worked Great
Thanks
Danny
Saturday, May 4, 2019 8:43 AM
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
It works!
Thank you so much, Darron.
Monday, May 6, 2019 9:37 PM | 1 vote
This worked for me thank you so much Darron!
Thursday, May 23, 2019 8:38 PM
That worked for me as well, Thanks Darron!!
Monday, May 27, 2019 11:13 AM
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
Worked !!! Thank !!!!
Wednesday, May 29, 2019 12:35 PM
Thx :) Darron works in Denmark too :)
U saved my day, hate to re install just for so little.
THX AGAIN.
Monday, June 3, 2019 4:23 PM
This helped me a bunch, thank you Darron!!
Wednesday, June 5, 2019 5:23 AM
Great fix, thank you. Worked like a charm
Wednesday, June 5, 2019 10:07 AM
Sorted, thanks
Wednesday, June 12, 2019 4:37 PM
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
Thanks Darron. This worked for me!
Tuesday, June 25, 2019 9:47 PM
Thank you! This fixed it for me.
Monday, July 8, 2019 10:50 PM
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
Dear MS, please pay Darron the money you normally give the forum moderators! He actually provided an answer that works instead of just copy/pasting a generic FAQ
Thursday, July 18, 2019 12:52 PM
Such a pleasure to see a brief and accurate explanation that actually works! My hat is off to you sir!
Wednesday, August 7, 2019 8:38 AM
It works for me too.
Sunday, August 25, 2019 4:58 PM
Hello,
I ran into this issue today and am ready to try your fix as it seems like what others agree works. I have such a dumb question and I'm sorry I'm not as tech savvy. Where is file you mention located (HKLM\software\microsoft\AppModel)? Is that in the Office installer or somewhere already on the C drive? I'm sure I can find it, just looking for a general path.
Monday, August 26, 2019 12:48 AM
That's a registry path. HKLM is HKey_Local_Machine
Friday, August 30, 2019 4:52 PM
something ever worked for me from this site is the above solution..
thanks a ton.
Friday, August 30, 2019 11:48 PM
Thanks. Was obvious, easy, and worked with that info. Big help.
Tuesday, September 17, 2019 1:48 AM
Great Darron! it is working for me too.
Martin Cortez
Tuesday, September 17, 2019 1:49 AM
Great Darron! it is working for me too.
Martin Cortez
Saturday, October 5, 2019 11:05 AM
Thank you so much. It's work :3
Tuesday, October 8, 2019 3:49 PM
Thank you! I hate MS...
Monday, December 2, 2019 10:56 AM
Thank you so much. Your solution worked like a boss
Friday, December 13, 2019 2:19 PM
This just worked for me after a whole day struggle. Thanks Darron!
Friday, January 10, 2020 9:09 PM
Can also confirm this worked for me as well.
Dell OptiPlex 7460 AIO
Bloatware Removed
Tuesday, January 21, 2020 1:40 PM
This worked for me.
Wednesday, February 26, 2020 10:05 PM
Hi,
It really help, recently I just follow the process & resolve this issue in Windows 10 (Version 1809) to install office 2013...
Regards
Anand Singh
Wednesday, March 18, 2020 12:09 PM
The ultimate fix is to rename or delete HKLM\software\microsoft\AppModel
This works every time. Deleting it hasn't had any negative effects so far.
Darron...
It works. Thank you, Darron
Tuesday, June 23, 2020 11:29 AM
Its worked for me as well ..... Thanks Darron