Adobe Acrobat Reader crashes in Windows 10


We are sorry for the inconvenience caused by this issue to you. We are aggressively working on the issues and finding out the right fixes for the issue. In the meantime, we have identified some workarounds that can help you resolve the issues. Please do try out the workarounds suggested in this post.

There are a couple of issues that are causing application crash soon after the file opens. The issues that are you seeing might fall in one of the categories stated below.

Issue 1) Compatibility Mode for Windows 7

A crash is observed on running application with Windows 7 compatibility mode. To check if this is causing the application to crash on your machine and to fix this anomaly, please follow the steps given below:

  1. Right click on the application icon of Adobe Acrobat Reader
  2. You will see a Properties Dialog.
  3. Switch to Compatibility View tab as shown in the snapshot below and turn off “Run this program in compatibility mode for:”

This should solve the issue.

Issue 2) Missing registry value “tBuiltInPermList”

There is a registry value which if not found by application, crashes the application.

To validate if your issue falls under this category and to fix it, please follow the steps given below:

1. Press on the search windows icon and enter “regedit” as shown below:

Screen Shot 2017-01-13 at 2.45.27 PM.png

2. Click on the regedit command to open registry keys.

3. Navigate to the registry key shown below:

4. Check that you have the highlighted registry value “tBuiltInPermList” present in the registry hive.

5. If not, rename “cDefaultLaunchAttachmentPerms”

This should solve the issue.

P.S. There is a likelihood that you might not be able to use the workarounds suggested above in case if there are some restrictions policies in your enterprise. In such a scenario, kindly contact your network admins and check if it feasible for them to push the changes suggested here.

Save SSH Sessions in Terminal

Save SSH password for use in “Terminal” (OSX)


Make aliases in my


file, which gets exe­cuted every­time you start your Ter­mi­nal win­dow (so it’s a good place to put your short­cuts and any code you wish to exe­cute when the ter­mi­nal starts, such as paths).

    1. Start the Terminal.
    2. Open the pro­file file for the cur­rent user (you).
pico .profile
    1. Enter a new line for our shortcut.
alias s='ssh -2 -p 22'

Quick expla­na­tion for that com­mand in step 3. The let­ter “s” is the short­cut I make for con­nect­ing to the server. Change it to what you wish. This will mean that when I start Ter­mi­nal, all I need to do is type “s” and it con­nects me via SSH to the server. The “-p” switch is an impor­tant one because some of us with para­noid secu­rity set­tings might have a dif­fer­ent port num­ber than the default port 22 for secure SSH. The rest user/host stuff is self-explanatory. The “-2” is to force SSH2 con­nec­tions instead of older vanilla SSH.

Now. Save the pro­file file and source it to try it out:

source .profile

Sourc­ing is only for this one time, for your cur­rent Ter­mi­nal win­dow, which had already exe­cuted the pro­file file *before* we added this alias. When you start a new Ter­mi­nal ses­sion, these aliases et al will be auto­mat­i­cally set for you.

Done. Now your pro­file has the alias for “s”. From now when you type “s” in your Ter­mi­nal, it will con­nect, but it will ask you for a pass­word.