FAQ: MB Pro Security Workaround For Windows Vista/7/8/8.1 |
|
|
|
Important
Note: The information below only applies to
MicroBase Pro v2.0 which has now been superseded by a newer version. DSS strongly
recommends that
all users update to the latest version of MicroBase Pro via the auto-update process.
You can learn how to update to a newer version of MicroBase
Pro here. |
|
What Versions Of Windows Need The Security Workaround? When MicroBase Professional v2.0 is installed under Windows Vista, Windows 7 or Windows 8/8.1, user permissions may not be set correctly and MicroBase Professional may not be able to save certain data types. When this is the case, users are not able to save modified copies of group files or message attachments. Users may be able to download application notes but then cannot open them for viewing. Important Note: You only need to perform the Security Workaround if you are running MicroBase Pro v2.0 under Windows Vista/7/8/8.1. If you are running a version of Windows which is earlier than Windows Vista, or if you have updated to MicroBase Pro v2.1 or later, this page DOES NOT apply to your installation.
Warning: You must be extremely careful to
perform all of the steps in the exact order shown below. |
|
For MicroBase Pro v2.0 Installations Under Windows
Vista And
Windows 7
Follow the following steps to perform the Security Workaround in Windows Vista or Windows 7:
|
|
For MicroBase Pro v2.0 Installations Under Windows 8
Follow the following steps to perform the Security Workaround in Windows 8:
|
|
For MicroBase Pro v2.0 Installations Under
Windows 8.1
Follow the following steps to perform the Security Workaround in Windows 8.1:
|
|
What If I Have Run MicroBase Pro v2.0 Before Performing The Security Workaround? If you have already run MicroBase Pro v2.0
before performing the security workaround, you may need to delete your downloaded
Group Files and Application Notes, and then download them again in order to make
them viewable. |
|
Did you find this article useful? Please tell us. |
|
Back to FAQs page. |