Office 2016 uninstalls my Visio 2013

Anonymous
2015-09-23T05:20:30+00:00

So, even though I had followed the instructions to install Office 2016 from Office 365 home, it was not successful even after 5 tries, restarting, uninstalling, restarting...my biggest issue is Visio 2013. I purchased it as I need it! But why can't I find any way to just upgrade Visio from 2013 to 2016? There is no instruction! I do not want to buy the new Visio 2016 when I only purchased Visio 2013 a few months ago. Please help!!!

Microsoft 365 and Office | Access | 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
2015-09-24T23:09:57+00:00

Hi All,

We are reaching out to individuals on the thread through Private Messages with guidance on their issue.

For others facing the same problem please get back to us.

Thank you.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

300 additional answers

Sort by: Newest
  1. Anonymous
    2015-09-24T23:54:24+00:00

    And what was incorrect?

    1. The question related to Office 365, which will automatically upgrade subscribers to Office 2016.
    2. The Office 2016/Office 365 installation program uninstalls Visio 2013. There is no warning concerning this BEFORE the installation commences.
    3. Purchasers of Office 365 and Visio 2013 and Project 2013 are left with useless software, unless they wish to lug TWO computers around with them in order to be able to use both Office 365/2016 and Visio/Project 2013.

    So your reply was both unhelpful and insulting. But perhaps this is the official Microsoft response.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-09-24T16:46:37+00:00

    "When you contact Support, let them know you are upgrading your Office 2013 subscription to 2016 and are getting a message that Visio or Project needs to be removed. The support agents are being reminded of this situation and how to resolve it."

    Um, Mike, the problem is not that Support needs to be reminded of the resolution. The problem is the lack of a resolution. I'm sitting on a worthless, personal copy of Visio Pro 2013 right now.

    -Dan

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-09-24T13:44:29+00:00

    Mike, I appreciate the (robotic) response but, honestly, I suspect you are trying (or have been programmed) to make it appear that MS cares, which it does not.  Here's reality:

    I have been given 5 different numbers to call so far.  I've made about 12 calls, each one taking ~20min.  5 times they hung up on me during a transfer. 3 times they said "I've not idea."  2 times they said to uninstall Office or run Visio on another computer.  And 2 time, they said "sorry, without a pro account we cannot help."  And 1 time they said I would have to pay for help.  I have launched 3 chats.  2 were abandoned by the tech!  Seriously.  They said, "one sec" and then an hour later of me pinging them, I was booted.  The other called me but couldn't hear anything.

    Now, this is not a new issue with 2013 Visio and Project.  People had the exact same problem with the 2016 Office preview since at least May.  No solution was ever found.  On top of that, when you upgrade to 2016, there is no warning that 2013 Visio or Project will be nuked.  The only "solution" is to get a free trial of 2016 Visio, which forces me to create a useless onmicrosoft account (which I don't want), or I can pay $300 for 2016 Visio Standard.

    I think a little honesty would be appreciated.  MS decided to intentionally obfuscate the impact of its install as a way of forcing people to a monthly renewing service for Visio and Project under the "onmicrosoft" business banner.  By doing this, they build their DB which they can monetize to other parties.  I suspect that is the new MS reality.  The "renting" of SW while sacrificing privacy.

    The ethical solution would be for MS to offer a free upgrade to 2013 Visio and Project.  2nd best option, offer a ~$50 upgrade fee (which I hate but would probably do).  Or, 3rd, offer a free 2016 Visio/Project subscription for a year to reflect pain and suffering ("onmicrosoft" will never die, so I'd have to accept that too).  I noticed that I used the words "ethical" and "MS" in the same sentence, which means some part of me has hope here, which is probably foolish.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-09-24T12:45:22+00:00

    Why hasn't MS implemented the obvious fix for this problem.  You mean with thousands of programmers, hundreds of Office program managers, thousands of marketing weenies etc no one has though of applying a fix you already have.

    You make the "Single Image" MSI for computer builders. In a single install process (for the builder) consumers could use any one of 3 consumer class product keys to activate only the appropriate programs.  Do the same sort of thing inside of CTR.

    Why can't you do the same thing with the "click to not run" environment.  Since the apps are downloaded from your servers into CTR, just let the user select which applications to install/activate all in the single CTR.  The easiest way may be to add a check box during activation "do you have any of these other applications: ...."  If it is check, display another screen with room for the user to enter the required product keys all at once.  The trigger the install of the appropriate bundle of programs

    Or the more manual approach. Create installs that BUNDLE Office along with Visio and / or Project and/or the other orphan applications in the various permutations. 

    Or even easier, create an Office SUPER PRO bundle that includes all of the pro apps plus Project and Viso.  Sorry, it will cost a little in revenues, but the users will be happier.  The whole point of creating the Office bundle cludge in the 1990s was to sell all of the programs to entice people to use them. 

    There is no excuse for forcing uses to install conflicting CTR environments, especially when they often don't work together!

    Was this answer helpful?

    0 comments No comments