Unable to run Simulink due to .dll error after installing 2016b

I have 2019b on my machine and all works fine. I have now installed 2016b on same machine. When I try to run Simulink in 2016b. matlab will open and Simulink will attempt to intialize but fails with an error dialog indicating "Can't load 'C:\Program Files\MATLAB\R2016b\bin\win64\libmwsimulink.dll': The specified procedure could not be found."
I can find this .dll in the specified folder, and it has a size of ~36MB. What can be cauing this error?

[Suraj Kumar]

Hi John,

Are you using Dell backup and recovery (or are you using a Dell system)?

[John Reynolds]

Hi Suraj,

Yes, I am using a Dell laptop.

John

Answer 1

[Suraj Kumar]

Hi John,

I understand the issue that you are facing while running Simulink. This might be due to the interaction between MATLAB and Dell Backup and Recovery (possibly version 1.8), which leads to this error.

To resolve this issue, you can try the following workaround:

You can update the Dell Backup and Recovery to version 1.9 or later. Alternatively, you can either uninstall Dell Backup and Recovery or disable its shell extensions.

To disable the Dell Backup and Recovery shell extensions, use a utility such as http://www.nirsoft.net/utils/shexview.html to selectively enable or disable these shell extensions:

• C:\Program Files (x86)\Dell Backup and Recovery\Components\Shell\DBROverlayIconBackuped.dll
• C:\Program Files (x86)\Dell Backup and Recovery\Components\Shell\DBROverlayIconNotBackuped.dll
• C:\Program Files (x86)\Dell Backup and Recovery\Components\Shell\DBRShellExtension.dll

For more information regarding the issue, you can refer the following bug report from MathWorks:

https://www.mathworks.com/support/bugreports/1295315

Hope this works for you!

[John Reynolds]

Thank you for taking the time to answer, Suraj. I checked my Program Files (x86) directory and these folders and .dlls are not there. Ultimately, I contacted Mathworks Tech Support, who advised me to do a complete Uninstall and freh reinstall. I did that, and now it is working as expected.