Uninstall Office 2010

I have a windows virtual machine, I think Windows 7 (via vmware fusion 4.1.4) on my MBA that is running a Yosemite beta. Fusion 4.1.4 does not run on Yosemite, and probably never will. Fusion 7 is not worth it for me, but I thought I'd try to keep this old virtual machine alive by moving it over to a Mavericks iMac. I have installed Office 2010 on the virtual machine. I can see those Office apps in my Application folder on the MBA, so I suppose they will not move over to the iMac. How do I get rid of them on the MBA? Just trash them? I cannot run the virtual machine on the MBA, so I cannot uninstall them via the control panel. Suggestions? Thanks in advance.

Ask on the Fusion forums since that's the software that's creating the icons.
https://communities.vmware.com/welcome

Similar Messages

  • Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

    We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
    office 2013 click to run with appv5.
    When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence.  I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
    The application uninstall for Office 2010 is:
    The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
    also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml.  The silentuninstallconfig.xml was created from the original config.xml file and edited
    to these settings:<Configuration Product="ProPlus">
     <Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
     <Setting Id="Reboot" Value="Never" />
     <Setting Id="SETUP_REBOOT" Value="NEVER" />
     <OptionState Id="ProductFiles" State="Local" Children="force" />
     </Configuration>
    The detection method is the folder path to see that office 14 exists.  When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
    running the command line manually mapped to this location on a machine uninstalls office 2010 without issue. 
    Lync 2010 uninstall:
    Lync is an exe so I am using the LyncSetup.exe /silent /uninstall.  The application is in the supersedence tab for Office 365 2013. This never installs.  If I create a softare distribution and deploy it on its own it uninstalls without issue. 
    We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this.  The detection method for lync is file system folder and the Microsoft lync folder for detection.
    MS Office 15 (Office 365) was created with the click to run tool.  I can install this with the application I created using the appv5 package created with the click to run tool.  The issue is we need Office 2010 and Lync 2010 uninstalled first. 
    Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013. 
    I have looked at many articles and so far it is not working for us.  Any help appreciated to get us to the cloud.
    Thanks,
    Brit

    The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do.  The detection method seems to be hanging things up.  On the lync uninstall detection method I have
    the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
    I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
    These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
    to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
    product code for every version release of their product. In which case, Use the registry method.
    As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
    have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
    For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
    all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
    Dustin Estes - MCP | www.dustinestes.com

  • Problem uninstalling Office 2010

    My company is currently using Office 2010 ProPlus via O365 subscription.  We are preparing to update to Office 2013 and I am trying to create a script that will uninstall Office & Lync 2010 and install Office 2013.
    I'm having trouble finding a way to uninstall Office 2010 from a script.
    I've tried to follow the instructions I found here, but when I run the command:
    setup.exe /uninstall ProPlus /config uninstallconfig.xml
    I get an error:
    The product installation has been corrupted.  Run setup again from the CD, DVD, or other original installation source.
    The install source I'm using is a shared folder on our network, which is the same location Office 2010 was installed from.
    I've tried using both /uninstall ProPlus and /uninstall ProPlusSub as I'm not sure which one is correct.  I get the same error both ways.
    Any suggestions?

    Just like the error says that your installation has been corrupted. I would suggest you to use Microsoft Fix It tool to remove Office 2010:
    http://support.microsoft.com/kb/971179
    Or you might repair Office 2010 first, then try to use /uninstall command again.
    For the command, please check whether you have typed the correct ProductID. For more details about
    /uninstall, please refer to:
    http://technet.microsoft.com/en-us/library/cc178956(v=office.14).aspx#BKMK_uninstall
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • How to uninstall Office 2010 32 bit and install Office 2013 64 bit

    Hi Everyone,
    I am rather new to SCCM.  I have setup a SCCM 2012 SP1 system.  I am now trying to setup an Application where it will install Office 2013 64 bit.  Everything seemed to go smoothly until I tried testing it.  I received an error that I
    cannot install the 64 bit version of Office 2013 because Office 2010 32 bit is already installed.
    I tried to modify the MSP where it will uninstall Office 2010 before installing Office 2013 but apparently as soon as it starts it checks for the 32 bit installation and exits when it finds it.
    Could someone give me a detailed solution (since I am new to SCCM)?
    Ken

    While referring to older versions of office I think this link may apply: http://social.technet.microsoft.com/Forums/en-US/f255e17d-4e1f-4231-8a88-d63f41c83c52/how-to-automatcally-uninstall-office-2007-32-bit-for-installation-of-office-2010-64-bit?forum=officesetupdeployprevious
    Also you might create an office 2010 package, with an uninstall program that removes it.
    Then in your office 2013 package make the uninstall for 2010 to be run first. 

  • Deploy Office 2013 - Uninstall Office 2010

    Hello,
    I am planing to deploy Office 2013 and created a MSP File (Setup /admin) for the silent Installation - everything works fine - except the uninstallation of Office 2010. In the OCT I´ve selected the Option to remove previous Versions of Office. I can
    remeber that this works perfect in Office 2010 to remove Office 2007 too.
    But in Office 2013 this doesn´t work anymore, the installed applications wizard (appwiz.cpl) Shows both Version of Office are installed. What is the best way to remove the old Version silently and install Office 2013? I would like to have all in one
    "Application" deployed via SCCM 2012 SP1. 

    Have you looked at this document, or it's online equivalents:
    http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
    In the section "Setup command-line options for Office 2013", they say:
    /uninstall [ProductID]
    Runs Setup to remove the specified product from the user’s
    computer. Look up the value of [ProductID] in the Setup.xml
    file for the product that you want to modify.
    Example
    \\server\share\Office15\setup.exe /uninstall ProPlus
    where:
    Office15 is the root of the network installation point.
    ProPlus is the
    [ProductID] ([ProductID]
    is equal to the ID attribute of the
    Setup element listed in
    \\server\share\Office15\ProPlus.WW\setup.xml), where
    ProPlus.WW is the location of the Office Professional Plus 2013 installation files.
    You can customize the
    /uninstall option by using it with
    /config and a modified Config.xml file. This is necessary if you want to run a
    “silent”
    uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for user interactions, even when files are being used.
    To run a silent uninstall
    Using a text editor, edit the following element attributes in the
    \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml file:
    <Configuration Product="ProPlus">
    <Display Level="none"
    CompletionNotice="no" SuppressModal="yes"
    AcceptEula="yes" /> </Configuration>
    At the command line, use the following syntax:
    \\server\share\Office15\setup.exe /uninstall ProPlus /config \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml
    Note:
    In Office 2013, just as in Office 2010 and Office 2007, you cannot use the Setup.exe command line to set Windows Installer properties, such as
    PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked
    and unsupported properties, see Setup properties in Office 2010.
    The information also applies to Office 2013.
    Office Customization Tool (OCT) in Office 2013
    Config.xml file in Office 2013

  • Deploying Custom Office 2013, Uninstalling Office 2010

    We've just recently moved to SCCM for application and OS deployment, so we're setting up applications to be deployed through SCCM for the very first time. I've read a few guides to deploying Office 2013, and the majority of them follow the same procedure:
    Customize Office 2013 with OCT
    Create an application in SCCM by selecting proplusww.msi
    Edit the deployment type and replace proplusww.msi with setup.exe
    Some guides reference the .msp in the setup.exe command, some don't. e.g. "setup.exe /adminfile custom.msp"
    So, a few questions:
    Why should I use setup.exe vs proplusww.msi? I understood that the application model gives us more control, better autodetection, and less manual configuration. i.e. use MSI for applications
    If I should use setup.exe, do I really need to reference .msp? e.g. setup.exe /adminfile custom.msp I thought that when you customize the installer, and place the msp in the \updates folder, running the setup.exe still utilizes the msp file. 
    Some guides say I should also used an xml file for help with uninstalling Office 2013. e.g. An xml file with Display Level, SuppressModal, and AcceptEula set, then using the command "setup.exe /uninstall proplusr /config .\proplusr.ww\unisntall.xml".
    What instances would I need the xml, and which instances would I not?
    Finally, I would possibly like to install Office 2013 during OSD. Would that change any recommendations on how I create the Office 2013 SCCM application?
    I'd appreciate any help/advice anyone can give. I was not able to find any info directly from Microsoft on how best to deploy Office with SCCM. Nor was I able to find any info on using proplusww.msi vs setup.exe for deployment. Thanks.

    If you place the .MSP file in the Updates folder, the Setup.exe program will automatically process it without the need to specify in the command line.  The .XML and OCT .MSP are two different means of customizing the installation.  I typically
    use the OCT to create the .MSP and drop it in the Updates folder, then just call setup.exe with no switches to perform the silent install.
    Make sure you set the SETUP_REBOOT property to Never in the OCT, otherwise the install may perform an unexpected reboot that could potentially cause issues with ConfigMgr (especially if it's during imaging).
    Thanks for the info. What about proplusww.msi vs using setup.exe? I still haven't been able to find any documentation on using one vs the other when deploying through SCCM (as to why you should use one over the other). Almost every SCCM application deployment
    guide I come across always wants you to use the MSI, sometimes going to great lengths to find one, just to avoid using an exe. So, why does almost every SCCM Office deployment guide tell me to use setup.exe? Also, is it just me, or is there really not official
    best practice form Microsoft when deploying Office through SCCM?

  • Uninstall Office 2010/2013 to deploy Office 365 ProPlus

    following clarification is needed:-
    some of the pc is installed with Office 64 Bit edition, we are trying to remove the existing office (desktop) before deploying office 365 ProPlus. SCCM 2012 R2 is going to be used to uninstall office. my question is that can I remove/uninstall 64 bit Office
    using 32 Bit setup.exe or it has to be 64 bit for 64 bit office and 32 bit setup.exe for 32 bit office.
    also if I am looking for assistance to create query that can result in 64 bit and 32 bit office using SCCM. please paste the query in the response if possible.
    Thanks
    Farrukh
    Farrukh Anwar

    I would recommend that deploy a script that first removes the old version of Office and then Deploy the new version.
    My favorite script tool to use with SCCM is the PowerShell App Deployment Toolkit, and that would be great in this example too.
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

  • Uninstall Microsoft Office 2010 using intune

    Has anyone successfully uninstalled Office 2010 using Intune to push the command?
    I just upgraded all users to 2013 but would like to remove the old office.
    Thanks
    Ivan Nix

    I know this is very old but I’m trying to clean up old posts. Did you ever solve this? If so it would be good if you could post the solution to assist others. If not, at this
    stage, as nobody has answered, I would recommend that you call Intune support if the issue still exists.
    You will find your local Intune support number here
    http://technet.microsoft.com/en-US/jj839713.aspx
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Problem with report generation toolkit when installed new office 2010

    Dear all, I had  LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
    Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
    How can I inform Labview to link report generation toolkit to the old  MSoffice 2003?
    regards
    Max

    The Report Generation Toolkit is ActiveX based.  When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
    Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
    Regards,
    Peter D

  • Can not open Excel 2003 embedded worksheet in Office 2010

    I have seen many similar issues to this but I think I have some unique factors that are making my issue a bit tougher to resolve. I have a user who has a word doc which he opens in Word 2010. This doc has several embedded excel sheets. When he tries to click
    one of these embedded excel sheets to edit he gets an error:  "the program used to create this object is excel the program is not installed on your computer". It will give an option to repair which we have tried but it makes no difference.
    Some things to note that I think makes this case more unique than others I have googled.
    This seems to be the case only with embedded excel 2003 spreedsheets. He can open newer excel 2010 spreedsheets that more more recently added to the file.
    He previously had Office 2013 which we had to uninstall, and put Office 2010 on. This was done because of a piece of software this company uses that was not compatible with office 2013. (Personally I think this may be where the problem is as there seem to
    be remnants of Office 15 in the registry.)
    I have tried the standard fixes of Disabling the Com add-ins, running office repair, and trying to Convert the embedded spreedsheet to an Excel Binary. The convert failed and gave me a generic error about possibly not being allowed to save to the location
    or needing more memory or space but none of these are the case.
    I have not yet tried to uninstall office 2010 and reinstall and I am hoping that I won't have to. This issue just seems odd to me. Other users can edit these embedded spreedsheets fine which is why I think it has something to do with the fact that he downgraded
    from 2013 to 2010.
    Anyone of thoughts, ideas, suggestions? Thanks.

    Hi,
    I noticed that use newer excel 2010
    spreadsheets that more more recently added to the file. Did you try to embed the Excel 2010 file to Word 2010 test? If it works fine, I suppose that it was a compatibility issue.
    Because Excel 2010 had change the file format with Excel 2003.
    I recommend you try to install Office 2010 sp2 and compatibility pack.
    http://blogs.technet.com/b/office_resource_kit/archive/2013/07/31/download-the-new-microsoft-visio-compatibility-pack.aspx
    https://support.microsoft.com/kb/923505/en-us
    And there is a similar issue, we also could install the hotfix to test.
    http://social.technet.microsoft.com/Forums/office/en-US/b0dc1e24-847d-44e9-95c5-f789a0d50047/cannot-edit-embedded-excels-after-closing-document?forum=officesetupdeployprevious
    Regards,
    George Zhao
    TechNet Community Support

  • Going from Office 2010 to 2013 and Back to 2010 I lost My Outlook Search

    Hello--
    We are doing some beta testing and I had to install Office 2013 from 2010. I finished the testing and went back to 2010.
    Now, when I do a Windows search, my Outlook email is not included in the search results. This is a major loss to my productivity. I believe I read that Outlook email is not included in the Windows search with 2013, so that's probably why I lost it.
    Can you tell me how I can include Outlook email in my Windows searches again? I searched for solutions online and all I got were questions.
    Thanks!
    Stephen
    Stephen Davis

    Hi,
    Sorry for not having resolved this issue so far. We can try to uninstall Office 2010 first, then delete the following registry keys from the location:
    Win + R, type "regedit"(without quotes) then press Enter.
    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps
    carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,
    http://windows.microsoft.com/en-US/windows7/Back-up-the-registry
    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook
    HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15.0\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Outlook
    Once the keys are deleted restart the computer, then re-install Office 2010 to check the result.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here
    That fixed it. After I did the steps you indicated, I went back to the Indexing options and made sure the Office14 folder was included.
    Thansk
    Stephen Davis

  • Upgrading from Office 2010 to 365

    Upgrading from Office 2010 Pro to 365 Pro Plus - I know you must uninstall 2010 and install 365 or can run them concurrently. Question is - if you uninstall 2010 and install 365, what settings are lost and what settings are retained? Outlook signatures?  Word
    and Excel settings and preferences? 
    Also must the OST files be re-downloaded again?  I hear there's a 40% compression improvement so this might be ideal, just want to know if the GPO to not re-download the OSTs actually works in this scenario?

    Hi,
    Uninstall Office 2010 will not remove any user settings, the user settings will migrate upon the first use of each Office 2013 application.
    By default, when Outlook 2013 is installed, a new compressed version of the Outlook data file (.ost) is created. This new compressed version of the .ost is up to 40% smaller than the size of the .ost files that were created in earlier versions of Outlook.
    So it is recommended to use the new .ost file.
    The "Do not create new OST file on upgrade" policy also works for Outlook 2013, however you might need to download the new Outlook Group Policy template (Outlk15.admx). Outlook 2010 template should not work in this scenario.
    Regards,
    A.B.

  • Cannot uninstall Office 2013 Preview

    Firstly the standard route via Control Panel would not work – it just sat there for ages preparing to uninstall, but doing absolutely nothing as verified in Task Manager. So
    I looked at the recommended manual uninstall procedure (support.microsoft.com/kb/2739501)
    and the first step there is to navigate to %windir%\Installer and then find all programs in the ‘Microsoft Office <product name> 2013’ family, right-click and select ‘Uninstall’.
    Again (choosing MS Access as the first product to manually uninstall), the manual uninstall also sits there doing nothing just like the Control Panel uninstall did earlier. Any help with this would be much appreciated - I really don't want to be stuck
    on MSO 2013 Preview..

    It appears to be totally impossible to uninstall this software!!
    The quote from TheHoaryHound above seems spot on!!!
    The installation of the paid Office 365 Home Premium version on my first PC, an almost Dell new 64 bit Windows 8 desktop system, worked fine.  Yes, this install saw my preview version of Office 2013 already there but it successfully removed it during
    a 3 1/2 hour process.  
    Office 2010 is still installed on the 1st PC too and both versions are working (although the paid version Office 365 has some obvious bugs).  But the 2nd PC has been real grief.  That's an HP laptop
    running Windows 7 Pro.  I just can't seem to rid myself of the Office 2013 Preview no happen what I do.  Here is what I've tried so far:
    1.  Ran MS Fix It twice and rebooted each time afterwords.
    2. Ran the Office 365 paid install so many times I've lost count.  I thing the number is 5 because the first time it just died after 6+ hours.  (5 failed installs = 1 failed install + 2 Office 365 installs after running the preview uninstall
    "Fix It" + 2 Office 365 installs after uninstalls via the control panel.)  
    Granted the failure was probably due in part to high demand combined with scheduled maintenance done by my ISP who'd sent me a "mea culpa" email saying I should expect problems.  
    Each time rebooting of course.  Microsoft THINKS it's installed because they've decremented the install counters to 3 installs remaining.  However, when I click on a Office 365 app (any, all apps)
    the preview is back yet again.  (Sorry about the small type that's either a IE10 thing or a website thing.  I didn't change fonts.
    3. Ran manual uninstall of the Preview, also twice (and rebooted two more times.)  I think that totals 5 Office 365 failed install attempts.  (What is that quote about trying the same thing twice
    and expecting different results?)
     4.  I also have Office 2010 installed on the the laptop PC I'm having trouble with and I really need to keep it there as there's some legacy MS Access stuff I have to support.
    Does anybody have a good solution other than Fix It or the control panel that does not include uninstalling Office 2010?
    I'm completely baffled... re-installing Windows is not an option.

  • Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

    When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
    I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.)  I also tried using the OTC, custom XML
    file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
    Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
    instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
    Thanks

    Hi,
    Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
    You try to modify registry then you wont face issue.
     The issue when you hit a "1653" is that Windows
    Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
    error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
     these are the issues I've seen:
    Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "logging"= "voicewarmup"
    kirtesh

  • By default Office 365 Proplus save as Office 2010

    Hi,
    Operating System: Windows 7 (SP1); Office 2010 Professional SP1 and also Office 365 proplus...
    By default I have installed office 2010 and later I installed office 365 proplus online.
    My issue is when I am saving office365 proplus (Word,excel) file then by default it saving as office 2010.
    When I opening it by open with but there office proplus (word / excel) option is not available.
    All desktop files showing in office 2010 format.
    I office 365 proplus repair but issue is same.
    (FYI: when I uninstall office 2010 then by default office 365 proplus both saving and displaying) 
    Please anyone help me about to above issue to resolve before uninstalling office 2010..........

    Hi,
    I have tested this in my testing environment that by default Office 365 Pro Plus will take over your existing Office 2010 files if you install Office 365 Pro Plus later. And the new Office icon will show on all of your existing files.
    Usually, do a Online Repair of the Microsoft Office 365 Pro Plus will fix the broken of file type associations. Not sure how you repaired your Office 365 Pro Plus, please try again follow the steps below:
    1.Click Start, click Control Panel, and then click
    Programs and Features.
    2.Click your Microsoft Office program, and then click Change.
    3.Select Online Repair, and then click Repair.
    If the Online Repair doesn't fix the issue, I would suggest you to try using Microsoft Fix It tool to remoe Office 365 completely, then reinstall it:
    http://support.microsoft.com/kb/2739501
    Hope this helps, and feel free to post back with any feedback.
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

Maybe you are looking for