Update error code 30088-27 Office 2021 what to do to get corrected????

This is a user-to-user forum as stated in the FAQ. Microsoft decision makers never contribute here.

You can confirm my status as a Microsoft MVP through the mvp.microsoft.com site.

This is a user-to-user forum as stated in the FAQ. Microsoft decision makers never contribute here.

You can confirm my status as a Microsoft MVP through the mvp.microsoft.com site.

No wonder Microsoft keeps making blunders like the issue behind this thread. If Microsoft decision makers insist of keeping their heads in the sand we users will never get products in which we can trust.

In the past I have documented bugs and failures within Outlook up to and including Outlook 2021. My case was escalated to senior Level 3 engineers who confirmed and verified the bugs I reported. When I asked when the problems would be fixed I was told that the support team are not allowed to contact the development engineers. They were expected to find and fix the issues themselves. When dealing with a proven bug in the software all they could do, and did in my case, is close the case as unfixed (unfixable). There is no point of escalation, there is no decision maker intervention or review. The case was just closed as if the bugs don't exist!

In spite of the information provided here, I tried to follow the Microsoft instructions for resolving this issue. All I got was a corrupted Office 2016 installation (after running the online repair) with my registration/activation codes being deleted. (There was no warning that this was possible.) I contacted Microsoft Support to get my system restored and I was told I should have known that a repair can deregister a product! Unfortunately, I was not prepared for this possibility and did not have my activation codes handy. This risk was most certainly not mentioned in any of the Microsoft documents relating to this error. Neither the support consultant nor her manager were concerned about the licence revocation problem. They offered no assistance to retrieve my license or provide a solution. After a very mad scramble for many hours I finally found my activation codes and have since restored my access to my software.

Returning to this issue, The Microsoft agent's response to my problems was to uninstall Office and start again. I needed to show them this thread before they would even accept that this was not an isolated issue on my machine. When I pointed out that my perpetual licence had been deleted and a fresh installation would require a new license they told me to buy a new copy of the product! Their care factor was less than zero, or zero at best. This was the end of the Microsoft support offering.

To add insult to the whole situation, I bet most of you know what is coming..., after all the repairs and re-registration of Office 2016 the original update error remained.

Microsoft decision makers never contribute here.

My point exactly; they NEED to in this case.

Ian, the problems with Microsoft are nothing new. I was forced to Microsoft kicking and screaming when it modified its software for no reason other than to prevent it from working on OS/2.

I did have the early Windows programs and they suffered from the same issues. When Windows 1.3 came out, it wouldn't work with my Epson printer. I contacted support and they told me that I needed to get a generic printer (how much more generic can you get than Epson?). I had several other ink-jet printers at the office, but none of them would work properly. They then told me that all of my printers were defective and had to be replaced to work with Windows. I told them that it was easier and cheaper to replace Windows.

Six months later, I received a general mailing from MS talking about the new printer drivers that corrected problems with the Epson devices. By then, my Windows floppy disks were being used as drink coasters and I was running Desqview full time, moving on to OS/2.

Still the same mindset.

I can confirm that, on two different computers (Dell XPS laptop, plus custom-built desktop), this did NOT work.

As for everyone's complaints against Microsoft, I can say you are 100% correct. An ex-g/f of mine (from many years ago) was the Project Manager for MS Office 2000...and, two of the reasons she chose to leave the company were due to lack of support, and lack of communication. She told me that there was extreme difficulties in fixing problems because they received very little, if any, information provided by those having problems. Put another way, we can report all the problems we want, and even provide proof of said problems...but, very little of that information ever reaches the programmers. It's not-so-much that they (meaning, the programmers) "don't care" about fixing the problems. It's more that the 'chain', from the lowest-level customer support personnel, up to the actual programmers responsible for correcting the code, has MULTIPLE "broken links", all of which were 'created' by Microsoft management (or, should I say, mismanagement). She got fed up with the problems that management was the core cause of, left the company, and returned to the SF Bay Area.

The moral of this (as I'm sure 99.999% of you will understand) is, when it comes to Microsoft, we can, literally, "expect" products to be 'broken' (probably several times) throughout the life of said product. And, don't hold your breath expecting MS to 'fix' whatever they 'break'. In the end, their ultimate "solution" will be to release a new version, and figure out a way to 'force' as many users to 'upgrade' to the new version. Ever since Bill Gates stepped down as CEO, this appears to be the 'philosophy' that the company operates under.