If you’re like me, I cannot stand the extra page that is generated by Microsoft Word when you create an envelope to be printed. It wastes an perfectly fine piece of paper every time you want to print an envelope unless you hit print the first page only. Who does that? I don’t. I ended up using my Google-Fu and found this link above which shows you exactly how to get rid of the page. Make sure you save the file after you make the changes and delete the second page.
I’m not sure if this is placebo but I swear that the Office programs run faster and even the add-ins such as the Grammarly Add-In for Outlook runs a lot faster. I’m in the preliminary stages as I am still testing it out. But once I heard that Office 2019 was going to be installed by default as a 64-Bit application, I figured it was time to make the move.
I had a client who was experiencing Adobe InDesign 2019 crashing a few seconds after opening it. . It did not matter what file they were working with. I created a brand new file and within a few seconds of trying to draw with the Pen tool, InDesign would close out and crash. This was happening on a brand new iMac, with High Sierra and Adobe Creative Cloud.
I could not recreate the problem on my laptop which is a MacBook Pro with Mojave and I am using the same version of Creative Cloud/InDesign as my client.
I soon Googled and then searched Twitter and found that multiple people were having the same issue. I figured at that point it was probably an issue with the activation servers that the software uses to call home every once in a while.
Just the fact that the software is calling home so much and a mistake on one of Adobe’s server can cause such a large issue is very concerning. Especially when you’re paying these guys hundreds if not thousands of dollars per month to borrow their software. The last they could do is get it right.
According to this forum post from an Adobe staff member by the name of Steve, the issue was a server on Adobe’s end, which I guessed correctly: https://forums.adobe.com/thread/2581509.
Per the thread, things should be fixed. We’ll see.