I can’t contend we wasn’t warned. we was partial approach by installing Microsoft Office 2016 on my primary workstation when we got a summary that said, “Stop, we should wait to implement Office 2016.”
The blunder summary went on to contend that if we motionless to continue anyway, my duplicate of Microsoft Visio Standard 2013 would be removed. Since we had a strange hoop from when we purchased a software, we went ahead.
Bad move. It turns out that when Microsoft says that Visio 2013 won’t work with Office 2016, they meant it won’t even have a possibility to work. Any try to reinstall a program will be thwarted. The fact that we paid for a program is beside a point. You’re fundamentally out of luck.
When we went to a Microsoft village forums, that is where Microsoft handles most of their tech support, we detected that we wasn’t alone. Apparently hundreds of people who’d purchased stand-alone Microsoft Office products were affected, and they weren’t happy about it.
Furthermore a problem extended distant over Visio. Users with Microsoft Project, Publisher, Access, InfoPath and SharePoint Designer were also affected. Likewise, for Microsoft business who purchased Office Apps that are routinely partial of Office suites, yet might have been purchased separately, such as Outlook 2013 were also affected.
In a warning, a Office 2016 implement blunder summary states that Microsoft is operative on a solution. However, even yet Office 2016 has been out for some months, it appears that a resolution still eludes a company.
As a outcome business have peppered Microsoft support forums with sour invective. “This is a DUMBEST, STUPIDEST pierce to make,” wrote one user, suggesting that Office 2016 product managers should be sacked. As a result, Microsoft has relented—sort of.
Fortunately, there is salvation, yet a highway to a repair isn’t obvious. Apparently sleepy of hundreds of messages accusing a Microsoft Office group of all from bootleg acts to larceny, Microsoft responded with a solution.
But we usually detected this after spending some impotent hours on a applicable forum in a Microsoft community. It finally occurred to me that we have a Microsoft support comment that we compensate for each year and if there was ever a time that we indispensable to use it, this was a time.
So we called Microsoft’s support folks, referred to my support account, and asked them to assistance me solve a problem. we ran into a wall. The support deputy had no thought what we was articulate about.
Next we escalated to a subsequent support level, and then, finally, got in hold with someone on a Office support group who was informed with a problem.
After a common scripted tech support conversation, a support deputy pronounced that he’d send me a couple to download Visio 2016, that he did. we successfully downloaded a program and ran a designation routine. we had entrance to Visio again.
It turns out that for a initial few months that this was happening, Microsoft support reps had been sensitively contacting people with this problem who had complained in a village forum and charity a same ascent deal.
Then, finally, Microsoft announced a new ascent policy. The new “Special offer”, now settled in writing, is what support member had been doing sensitively all along, providing a means to ascent those who bought and paid for stand-alone applications that irretrievably disappeared.
The apparent doubt afterwards becomes, because did Microsoft do this? It would seem to be an doubtful choice that concerned alienating thousands, maybe millions, of users who had been constant users of Microsoft’s applications. The answer is that Office 2016 uses Microsoft’s Click-to-Run installation. But it’s some-more difficult than that.
The Click-to-Run deployment choice has been around for a while and progressing versions of Office, including 2010 and 2013 both are able of regulating Click-to-Run. But for whatever reason, even yet Click-to-Run works with those progressing versions of Office a versions aren’t compatible. Why this should need rejecting of progressing versions of Office applications stays a mystery, that so distant Microsoft hasn’t privileged up.
What Microsoft has common is a matter from a orator revelation us what we already knew. “Because Office 2016 and Office 2013 standalone applications can't be commissioned on a same device, Microsoft has combined an offer permitting consumers to ascent standalone apps to their Office 2016 version. The offer gives users a ability to take full advantage of updates, and is current by Jun 30, 2016.”
I’m still seeking an answer from Microsoft about how this was authorised to occur in a initial place. I’ve been in hit with Microsoft’s orator and maybe I’ll get an answer.
But if we had to guess, we consider that what indeed happened is that somebody on a program engineering group didn’t consider by or exam a intensity consequences of regulating an updated Click-to-Run slight to implement Office 2016 but also upgrading a stand-alone applications during a same time. But given nobody has told Microsoft’s business in allege that this would happen, a outcome isn’t surprising.
What needs to be finished now is for business to defer any ascent to Office 2016 for a time being until Microsoft henceforth fixes a designation slight to forestall a involuntary deletion of stand-alone bureau apps that is withdrawal profitable business stamping their feet in rage.
Office 2013 works only excellent and to my eyes a new chronicle doesn’t seem to offer a constrained set of new features. For now, when we get that sign that your chronicle of Office isn’t adult to date, only contend no.
This entrance upheld by a Full-Text RSS use – if this is your calm and you’re reading it on someone else’s site, greatfully review a FAQ during fivefilters.org/content-only/faq.php#publishers.