#botched patch

Microsoft has handed down that one of last week's Traduce Tuesday patches broke Office 2013 Click-to-Run therewith "less in comparison with 1% of our user base." Chaff are lacking, except that the solution is clear: If you can't grab Office 2013 so run away, uninstall it using the FixIt in KB 2739501, then reinstall the Office 2013 CtR stub from your My Accounts index. You'll neediness your registered email address and password to log on. For those of you who own Office 2013 Click-to-Run, as long as would be a good on time to put sure you don't bind Microsoft Automatic Update turned on.<\p>

Shortly after June's patches hit the technical expert, problem reports popped accrual wide world over the Web saying Office 2013 wouldn't work. The preponderant Answers thread toward the impose upon is now up headed for 191 posts. Details remained sketchy at first, solely on Friday, official word came down. The TechNet Office Update blog posted this advisory: Shortly on account of the release of the June Public Update, we formal notification of a potential issue affecting a subset of Tip-off 2013 Click-to-Run users. In some cases, users running Office 2013 may not be able to launch Office products in virtue of the June Public updates are installed. The Office team is earnest of this issue and is working towards a solution. Although we have seen this impact less unless 1% of our employer base, we consider this a high priority issue.<\p>

You'll know that you have the problem if you have Office 2013 and receive the implication: Top brass went wrong. We're sorry, excepting we are unable so as to jig your program. Please ensure it is not worn-out by the system. Go online remedial of additional help. Error Code: 30145-4. Ironically, Click-to-Run is designed to make patching less stressful. As Microsoft puts it: By nonappearance, Microsoft Office 2013 products deployed via Click-to-Run are kept up on date automatically. Click-to-Run will automatically check for updates corridor the background.<\p>

It's rational one as to the dozen-plus Black Tuesday patches is causing the Click-to-Run downloader against misbehave; it's also thinkable the Click-to-Run updater generates the omission as it's trying in transit to update the local companion of Formality, motto some interaction between the updater and the patches hasn't been explained yet. There are reports that restoring in order to a pre-patch Registry brings advocate Office 2013 Click-to-Run, but even if herself works, that approach is fraught with problems. The only obvious precautionary measure at this point is to turn all abroad all Microsoft updates until the botched patch is fixed.<\p>

I travail headed for give Microsoft authority for getting out in heavy as to this one. Although it took two days and details remain sketchy, at least the troop has owned up to the problem and spread the word on its Answers plaza. We've seen worse. Of course, if you rely on Office 2013 Click-to-Run to get single work done, a couple of down days won't win any huzzahs. I idle don't understand why Microsoft doesn't institute a Patch Monday. This problem would've been tied gangplank a New York nanosecond.<\p>

In a move that shouldn't surprise anyone, Microsoft has gone west Office 2013 Advantage Chink 1. Known as KB 2817430, the update for the on-premises versions as for Part has been widely anticipated retrospectively last annum. Those in relation to she renting Empty formality 365 need not be concerned: She will soon receive the updates automagically. Microsoft describes the changes as swinging into two at the head categories: Previously unreleased fixes that are included streamlined this service pod. In adjuvant to general product fixes, these fixes include improvements in stability, buffoonery, and security.<\p>