www.seclore.com Sitemap

Seclore FileSecure Desktop Client

 
 
 
Release Notes for Seclore Desktop Client.
------------------------------

Seclore 3.16.3.0
Seclore Desktop Client 3.12.3.0
Jan 1, 2021

     1. Introducing the new and improved Receiver-only mode for Seclore for Windows (adminless). (#10104)
	a. Seclore now offers an adminless agent with the Receiver-only mode turned on by default.
	b. The Receiver-only mode allows users to access Seclore-protected emails and attachments, share such emails and attachments with other users, and track and revoke access.
	c. This mode also allows users to view the permissions widget while accessing Seclore-protected files in native applications.
	d. It offers only recipient features and not protection features.
     2. Fixed the issue where users were unable to send inline image attachments with Seclore-protected emails in certain rare scenarios. (#9884) 
     3. Fixed the issue where Outlook would shut down unexpectedly in certain rare scenarios. (#9883)
	a. Before the fix: When composing an email in Outlook in RTF (without clicking on ‚??Seclore It‚??) with an unwrapped protected attachment and an inline image attachment, Outlook would shut down unexpectedly or the email would get sent with an error in the header in some cases.
	b. After the fix: This issue is now resolved.
     4. Fixed the issue where the web single sign-On (Web SSO) feature wouldn‚??t work in certain scenarios. (#9580)
	a. Before the fix: While accessing the Policy Server URL after 15 minutes of inactivity (that is, no activity with protected files/emails), the Web SSO feature wouldn‚??t work and users would be asked to log in again. 
	b. After the fix: Web SSO would work even after 15 minutes of inactivity. 
     5. Fixed the issue where URLs wouldn‚??t open from a custom application (Spectrum) when Seclore for Windows is installed. (#10180)
     6. Other fixes. (#8027, #8836, #8756)

------------------------------

Seclore 3.16.1.0
Seclore Desktop Client 3.12.2.0
Dec 1, 2020

      1. Seclore‚??s Right Click > Classify‚?Įfeature‚?Įis now configurable.‚?Į(#10052)‚?Į 
	a. Earlier,‚?Į‚??Right Click > Classify‚??‚?Įwas available as a default‚?Įfeature for all enterprises.‚?Į 
	b. Now, this feature is disabled by default to allow enterprises to work seamlessly with third party classification solutions; however, if needed, it can be enabled again on all previous versions of policy server to get the earlier experience .  
	c. To enable this feature, it will need to be explicitly enabled during the installation or upgrade process.
      2. Fixed the issue where protected files wouldn‚??t open in certain rare scenarios. (#9844) 
	a. Before the fix: Protected files wouldn‚??t open from a location where the file path along with the file name would exceed 260 characters. 
	b. After the fix: These issues are now resolved. 
      3. Other fixes. (#8867, #10011, #9076) 

------------------------------

Seclore 3.16.0.0
Seclore Desktop Client 3.12.1.0
Nov 1, 2020

     1. Introducing browser-based login for Seclore for Windows. (#9621)‚?Į‚?Į 
	a.Now, you can login to the Seclore agent on Windows with your default browser.  
	b.While logging in you‚??ll be directed to an authentication page on your browser.  
	c.All other login features remain the same. 
     2.Fixed the issue where protected PDF files wouldn‚??t open in certain rare scenarios. (#9560)‚?Į‚?Į
        a.Before the fix:‚?Į‚?ĮProtected PDF files wouldn‚??t open with Adobe Acrobat Pro when McAfee Endpoint Security is installed. 
        b.After the fix:‚?ĮThis issue is now resolved.‚?Į‚?Į 
     3.Fixed the issue where a Seclore message shows the file path instead of the file name in certain rare scenarios. (#9745)‚?Į‚?Į 
        a.Before the fix: Upon trying to edit and close a Seclore-protected file with only ‚??Read‚?? permission, Seclore shows a message telling the user that they do not have permission to edit the document. This message would show the file path instead of the file name. 
        b.After the fix:‚?ĮThis issue is now resolved.  
     4. Fixed the usability issue where the Policy Server name would reflect incorrectly in the ‚??About‚?? dialog box of the agent. (#9876)‚?Į‚?Į  
        a.Before the fix: The Policy Server URL link would reflect the name of the Policy Server in the ‚??About‚?? dialog box which could not be changed.  
        b.After the fix: Now the URL would simply reflect the term ‚??Policy Server‚??.   
     5. Other fixes.‚?Į(9806, 8576, 9318, 9471, 9958, 9996, 9972, 9970, 9973) 
------------------------------
Seclore 3.15.0.0
Seclore Desktop Client 3.12.0.0
Oct 1, 2020

    1.Enhanced the user experience of the error/success message screens for desktop protection. (#9749)‚?Į  
	a.Completely re-designed the error/success message screens that are displayed when the user invokes Right-click > Seclore It for protecting files. 
	b.Messages are now wrapped with a more intuitive layout to enhance usability.‚?Į   
    2.Added support to retain classification metadata information in‚?ĮSeclore-protected files when they are edited and saved using the Seclore agent. (#9646, #9683)  
    3.Fixed the issue where Outlook was shutting down unexpectedly in certain rare scenarios. (#9807)‚?Į   
	Before the fix:‚?ĮOutlook would shut down randomly, when composing an email in RTF (Rich Text Format) format and attaching another Outlook email (or any Outlook item) as an attachment.   
	b.After the fix: Protecting an email in RTF format with any Outlook item as an attachment, now works as expected. 
    4.Fixed the issue where the Word app shuts down unexpectedly in certain rare scenarios.  (#9693)‚?Į ‚?Į   
	a.Before the fix:‚?Į Word would shut down unexpectedly when a user selects some text in a protected Word document and then clicks elsewhere while another unprotected document was open in the background. This issue occurs only in Office 365 version 2007 (Build 13029.20308) or later, i.e., August 2020 release.       
	b.After the fix: This issue is now resolved.   
    5.Fixed the issue which occurs in Seclore-protected Excel files in certain rare scenarios. (#9941)‚?Į ‚?Į ‚?Į   
	a.Before the fix:‚?ĮWhen opening a Seclore-protected Excel file that has reference links to any other file, it works the first time, but doesn‚??t work on the 2nd attempt. This happens with standalone Office 2013 or 2019 versions only, but not with O365 versions.       
	b.After the fix: This issue is now resolved.    
    5.Other fixes. (#9572, #9635)  
------------------------------
Seclore 3.14.3.0
Seclore Desktop Client 3.11.2.0
Sept 15, 2020

    1.Fixed the usability issue where the message box that pops up for save intimation while closing MS PowerPoint after editing, displays complete file path as name. (#9701) 
	a.Before the fix: When the user closed a MS PowerPoint file, the save intimation popup that appears displays the location of the file rather than the file name. 
	b.After the fix: Now When the user closes a MS PowerPoint file, the save intimation popup that appears displays the file name. 
    2.Fixed the authentication issue that arises due to difference in time between the client and server machine. (#9743) 
	a.Before the fix: If there was a time difference between client and server machines, user authentication would fail intermittently. 
	b.After the fix: Now if there is as time difference between client and server machines, user authentication will not fail. 
    3.Other Fixes. (#8248, #8940, #9353, #9689, #9715, #9738, #9657, #9759) 
------------------------------
Seclore 3.14.1.0
Seclore Desktop Client 3.11.1.0
Aug 15,2020

    1.Fixed the issue where protected files opened from folders configured with OneDrive Sync Agent do not open with MS Office 2016.
	a.Before the fix: MS Office files protected without html wrapping, when opened from the local One Drive Sync folder fail to open in Standalone Office 2016 (Version 16.0.5017.1000 and above). 
	b.The issue is observed only for natively protected files and not HTML wrapped files
	c.After the fix: The protected file should open without any issue.  
------------------------------
Seclore 3.14.0.0
Seclore Desktop Client 3.11.0.0
1st Aug,2020
 
    1.Introducing the In App-protection for Microsoft Office apps. 
	a.Seclore presents the ‚??Seclore It‚?? button in all Microsoft Office apps for single-click protection from within the open file. 
	b.User can enable the button while editing an unprotected document. 
	c.Once the user closes the unprotected file with the Seclore It button enabled, the file gets protected and the user is prompted to change the file permissions and add recipients. 
	d.File permissions can also be added to the protected file while emailing, using Smart Sharing. 
    2.Extending Seclore‚??s email protection  capability to third-party tools. 
	a.Third-party tools can now integrate with Seclore‚??s email protection interface in Outlook allowing them to leverage end-to-end security for emails and attachments in collaboration with their product features. 
    3.Introducing HTML preserve feature for files protected using Universal Protection. 
	a.Now files protected using Universal Protection will open directly in the edit mode when opened using the native app. 
	b.Users can edit and save changes directly in such files without the need for unprotecting and opening them in the native app for editing. 
    4.Introducing Share and Protect + Share feature in the Endpoint SDK along with notification module.  
    5.Incorporated the new HTML buffer file, that displays user instructions for file open in the Raw HTML content. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content. 
    6.Fixed the issue where the PS login page was displayed instead of a prompt asking the user to allow login using the credentials logged into the Desktop Client. 
	a.Before the fix: When the user was already logged into the Desktop Client and opens the PS URL in the chrome browser, a prompt was displayed asking the user to allow login using SSO of the Desktop Client. 
	b.Instead the PS Login page was displayed, and the user had to login again using his credentials. 
	c.After the fix: Now the user will be directed to the SSO prompt allowing to login directly using the Desktop Client login. 
	d.The Policy Server URL must be the same as the one logged in using the Desktop Client.  
------------------------------
Seclore 3.13.1.0
Seclore Desktop Client 3.10.1.0
July 1, 2020

    1.Introducing OAuth based improved authentication architecture. 
    2.Enhancements in Endpoint SDK 
        a.Introducing HTML wrapping with Endpoint SDK for Advanced Protection.  
        b.Introducing Endpoint SDK in the Adminless Seclore for Windows.  
------------------------------
Seclore 3.13.0.0
Seclore Desktop Client 3.10.0.0
Jun 1, 2020

    1. Introducing a new Adminless agent for Windows. (#9306, #8782) 
       a. The user has an option to download and install either Admin or Adminless mode of the new agent.
       b. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows. 
       c. This client will provide all the capabilities that are available for the agent in the Admin mode. 
       d. Users can download both the versions of the Desktop Client from the Online Access tab of the Policy Server.
       e. The option to download both the modes of Desktop Client will be available in the Policy Server version 3.9.1.0 onwards.
       f. Additionally, when you click the Download the Seclore app option in the buffer file for agentless access, you will be prompted to download the Adminless Desktop Client instead of Seclore Lite for Windows. 
       g. On updating Seclore Lite for Windows version 3.3.5.0, the Desktop Client in the Adminless mode will be installed in the system.
    2. Introducing the capability of printing the watermark over large images in protected PDF files. (#9069)
       a. In case of protected PDF files containing large or scanned images, printing the files with the watermark behind the image makes the purpose of the watermark redundant.
       b. Seclore has enabled the capability of printing the watermark over the content and images of a protected PDF file, if the PDF file contains large images.
       c. This feature is enabled if the image covers more than 50% of the page. This percentage of page size is set by default.
       d. The percentage can also be configured as per requirement.
       e. If the protected PDF files do not contain large images, the watermark will appear behind the content and smaller images on printing.
       f. This feature will be disabled in the Desktop Client, by default.
    3. Fixed the issue where watermark was not displayed for decrypted in-line protected email body in Outlook. (#8996)
       a. Before the fix: If the user was logged in to the Desktop Client and had access to a protected email body, the email was displayed in-line in Outlook without the watermark.
       b. After the fix: The decrypted in-line email body with the watermark will now be displayed for protected emails.
    4. Fixed the issue where the buffer file was not properly displayed when an HTML-wrapped file was opened in the browser for the first time. (#9214)
       a. Before the fix: When an HTML-wrapped file was opened in a browser, the buffer file was not displayed properly.
       b. Instead an error message was displayed stating that the client was unable to connect to the Policy Server.
       c. After the fix: The buffer file will be displayed successfully.
    5. Fixed the issue where in certain cases Outlook stopped functioning when user forwarded or replied to unprotected emails containing inline attachments. (#9228)
       a. Before the fix: When a user opened an unprotected email with inline attachments on a new window (double-click or pop-out) in Outlook and clicked on either Reply/Forward, he was prompted to download the external content before sending.
       b. On clicking No, Outlook stopped functioning.
       c. This was observed when Desktop Client of version 3.9.0.0 or above was installed in the system.
       d. This happens when inline attachments are not downloaded before Reply or Forward action.
       e. After the fix: Outlook will remain functional and the email will be forwarded, or the reply will be sent successfully.
    6. Other fixes. (#9277)
------------------------------
Seclore 3.12.2.0
Seclore Desktop Client 3.9.4.0
May 15, 2020

    1. Fixed the issue where on clicking F12 key from the keyboard, a protected Word (O365) document was displaying an error instead of getting saved. (#9128)
       a. For a Seclore-protected document, users with Edit permissions on Word documents can save it after editing by using the shortcut F12 key from the keyboard. 
       b. Before the fix: When a user, with Edit permission, tried to save a protected Word document using the F12 shortcut key, an error was displayed. 
       c. The error prompted the user to use File >> Save As to save the document instead.
       d. After the fix: A protected Word document can now be saved as a new file using the F12 shortcut key. 
    2. Fixed the rare issue where Microsoft Outlook stopped functioning when an email containing Microsoft AIP protected attachments and inline attachments was selected in the inbox. (#9157)
       a. Before the fix: When a user selected an email containing Microsoft AIP protected documents and inline attachments, Outlook stopped functioning. 
       b. This also occurred when Outlook is started and there are emails of the above-mentioned nature in the inbox. 
       c. After the fix: When such emails are selected, Outlook will work as expected.
       d. Users can view emails containing Microsoft AIP protected attachments in Outlook.
    3. Fixed the issue where the Learn More URL for Universal Protection in the Seclore Email Protector in Outlook redirected the user to a blank page in the Seclore Online help. (#9183)
    4. Fixed the issue where a newly added signature was not saved in a protected PDF file. (#7249)
       a. Before the fix: When a user opened a protected PDF file and added a signature (Fill and Sign option), the signature did not appear on saving the PDF file.
       b. The signature did not appear even on Save As or closing and opening the PDF file after adding the signature.
       c. After the fix: A newly added signature in a protected PDF file gets added and saved successfully on saving the PDF file.
------------------------------
Seclore 3.12.1.0
Seclore Desktop Client 3.9.3.0
Apr 16, 2020

    1. Introducing editing and saving of HTML wrapped Seclore-protected files. (#8843) 
       a. Now, when you open an HTML wrapped protected file by double-clicking on it, it will open in the native application. 
       b. After editing in the native application if you click Save, the content is updated in the HTML wrapped file itself. 
       c. When you close the file, the HTML wrapping is preserved. 
       d. If you close an HTML wrapped protected file opened in the native application after editing, the Save dialog box prompts you to save the file before closing the application. 
       e. For files protected using Universal Protection, the HTML wrapped file will open in the native application as well. 
       f. However, on saving after changes, the Save As dialog box appears. 
       g. On saving, an unprotected file is saved on your machine. 
       h. This works on all file formats with the exception of image and text file formats
    2. Fixed the issue where incorrect error messages in the local language of the user was displayed on opening a file in certain cases. (#9019) 
       a. Before the fix: Incorrect error message for invalid PS certificates while opening a file, was displayed in the local language of the user. 
       b. After the fix: The correct error message in English will be displayed in the above-mentioned case. 
    3. Fixed the issue where if a file with read permission was opened from a network location, another file from the network failed to open. (#8204) 
       a. Before the fix: The user opened a protected file from a network location with read permission. 
       b. When the user tried to open another protected file of the same native application from a network location, it failed to open. 
       c. After the fix: Protected files from network locations open successfully one after the other. 
    4. Fixed the issue where the Open With window was displayed instead of opening a protected PDF file directly with right-click >> Seclore‚??s Open With Adobe Acrobat Reader DC option. (#8941)
       a. Before the fix: When user opened a protected PDF file using right-click >> Seclore‚??s Open With Adobe Acrobat Reader DC, the Open With window was displayed instead of opening the file directly.
       b. This happened when both Adobe Acrobat XI and Adobe Acrobat Reader DC were present in the system.
       c. After the fix: The file will directly open in Adobe Acrobat Reader DC.
    5. Discontinued support for Adobe Reader X. (#8972)
    6. Other fixes. (#9031, #8921, #9008) 
    7. Security fixes. (#8936, #7447, #8637)
------------------------------
Seclore 3.12.0.0
Seclore Desktop Client 3.9.2.0
Apr 1, 2020

    1. Introducing automatic HTML wrapping when files are protected using the Seclore agent. (#8671, #8672, #8745, #8822) 
       a. After this release, when a user protects a file using right-click >> Seclore It!, the file gets protected as well as HTML wrapped automatically. 
       b. This will remove the additional step of HTML wrapping a file after protecting it. 
       c. This ensures consistency with files protected using Universal Protection which are HTML wrapped automatically. 
       d. HTML wrapping must be enabled in the Policy Server configuration page. 
       e. If HTML wrapping is disabled, the file will only get protected and HTML wrapping will not be applied to it.
       f. In the right-click context menu, the ‚??Convert to agentless format‚?? option is changed to 'Convert to HTML format'.
       g. To convert an HTML wrapped file to the native format, ‚??Convert to native format‚?? option is added in the right-click context menu. 
       h. This feature will not be available in the presence of Boldon James classification or Seclore-classification based protection.  
    2. Introducing Universal Protection for Symantec and Forcepoint Endpoint DLP based protection. (#8882, #8883, #8884)  
       a. Earlier, files with standard formats were discovered by Symantec and Forcepoint DLPs and protected using Seclore. 
       b. Files with non-standard formats were not protected. 
       c. After this release, non-standard file formats will be protected using Universal Protection when discovered by Symantec and Forcepoint Endpoint DLPs. 
       d. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection. 
    3. Adding GDPR compliance to Seclore. (#8915) 
       a. When user logs in on the Policy Server or agents, the ‚??Terms of Service‚?? and ‚??Privacy Policies‚?? will be available to the user to view.
       b. These policies will inform the user of the kind of information Seclore will collect and how it will be used.  
    4. Fixed the issue when a protected Word or Excel file was saved as unprotected when saving to OneDrive using the AutoSave option. (#8185) 
       a. Before the fix: The user opened a protected Word or Excel file with less than Full Control permission. 
       b. When the user clicked the AutoSave option and configured it to be saved on OneDrive, the file was saved as an unprotected file. 
       c. After the fix: The AutoSave option will be disabled for protected Word, Excel and Powerpoint files. 
    5. Made the error messages informative in case the Seclore agent is not able to process a user action. (#8910) 
       a. Now the user will be able to know the nature of the error from the error message itself. 
       b. This will help the users and system administrators to resolve the issue at the earliest for uninterrupted use of Seclore. 
    6. Fixed the issue where the Seclore icon was not visible on the taskbar when the agent was active on the Desktop. (#8912) 
       a. Before the fix: The Seclore icon on the taskbar appeared black when the agent was active on the Desktop. 
       b. After the fix: The Seclore lock icon will be visible on the taskbar when the agent is active on the Desktop.
    7. Fixed the issue where the users with no access or expired access could view the buffer file or the data itself after RAR. (#8838)  
       a. Before the fix: For a user who did not have access to a protected file, the RAR dialogue box appeared. 
       b. After the user requested access permission to the protected document, the buffer file was displayed.
       c. For a user with expired access, after RAR the document opened with the data. 
       d. After the fix: After RAR, in both the scenarios mentioned above, the document will close. 
       e. Users will have access to the document and can view it only after the owner of the protected file assigns or renews permissions.    
    8. Other fixes. (#8102)
------------------------------
Seclore 3.11.1.0
Seclore Desktop Client 3.9.1.0
Mar 1, 2020

    1. Fixed the rare issue where protected image files were not opening using MS Paint in presence of Boldon James classification. (#8820)
       a. Before the fix: When the user, with Boldon James classification installed, right clicked on a protected image file and selected Open with >> MS Paint, the image did not open. 
       b. This was observed with the Desktop Client version 3.8.12.0 and above. 
       c. After the fix: The protected image files opened in MS Paint, as expected.
    2. Fixed the issue where protected files with multiple ‚??%s‚?? in the filename stopped working on opening or unprotecting in offline mode. (#8818) 
       a. Before the fix: Protected files having multiple (either consecutive or separated) ‚??%s‚?? in their filenames stopped working when opened.
       b. Also, when user tried unprotecting such a file (Right click >> Advanced >> Unprotect), the file did not function as expected.
       c. After the fix: Users will be able to open and unprotect protected files in offline mode with multiple ‚??%s‚?? in their filenames successfully.
    3. Fixed the issue where the Undo action did not work after editing and saving a protected Excel file. (#8768)
       a. Before the fix: After a user opened, edited and saved a protected Excel file, the Undo action did not work like it should in case of an unprotected Excel file.
       b. After the fix: Undo changes can be performed even after saving changes in a protected Excel file.
    4. Fixed the issue where a protected file lost all the attributes after it was HTML wrapped. (#8590)
       a. Before the fix: When a protected file was HTML wrapped, the file lost all its attributes.
       b. These attributes included Read Only mode, hidden attribute, change in creation date, etc.
       c. After the fix: Protected files, when HTML wrapped, will retain the above mentioned attributes.
    5. Fixed the issue where in case of cloned Windows machines, the installation report of the Seclore Desktop Client displayed only a single entry. (#8470)
       a. Before the fix: When a machine was cloned and Desktop Client was installed in the cloned machine, it replaced the installation entry of the previous machine.
       b. Due to this, the installation report did not record the actual number of installations of the Seclore Desktop Client.
       c. After the fix: The installation report will display the installation of Desktop Client in the cloned machine as a separate entry.
       d. This will ensure that the actual number of installations of the Desktop Client is recorded in the installation report.
    6. Other fixes (#8856, #8842, #8841, #8831, #8827, #8805, #8798, #8776, #8734, #8732, #8679, #8514, #8641, #8591, #8533, #8529, #8495, #8480, #8478, #8392, #8379, #8365, #8182, #7048, #7050, #8788) 
------------------------------
Seclore 3.11.0.0
Seclore Desktop Client 3.9.0.0
Feb 1, 2020

    1. Introducing Universal Protection for protecting any file format with sensitive enterprise information. (#8447)
       a. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the ‚??Seclore It‚?? button in Outlook.
       b. With this new feature, users can now protect any file format on their desktop or in Outlook. 
       c. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).  
       d. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
       e. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission. 
       f. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to ‚??Save As‚??. 
       g. Authorized recipients can also Unprotect these files. 
       h. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html. 
       i. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature. 
       j. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
       k. Requires Policy Server 3.8 or higher. 
    2. End of Advanced Protection support for certain outdated file extensions. (#8554)
       a. Certain file formats will not be supported by Seclore for Advanced Protection, going forward.
       b. These file formats will be included under Universal Protection and the permissions granted for Universal Protection will be applicable.
       c. When the Policy Server is updated and the Desktop Client is not updated, files in these formats, which were previously protected using Advanced Protection, will continue to grant the previously applied permissions.
       d. When the Desktop Client is updated, files in these formats, which were previously protected using Advanced Protection, will prompt the user to get the file re-protected using Universal Protection from the owner on access.
       e. This is regardless of the Policy Server being updated or not.
    3. Fixed the issue where the PowerPoint files (protected and unprotected) stopped functioning when a user moved through a list of files in the File Explorer with the Preview Pane enabled. (#8573)
       a. Before the change: When a user enabled the Preview Pane (View >> Preview Pane) in the File Explorer and moved through a list of files, PowerPoint files open in the background stopped functioning.
       b. This particular behaviour was not observed for other Microsoft Office file formats as preview is disabled for file formats like Word and Excel.
       c. After this change: PowerPoint files will function and remain open as expected even with the Preview Pane enabled in the File Explorer.
    4. Fixed the issue where the default browser icon was displayed for a HTML wrapped file. (#8619)
       a. Before the change: When Desktop Client was installed in the system, the original file format icon (Word, Excel, PowerPoint, etc.) was not displayed for HTML-wrapped files.
       b. Instead, the default browser (for example, Chrome icon) was displayed.
       c. This usually occurred after restarting the system.
       d. This was previously rectified by running the Repair Installation tool of the Desktop Client (Click on the Seclore tray icon >> Repair Installation >> OK).
       e. After the change: The default file format icon will be displayed for HTML-wrapped files throughout.
       f. Exception: Files with .smail extensions will continue to display the default browser icon or HTML icon.
    5. Fixed the issue where the default file format icon was not displayed for HTML-wrapped files when a copy of the file was created or when an HTML-wrapped file was downloaded multiple times. (#8669)
       a. Instead, the default browser icon was displayed.
    6. Fixed the issue where the lengthy email IDs of the file owners spilled over the permission widget of an open protected file. (#8257)
       a. Before the change: When the user clicked the ‚??S‚?? button in an open protected document, the email ID of the owner spilled over the permission widget.
       b. After the change: For lengthy email IDs, part of the email ID is visible, and three dots are added after that.
       c. The user can hover over the dots and view the complete email ID as a tooltip.
    7. Fixed the issue where Outlook stopped functioning when the user clicked on the ‚??Seclore It‚?? button for protecting emails and attachments. (#8683)
       a. Before the change: While composing an email from the Outlook application when the user clicked on the ‚??Seclore It‚?? button from the Menu ribbon, Outlook stopped functioning.
       b. This issue was observed for users with Policy Server version 3.7.4.0 and above.
       c. After the change: When the user clicks the ‚??Seclore It‚?? button on the Menu ribbon in the Outlook application, the Seclore options will be displayed, as expected.
    8. Security fixes (#8705, #8580) 
    9. Other fixes (#8766)
------------------------------
Seclore 3.10.16.0
Seclore Desktop Client 3.8.12.0
Jan 1, 2020

    1. Fixed the issue where if a file with "% S" characters in its file name is attached to an email in Outlook, the Outlook app stopped functioning as expected. (#8469)
    2. Fixed the issue where Outlook stopped functioning as expected when an email group contained the ID of an ex-employee (deactivated email ID). (#8472)
       a. After this fix, the email will be sent to the remaining recipients of the email group.
       b. In case the ex-employee is the only recipient of the email, a delivery failure message will be received by the sender.
    3. Fixed the issue where the cross-referencing option in a protected Word document was disabled. (#8484)
    4. Updated the Seclore tooltips displayed in Outlook, providing clearer and more intuitive description for each of Seclore permission options. (#8578)
    5. Fixed the issue where if a Seclore-protected PDF document didn‚??t open as expected, it could potentially lead to loss of data in certain rare cases. (#8522)
       a. Before the fix: If the protected PDF document didn‚??t open as expected, the buffer file was displayed in editable mode in certain cases.
       b. In this case, if the user unknowingly saves the document, there is a potential for loss of data from the original document.
       c. After the fix: The buffer file is opened in Read-only mode to ensure there is no loss of data. 
    6. Fixed the issue introduced in the latest Google update, where an error was displayed if the user tried to login to the agent using Google authentication. (#8577)
    7. Other fixes. (#8412, #8479, #8236, #8395, #8396, #8397, #8512)
------------------------------
Seclore 3.10.15.0
Seclore Desktop Client 3.8.11.0
Dec 1, 2019

   1. Discontinued the image viewer that was bundled viewer along with the Seclore agent. (#8187)
      a. Seclore now uses the built-in image rendering capabilities of Windows to open Seclore-protected image files.
      b. This reduces the size of the agent installer by a few MB.
   2. Fixed the random issues that were observed when opening protected documents in certain scenarios. (#8507)
      a. In cases where Adobe Reader or Acrobat was reinstalled, it was leading to issues with opening protected PDF documents. 
      b. For other formats, a similar issue was seen in certain cases when a user opens a file using ‚??Right-click > Open with‚?? in Windows Explorer. 
   3. Fixed the rare issue where protected documents didn‚??t open as expected when the user was a Built-in Administrator. (#8386)
      a. In certain rare cases (usually on server-based virtual machines), the logged in user may be a part of the Built-in Administrators group. 
      b. In certain cases, such a user may not be able to open protected documents as expected. 
      c. He/she may see only the Buffer page or in certain cases, the Office app (Word, Excel or PowerPoint) may shut down unexpectedly.
   4. Other fixes. (#8377, #8390, #8435, #8446)

------------------------------
Seclore 3.10.14.0
Seclore Desktop Client 3.8.10.0
Nov 1, 2019

   1. Added support for the latest Google Chrome browser version 76 and above for Auto-login to the Policy Server in the browser when the user is already logged in to the Desktop Client. (#8120)
   2. Fixed two issues that occur in the latest version of Microsoft Excel 1909 or later:
      a. The login page was not displayed as expected when the user is not already logged in. (#8260)
      b. The Seclore badge (displaying user permissions) was not visible after the file was opened. (#8235)
   3. Minor fixes in the UI for the newly updated Desktop Client UI. (#8155, #8156, #8157, #8321, #8322)
   4. Fixed the minor issue where the file name was appearing in upper case in certain activities logged on the Policy Server. (#8329)
   5. Other fixes. (#8304)

------------------------------
Seclore 3.10.13.0
Seclore Desktop Client 3.8.9.0
Sep 1, 2019

   1. Significantly enhanced the user experience for Agentless access of protected documents by revamping the content and behavior of the HTML pages displayed in the browser. (#8073)
      a. Enhanced the messaging and visual layout to make it more intuitive for first time users when opening protected documents directly in the browser.
      b. Added special handling for users of the Chrome browser to open protected documents in the native app when the agent is installed.
      c. Requires Seclore Policy Server 3.7.5 or higher.
   2. Enhanced the Seclore tray by improving the visual design and dropping unused options. (#8024)
      a. Before the change: When user left clicked on the Seclore icon in the notification area, a small screen was displayed with options that were not utilized by the user.
      b. After the change: Only the important options are displayed now, when the user right-clicks on the Seclore icon. The left-click is disabled.
   3. Enhanced the user experience and functionality of the Error Reporting Tool. (#8106)
      a. Revamped the user interface with better design and aesthetics. 
      b. Added the capability for the user to give consent before system details and application logs are captured by the tool. 
      c. Enhanced the processing performance.
   4. Fixed the issue where protected documents open in the background, if opened from any folder other than the Desktop, when the user is already logged in. (#8058)
      a. This issue occurred while opening Word and PowerPoint documents.
      b. This issue did not occur, if user is not logged in and performs explicit authentication while opening a file, if communication to the Policy Server was slower and for large files.
   5. Fixed the issue where Outlook stopped responding when the user tries to access any folder in Outlook after clicking on the inline protected email body. (#8075)
   6. Changed the error message for unsaved Microsoft Word and Microsoft Excel files to convey a clear and short message to the user for saving the file. (#8105)
      a. Before the change: The message was lengthy and complex. It did not convey the actual steps to manually save the protected file before closing it.
      b. After the change: A more intuitive dialog box with clearer message stating to manually save the document before closing it.
   7. Other fixes (#7906, #8021, #8089)

------------------------------
Seclore 3.10.12.0
Seclore Desktop Client 3.8.8.0
Sep 1, 2019

   1. Added system controls in the Desktop Client to discontinue support for Windows Server 2008 R1. (#8036)
      a. Any Desktop Client installed on Windows Server 2008 R1 will not be upgraded automatically by the regular patch upgrade mechanism.
      b. The agent will be frozen on the last supported version i.e. Desktop Client 3.8.7.0
      c. To continue agent upgrades, install a newer OS version i.e. Windows Server 2008 R2 or higher.
      d. Desktop Clients that are frozen at version 3.8.7.0 will be clearly indicated in the Agent Installation Report that is available to the System Admin in the Seclore Policy Server.
      e. Microsoft discontinued Mainstream support for Windows Server 2008 in 2015.

------------------------------
Seclore 3.10.11.0
Seclore Desktop Client 3.8.7.0
Aug 1, 2019

   1. Fixed the issue where downloading and opening a protected document from the Chrome browser‚??s download bar was not opening in the native application, as expected. (#7919)
      a. When the Seclore agent is installed, the user expects a protected document to open locally in the native application.
      b. Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application. 
      c. This was happening because Google‚??s Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them. 
      d. After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application. 
      e. Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.
   2. Improved the performance of protecting emails using the ‚??Seclore It‚?? button in Outlook. (#7958, #7998)
   3. Improved the error message displayed in Outlook when a user right-clicks on a document and selects ‚??Send to > Mail recipient‚?? with Seclore Data Classification enabled. (#7996)
      a. When Outlook is configured as the default Mail app in Windows, the user can right-click on a document and select ‚??Send to > Mail recipient‚?? to automatically compose a new email in Outlook and attach the document. 
      b. In the above case, if the user has auto-protection with Seclore Data Classification enabled, the email doesn‚??t get automatically protected as expected. 
      c. Due to a technical limitation in Outlook, the email cannot be sent. 
      d. Before the fix: In the above case, the system was displaying a generic error message that was not very helpful to the user.      
      e. After the fix: The new error message will clearly inform the user that this method of composing an email is not supported.
      f. The message will also instruct the user to always compose emails using the ‚??New Email‚?? button in Outlook.  
   4. Fixed the issue where, A Copy of the already opened file opens again, on selecting 'Restore' option shown in a second PDF file that is opened. (#8033)
      a. The ‚??Restore‚?? option should not appear at all when a user opens a second PDF file while the first is already open.
      b. Before the change: In case of an unprotected file, when the user clicked on the ‚??Restore‚?? option in the second Adobe window, a copy of the first open file was displayed. In case of a protected file, when the user clicked on the ‚??Restore‚?? option in the second Adobe window, the buffer file was displayed.
      c. This issue was consistent on Continuous track May 2019 release of Adobe.
      d. After the change: The ‚??Restore‚?? pop-up and option does not appear when opening two PDF document one after the other on Adobe Acrobat Standard DC Continuous, Adobe Acrobat Pro DC Continuous and Adobe Acrobat Reader DC Continuous.
   5. Added support for rarely used versions of Adobe Acrobat Reader, Acrobat Standard and Acrobat Pro. (#7970)  
      a. Adobe Reader 2015 (Classic)
      b. Adobe Reader 2017 (Classic)
      c. Acrobat Pro 2015 (Classic)
      d. Acrobat Pro 2017 (Classic)
      e. Acrobat Standard DC (Continuous)
   6. Other fixes. (#7907, #7589)

------------------------------
Seclore 3.10.10.0
Seclore Desktop Client 3.8.6.0
July 16, 2019

   1. Fixed the rare issue that impacts the usage of a protected document in certain versions of Word 2016, when it is opened directly from a shared network drive. (#7950)
      a. Before the fix: If the user opens a protected document directly from a shared network drive, all the application controls get disabled.
      b. This is observed only in certain versions of Word 2016 that are operating with a one-time volume license. O365 and other subscription-based licenses do not present this same issue.
      c. After the fix: This issue is now resolved.
   2. Fixed the Microsoft Outlook issue where the application goes into a non-responding state in certain rare cases. (#7977)
      a. Before the fix: This issue occurs when a user has a protected email body open inline within his/her Outlook application window and selects some text, then clicks on Reply or Reply All or Forward.
      b. In some cases, the application goes into a non-responding state.
      c. After the fix: This issue is now resolved.
   3. Fixed the Outlook performance issue that is observed when sending an email to a very large Distribution List. (#7978)
      a. Before the fix: Sending an unprotected email to a very large Distribution List, would sometimes put the Outlook application into a non-responding state.
      b. After the fix: This issue is now resolved.

------------------------------
Seclore 3.10.7.0
Seclore Desktop Client 3.8.5.0
June 01, 2019

   1. Added support for Exchange Shared Mailbox groups in the Email Protector for Outlook. (#7884)
      a. Before this change: If a protected email was sent from a Shared Mailbox (i.e. the Mailbox group is the Sender), it was not accessible to the other members of the group. 
      b. After this change: Any email that is either sent to or sent from a Shared Mailbox, will always be accessible to all its group members.
   2. Enhanced the user experience of the Smart Sharing feature by switching ON the Smart Sharing button every time a new email is composed. (#7854)
      a. Before this change: If a user switched OFF Smart Sharing in an email and sent it, the next time he/she composes a new email, Smart Sharing would still be OFF.
      b. Since Smart Sharing is switched OFF only in the rarest of cases, this would require the user to remember to switch it ON when composing the next email. 
      c. After this change: Every time a new email is composed, the Smart Sharing switch will always be ON.
   3. Optimized the login process for authenticating with the Policy Server in the Email Protector for Outlook. (#7850)
   4. Re-designed and enhanced the intuitiveness of the user prompt in Email Protector for Outlook that reminds users to click on the Seclore It button. (#7851)   
   5. Enhanced the user experience for opening unprotected documents in LibreOffice. (#7873) 
      a.Before this change: When opening any document, the same system process was invoked that would reload the document content.   
      b. After this change: Unprotected documents will not be reloaded and will now open faster.  
   6. Fixed the issue where Right-click > Seclore It was not working in some rare cases where the Windows Temp folder was set to some very specific value. (#7731) 
      a. Before the fix: In case the Temp folder was set to a value like ‚??C:\‚?? or ‚??D:\‚??, the Right-click > Seclore It feature was not working as expected. 
      b. After the fix: This issue has now been resolved.  
   7. Fixed the issue where a document could not be opened in Offline mode in certain rare cases. (#7848). 
      a. Before the fix: A protected document could not be opened in Offline mode i.e. without connectivity to the Policy Server, if the Policy Server ID contained an ampersand (&).   
      b. After the fix: This issue is now resolved.  
   8. Other fixes. (#7827, #7882)

------------------------------
Seclore 3.10.5.0
Seclore Desktop Client 3.8.4.0
May 01, 2019

   1. Fixed the issue in Outlook Email Protector when emails were Smart Shared, where recipients were not getting registered as new users if their email ID contained a single quote (‚??). (#7792)
   2. Other fixes. (#7783, #7807, #7808, #7818)
   
------------------------------
Seclore 3.10.3.0
Seclore Desktop Client 3.8.3.0
Apr 15, 2019

   1. Enhanced support for Agentless access by preserving the HTML Wrapper even when the document is accessed using an agent. (#7740)
      a. Before this change: Whenever a user having a Seclore agent opens a protected document that is HTML Wrapped, the HTML Wrapper is removed, before it is opened.
      b. E.g. if a protected document ‚??sample.docx.html‚?? is opened using the Desktop Client, the HTML Wrapper will first be removed, and the document will be renamed to ‚??sample.docx‚?? before it is opened.
      c. After this change: When sample.docx.html is opened, the HTML Wrapper will NOT be removed, and the document will open in Read-only mode.
      d. This document can be shared further with anyone who can easily access it without an agent installed.
      e. Preserving the HTML Wrapper helps to keep it more accessible to external users who can directly open it in the browser without an agent.
      f. Only if the user edits and saves the document, the updated version will be saved without the HTML Wrapper.
   2. Enhanced the new end point SDK released in version 3.8 to support integration with applications that run as a system process. (#7690)
      a. New integration mechanism for protecting documents on the end point by applications like DLP and file scanning tools that run as background process at the system level.
      b. Provides a better user experience by making the logged-in user the File Owner.
   3. Fixed the issue where an unnecessary error message was being displayed when opening unprotected text and OpenOffice documents in Microsoft Office applications. (#7727)
      a. Before the fix: When a user attempts to open an unprotected text or OpenOffice document in Microsoft Word or Excel, an error message is displayed saying ‚??Seclore does not support viewing and processing of ‚??.TXT‚?? format in Microsoft Office‚??.
      b. Simple workaround: Just clicking on the ‚??OK‚?? button opens the file as expected.
      c. After the fix: No such error message is displayed.
   4. Minor UI alignment adjustment in the ‚??Seclore It‚?? Outlook permission labels and checkboxes. (#7782)
   5. Added support for Russian language in the Issue Reporting tool. (#7706)
   6. Other fixes. (#6080, #7611, #7663)

------------------------------
Seclore 3.10.2.0
Seclore Desktop Client 3.8.2.0
Apr 15, 2019

   1. On a periodic basis, Seclore will discontinue support for older and obsolete platforms and applications to ensure that the risk to enterprise data is always under control. 
      a. Older versions of Operating Systems and Office applications that are no longer being supported by Microsoft are often a security threat to the enterprise. 
      b. At the appropriate time, Seclore discontinues support of such obsolete software components to ensure that they do not pose a threat to the enterprise data security program. 
   2. Added system controls in the Desktop Client to discontinue support for obsolete Operating System versions. (#7670) 
      a. Discontinued support for Windows XP, Windows Vista and Windows Server 2003.  
      b. Any Desktop Client installed on either of the above-mentioned operating systems will not get upgraded automatically by the regular patch upgrade mechanism. 
      c. The agent will be frozen on the last supported version i.e. Desktop Client 3.8.1.0. 
      d. To get the Desktop Client to start upgrading again, install a newer (supported) Operating System and the latest version of the Desktop Client.   
      e. Desktop Clients that are frozen at version 3.8.1.0 will be clearly indicated in the Agent Installation Report that is available to the System Admin in the Seclore Policy Server. 
      f. Microsoft discontinued support for Windows XP in April 2014 and Vista in April 2017. Vista was also Microsoft‚??s least accepted Windows version of all time. 
      g. Microsoft discontinued support for Windows Server 2003 in July 2015. 
   3. Added system controls in the Desktop Client to discontinue support for Microsoft Office 2003. (#7670)
      a. Users will not be able to open Seclore-protected documents in Office 2003 applications.
      b. Any newer version of Microsoft Office can be installed on the same desktop to open Seclore-protected documents.  
      c. Microsoft discontinued support for Office 2003 in April 2014. Office 2003 is also not compatible with Windows 8 or higher. 
   4. Added system controls in the Desktop Client to discontinue support for Adobe Acrobat Reader 8 and 9. (#7670)
      a. Users will not be able to open Seclore-protected PDF documents in Acrobat Reader 8 or 9.
      b. Adobe discontinued support for Acrobat Reader 9 in June 2013 and version 8 even earlier.

------------------------------
Seclore 3.10.1.0
Seclore Desktop Client 3.8.1.0
Mar 14, 2019

   1. Fixed the installation issue that occurs when the operating system language is set to anything other than English. (#7712)

------------------------------
Seclore 3.10.0.0
Seclore Desktop Client 3.8.0.0
Mar 1, 2019

   1. All new end point SDK provided to simplify the end point protection process and make it more efficient. (#7482)
      a. New integration mechanism for protecting documents on the end point by applications like Classification and DLP tools.
      b. Provides a better user experience by making the logged-in user the File Owner.
      c. Simplifies the integration process for any end point application to protect with Seclore.
   2. Updated Seclore Email Protector for Outlook to make it compatible with Seclore Protector for Data Classification 3.1.0.0, which can automatically protect documents classified using Boldon James Email Classifier. (#7416)
   3. Added the ability to configure default protection permissions for protected content. (#7652, #7654)
      a. The following options can be configured: i) Default permissions for protected files and email attachments, and ii) Whether to protect the email body (for Email Protector)
      b. These options can be configured in the Policy Server and can be changed by the protector before protecting files and emails
      c. Requires Policy Server 3.7.0.0
   4. Fixed the rare issue where an unprotected Excel file could not be opened from a folder synced to OneDrive. (#7481)
   5. Fixed the issue where only the first few pages of very large, multi-page PDF documents would be printed. (#7648)
   6. Other fixes. (#7444, #7490, #7491, #7605, #7656)

------------------------------
Seclore 3.9.5.0
Seclore Desktop Client 3.7.4.0
Feb 1, 2019

   1. Updated the Spanish language pack. (#7461)
   2. Updated the Russian language pack. (#7462)
   3. Other fixes. (#7592)

------------------------------
Seclore 3.9.4.0
Seclore Desktop Client 3.7.3.0
Jan 1, 2019

   1. Fixed the issue where Outlook meeting invites were not sent on synchronization when the ‚??Send immediately when connected‚?? option was unchecked. (#7421)
      a. Before the fix: When the ‚??Send immediately when connected‚?? option is OFF, the meeting invite was not sent even after synchronization.
      b. After the fix: Users will now be able to send meeting invites even when this option is turned OFF.
   2. Fixed the rare issue where the Compose window continued being displayed even after a protected email was sent. (#7423)
   3. Fixed the issue where Seclore Email Protector callout tutorial in the Outlook Compose window becomes transparent in the presence of existing text in the background (email body). (#7489)
   4. Other fixes. (#7430)

------------------------------
Seclore 3.9.2.0
Seclore Desktop Client 3.7.2.0
Dec 1, 2018

   1. Enabled co-authoring of unprotected documents in OneDrive sync folders. (#7257)
      a. Before the change: Co-authoring of all documents were disabled in OneDrive sync folders to ensure the data integrity of Seclore-protected documents.
      b. After the change: Unprotected documents can now be co-authored as expected in OneDrive sync folders.
      c. Co-authoring in OneDrive will still be disabled for Seclore-protected documents to ensure data integrity and security.
   2. Fixed the rare issue that occurs when multiple users attempt to Protect the same document in a shared folder. (#7177)
      a. Before the change: If a document in a shared folder is simultaneously Protected by multiple users, it could lead to corruption of data.
      b. After the change: The agent now ensures that more than one user cannot protect the same document even when it resides in a shared folder.
   3. Fixed the error message displayed to the user when they attempted to protect a protected file. (#6602)
      a. Before the fix: The entire file path was mentioned in the error message, making it too long and hard to read.
      b. After the fix: The file path is no longer mentioned in the message, so it is much more readable for the end user.
   4. Other fixes. (#7412, #7274)

------------------------------
Seclore 3.9.1.0
Seclore Desktop Client 3.7.1.0
Nov 1, 2018

   1. Fixed the issue where the protected email body content and Seclore notifications were not displayed correctly for the following combinations of Windows and Office versions: Windows 10 (1703 or later) and Office 1808 or later. (#7221)
   2. Fixed the issue where Outlook would crash while replying to meeting invitations in Calendar if the email (including the email signature) contained more than one inline image. (#7309)

------------------------------
Seclore 3.9.0.0
Seclore Desktop Client 3.7.0.0
Oct 16, 2018

   1. Enhanced the file opening process to make protected Office documents open faster. (#7145)
      a. Protected MS Office documents will now open faster than before.
      b. This will be especially noticeable for large documents and documents with many references to other documents. 
      c. Conflicts with other Office add-ins will also be reduced. 
      d. This feature is not applicable to protected PowerPoint documents.
   2. Other fixes. (#7312)

------------------------------
Seclore 3.8.4.0
Seclore Desktop Client 3.6.3.0
Oct 1, 2018

   1. Added support for Google Chrome version 66 and above for enabling Auto-login to Policy Server in the browser when already logged in to the Desktop Client. (#7253)
      a. Before the fix: Seclore‚??s existing Auto-login to Policy Server feature - that worked with the earlier versions of Chrome - stopped working when Google introduced some changes in Chrome version 66.
      b. After the fix: The Desktop Client has now been modified to enable the Auto-login feature with any supported version of Chrome. i.e. any Chrome version released in the last 12 months.
   2. Fixed the issue where protected ppt and pptx files did not open if local agents of Digital Guardian and Trend Micro where installed on the same computer as the Desktop Client. (#7256)
   3. Other fixes. (#7021, #7173, #7269)

------------------------------
Seclore 3.8.3.0
Seclore Desktop Client 3.6.2.0
Sep 1, 2018

   1. Added support for Windows Server 2016. (#7175)
   2. Fixed the issue where external links would break when working with multiple protected Excel documents in a very specific scenario. (#7020)
      a. Before the fix: The issue occurred only when the user had Full Control permission on three Excel documents A, B and C. Document A contained references of document B, and document B contained references of document C.
      b. If the user opened A and chose the Update option in the Update Links dialog box, links to B got updated automatically.
      c. After 15 minutes, if the user opened B and chose the Update option, an invalid error message was displayed stating ‚??All links of the workbook ‚??‚?? will be broken and the workbook will be opened in read-only mode because you do not have the required permissions to copy data from linked file(s) ‚??‚?? to this workbook.‚??
      d. If the user clicked ‚??OK‚?? on this error message, the links were automatically broken.
      e. After the fix: This error has now been fixed and the Excel links in all such documents will get updated automatically if the user has Full Control permission.
   3. Fixed the rare issue where unprotected Excel documents did not open if Protected View was enabled. (#7114)

------------------------------
Seclore 3.8.1.0
Seclore Desktop Client 3.6.1.0
Aug 1, 2018

   1. Fixed the issue where protected Excel documents would not open on Microsoft Office 2013 (32 bit) updated with KB 4133083 (May 2018) and KB 4299875 (June 2018). (#7000)
   2. Fixed the issue where a Seclore-protected document would not open as expected from a OneDrive synced folder on the local desktop. (#7075)
      a. Before the fix: In certain cases, documents opened from a OneDrive synced folder with co-authoring enabled were not opening as expected.
      b. This issue was observed with Microsoft Office 365 (version 1807).
      c. It did not occur when a protected document was opened from any other (unsynced) folder.
      d. After the fix: Documents can now be successfully opened even from a OneDrive synced folder.
      e. Expected Behavior: The co-authoring feature in Office 365 will be automatically switched off for both protected and unprotected documents.
         Here is a reference link for multiple situations where co-authoring gets blocked anyway:
         https://support.office.com/en-us/article/troubleshoot-co-authoring-in-office-bd481512-3f3a-4b6d-b7eb-ebf9d3626ae7
         In a future release, it may be possible to enable co-authoring for unprotected documents.
   3. Fixed an issue where another application (NG80exec.exe) was facing a conflict with the Seclore Desktop Client. (#6896)
   4. Other fixes. (#6951, #7005, #7009)

------------------------------
Seclore 3.8.0.0
Seclore Desktop Client 3.6.0.0
July 1, 2018

   1. Outlook 2010 now supports all the latest Email Protector features. (#6719)
      a. Inline View: Authorized users can view a protected email body within the Outlook message window itself.
      b. Request Access: Users can request for access to a protected email or attachment with just one click.
      c. Track: Keep at track of both authorized and unauthorized activities on your protected emails.
      d. Revoke Access: Retract your emails from at any time after sending them, either for a specific recipient or all recipients. The ‚??Unsend‚?? button for your email that you‚??ve always wanted but never had!
      e. Date Expiry: Automatically expire access to your protected email.
      f. Requires: Policy Server 3.3.0.0 or higher.  
   2. Added a new ‚??Smart Sharing‚?? feature in Email Protector for Outlook on Windows, Mac and for Agentless Access in the browser. (#6727)
      a. When a user with Share permission forwards (or replies to) an email, the protected email message and attachments will be Shared (i.e. given permissions) with recipients automatically.
      b. If the Sharer has Edit or more permissions, the recipients will get Read and Edit permissions. If the Sharer has only Read permission, the recipients will also get Read permission only.
      c. End users can switch this off if not required.
      d. Requires Policy Server 3.5 or higher.
   3. The email attachment that contains the protected email body is now renamed to ‚??Email_.smail.html‚??. (#6722)
      a. Earlier the attachment was named as ‚??Email_body.smail.html‚??
      b. The new name will be more useful for the user when viewing multiple downloaded attachments in a folder, since it contains the subject line.
   4. Users no longer need a Protector license for Sharing (Redistributing) protected emails and documents.
      a. Earlier, every user needed a Protector license to use the ‚??Share‚?? permission.
      b.Removing this requirement will allow even external users to Share documents and emails more freely with those who really need access.
   5. Fixed the issue in Email Protector for Outlook 2013 where the protected email body was not displayed in certain rare cases. (#6778)
      a. Before the fix: If a protected email body was already open in the Outlook message pane and the user clicked on an email attachment, Outlook displayed the content in the preview pane. If the user now went back to the main email message pane, the protected email body was not displayed.
      b. If a protected email body was already open in the Outlook message pane and the user double-clicked on an email attachment, Outlook prompted the user to either Open or Cancel. If the user cancelled and went back to the protected email body, the content was not displayed in the main message pane.
      c. After the fix: In both these cases, the protected email body will now show as expected.
   6. Provided the capability to switch off the Protect Email Body feature for all users. (#6726)
      a. When switched off, the Protect Body checkbox will be disabled for all users of the Policy Server.
   7. Fixed the issue where the notification bar goes blank sometimes when resizing the message pane. (#6780)
      a. At the top of any protected email body, there is a notification bar with the line ‚??This is a protected email‚??.
      b. Before the fix: Sometimes when the user is viewed a protected email and the message pane is resized (i.e. by dragging the separator between the message pane and the email list) the notification bar went blank.
      c. After the fix: The notification bar is always displayed as expected.
   8. Minor UI enhancements in the Outlook menu (ribbon) for better aesthetic appeal. (#6728)
      a. Aligned the checkboxes for assigning permissions i.e. Read, Edit, Print etc.
      b. Modified the icon displayed on the main ‚??Seclore It‚?? button.
   9. Updated the Spanish language translations for all features up to this current version i.e. Desktop Client 3.6.0.0. (#6994)
   10. Other fixes. (#6779, #6782, #6783, #6900)

------------------------------
Seclore 3.7.4.0
Seclore Desktop Client 3.5.4.0
July 1, 2018

   1. Fixed the rare issue where Outlook would become unresponsive while forwarding an unprotected email thread containing multiple instances of the same attachment (e.g. email footers). (#7010)

------------------------------
Seclore 3.7.3.0
Seclore Desktop Client 3.5.3.0
June 1, 2018

   1. Added support for protecting documents with multibyte characters (e.g. Kanji) in their names. (#6712)
   2. Fixed the issue where protected pptx and xlsx documents did not get protected when the user‚??s cache location was a network folder. (#6861)
   3. Fixed the issue where protected Office documents opened in Protected View and their contents were not displayed. (#6812)
      a. From this release, Protected View will not affect Seclore-protected documents.
      b. Protected View settings for unprotected documents will remain unchanged.
   4. Fixed the rare issue where an error would occur while sending a protected email body if the sender was configured with Microsoft Exchange. (#6897)
   5. Known issues in this release:
      a. A protected Microsoft Office document located on the network - and opened from the ‚??Recent Documents‚?? list - opens in Protected View and its contents are not displayed (even after clicking ‚??Enable editing‚??).
      b. If an unprotected Excel document is opened from an untrusted location when a protected Excel document is already open, the Seclore permission badge is displayed on the unprotected document.
   6. Other fixes. (#6935)

------------------------------
Seclore 3.7.2.0
Seclore Desktop Client 3.5.2.0
May 20, 2018

   1. Other fixes. (#6921)

------------------------------
Seclore 3.7.1.0
Seclore Desktop Client 3.5.1.0
May 1, 2018

   1. Providing additional data from the agent to the Policy Server for generating the Agent Installation Report. (#6802)

------------------------------
Seclore 3.7.0.0
Seclore Desktop Client 3.5.0.0
Apr 16, 2018

   1. Launched the new Seclore Data Classification for improved document Classification and Auto Protection powered by Boldon James. (#6623)
      a. Users can classify documents from within MS Office applications: Word, Excel, PowerPoint.
      b. Classification can be made mandatory by adding a rule in the server configuration settings. 
      c. Once a document is classified, it can be protected automatically, by configuring a Seclore Policy mapped to the Classification label. 
      d. The Classification is updated in the document whenever it is saved. 
      e. The document gets protected only after it is closed. 
      f. If Classification is mandatory, the user cannot save the document until he/she classifies it.  
      g. Expected Behavior: Documents that were classified before the Seclore Auto Classification addon is deployed will be auto protected whenever they are opened and closed.   
      h. Expected Behavior: A user needs a Classification license to Classify documents and a Protector license for them to be automatically protected. Without a Protector license, documents will not be protected.    
   2. Added support for Adobe Acrobat Pro to access protected PDF documents with Advanced Protection controls. (#6586, #6687)
      a. Users can simply double-click on protected PDF files to open them with Acrobat Pro. 
      b. Requires: Windows 7, 8.1, 10 and Acrobat Pro XI or DC. 
      c. All Advanced Protection controls (WHO, WHAT, WHEN, WHERE) will be enforced including: Edit, Print, Screen Capture, Copy Data, Offline etc.  
      d. The Seclore permissions badge will display the current user‚??s permissions on the document.
      e. Expected behavior: The tabbed interface for viewing multiple documents in the same window will be disabled. Each document will open in a separate Acrobat window. 
      f. Expected behavior: Some features will be blocked for security purposes: Send via mail, Send and Track, Online printing, SharePoint based reviews, Online collaboration, accessing via any online service like Box, Dropbox, OneDrive etc. 
      g. Expected behavior: Copying data between two protected documents will not be available as of now, even though the user may have permission to do so.       
   3. Fixed the issue that occurs in rare cases when a user tries to unprotect the same document more than once at the same time. (#6368) 
      a. Before the fix: A user may Right-click > Unprotect a folder having multiple protected documents. 
      b. Before the operation completes, the same user may go to an individual document in that folder and Right-click > Unprotect it. 
      c. In certain rare cases, when multiple unprotect operations were in progress on the same document, it would lead to a conflict and loss of data. 
      d. After the fix: The agent ensures that there is no impact of multiple Unprotect operations on the same document.     
   4. Added support for ‚??Staat der Nederlanden Root CA ‚?? G3‚?? in the list of trusted root certificates for SSL communication between the Desktop Client and Policy Server. (#6751) 
   5. Fixed the issue introduced in the 3.4.1 release where only 1 upgrade patch was getting installed with each computer restart. (#6688)
      a. Before the fix: Up to version 3.4 of the Desktop Client, if multiple upgrade patches were available, only two patches were installed with each computer restart. 
      b. In release 3.4.1, only one patch was getting installed with each restart. 
      c. After the fix: Now up to four patches will be installed with each restart, as expected.     
   6. Fixed the rare issue that occurs in a very specific scenario when working with multiple protected and unprotected Excel documents and has a formula referencing multiple documents. (#6753)
      a. Before the fix: The issue occurs when a protected Excel document has a formula referencing two unprotected documents (D1, D2), another formula referencing another unprotected document (D3) and a formula referencing a protected document (D4) on which the user doesn‚??t have permission. 
      b. In this scenario, an error message was displayed and the file would not open.  
      c. This was due to a conflict with Excel when Seclore breaks the links to the referenced documents to ensure the security of the content. 
      d. After the fix: The document will now open after breaking the links appropriately, as expected.    
   7. Fixed the issue that occurs in certain cases when opening an unprotected ‚??xlsx‚?? documents in Excel 2016 from a Microsoft OneDrive folder. (#6609)
      a. Before the fix: When opening an unprotected ‚??xlsx‚?? document in Excel 2016 from a OneDrive folder, the user was seeing an error with the message: Error ‚??32‚?? reading file.
      b. The user had to click on ‚??OK‚?? button for the document to open in Excel. 
      c. After the fix: This error message is not displayed now and the document will directly open in Excel.   
   8. Other fixes. (#6621, #6768, #6804) 

------------------------------
Seclore 3.6.2.0
Seclore Desktop Client 3.4.2.0
Mar 16, 2018

   1. Extended the usability enhancements for Screen Capture control to Windows Server 2008 R2 as well. These were earlier released for Windows 7, 8, 8.1, 10 and Server 2012. (#6549)
      a. When a user doesn't have Screen Capture permission on a document, screenshots are blocked only in the specific application in which the document is open.
      b. E.g. If a user doesn't have Screen Capture permission on an open Word document, then screenshots are blocked on all other Word documents as well. In any other application like Excel or PowerPoint etc, screenshots will be allowed.
   2. Fixed a minor issue in the Seclore Text Editor when a file is saved without an extension. (#6561)
      a. Before the fix: If the user did not select an extension, the file would get saved without any extension.
      b. After the fix: If the user didn‚??t add an extension, the ‚??.txt‚?? extension would be automatically added.  
   3. Updated the Spanish language translations for all features up to Desktop Client 3.4.0.0. (#6596) 
   4. Other fixes. (#6349, #6412, #6464)

------------------------------
Seclore 3.6.1.0
Seclore Desktop Client 3.4.1.0
Feb 16, 2018

   1. Fixed the issue where Office documents could not be launched directly in Microsoft Office from Dropbox online ‚?? and subsequently no local protected document would open in Microsoft Office. (#6384)
      a. Now Office documents can be launched in Office successfully from Dropbox online. 
      b. Subsequently all local Office documents can also be opened normally from any location. 
   2. Fixed the rare issue where Excel files could not be opened after a computer restart. (#6385) 
      a. This issue occurred because Excel file associations would get affected upon restart.
      b. The Seclore Troubleshooter now runs automatically during shut down and disassociates file associations so that Excel formats (xlsx, xlsm, xlsb) are associated correctly upon restart.
   3. Other fixes. (#6219)

------------------------------
FileSecure 3.6.0.0
Seclore Desktop Client 3.4.0.0
Feb 1, 2018

   1. Significantly enhanced Email Protector for Outlook to improve the user experience. (#6286)
      a. Authorized recipients will now see a protected email body within the Outlook message window itself. 
      b. The protected body will also be displayed within the reading pane in the preview mode. 
      c. The recipient can reply or forward the email with inline (interleaved) comments that include the original email content.
      d. Recipients who don‚??t have access, can Request Access with one click from within the Outlook message window itself.   
      e. After sending a protected email, the sender can now track it by invoking the email from the Sent Items folder and clicking the Track button. 
      f. The Track screen displays all recipient activities on the protected body and attachments in the last 7 days. 
      g. Alongside the Track button is a Revoke button that allows the sender to revoke access from any of the recipients. 
      h. Once revoked, a recipient will not have access to either the protected email body or attachments for which the sender was the File Owner.   
      i. When protecting an email, the sender now has the option of setting an expiry date for the protected body and attachments.  
      j. Requires: Outlook 2013 or 2016. 
      k. Requires: Policy Server 3.3.0.0
   2. Expected Behavior for Email Protector: 
      a. The permissions selected when protecting an email i.e. Read, Edit, Print etc, will be enforced only on the attachments and not on the protected body. 
      b. The email body is protected with Basic Protection controls only, so authorized recipients will be allowed to edit, print and copy content out without any restrictions.  
      c. Older versions of the Desktop Client are not compatible with this version. An email body protected with this new version will not be accessible using an older version of the Desktop Client.  
   3. Other fixes. (#6316, #6317)

------------------------------
FileSecure 3.5.4.0
Seclore Desktop Client 3.3.6.0
Jan 16, 2018

   1. Fixed a very rare issue where copying an image out of a protected file doesn‚??t work as expected. This occurs only with a very specific combination of operations. (#6249)
   2. Other fixes. (#6290)

------------------------------
FileSecure 3.5.3.0
Seclore Desktop Client 3.3.5.0
Jan 16, 2018

   1. Fixed an issue in the Outlook Email Protector by enhancing the email ID validation check to include some more boundary conditions before sending a protected email. (#6328)

------------------------------
FileSecure 3.5.1.0
Seclore Desktop Client 3.3.4.0
Dec 16, 2017

   1. Added support for HTML wrapping of additional file formats. (#6169)
      a. Microsoft Office: docm, xlsm, xlsb, pptm
      b. Text: csv
      c. Images: bmp, png, jpg/jpeg/jpe/jfif, tif/tiff, gif
      d. OpenOffice: odt, ods, odp, odg, odf
   2. Improved the usability of the Screen Capture control on Windows 7 computers. (#6170)
      a.When a user doesn‚??t have Screen Capture permission on a document, screenshots are blocked only in the specific application in which the document is open.
      E.g. If a user doesn‚??t have Screen Capture permission on an open Word document, then screenshots are blocked on all other Word documents as well.In any other application like Excel or PowerPoint etc, screenshots will be allowed.
      b.This capability was earlier released for Windows 8 and higher in version 3.0 of the Desktop Client.
   3. Users will now have an additional Right-click menu option to convert protected files to HTML encoded format. (#6194)
      a. Additional option in the Right-click menu called ‚??Convert to Agentless format‚?? is now available.
      b. Anyone sharing protected files with external users can now ensure that external users have a seamless experience by automatically opening the file in the Seclore Online Editor (or Viewer).
      c. Formats supported: MS Office (docx, doc, docm, xlsx, xlsm, xlsb, xls, pptx, pptm, ppt), pdf, text (rtf, csv, txt), images (bmp, png, jpg/jpeg/jpe/jfif, tif/tiff, gif) and OpenOffice (odt, ods, odp, odg, odf).
   4. Enhanced user experience by simplifying the Right-click menu options for a protected file. (#6195)
      a. Renamed ‚??View File Details‚?? to ‚??Track and Manage‚??, which invokes a condensed version of the file dashboard for the File Owner.
      b. Dropped rarely used options: ‚??View Activity Log‚??, ‚??Activate file‚??, ‚??Inactivate file‚??, ‚??Transfer Ownership‚?? and ‚??Activity As Different User‚??. 
      c. Also dropped ‚??Change Permissions‚?? menu option since it is already available in the Track and Manage screen for the File Owner and Sharer.
   5. Fixed a compatibility issue with the FireEye Endpoint agent on Windows 7 OS. (#5808)
   6. Updated the Spanish language translations for all features up to Desktop Client version 3.3.3. (#6251)
   7. Other fixes. (#6171)

------------------------------
FileSecure 3.4.1.0
Seclore Desktop Client 3.3.3.0
Nov 16, 2017

   1. Fixed the issue where the Chrome browser was not working as expected on Windows 7 if McAfee DLP Endpoint was installed (#5837)
      a. Before the fix: If the Seclore Desktop Client and McAfee DLP Endpoint were installed on the same computer, the Chrome browser window would never be displayed.
      b. After the fix: The Chrome browser window displays as expected.  
   2. Fixed the issue in the Spanish language pack where the Spanish version of the HTML Wrapper was not being used when protecting a file. (#6027)
      a. Before the fix: The English version of the HTML Wrapper was being used even when the agent locale was set to Spanish. 
      b. After the fix: The Spanish version of the HTML Wrapper is used if the agent locale is Spanish. 
   3. Fixed the issue introduced in the upcoming MS Office update version 1710, where protected Excel documents are not opening as expected. (#6104)
      a. Before the fix: When the Excel application is not running (i.e. no Excel document is open), if the user double-clicks on a protected Excel document, an error message was displayed.  
      b. If the Excel application was already running or if another Excel document was already open, no such error is displayed, and the document opens as usual.    
      c. After the fix: Protected Excel documents open as usual even if Excel is not running. 
   4. Other fixes.(#5926, #5933)
   
------------------------------
FileSecure 3.3.2.0
Seclore Desktop Client 3.3.2.0
Oct 16, 2017

   1. Fixed the issue where OpenOffice displayed a prompt for file recovery in certain cases even when it was not needed. (#3373, #5887)
      a. Before the fix: When certain types of OpenOffice files were opened, then closed and re-opened, the file recovery prompt was displayed even though it was not needed.
      b. After the fix: File recovery will only be prompted when really needed.
   2. Fixed the issue where the user was not able to scroll within a protected Excel document immediately after opening it. (#5898)
      a. Before the fix: Immediately after opening a protected document, the user was unable to scroll through it. He had to click inside the document at least once to get scrolling to work.
      b. After the fix: The scrolling feature now works immediately after the document is opened.
   3. Fixed the issue introduced in the latest MS Office update Version 1708, where protected Excel documents were not opening as expected. (#5905)
      a. Before the fix: When the Excel application is not running (i.e. no Excel document is open), if the user double-clicks on a protected Excel document, an error message was displayed.
      b. If the Excel application was already running or if another Excel document was already open, no such error is displayed, and the document opens as usual.
      c. After the fix: Protected Excel documents open as usual even if Excel is not running.
   4. Fixed the issue where Outlook was shutting down unexpectedly when user clicked the Next or Previous arrow buttons in the message reading pane. (#5921)
      a. Before the fix: In the message reading pane when using the Up or Down arrows to navigate to the Next or Previous message, sometimes Outlook shut down unexpectedly.
      b. After the fix: Using Next or Previous arrows works fine.
   5. Other fixes. (#5907, #5923)

------------------------------
FileSecure 3.3.1.0
Seclore Desktop Client 3.3.1.0
Sep 26, 2017

   1. Fixed the issue in the Seclore Email Protector for Outlook where attachments were getting HTML wrapped even when the HTML wrapping feature was not supported or was disabled in the Policy Server. (#5908)
      a. Before the fix: When user sent an email from Outlook, attachments would get HTML wrapped even when the HTML wrapping feature was not supported or was disabled in the Policy Server.   
      b. After the fix: The email attachments get HTML wrapped only if the HTML wrapping feature is enabled in the Policy Server.

------------------------------
FileSecure 3.3.0.0
Seclore Desktop Client 3.3.0.0
Sep 16, 2017

   1. Enhanced the Seclore HTML wrapping process to include internal users too. (#5857)
       a. Before this release, HTML wrapping used to occur only if at least one email recipient was external to the organization
       b. From this release onwards, HTML wrapping will always occur ‚?? regardless of whether the recipient(s) are internal or external. 
   2. Fixed the issue in the Seclore Email Protector for Outlook where attachments were not getting protected in certain rare cases. (#5833)
       a. Before the fix: At times, if the receiver forwarded an email and protected it, the attachments would not get protected. This was happening when the original email was not sent from Outlook.   
       b. After the fix: The forwarded email attachments get protected as expected.   
   3. Fixed the issue in the Seclore Email Protector for Outlook where clicking ‚??OK‚?? in an ‚??Unexpected Error‚?? dialog box would actually send the email (in its current form - without rectifying the error) instead of going back to the compose window. (#5858)
   4. Fixed the issue where Autologin did not work and users would need to log in frequently (e.g. after computer restart) ‚?? if the Policy Server ID contained the ‚??&‚?? character. (#5860)
   5. Fixed the issue where two Seclore It! buttons were displayed in the Outlook ribbon when both the Desktop Client and Lite for Windows were installed. (#5564)
   6. Fixed the issue in the Seclore Email Protector where user creation failed for users whose email IDs contained single quotes. (#5550)
       a. This issue primarily occurred because Outlook added quotes to the email ID when users where selected from the suggestion list. It has now been fixed. 
   7. Fixed the issue in the Seclore Email Protector where the email body was not sent as part of the protected email when: (#5846)
       a. The email body format was HTML.
       b. The body contained only embedded objects and no written content.
       c. The ‚??Protect Body‚?? option was checked. 
   8. Fixed the issue in the Seclore Email Protector where embedded objects in the email body were also sent unprotected as separate attachments (as well as in the protected document containing the email body) when: (#5847)
       a. The email body format was RTF.
       b. The body contained embedded objects (except either a shape or a blank table only) and some written content.
       c. The ‚??Protect Body‚?? option was checked.
       d. The recipient was viewing the email in Gmail in the browser. 
   9. Fixed the issue in the Seclore Email Protector where only a ‚??winmail.dat‚?? file was sent as an attachment, and everything else was dropped, when: (#5877)
       a. The email body format was RTF.
       b. The body contained only embedded objects with NO written content.
       c. The ‚??Protect Body‚?? option was checked.
       d. The recipient was viewing the email in Gmail in the browser.
   10. Other issues. (#5874, #5859)

------------------------------
FileSecure 3.2.0.0
Seclore Desktop Client 3.2.0.0
Sep 1, 2017

   1. Enhanced the Seclore Image Viewer by improving the print quality for high resolution TIFF images on Windows 7, 8, 8.1 and 10. (#5829)
       a. Before this enhancement: For certain high definition TIFF images the print quality was not good enough. This was due to a limitation of the image rendering engine.   
       b. After this enhancement: Images are now rendered using the Windows Photo Viewer engine, which provides significantly better print quality for even high resolution TIFF images. 
       c. Requires: Windows 7, 8, 8.1 and 10. For Windows XP the earlier rendering engine will continue to be used.   
   2. Fixed the issue in the Seclore Email Protector for Outlook where attachments were not getting protected in certain rare cases. (#5833)
       a. Before the fix: At times, if the receiver forwarded an email and protected it, the attachments would not get protected. This was happening when the original email was not sent from Outlook.   
       b. After the fix: The forwarded email attachments get protected as expected.

------------------------------
FileSecure 3.1.0.0
Seclore Desktop Client 3.1.0.0
Aug 16, 2017

   1. Improved usability of the Seclore Email Protector to show the Seclore options in the Outlook ribbon only when required. (#5619)
       a. The options displayed next to the Seclore It! button in the Outlook ribbon will now be hidden to start with. 
       b. These options will be visible only when the user clicks ‚??Seclore It!‚??. Clicking ‚??Seclore It!‚?? again will hide them once again.
   2. Enhanced the usability and intuitiveness of the auto-forward feature in the Seclore Email Protector for Outlook. (#5619)
       a. Earlier behavior: When a protected document was attached to an email and the sender had Share (Redistribute) permission (or was the File Owner), the Seclore add-in would automatically Share the protected document to the email recipients. The recipients would be given Read and Edit permissions automatically and this would happen in the background without the user being informed about it.  
       b. With this change, when a protected document is attached to an email in Outlook, the document will NOT be automatically Shared (Redistributed). 
       c. The user will see an alert below the list of attachments telling him to click the ‚??Seclore It!‚?? button to Share the protected attachments to the email recipients. 
       d. The message is displayed in a yellow-colored message bar, which is typically used in MS Office to ensure the user‚??s task flow is not obstructed. 
       e. The protected attachments will be shared only if the user intentionally clicks on ‚??Seclore It!‚?? and chooses the permissions that he wants to give the email recipients.   
   3. Fixed the issue where an Outlook email saved on the local computer as a .msg file was not opening in certain cases. (#5634)
       a. Before this fix: If the .msg file was opened once in Outlook, then closed and opened again, it would not open. The file would open only when Outlook was restarted.
       b. After this fix: The .msg file always opens properly.   
   4. Added a new feature called Enhanced Basic Protection to improve the user experience for protected SOLIDWORKS design assemblies. (#5693, #5694, #5695)
       a. SOLIDWORKS design assemblies that have interlinked part files can be protected in Hot Folder Server with Seclore‚??s Basic Protection i.e. Who, Where and When controls only. 
       b. Before this fix: When the user opened the main assembly file, the interlinked part files would not open automatically. The user had to manually open every part file to see the complete design assembly in one view.
       c. After this change, when the user opens the assembly file, the interlinked part files will open automatically in the background. 
       d. These files will not be appended with ‚??.seclore‚?? and will retain their original extension. 
       e. Formats supported: SOLIDWORKS assembly (.SLDASM), part (.SLDPRT) and drawing (.SLDDRW) 
       f. Applications supported: SOLIDWORKS 2016 and 2017      
   5. Other fixes. (#5684, #5707, #5732)

------------------------------
FileSecure 3.0.2.0
Seclore Desktop Client 3.0.1.0
Aug 1, 2017

   1. Fixed the issue where the Outlook Summary page was not displaying summarized information as expected. (#5689)
       a. Observation: When a user clicks on the top-most link in the folder list on the left pane, a summary page is displayed. It appears like a dashboard with high-level numbers for calendar items, tasks and messages. These numbers were not displayed properly due to a conflict with the Seclore Email Protector add-in.
       b. After this fix, the information on the summary page is displayed properly.
   2. Fixed the issue in Adobe Reader 11 and DC, where users with Read-only permission were not able to search (using Ctrl + F) in protected PDF files. (#5635)
       a. Observation: Consider a user has Read-only permission on a protected file. If he opens the file and uses the search feature once, then closes and re-opens it again, he was unable to search again.
       b. After this fix, users with Read-only permission can always search in protected PDF files.
   3. Improved the usability of certain scenarios for linked protected Excel files. (#5562)
       a. Observation: Consider the scenario where an Excel file contains a formula that refers to another Excel file and both are protected. When opening the main file, the user gets a Seclore prompt asking him to choose whether to update the links or not. If the user chooses ‚??Yes‚?? and has valid access (i.e. View and Copy Data permissions) on the linked file, the data will get properly updated in the main file. If he doesn‚??t have access, the links will be broken and the file will open in read-only mode.
       b. Before this fix: If the user chooses not to update the links, Seclore was forcibly breaking the links and opening the file in read-only mode for security reasons.
       c. After this fix: If the user chooses not to update the links, Seclore will validate his access (View and Copy Data) on the linked file. If he has access, the links will be preserved and the file will be editable, without any compromise in security.
   4. Enhanced the Screen Capture control to block screenshots only for the specific document on which the user doesn‚??t have Screen Capture permission. (#5750)
       a. Before the fix: If the user had a protected file open on which he doesn‚??t have Screen Capture permission, he couldn‚??t take screenshots of any other file ‚?? even unprotected files.
       b. After the fix: The Screen Capture is blocked only for the file on which he doesn‚??t have Screen Capture permission. On any other file, it works fine.
   5. Other fixes. (#5746, #5747, #5748, #5749, #5752, #5753, #5772)

------------------------------
FileSecure 3.0.0.0
Seclore Desktop Client 3.0.0.0
Jun 16, 2017

   1. All new Seclore badge displayed on a protected file if it is open in a native Microsoft Office app or Adobe Reader. (#5510, #5543)
       a. The badge appears in the lower right corner of the window and clicking on it displays the user‚??s permissions and the name of the File Owner.
   2. Added a new summary screen that is displayed when a user right clicks on a protected file and chooses ‚??View File Details‚??. (#5574)
       a. The File Owner will see a short Activity Summary with the most frequent users.
       b. Authorized recipients will see their own file permissions on that file.
       c. Unauthorized users will be shown a link to request access from the File Owner.   
   3. Added the feature to automatically login to the Policy Server when the user is already logged in to the local agent. (#5513, #5572)
       a. Supported in Internet Explorer 9, 10, 11, Chrome and Firefox on Windows 7, 8, 8.1, 10.
       b. Expected Behavior: ‚??InPrivate‚?? browsing mode in Internet Explorer or ‚??incognito‚?? mode in Chrome is not supported. 
       c. User will always be prompted to login if the browser is not supported.  
   4. Improved usability of the Screen Capture control by blocking screen shots only if the document on which it is blocked is visible to the user. (#5512, #5537)
       a. Screen capture will not be blocked.
       b. Screen Capture will be allowed as long as the document on which it needs to be blocked is minimized or hidden behind another window. 
       c. This will be supported in Windows 8, 8.1, 10 and Server 2012. 
       d. On older Windows versions, screen shots will be blocked if any open file has Screen Capture blocked regardless of whether it is minimized or hidden.
   5. Fixed the issues observed in Office 2016 after installing the latest Office update released by Microsoft on June 13th, 2017. 
       a. Observation 1: Compose an email in Outlook with an unprotected attachment, click ‚??Seclore It!‚?? and send the email. After clicking the ‚??Send‚?? button, Outlook was shutting down unexpectedly. (#5687)
       b. Observation 2: When one file is already open in Excel, try to open another file. If any of these files is Seclore protected, Excel was shutting down unexpectedly. (#5685) 
       c. Observation 3: Attempt to open a protected file in PowerPoint. The application was shutting down unexpectedly. (#5686)
       d. The latest Microsoft Office patch released on June 13th, 2017 was conflicting with the Seclore add-ins for Outlook, Excel and PowerPoint in Office 2016. 
       e. Versions affected: Microsoft Office 1705 - Build 8201.2102 (16.0.8201.2102) and 1705 - Build 8201.2075 (16.0.8201.2075).
       f. This Seclore update resolves these conflicts and the applications behave as expected.
   6. Other fixes. (#5573)

------------------------------
FileSecure 2.109.2.0
Seclore Desktop Client 2.57.2.0
Jun 1, 2017

   1. Fixed the issue in Outlook Email Protector where email IDs containing single quotes (‚??) were not getting registered as new users. (#5561)
   2. Fixed the intermittent issue that slowed down the file opening process in certain network environments due to delay in fetching the Windows domain name. (#5576)
   3. Other fixes. (#5530, #5558, #5566, #5600)

------------------------------
FileSecure 2.109.1.0
Seclore Desktop Client 2.57.1.0
May 23, 2017

   1. Enhancements for providing a much simpler new user onboarding experience with the next version of the Policy Server. (#5483)
   2. Fixed the issue where the Seclore Desktop Client was conflicting with some undisclosed changes made by Microsoft in Windows 10 release 1703 (also called Creators Update). (#5547)
   3. Fixed the issue where some hyperlinks were not opening in the browser as expected. (#5582)
   4. Other fixes. (#5524, #5538)

------------------------------
FileSecure 2.108.2.0
Seclore Desktop Client 2.56.5.0
Apr 16, 2017

   1. Fixed the issue where Autodesk Revit would shut down if a protected file was opened from Windows Explorer (or from inside Revit) when it was already open as a linked file in another protected file. (#5488)
   2. Other fixes. (#5422, #5431, #5486)

------------------------------
FileSecure 2.108.1.0
Seclore Desktop Client 2.56.4.0
Apr 1, 2017

   1. Fixed the issue where Microsoft Excel stops responding when the data source of a Pivot table is changed in a protected document. (#5373)
   2. Other fixes. (#5422, #5427, #5521)
   
------------------------------
FileSecure 2.106.3.0
Seclore Desktop Client 2.56.3.0
Mar 1, 2017

   1. Added a new tool called ‚??Seclore Issue Reporting‚?? for capturing device and application information to help in faster troubleshooting. (#5347) 
   2. Fixed the issue where Microsoft Word shuts down if a protected file is saved in a folder where a file with .url extension is already present. (#5339)
   3. Other fixes. (#5183, #5215, #5348) 

------------------------------
FileSecure 2.106.2.0
Seclore Desktop Client 2.56.2.0
Feb 23, 2017

   1. Added support for Autodesk DWG TrueView 2017. (#5173)
   2. Fixed the rare issue where unprotected Excel files with ‚??Share Workbook‚?? feature enabled, were opening in read-only mode for some users. (#5129)
   3. Fixed the issue where protected PDF files were not opening on some Windows 10 computers. (#5219)
   4. Fixed the issue where opening and scrolling protected files on certain high definition displays affects performance. (#5128)
   5. Other fixes. (#5077, #5108, #5174, #5181, #5213, #5220, #5221, #5403)

------------------------------
FileSecure 2.105.0.0
Seclore Desktop Client 2.55.0.0
Jan 15, 2017

   Features:
   
   1. Enhanced email collaboration with protected files and made it more seamless and trouble free (#5144):
       a. Automatic Forwarding (Redistribution) of protected attachments to the email recipients, whenever they are sent from Outlook. 
       b. The sender should have Forward permission on the protected attachments. 
       c. This works automatically in the background without the need to click on the ‚??Seclore It!‚?? button. 
       d. The ‚??Seclore It!‚?? button can still be used to protect other unprotected attachments.   
       e. Any unregistered users in the recipient list will get registered in Seclore automatically. 
   2. Updated the icon overlay on protected file icons to display the new Seclore red lock image. (#5137)

   Bug Fixes: 
   
   1. Fixed the issue where the Seclore icon overlay was displayed as a black box or not displayed at all on high-DPI computers. (#4885, #4887)
   2. Fixed the issue where the Seclore context menu icons were displayed in a smaller size on high-DPI computers. (#4886)
   3. Fixed the rare issue where protected image files would not open in Microsoft Paint. (#5134)
   4. Fixed the rare issue where files stored on the network on which the user had only the ‚??View‚?? permission would not open in some applications. (#4754, #5158)
   5. Other fixes. (#5115, #5123, #5135, #5136, #5142)

------------------------------
FileSecure 2.103.0.0
Seclore Desktop Client 2.54.0.0
Dec 15, 2016

   Features: 
   
    1. One Time Login and automatic user authentication. (#5051)
        a. Users need to log in just once after the Desktop Client is installed.
        b. Once logged in, the user stays logged in even after a system restart.
        c. No change in behaviour for Windows AD users who get authenticated via Single Sign-On.
    2. Strengthened internal product security for client-server communication with an additional encryption layer within the SSL tunnel. (#5049)
  
   Bug Fixes: 

    1. Other fixes. (#5029, #5106) 

------------------------------
FileSecure 2.102.0.0
FileSecure Desktop Client 2.53.0.0
Dec 1, 2016

   Features: 
   
    1. Added support for opening protected files with .rh and .vds extensions in SAP 3D Visual Enterprise Viewer (versions 8 and 9) on Windows 7, 8, 8.1 and 10. (#5017)

   Bug Fixes:
   
    1. Issue: Google‚??s login page appeared distorted. (#5027)
       Resolution: Fixed this issue. 
    2. Issue: In certain rare cases, protected CSV files did not open in Seclore Desktop Client when opened directly from Microsoft Outlook. (#4929)
       Resolution: Fixed this issue. 
    3. Issue: When a protected PDF file was opened and the ‚??Show Access Permissions of document‚?? option in Seclore Desktop Client (in Settings > Manage Preferences) was kept unchecked, the Adobe Reader window appeared greyed out. (#4969)
       Resolution: Fixed this issue. 
    4. Other fixes. (#5067)

------------------------------
FileSecure 2.101.1.0
FileSecure Desktop Client 2.52.4.0
Nov 15, 2016

   Enhancement:
   
    1. Updated the End User License Agreement (EULA) in Spanish, German and Russian. (#5006)

   Bug Fixes:
   
    1. Issue: In certain rare cases, Adobe Reader was displaying the license agreement every time a PDF file was opened on a Windows 10 device. (#5005)
       Resolution: Fixed this issue. 
    2. Other fixes: (#4988, #5002, #5003, #5004)  
   
------------------------------
FileSecure 2.100.0.0
FileSecure Desktop Client 2.52.3.0
Oct 1, 2016

   Bug Fix: 

    1. Issue: When an unprotected file in SharePoint was directly opened in Office 2013 or 2016, it was displaying the ‚??Save As‚?? prompt after editing and saving. (#4979)
       Resolution: Fixed this issue.
   
------------------------------
FileSecure 2.99.0.0
FileSecure Desktop Client 2.52.2.0
Sep 15, 2016

   Bug Fixes: 
   
    1. Issue: Microsoft Outlook would crash when a user clicked on ‚??Add Note‚??. (#4952)
       Resolution: Fixed this issue. 
    2. Issue: Microsoft Outlook prompted to disable the Seclore Email Protector add-in when it took a long time to load. (#4953)
       Resolution: Fixed this issue.
    3. Issue: In certain rare cases on certain computers, the user was not authenticated by pressing Enter after typing in the login ID and password. (#4948)
       Resolution: Fixed this issue.
    4. Other fixes: (#4959, #4955, #4910, #4954)

------------------------------
FileSecure 2.98.0.0
FileSecure Desktop Client 2.52.1.0
Sep 1, 2016

   Bug Fix: 

    1. Issue: In certain rare cases, cell referencing in Microsoft Excel did not work as expected. (#4901)
       Resolution: Fixed this issue.

------------------------------
FileSecure 2.97.0.0
FileSecure Desktop Client 2.52.0.0
Aug 15, 2016

   Features: 
   
    1. Microsoft Office 2007 is now supported on Windows 10. (#4837)
    2. The Seclore event framework that enables Auto Classification is now compatible with Windows 10. (#4838)
    3. The ‚??Share your details‚?? prompt (displayed when the first protected file was opened on a computer) has now been dropped. The same user consent is now included in the license agreement. (#4868)

   Bug Fixes: 

    1. Issue: In certain cases, unprotected files could not be edited and saved in Adobe Acrobat Pro. (#4654)
       Resolution: Fixed this issue.
    2. Issue: If the Classification description was more than 1000 characters, Right-click > ‚??Seclore It!‚?? did not work as expected. (#4794)
       Resolution: Fixed this issue.
    3. Issue: In certain rare cases, some other applications were conflicting with the Seclore Desktop Client and not functioning as expected. (#4839, #4840)
       Resolution: Fixed this issue. 
    4. Issue: In certain rare cases, when a protected file on a network folder was opened and edited, it could not be saved back in the same folder. (#4842, #4843)
       Resolution: Fixed this issue. 
    5. Issue: When using Citrix XenApp virtualization, protected and unprotected PDF files were not opening as expected when both Adobe Acrobat Reader and Pro were installed on the same computer. (#4844)
       Resolution: Fixed this issue. Protected PDF files will open in Adobe Acrobat Reader and unprotected files will open in Adobe Acrobat Pro.   
    6. Issue: On certain high definition displays, some application screens were not displayed properly. (#4847)
       Resolution: Fixed this issue. 
    7. Other fixes: (#4845, #4846, #4863) 

------------------------------
FileSecure 2.94.0.0
FileSecure Desktop Client 2.51.0.0
Jun 15, 2016

   Bug Fixes: 

    1. Issue: Conflict with the Desktop Client event framework and Adobe Reader DC. (#4567)
       Resolution: Fixed this issue.  
    2. Issue: Since Jan-2016, Windows 8, 8.1 and 10 only trust installers with SHA-256 digital signatures, and Windows 7 and XP only recognize SHA-1 signatures. The same Desktop Client installer was not compatible with all supported Windows versions. (#4592)
       Resolution: The installer is now digitally signed with both SHA-1 and SHA-256 to be compatible with all supported Windows versions. 
    3. Other fixes: #4595, #4445, #4599, #4603, #4604

------------------------------
FileSecure 2.93.0.0
FileSecure Desktop Client 2.50.1.0
May 31, 2016

   Bug Fix:

   1. Issue: In Autodesk Revit 2014, closing a protected file takes a long time and the application appears to get hanged. (#4698)
      Resolution: Fixed this issue.  

------------------------------
FileSecure 2.91.0.0
FileSecure Desktop Client 2.50.0.0
Apr 15, 2016

   Features: 
   
    1. Enhanced Seclore Email Protector for Outlook with a revamped UI and a new permission.
        a. Improved usability of the permission options by replacing buttons with checkboxes. (#4531)
        b. Added a new permission called 'Forward' that gives recipients 'Share' permissions on the email body (if protected) and protected attachments. (#4530)
        c. Enhanced the user experience for first time users with a message illustrating the capabilities of Email Protector and how it can be used. (#4509)
  
   Bug Fixes: 

    1. Issue: In certain rare cases, un-installing and re-installing the Desktop Client did not function properly. (#4568)
       Resolution: Fixed this issue.
    2. Issue: Issue: In certain rare cases, UI buttons which should be disabled only for protected files were disabled for unprotected PowerPoint files too. (#4459)
       Resolution: Fixed this issue.
    3. Other fixes: #4520, #4521, #4522, #4523, #4526, #4529, #4532

------------------------------
FileSecure 2.89.0.0
FileSecure Desktop Client 2.49.1.0
Mar 3, 2016

   Bug Fixes: 

    1. Issue: Print Screen Monitor service does not start on machine restart in certain rare cases. (#4450)
       Resolution: Fixed this issue. 
    2. Issue: In certain rare cases, when the user tries to close the Excel application (with the ‚??X‚?? button) an invalid message was displayed: ‚??Please close all protected files one by one‚??, even though only 1 file was open. (#4513)
       Resolution: Fixed this issue.
    3. Issue: If a protected file‚??s extension is changed to an unsupported extension that doesn‚??t have an associated application, the ‚??Open with‚?? dialog was not working as expected. (#4511)
       Resolution: Fixed this issue. The ‚??Open with‚?? dialog now works as expected.
    4. Issue: If an unprotected file of a Seclore standard supported format doesn‚??t have an associated application, the ‚??Open with‚?? dialog was not working as expected. (#4510)
       Resolution: Fixed this issue. The ‚??Open with‚?? dialog now works as expected.
    5. Issue: In certain rare cases, a very large log file was getting generated when registry changes were frequently taking place for a particular registry key. (#4515) 
       Resolution: Fixed this issue.
    6. Issue: In the previous release of the Desktop Client, when unprotecting more than 1 file, the progress bar was getting hidden behind the existing Windows. (#4458)
       Resolution: Fixed this issue.
    7. Issue: Minor UI fix on the File Protector error message display page. (#4465) 
       Resolution: Fixed this issue.
    8. Issue: In certain rare cases the ‚??Detect and Repair‚?? command was not working in case the Email Protector library was missing. (#4487)
       Resolution: Fixed this issue. 
    9. Other fixes: #4516

------------------------------
FileSecure 2.88.0.0
FileSecure Desktop Client 2.49.0.0
Feb 15, 2016

   Features: 
   
    1. Support for 32-bit versions of Windows 8, 8.1 and 10. (#4404)
    2. Added new APIs for desktop application integration. (#4430)
    3. Updated the Spanish language pack. (#4476) 

   Bug Fixes: 

    1. Issue: In certain rare cases, when saving a large unprotected Excel file on the network, a false error was displayed: ‚??Someone else is working on the file‚??, even though no one was working on it. (#4451)
       Resolution: The message will not be displayed. 
    2. Issue: In certain rare cases, the Email Protector was not able to resolve email addresses from Microsoft Exchange. (#4422)
       Resolution: Fixed this issue. 
    3. Issue: Outlook 2007 or 2016 would shut down when an email in Rich Text format with an embedded object and attachment was protected with Email Protector. (#4472) 
       Resolution: The user will be prompted to convert the email to HTML format. 
    4. Issue: Using Email Protector was causing Outlook to shut down in certain rare cases when it was not able to find an email address for a local contact group. (#4473)
       Resolution: Fixed this issue. 
    5. Issue: In Seclore Email Protector, when a blank email is sent in plain text format with message protection enabled, the recipient gets a misleading email saying that the main message is protected and attached. However there is no such attachment. This happens in Outlook 2013 and 2016 only. (#4474) 
       Resolution: Fixed this issue. 

   Expected Behavior:
   
    1. The following is not currently supported on Windows 8 and 8.1: 
        a. Microsoft Office 2003 
        b. Adobe Reader 8.x and 9.x 
        c. Open Office 3.1 and earlier  
        d. PowerPoint Viewer and Visio Viewer
        e. Opening protected AutoCAD files (DWG and DXF) 
    2. The following is not currently supported on Windows 10: 
        a. Microsoft Office 2003 and 2007 
        b. Adobe Reader 8.x, 9.x and 10.x 
        c. Open Office 2.x and 3.x 
        d. Seclore Event Framework and Auto Classification
        e. PowerPoint Viewer and Visio Viewer
        f. Opening protected AutoCAD files (DWG and DXF)
    3. In rare cases Microsoft Office applications may hang when trying to save file changes due to the Windows Search service running in the background. This is a Windows issue and may happen even without the Desktop Client installed.  

------------------------------
FileSecure 2.87.0.0
FileSecure Desktop Client 2.48.0.0
Jan 31, 2016

   Features: 

    1. All new File Protector feature for the Seclore Desktop Client. (#4405) 
        a. A simple and intuitive interface for selecting users and assigning permissions to them: Read, Edit, Print and Full Control
        b. Allows new users to be given access to a file by just entering their email addresses
        c. Automatic registration and approval for new users along with file protection
        d. Allows user-specific permissions in addition to Policy-based permissions to be defined on the same file 
        e. The Right-click menu option to protect a file is now called 'Seclore It!' 
        f. Requires Policy Server 2.44.0.0 or higher
    2. Enabled the new File Permissions screen to be displayed from within the Seclore Desktop Client. (#4405) 
        a. Invoke this screen for a file using Right-click >> Advanced >> Change Permissions
        b. Requires Policy Server 2.46.0.0 or higher

   Bug Fixes: 

    1. Issue: Microsoft PowerPoint 2007 or later on Windows 8 or later shuts down if a user attempts to Insert >> Video or Screen Recording. (#4388, #4381)
       Resolution: Fixed this for unprotected files and disabled these buttons for protected files. 
    2. Issue: Adding a stamp in a protected PDF file was disabled in Adobe Reader XI onwards. (#4389)
       Resolution: Stamps can now be used in protected files. 
    3. Issue: Adobe Reader XI or later would shut down when adding a stamp to favourites with a protected file open. (#4270)
       Resolution: Fixed this issue.
    4. Issue: Unprotected PDF and Image files would not open in Windows 8 and above if not associated with any application. (#4425) 
       Resolution: Fixed this issue.
    5. Other fixes: #4423, #4424   

   Expected Behavior:
   
    1. In PowerPoint 2007 or later on Windows 8 or later, the option to Insert >> Video or Screen Recording is not available when a protected file is open.
    2. When a user has a protected file open in Adobe Reader and then attempts to open another unprotected file using either drag and drop or the File >> Open menu, the unprotected file will be opened in read-only mode. If the user edits the unprotected file, he will be prompted to ‚??Save As‚?? with a new file name or location.
    3. In some rare cases Microsoft PowerPoint 2007 or later on Windows 8 or later shuts down when using Screen Recording in an unprotected file if there is another protected file open.
 
------------------------------
FileSecure 2.85.0.0
FileSecure Desktop Client 2.47.0.0
Jan 15, 2016

   Feature:

    1. All new Request Access module that allows users to request for access on a file. (#4387)
    2. Automatic registration of new users along with the access request.
    3. Real-time email notifications sent to the File Owner with the requester‚??s details and comments.
    4. One-click Approval or Decline options provided within the email notification itself.
    5. Easier and dynamic permission assignment even after the information is shared.
    6. Requires Policy Server 2.47.0.0 or higher.

   Bug Fix:

   1.  In McAfee DLP 9.3 a specific minor release version was incompatible with the Seclore Desktop Client. (#4406) 
       Resolution: The Seclore Desktop Client was changed to take care of this in all release versions of McAfee DLP 9.3.

------------------------------
FileSecure 2.84.0.0
FileSecure Desktop Client 2.46.0.0
Dec 4, 2015

   Feature:
   
   1. Support for MS Office 2016 32-bit and 64-bit. (#4283) 

   Bug Fixes:

   1. Issue: FileSecure red lock icon was not getting displayed on files synced to Box. (#4341)
      Resolution: Desktop Client has been changed to take care of this issue.
   2. Other fixes. #4293, #4333, #4348
   
   Known Issues / Limitations:

   1. A PPT file that is created in a particular version of PowerPoint and opened in a newer version opens in read-only mode. This only happens when the file is opened from a network shared folder. It works fine if the file is opened from the local computer or saved once and reopened. 
      E.g. File created in PowerPoint 2007 and opened in PowerPoint 2016 opens in read-only mode from a network shared folder. 
   
------------------------------
FileSecure 2.82.0.0
FileSecure Desktop Client 2.45.0.0
Nov 5, 2015

   Feature:

   1. Support for Basic Protection of ANY file format in the enterprise. (#4281, #4282)
       a. Enforcing Basic Protection controls ‚?? Who, When and Where for any file format.
       b. Seamless end user experience by enabling ‚??double-click to open‚?? any file in any application.

------------------------------
FileSecure 2.81.1.0
FileSecure Desktop Client 2.44.2.0
Oct 21, 2015

   Feature:

   1. Support for e-mail message protection along with attachments in Microsoft Outlook. (#4225)
       a. All types of e-mail messages are supported.
       b. After protection, e-mail message is sent as an attachment.
       c. The file is named as e-mail's subject prefixed with 'Message_'.
       d. Available in Microsoft Outlook 2007 (32-bit), Microsoft Outlook 2010 (32-bit and 64-bit) and Microsoft Outlook 2013 (32-bit and 64-bit).

------------------------------
FileSecure 2.81.0.0
FileSecure Desktop Client 2.44.1.0
Oct 10, 2015

   Bug Fix:

   1. Issue: At times, opening of protected files in offline mode take longer time. (#4251)
      Resolution: Desktop Client has been changed to take care of this issue.

------------------------------
FileSecure 2.80.0.0
FileSecure Desktop Client 2.44.0.0
Sept 15, 2015

   Features:
   
   1. Support for Windows 10 64-bit. (#3775)  
   2. Support for Adobe Reader DC on all supported versions of Windows. (#4018)
   3. Mechanism to unpackage and repackage FileSecure Offline Package files in silent mode. (#4138)
   4. Improved look and feel of the FileSecure Desktop Client Installer. (#4137)
   
   Bug Fixes:

   1. Issue: Desktop Client tray consumes large amount of system memory if kept running for long duration. (#4135)
      Resolution: Desktop Client has been changed to take care of this issue.
   2. Other fixes: #4136
   
   Known Issues / Limitations:

   1. Windows 10 32-bit version is NOT supported in this release. 
   2. Following modules are currently not supported on Windows 10 -
      a. FileSecure Event Framework: Module that throws events whenever user closes a file, which is used in features like Automatic Classification. This means that Automatic Classification which prompts user to classify file on close is NOT supported in this release. 
      b. DWG / DXF Viewer: DWG / DXF Viewer is not supported on Windows 10 in this release.
      c. PowerPoint Viewer: PowerPoint Viewer 2010 is not supported on Windows 10 in this release. User will not be able to open a protected PPT/PPTX file in Microsoft PowerPoint Viewer on Windows 10.
      d. Visio Viewer: Visio Viewer (2013 and 2010) is not supported on Windows 10 in this release. User will not be able to open a protected Visio file using Visio Viewer on Windows 10.
      e. Open Office 2.4.3, 3.0, 3.1, 3.2: Open Office 2.4.3, 3.0, 3.1 and 3.2 are not supported on Windows 10 in this release. Only Open Office version 4.0.1 is supported on Windows 10.
      f. Adobe Reader 8 / 9 / X: Adobe Reader version 8.x, 9.x and 10.x are not supported on Windows 10 in this release. User will not be able to open protected documents in Adobe Reader 8.x, 9.x or 10.x versions on Windows 10.
      g. MS Office 2003 / 2007: Microsoft Office 2003 and 2007 are not supported on Windows 10 in this release. User will not be able to open protected documents in Microsoft Office 2003 and 2007 versions on Windows 10.
   3. An indexing service runs on Windows 10 which automatically indexes all files (properties as well as content) as soon as they are created or updated. This makes the application hang in some remote situations. Independent of Seclore FileSecure, this is observed to happen 1 in 100 cases. With FileSecure, it is observed to happen 1 in 75 cases.
   4. Protected excel file with On Load macro does not open if user does not have required permissions on linked files.
   5. Protected excel file with On Load macro does not open if user deny to fetch permission of linked files.
   6. Hyper-links for internet present in protected pdf files will not be functional in Adobe Reader DC.

------------------------------
FileSecure 2.78.0.0
FileSecure Desktop Client 2.43.0.0
July 31, 2015

   Feature:
   
   1. Support for protecting e-mails sent using Microsoft Outlook. (#4023)
       a. Easy and intuitive user interface for protecting e-mails with a single click.
       b. Protection options are available in the Outlook ribbon itself.
       c. New external users are registered automatically.
       d. Supports all the FileSecure supported formats.
       e. Available in Microsoft Outlook 2007 (32-bit), Microsoft Outlook 2010 (32-bit and 64-bit) and Microsoft Outlook 2013 (32-bit and 64-bit).
       f. Requires Policy Server 2.42.1.0 or higher.
       g. This feature replaces the "Secure Send" feature of FileSecure Desktop Client which was available in Microsoft Outlook. 
   
   Bug Fixes:

   1. Issue: At times, when macros in Excel edit many cells in the file, it makes the process very slow. (#4032)
      Resolution: Desktop Client has been changed to take care of this issue.
   2. Issue: Installer fails to abort in any erroneous scenario on Windows 8.1. (#4026)
      Resolution: Desktop Client Installer has been changed to take care of this issue.
   3. Issue: Information shown to users about the supported Visio Viewer versions is incorrect. (#4025)
      Resolution: Desktop Client has been changed to display the correct supported versions.
   4. Other fixes: #4024
   
   Known Issues / Limitations:

   1. E-mail attachments sent via an automatic forward or reply will not be protected. 
   2. E-mail attachments sent via the mail merge feature will not be protected.
   3. From this version onwards support of protection of files in Microsoft Outlook 2003 using "Secure Send" has been deprecated. 

------------------------------
FileSecure 2.75.2.0
FileSecure Desktop Client 2.42.3.0
June 12, 2015

   Bug Fixes:

   1. Issue: Editing Microsoft Excel file is slow when file is linked to many other Excel files. (#3969)
      Resolution: Desktop Client has been changed to take care of this issue.
   2. Issue: User is not allowed to Edit Links unless he/she saves the Excel file. (#4015)
      Resolution: Desktop Client closes the file if user links to unauthorized file by editing links. User was forced to save the document before editing links to avoid any data loss in above scenario. Now, User can Edit Links without saving the file if he/she is sure that changing links will not lead to above scenario. 
   3. Other fixes: #3959

------------------------------
FileSecure 2.75.0.0
FileSecure Desktop Client 2.42.2.0
May 8, 2015

   Features:

   1. A completely new and redesigned login window that displays the new Policy Server login page. (#3844, #3873)

   Bug Fixes:

   1. Issue: In some remote cases, Microsoft Office applications fail to start when Auto Classification is enabled. This issue is primarily observed when application is Microsoft Office 2007 and OS is Windows 8. (#3843)
      Resolution: Desktop Client has been changed to take care of this issue.
   2. Other fixes: #3750, #3862

------------------------------
FileSecure 2.72.2.0
FileSecure Desktop Client 2.42.1.0
Mar 31, 2015

   Bug Fixes:

   1. Issue: User experiences delay in opening unprotected file in Microsoft Office from shared folder over slower network. (#3818)
      Resolution: Desktop Client has been changed to optimize the way unprotected files are processed during opening.
   2. Issue: Microsoft Excel crashes on saving specific file with multilingual content. (#3782)
      Resolution: Desktop Client has been changed to take care of this issue.
   3. Issue: Microsoft Office hangs on start if McAfee DLP is configured to monitor sensitive files opened by Microsoft Office. (#3816)
      Resolution: Desktop Client has been changed to avoid deadlock situation which caused this issue.
   4. Issue: Protected files cannot be processed in AppConnect enabled application if AppConnect is configured to exclude all files created in output folder and input files are also placed in the same folder. (#3781)
      Resolution: Desktop Client has been changed to take care of this issue.
   5. Issue: User experiences delay in shutting down machine if Desktop Client upgrade is required. (#3780)
      Resolution: Desktop Client has been changed to apply only 2 patches when machine is shutting down. This means user have to restart machine multiple times if there are more than 2 upgrade patches available.
   6. Issue : In some remote cases, when the machine is very slow or has many processes running at start-up, Desktop Client is unable to start.
      Resolution: Desktop Client has been changed to take care of this issue. (#3829)
   7. Other fixes: #3779, #3783

------------------------------
FileSecure 2.71.0.0
FileSecure Desktop Client 2.42.0.0
Feb 16, 2015

   Feature:

   1. Support for the Microsoft Paint application to open protected image files on Windows 7, 8, 8.1, 2008 Server and 2012 Server. (#3733)

   Bug Fixes:

   1. Issue: PowerPoint files were opening in read-only mode in Office 2013 after applying the MS Office November 2014 update. (#3653)
      Resolution: FileSecure Desktop Client has been changed to take care of this.
   2. Issue: Event Trace Log (ETL) files were affecting the smooth functioning of MS Office. (#3711)
      Resolution: FileSecure Desktop Client has been changed to take care of this.
   3. Issue: The user was not able to open a file in Office 2013 from a network folder if he/she did not have the Edit permission on the file. (#3751)
      Resolution: FileSecure Desktop Client has been changed to take care of this.
   4. Other fixes: #3730, #3731

   Known Issues / Limitations:

   1. A PPT file that is created in a particular version of PowerPoint and opened in a newer version opens in read-only mode. This only happens when the file is opened from a network shared folder. It works fine if the file is opened from the local computer or saved once and reopened. 
      E.g. File created in PowerPoint 2007 and opened in PowerPoint 2010 or 2013 opens in read-only mode from a network shared folder. 

------------------------------
FileSecure 2.70.0.0
FileSecure Desktop Client 2.41.1.0
Jan 6, 2015

   Feature:

   1. a. Linking protected Excel files is now much easier than before
      b. Very often Excel files have formulas that are picking up data from another linked (referenced) Excel file. 
      c. Prior to this release, if the linked file was protected, the user had to open it before the data would be available to the formula in the main file. 
      d. With this change, the linked Excel file need not be explicitly opened by the user. 
      e. FileSecure will open the linked file automatically in the background, without the user having to do anything further. 
      f. This greatly simplifies the user experience, since it was always difficult for users to open all the linked files along with the main file. 
      g. If the user does not have permissions on the linked file, the related formulas will be converted to values and the main file will become read-only. This ensures that the formulas are preserved in the original file even when the Excel link is broken. 
      h. This feature is available in MS Office 2007, 2010 and 2013.
      i. All standard Excel formats are supported including XLS, XLSX, XLSM and XLSB. 
      j. i. The linking of Excel files will follows the same rules as the Copy Data permission i.e.
         ii. A user should have the same or lesser rights on the main file to be allowed to Copy Data from the linked file. 
         iii. A user may Copy Data from a protected file to an unprotected file only if he/she has Full Control permissions on the protected file. 
         iv. Both files should be protected by the same Policy Server, etc (#3222, #3534, #3547, #3548, #3658)

   Bug Fixes:

   1. Issue: Any 64-bit application using Desktop Client APIs crashes on calling IDCSelectProtectionDetailsW(). (#3657)
      Resolution: FileSecure Desktop Client has been changed to take care of this.
   2. Issue: AppConnect was not able to process a file in a custom Java application. (#3663)
      Resolution: FileSecure Desktop Client has been changed to take care of this.
   3. Other fixes: #3639, #3652, #3660, #3662

------------------------------
FileSecure 2.66.0.0
FileSecure Desktop Client 2.41.0.0
Nov 14, 2014

   Features:

   1. Spanish language support in FileSecure Desktop Client. (#3589)
   2. Support for Event Framework for 64-bit processes. This means Auto Classification component which prompts user to classify file when closed can be used for 64-bit applications also. (#3557)

   Bug Fixes:

   1. Issue: MS Office hangs if FileSecure protected MS Office files containing lots of images is opened. (#3554, #3555)
      Resolution: FileSecure Desktop Client has been changed to take care of this issue.
   2. Issue: Desktop Client communicates with Policy Server over SSLv2 and SSLv3 only. It does not communicate over TLS protocols. (#3588)
      Resolution: FileSecure Desktop Client has been changed to communicate over SSLv3, TLSv1.0, TLSv1.1 and TLSv1.2 by default. Registry configuration is provided to configure which protocols should Desktop Client use to communicate. SSLv2 is completely disabled.
   3. Other fixes: #3556, #3586, #3590, #3591, #3592, #3597

------------------------------
FileSecure 2.65.0.0
FileSecure Desktop Client 2.40.0.0
Oct 10, 2014

   Features:

   1. Desktop Client Library consists of a set of APIs built to use the various frameworks/features provided by FileSecure Desktop Client like Authentication of user, Protection of files. This release comes with enhanced capability of this library with feature addition such as Unprotection of files, use of multi-lingual framework. For details please refer the documentation of the library. (#3520)
   2. Optimized the framework for support of a new language within FileSecure Desktop Client. Going forward it will becomes easier and faster to incorporate a new language for Desktop Client. (#3530)

------------------------------
FileSecure 2.64.2.0
FileSecure Desktop Client 2.39.2.0
Sept 22, 2014

   Bug Fixes:

   1. Issue: User cannot open text file in SciTE with file path containing non-English character like Chinese. (#3494)
      Resolution: FileSecure Desktop Client has incorporated latest SciTE which supports Unicode characters in file path.
   2. Issue: File content is lost during Save in Open Office if User switches to another document immediately after saving. This is also possible when User is Saving file as another file. (#3496)
      Resolution: FileSecure Desktop Client has been changed to take care of this. Limitation of this is that User is not allowed to Save/Save As another document till earlier Save/Save As operation is in progress.
   3. Other fixes: #3493, #3498

------------------------------
FileSecure 2.64.1.1
FileSecure Desktop Client 2.39.1.1
Sept 10, 2014

   NOTE: #3222: Enhancement in behaviour Excel Interlinking in FileSecure Desktop Client has been reverted to earlier behaviour in this release.

------------------------------
FileSecure 2.64.1.0
FileSecure Desktop Client 2.39.1.0
Sept 5, 2014

   Bug Fixes:

   1. Issue: User must open linked (referred) files in Microsoft Excel before opening main (referring) file to update formulas using latest information from linked files. (#3222)
      Resolution:
         a. Links and formulas are updated in file if User has appropriate permissions on all linked file when file is opened. In the process, permissions for linked files are fetched from Policy Server when main file is opened.
         b. Links are broken and formulas are converted to value if User does not have appropriate permissions on any one linked file when main file is opened. 
         c. User must open the file to enter formula linking to the file.
         d. For simplicity, User is not allowed to open different files using credentials of different users. Also, User is not allowed to open different files protected by different Policy Servers.
         e. This issue has been fixed in Microsoft Office 2013 (32-bit and 64-bit), Microsoft Office 2010 (32-bit and 64-bit) and Microsoft Office 2007. Behaviour in Microsoft Office 2003 and Microsoft Office XP has not been changed.
         f. Linked file can be in XLS, XLSX, XLSM, XLSB format only. Other formats like CSV are not supported.

         ** Please refer documentation for detailed behaviour and limitations.
   2. Issue: Microsoft Access takes time to start on Windows XP after installing Desktop Client. (#3495)
      Resolution: Desktop Client has been changed to take care of this issue.

------------------------------
FileSecure 2.64.0.0
FileSecure Desktop Client 2.39.0.0
July 25, 2014

   Features:

   1. Support for 64-bit Offline Identity Establishment Component. This is pre-requisite to support 64-bit application in AppConnect. AppConnect Client with 64-bit application support is released along with this release. (#3403)

   Bug Fixes:

   1. Issue: Microsoft Excel crashes when copied cells from protected Excel file are pasted as Excel Worksheet using Paste Special option into protected Microsoft Word file. (#3345)
      Resolution: FileSecure Desktop Client has been changed to take of this issue.
   2. Issue: Microsoft Office Plugin gets disabled if User has Microsoft Office 2013 and any other version of Microsoft Office is installed on his/her machine. (#3407)
      Resolution: FileSecure Desktop Client has been changed to make sure that plugins for all Microsoft Office versions are enabled.
   3. Issue: Desktop Client installation stops if AutoCAD True View 2012 is not properly installed. This behaviour is observed when ProgId for AutoCAD True View 2012 is not present in Windows Registry. (#3408)
      Resolution: FileSecure Desktop Client has been changed to continue installation even if AutoCAD True View is not installed properly.
   4. Issue: Desktop Client supported applications experience performance degradation on high-end machines (24 GB RAM and 12-core processor) after Desktop Client is installed. Machine with normal configurations are not affected. (#3412)
      Resolution: Desktop Client logging was degrading the performance on such high-end machines. FileSecure Desktop Client has been changed to improve logging speed.
   5. Issue: Desktop Client does not trust many new ROOT CAs. (#3413)
      Resolution: FileSecure Desktop Client has been changed to include latest ROOT CAs.
   6. Issue: Property Sheet Extension is not unregistered from Windows Shell when Desktop Client is uninstalled. (#3406)
      Resolution: FileSecure Desktop Client has been changed to un-register Property Sheet Extension from Windows Shell during un-installation.

------------------------------
FileSecure 2.61.1.0
FileSecure Desktop Client 2.38.1.0
June 20, 2014

   Bug Fixes:
   1. Issue: User is not allowed to consume AppConnect packaged file if he does not have EDIT permission on the file. (#3343)
      Resolution: This restriction has been removed and User can consume AppConnect packaged file even if he does not have EDIT permission.
   2. Issue: Microsoft Word crashes when User pastes cells from unprotected Excel file to Word file as Excel Workbook using Paste Special option and tries to edit pasted Excel Workbook. User selects some cells in Excel file, switches to Word file and uses Paste Special option and chooses to paste copied cells as Excel Workbook. Copied cells are pasted as Excel Workbook like an embedded Excel Workbook which can be edited by double clicking on it. Word crashes when User tries to edit the Excel Workbook. This issue is applicable to all Microsoft Office versions. (#3344)
      Resolution: Desktop Client has been changed to take care of this issue.
   3. Issue: PowerPoint throws error while saving the file after Slide is pasted from protected Word file to PowerPoint file. User copies PowerPoint Slide from protected Word file and pastes in any PowerPoint file. After this, PowerPoint enters into a state where it does not allow user to Save or Save As the PowerPoint file. This issue is applicable to all Microsoft Office versions.(#3346)
      Resolution: Desktop Client has been changed to take care of this issue.

------------------------------
FileSecure 2.58.0.0
FileSecure Desktop Client 2.38.0.0
April 22, 2014

   Features:
   
   1. Support for Open Office 4.0.0. (#3109)
   2. Support for Open Office 4.0.1. (#3110)
   3. Introduction of 'Classification Only' mode. In 'Classification Only' mode, Desktop Client allows user to use Office Clipboard but does not allow to open protected files. User's Office settings are reset whenever the 'Mode' of Desktop Client is switched from 'Normal' to 'Classification Only' or vice-versa. (#3113)
   4. Support for Event Framework on Windows 8/8.1. This means Auto Classification component which prompts user to classify file when closed can be used on Windows 8/8.1. Applications supported for Auto Classification will be same as supported on other OS like Microsoft Office, Open Office, Adobe Reader etc. This is applicable to Windows 8/8.1 64-bit machines, since Desktop Client is also supported on 64-bit versions. (#3114, #3115)

   Bug Fixes:

   1. Issue: When protected files are opened from SharePoint, FileSecure Desktop Client is unable to display the content and shows the buffer template instead within the browser. Now if the user still goes ahead and saves the protected files, it leads to data loss of the file with only buffer template being saved. In case of SharePoint this Buffer template is also saved back automatically in the Document Library of SharePoint leading to files being overridden in SharePoint also. (#3116)
      Resolution: Desktop Client has been changed to identify difference between Buffer template file and the actual content of file. Desktop Client makes use of this information while saving the files. If user attempts to save Buffer templates, it disallows this operation, hence prevents data loss. For this, Buffer files needs to be customized to include pre-defined property in metadata or pre-defined text in XLS Buffer file. This issue is applicable to MS Office 2013, 2010 and 2007 for all MS Office formats i.e. doc, docx, docm, xls, xlsx, xlsm, xlsb, ppt, pptx, pptm etc.
   2. Issue: Working with FileSecure Protected Shared Workbook leads to excel crashing and data loss. 'Workbook Sharing' feature of Excel allows simultaneous edit of file by multiple users. This feature of Excel conflicts with FileSecure and makes the application unstable, making it crash at times with loss of data. This issue is applicable to Microsoft Excel 2003, 2007, 2010 and 2013. (#3159)
      Resolution: Desktop Client while opening protected Excel files will remove 'Workbook Sharing' for Excel files. This means that this feature of simultaneous edit will not be available for protected files. At times, to remove this 'Sharing' password is required. In such a case user will be prompted to enter the password before protected files can be opened successfully.
   3. Issue: In some remote cases, FileSecure Desktop Client behaves erratically in Microsoft Office applications, leading to file corruption and loss of data. This is applicable to all versions of Microsoft Office, primary being Microsoft Excel. (#3160)
      Resolution: FileSecure Desktop Client has been changed to resolve the issue.
   4. Event framework generates events for excluded files also. This means, Auto-Classification user is prompted to classify files which are present in folders excluded from auto-classification. (#3207)
      Resolution: Desktop Client has been changed to not generate events for excluded files.
   5. Look and Feel of Manual & Auto-Classification window is not consistent. (#3210)
      Resolution:  FileSecure Desktop Client has been changed to apply same Look and Feel 'Select Classification' window in both cases.
   6. Other fixes: #3157, #3158, #3161

   Known Issues / Limitations:

   1. With this release of Desktop Client, fix for issue where User is asked to save the file on close even after saving using Ctrl + S option, has been rolled back, in MS Office 2003. Please refer #3019 below for more details of the issue.
   2. Sometimes, Microsoft Excel itself fails to detect that protected XLSX file placed on network is 'Shared', even though it is. In such a scenario, Desktop Client does not remove 'Sharing' from the file when it is opened. In this case, file opens in Exclusive mode and not 'Shared' mode like normal network file hence other users are not allowed to open the same file in editable mode. This issue is applicable to Microsoft Office 2010 (32-bit/64-bit) and Microsoft Office 2013 (32-bit/64-bit).

------------------------------
FileSecure 2.56.1.0
FileSecure Desktop Client 2.37.1.0
Mar 14, 2014

   Bug Fixes:

   1. Issue: Microsoft application crashes in remote scenarios. In some remote cases, Microsoft Office application crashes on close of application, when protected documents are open. This issue is applicable to all versions of Microsoft Office. (#3075)
       Resolution: Desktop Client has been changed to take care of crash.
   2. Other Issues: #3119

------------------------------
FileSecure 2.56.0.0
FileSecure Desktop Client 2.37.0.0
Feb 25, 2014

   Features:

   1. Support for Open Office 3.3 (#3084) 
   2. Support for Open Office 3.4 (#3080)
   3. Support for Open Office 3.4.1 (#3091)
   4. Enhanced Desktop Client installation report. FileSecure Policy Server provides a report wherein an OU admin can identify the machines on which FileSecure Desktop Client is installed along with other details like version, IP address, machine name etc. To make this report complete and more informative, FileSecure Desktop Client will send current FileSecure version as part this request. Current FileSecure version will be available as a part of the report in subsequent release of Policy Server. Older Policy Server will not show/include current FileSecure version in the report. (#3083)

   Bug Fixes:

   1. Issue: Microsoft PowerPoint hangs on opening file when Auto Classification is enabled. PowerPoint goes in a non-responsive state when FileSecure Auto Classification is enabled along with FileSecure MSOffice Plugin. This is due to synchronization/deadlock state between FileSecure MSOffice Plugin and FileSecure Auto Classification component in a particular scenario. This issue is observed primarily with Office 2007 but issue has been fixed in all version of Microsoft Office. (#3075)
       Resolution: Desktop Client has been changed to take care of this synchronization issue.
   2. Issue: FileSecure protected "secure" PDF file stored locally does not open in Adobe Reader X. Secure PDF file which is FileSecure protected does not open if opened from local machine. Such file opens if opened from network folder. This issue is observed with Adobe Reader X only. (#3076)
       Resolution: Desktop Client has been changed to take care of this issue.
       * Secure PDF restricts user access, printing, text copying and document editing with password protection.
   3. Issue: Only application window opens when file is opened using FileSecure Open/Open With. At times only application window opens (like blank Excel window) instead of actual document, when user tries to open a file using right click FileSecure Open or Open With option. This issue is observed primarily in Microsoft Office. (#3077)
       Resolution: Desktop Client has been changed to take care of this issue.
   4. Issue: Excel hangs on close in remote scenarios. In some remote cases, Microsoft Office Excel goes in a non-responsive state when application is closed and protected file was opened in that instance of Excel. This issue is applicable to all versions of Microsoft Office. (#3078)
       Resolution: Desktop Client has been changed to take care of this issue.
   5. Issue: Primary Policy Server is missing from registry in remote scenario after Desktop Client is upgraded. In some remote cases, entry for Primary Policy Server URL has been observed to be missing from the registry of the machine on which FileSecure Desktop Client is installed. Due to this, currently user is not able to perform some operations like classification. Also in this case, FileSecure and machine details of the user is not captured in the DC installation report, available as a feature in Policy Server. (#3081)
       Resolution: Desktop Client has been changed to take care of this issue. In such a case, it will pick up the base upgrade URL (also present in registry) and derive Primary Policy Server URL from it and make an entry for the same. This will be done automatically on every machine start. It will also be ‚??repaired‚?? as part of Detect and Repair, if user has admin rights.
   6. Issue: Delay in copy-paste when WebSense DLP is installed. At times, a small delay is observed, while copying data from any application like Lotus Notes Mail Client or Web browser to a document open in Microsoft Excel. This issue only occurs when FileSecure Desktop Client and WebSense DLP both are present on the machine. (#3085)
       Resolution: Desktop Client has been changed to optimise copy data from any other application to an unprotected document. 
           * This issue still persists if data is copied from protected document and pasted in any FileSecure supported application.
   7. Issue: OpenOffice file is not considered as FileSecure classified once edited in OpenOffice 4.x. When an Open Office file is FileSecure classified and then edited in Open Office 4.x version, then file is not considered as classified. This is due to Open Office 4.x changing some metadata information, in the process making FileSecure classification metadata property invalid. (#3088)
       Resolution: Desktop Client has been changed to take care of this. Going forward, even though file is classified and edited in 4.x, file will be remain classified.

------------------------------
FileSecure 2.55.2.0
FileSecure Desktop Client 2.36.2.0
Feb 03, 2014

   Bug fixes:
   
   1. Issue: In some remote cases, Microsoft Office crashes and results in data loss due to files not being recovered. This issue is applicable to all versions of Microsoft Office. (#3087)
      Resolution: Desktop Client has been changed to take care of this issue. This fix will apply to all versions of Microsoft Office.

------------------------------
FileSecure 2.55.1.0
FileSecure Desktop Client 2.36.1.0
Jan 24, 2014

   Bug fixes:
   
   1. Issue: Protected Word file gets corrupt on save when image is copied from protected PowerPoint file. Open protected PPT/PPTX file with image in PowerPoint and copy image from PPT file and shift focus to protected Word file. Word file will show garbage content and same is saved when Word file is saved. This issue is observed in Microsoft Windows 7, Windows 8 and Windows 8.1. (#2980)
      Resolution: Desktop Client has been changed to take care of this issue. This fix will apply to Microsoft Windows 7, Windows 8 and Windows 8.1.
   2. Issue: Protected Office file does not open in MS Office 2013 (64-bit) using Right Click -> Open option. (#2989)
      Resolution: Desktop Client has been changed to take care of this issue.
   3. Issue: User is asked to save the file on close even after saving using Ctrl + S option. This only happens if user uses keyboard shortcut to save it. This issue is not observed if user uses Save button to save the file. This issue is applicable to all Microsoft Office versions. (#3019)
      Resolution: Desktop Client has been changed to take care of this issue.
   4. Issue: User cannot copy Form Elements from unprotected PDF to another unprotected PDF in Acrobat Professional. As soon as Desktop Client is installed, Adobe Reader is converted to SDI application. This means one process of Adobe Reader can open one PDF file only. However, Adobe Professional is also converted to SDI application. This creates and issue since Adobe Professional does not allow to copy Form Elements across different process of Adobe Professional hence user can not copy Form Elements across PDF files. (#3029)
      Resolution: Desktop Client is changed to convert only Adobe Reader into SDI application.
   5. Issue: In some cases, user cannot protect files from mapped network drive. Whenever user tries to protect file on mapped network drive, Desktop Client tries to convert mapped file path to UNC (Universal Naming Convention) path. Desktop Client does not expect any error during this conversion and hence does not address this error which causes this issue. (#3030)
      Resolution: Desktop Client has been changed to take care of error handling during path conversion and treat path as normal path.
   6. Issue: At times, Microsoft Excel crashes on close. This is a random behavior and applicable to all versions of Microsoft Excel. (#3031)
      Resolution: Desktop Client has been changed to take care of this issue.
   7. Issue: Protected and Unprotected Office file get replaced with Buffer File if recovered after Microsoft Office crashes. MS Office creates recovery files for all open files whenever it crashes so unsaved data can be recovered. On start of the Office, it tries to recover data from recovery files and replaces original files. When user is working on protected and unprotected files, it is possible that these recovery files get protected. If these recovery files are protected, it is not possible to recover data using protected recovery files. This issue is applicable to all version of Microsoft Office. (#2981)
      Resolution: Desktop Client removes protected recovery files so Office does not try to recover using protected recovery file hence does not replace original file with Buffer File.  This means, user will not be able to recover unsaved data of protected files ever. Also at times user will not be able to recover unsaved data of unprotected file.
   8. Other Issues: #2797, #2997

------------------------------
FileSecure 2.54.0.0
FileSecure Desktop Client 2.36.0.0
Dec 13, 2013

   Features:

   1. Support for Windows 8.1 (64-bit). All the features, restrictions and known issues applicable to Windows 8.0 are applicable to Windows 8.1 also. Please refer to the release notes of DC version 2.35 for the same. (#2934) 
   2. Allow editing of profile on double click of profile in System Tray. Currently, user has to select Profile and choose Profile -> Edit menu to edit the Profile. Now, user can edit Profile on double click on Profile in System Tray. (#2937)

   Bug Fixes:

   1. Issue : Non-English Microsoft Excel crashes on sorting. In case user has non-English Microsoft Excel and tries to sort filtered cells, Microsoft Excel crashes. This is possible when user is working on protected file or unprotected file when protected file is open in Microsoft Excel. This issue is observed in Microsoft Office 2007/2010/2013. This issue is caused by APIs which FileSecure Desktop Client uses to open the file in Microsoft Office. Microsoft has provided fix for Office 2007 but not for Office 2010/2013 however they have provided alternate API for opening files.(#2209)
       Resolution : Desktop Client will use alternate API to open file in Microsoft Office for Excel. This fix will apply to Microsoft Office 2007/2010/2013.
   2. Issue : Print area is lost in protected files opened in Non-English Microsoft Excel. In case user has non-English Microsoft Office and has Excel file with Print Area defined, Print Area is lost when file is opened. This is possible when user is working on protected file or unprotected file when protected file is open in Microsoft Excel. This issue is observed in Microsoft Office 2007/2010/2013. This issue is caused by APIs which FileSecure Desktop Client uses to open the file in Microsoft Office. Microsoft has provided fix for Office 2007 but not for Office 2010/2013 however they have provided alternate API for opening files. (#2735)
       Resolution : Desktop Client will use alternate API to open file in Microsoft Office for Excel. This fix will apply to Microsoft Office 2007/2010/2013.
   3. Issue : Invalid IP address with value 0.0.0.0 present in Desktop Client installation report. This happens if Desktop Client fetches information for installation report before IP address is assigned to the machine. (#2884)
       Resolution : Desktop Client will get IP address used to connect to Policy Server and send that IP address as a part of Desktop Client installation details to Policy Server. If it is not able to get IP address used to connect to Policy Server (in case like Microsoft XP), it will query all IP addresses before sending installation details and send only first 10 of the list. It will never send installation details if IP address is 0.0.0.0.
   4. Issue : Protection and other activities fail in VDI (Virtual Desktop Virtualization) because of multiple IP addresses. In some VDI setups, concept of IP virtualization is used which assigns multiple (more than 100, at times) IP address to the machine instead of a single one. In such case, Policy Server is not able to store all IP addresses in database because of size constraint on database table column. (#2885)
       Resolution : Desktop Client will get IP address used to connect to Policy Server and send that IP address as a part of machine details to Policy Server. If it is not able to get IP address used to connect to Policy Server (in case like Microsoft XP), it will query all IP addresses before sending machine details and send only first 10 of the list.
   5. Issue : Protected DOC/XLS file opened in Microsoft Office can be saved and stripped  i.e. the protected content is lost and only the buffer file remains. This happens in cases where the user opening the file either does not have FileSecure Desktop Client installed on the machine or the FileSecure MS Office Plugin does not get loaded in Microsoft Word/Excel for some reason. (#2886)
       Resolution : The issue is fixed for cases when FileSecure Desktop Client is installed on the machine but FileSecure MS Office Plugin does not load for some reason. When a user that has FileSecure Desktop Client installed and properly running on the machine and the user opens a protected office file in MS Office, the file will now not get stripped. 
       * Please note that this issue is still present in cases where the user does not have FileSecure Desktop Client installed on the machine.
   6. Issue : At times detail of machine with Desktop Client installed is not captured in the Installation report available with Policy Server. This is possible when user installs Desktop Client and logs into the machine for the first time. In such a case, Desktop Client tries to send installation details to Primary Policy Server and also tries to download Profile for Primary Policy Server at the same time. If Profile for Primary Policy is not downloaded before Desktop Client attempts to send installation details, it will result in that machine details being missed from the report till the user logs into the machine again. (#2911)
       Resolution : Desktop Client will check whether Primary Policy Server Profile is available or not before every attempt to send installation details.
   7. Issue :  Microsoft Excel crashes on save of unprotected file opened in Protected View. This is applicable to Microsoft Office 2010/2013. Office files open in Protected View if they fail security checks like opening from unsafe locations, older version of file etc. Desktop Client is not able to get which document is active when file is opened in Protected View and hence crashes. (#2936)
       Resolution : Desktop Client has been changed to ensure smooth working of application.
   8. Issue : At times when applications are launched from Internet Explorer to open files, they fail to do so. This happens since when FileSecure Desktop Client is present on the machine, Desktop Client application is launched first which exits after launching the desired application. In such a case Internet Explorer deletes the downloaded file from temporary location before the desired application can open the file. 
       Resolution : Desktop Client has been changed so that Desktop Client application does not exit till desired application is running.
   9. Issue : Protected file does not open in Adobe Reader if application is launched with file path without quotes. This happens only if file path contains space. (#2944)
       Resolution : Desktop Client has been changed to take care of such file path.
   10. Issue : Unprotected document which open in MS Office Protected View does not open in editable mode. This happens only when a protected document is already open in the application. This is applicable to Microsoft Office 2010/2013.
       Resolution : Desktop Client has been changed to ensure smooth working of unprotected files within MS Office applications.
   11. Other(#2825, #2882, #2963)

   Known Issues / Limitations:
   1. At times, protected files do not open on Windows 8/8.1. This happens when OS itself registers as Print Screen key handler instead of FileSecure Desktop Client, hence it does not allow to open protected files. This is typically seen in cases where machine is configured to allow user to log on to the machine automatically without providing any user credential. Currently there is no known solution for this except for enabling user credential on the machine.
   2. Protected files do not open in MS Office Protected View. This is applicable to Microsoft Office 2010/2013. Office files open in Protected View if they fail security checks like opening from unsafe locations, older version of file etc.


------------------------------
FileSecure 2.52.0.0
FileSecure Desktop Client 2.35.0.0
Oct 18, 2013

   Features:

   1. Support for Windows 8 64-bit. (#1660, #2873) 
   2. Support for MS Office 2013 64-bit. (#2874, #2466)
   3. Significantly improved the speed of opening, saving and protecting a document. (#1722)
   4. Support for Foxit Reader is deprecated. Users can not open FileSecure protected documents using Foxit Reader. Foxit Reader supplied along with FileSecure will also get uninstalled automatically on upgrade. (#2875)

   Known Issues / Limitations:

   1. Windows 8 32-bit and 8.1 32/64-bit version is NOT supported in this release. Desktop Client Installer will get installed with an error in such cases BUT none of the FileSecure components will run and user will not be able to open any protected documents. User would be required to uninstall the same manually.
   2. Following modules are currently not supported on Windows 8 -
      a. FileSecure Event Framework: Module that throws events whenever user closes a file, which is used in features like Automatic Classification. This means that Automatic Classification which prompts user to classify file on close is NOT supported in this release. 
      b. DWG / DXF Viewer: DWG / DXF Viewer is not supported on Windows 8 in this release.
      c. PowerPoint Viewer: PowerPoint Viewer 2010 is not supported on Windows 8 in this release. User will not be able to open a protected PPT/PPTX file in Microsoft PowerPoint Viewer on Windows 8.
      d. Visio Viewer: Visio Viewer (2013 and 2010) is not supported on Windows 8 in this release. User will not be able to open a protected Visio file using Visio Viewer on Windows 8.
      e. Open Office 2.4.3, 3.0, 3.1: Open Office 2.4.3, 3.0 and 3.1 are not supported on Windows 8 in this release. Only Open Office version 3.2 is supported on Windows 8.
      f. Adobe Reader 8 / 9: Adobe Reader version 8.x and 9.x are not supported on Windows 8 in this release. User will not be able to open protected documents in Adobe Reader 8.x or 9.x versions on Windows 8.
   3. An indexing service runs on Windows 8 which automatically indexes all files (properties as well as content) as soon as they are created or updated. This makes the application hang in some remote situations. Independent of Seclore FileSecure, this is observed to happen 1 in 100 cases. With FileSecure, it is observed to happen 1 in 75 cases.
   4. When a protected file is open and active in an application and user clicks on the File Open Dialog to select some files, in such a case if the user performs a copy paste within the File Dialog the new file created will be protected. This protected file will have the same credential as the file opened in the application. This issue is observed in Win7 32/64-bit and Windows 8.
   5. All known issues and behaviour observed in MS Office 2013 32-bit is applicable to MS Office 2013 64-bit. Please refer Release Notes of Desktop Client 2.32.0.0 release.

   Known Behaviour: 

   1. Following applications are not supported on Windows 8 by the application providers, hence not supported on Windows 8 by Seclore FileSecure -
      a. AutoCAD Applications : None of the AutoCAD version currently supported by Seclore FileSecure can work on Windows 8. This is a limitation of AutoCAD itself. Please refer link - http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15412189&linkID=9240617#section8
      b. Microsoft Office 2003 : MS Office 2003 can not be installed on Windows 8, hence not supported by Seclore FileSecure. Please refer link - http://support.microsoft.com/kb/2777626
   2. First time a user opens any extension on Windows 8, Windows prompts the user which application to use to open the file. That extension gets associated with the application. This may create problems while opening protected files for certain extensions like pdf, txt, images etc. User may need to logout and login again for the system to work normally and open protected files.
   3. Whenever user closes any document - protected / unprotected in MS Office and at least one protected document is open, the user will be prompted to save the document manually if the document is dirty. There is a slight change in behaviour for all versions of Windows and MS Office. This behavior is not applicable to MS Office 2003 and MS PowerPoint 2007.
   
 ------------------------------
FileSecure 2.51.1.0
FileSecure Desktop Client 2.34.1.0
Oct 16, 2013

   Bug Fixes:

   1. Issue : Protected PPT files placed on network folder and opened from MSOffice PowerPoint  get "stripped" i.e. the protected content is lost and only the buffer file remains. This happens in cases where the user opening the file either does not have FileSecure Desktop Client installed on the machine or the FileSecure MS Office Plugin does not get loaded in PowerPoint for some reason. (#2878)
       Resolution : The issue is fixed for cases when FileSecure Desktop Client is installed on the machine but FileSecure MS Office Plugin does not load for some reason. When a user that has FileSecure Desktop Client installed and properly running on the machine and the user opens a protected PPT file in MSOffice PowerPoint, the file will now not get stripped. 
       * Please note that this issue is still present in cases where the user does not have FileSecure Desktop Client installed on the machine.
   
------------------------------
FileSecure 2.51.0.0
FileSecure Desktop Client 2.34.0.0
Oct 11, 2013

   Features:

   1. Russian language support in FileSecure Desktop Client.(#2847)

   Bug Fixes:

   1. Issue : Excel application crash if FileSecure Desktop Client is installed on the machine & AD RMS is also enabled. (#2840, #2843)
       Resolution : Desktop Client has been changed to ensure that the applications run smoothly without any interference. 
   2. Issue : When Desktop Client is installed on a machine with multiple monitors, Alt+PrnScr combination of keys does not capture active window's screenshot.(#2863)
       Resolution : Desktop Client has been changed to ensure the expected behavior when Alt+PrnScr combination of keys is pressed.
   3. Issue : When Desktop Client is installed on a machine, all combinations of Alt+PrnScr+ does not capture active window's screenshot. (#2864)
       Resolution : Desktop Client has been changed to ensure the expected behavior when these combination of keys is pressed.
   4. Issue : In MS Powerpoint 2010 64 bit application, protected pptx documents open in read-only mode from local as well as non-mapped network folders.(#2865)
       Resolution : Desktop Client has been changed to ensure that pptx documents open in write mode from local folders, when access rights is appropriate. 
       * This issue still persists with non-mapped network folders.
   5. Issue : Microsoft Word crashes if user saves a protected file using keyboard shortcuts.(#2869)
       Resolution : Desktop Client has been changed to ensure that application does not crash. 
   6. Other fixes : #2870

   Known Issues:

   1. Template files (Buffer files) for Russian language for the formats - xls, csv, txt, rvt, rfa are in English language only.
   2. FileSecure tab in file properties (Right click on file) for protected files in German language appears in English only.
   3. For Russian Desktop Client - Text on button in UI does not show completely in Classic theme on Windows. User would be required to change the theme in such cases. This behavior in Desktop Client is a result of OS behavior.
   4. Mail template for Russian language for the Lotus Notes SecureSend plugin is in English language only.

------------------------------
FileSecure 2.50.1.0
FileSecure Desktop Client 2.33.1.0
Sept 28, 2013

   Bug Fixes:

   1. Issue : User login on some machines with Windows7 Operating System was extremely slow after applying the previous DC upgrade. At times user was not able to login even after a long wait. (#2866)
       Resolution : Desktop Client has been changed to ensure smooth user login on machine, as before.  

------------------------------
FileSecure 2.49.0.0
FileSecure Desktop Client 2.33.0.0
Sept 04, 2013

   Features:

   1. FileSecure administrator wants to capture a report of Desktop Client(s) deployed within his/her organization. The need is to capture details like list of machine name/IP addresses and Desktop Client version(s) for all machines deployed in the organization, where the Policy Server is the Primary Policy Server. For this, Desktop Client should send information of installed components and their versions to Primary Policy Server on each user log on and also periodically. These details should be stored on the Policy Server. Desktop Client has been changed in this version to start sending this information to the Policy Server. In subsequent releases of the Policy Server, this report will be made available on the Policy Server portal for the administrator. (#2758)

   Bug Fixes:

   1. Issue : Jaspersoft iReport application, which use java virtual environment was unable to start. (#2713)
       Resolution : Desktop Client has been changed to ensure that these applications run smoothly without any interference. 
   2. Issue : If an offline license file had got downloaded on the user's machine in the past and he/she tried to access the file in online mode, the offline license file is expected to get deleted if the user does not have offline rights anymore. It was observed that the offline license was not getting deleted which means that the user could use the offline license till it is expired. (#2752)
       Resolution: Offline license file gets deleted as soon as the user opens the file in online mode, if he/she does not have Offline rights.
   3. Issue : Consider this scenario. User has a protected file A.xls open. User is opening another file B.xls. It could be protected or unprotected. B.xls has formulae which refer to A.xls, however user does not have rights on A.xls to Copy Data into B.xls. When user tries to open B.xls, the formulae in B.xls get changed to refer to itself instead of A.xls. This resulted in incorrect or "#Error" value getting displayed in B.xls. (#2753)
       Resolution : The excel document opening process is changed such that when B.xls opens, it's formulae which are referring to A.xls are replaced with it's current values. When B.xls now opens, it has the last updated values. It still does not update values by referring to A.xls as user does not have rights to Copy Data from A.xls into B.xls. However, user will be able to see the last updated values in B.xls. Please note that currently this behaviour is present only when A.xls is already open before opening B.xls. If A.xls is not open at the time of opening B.xls then it will follow the normal open process. 
   4. Issue : When a user opened a zip file using 7Zip tool and double clicked on any of the files, it was observed that the file did not open as expected. This was observed for protected as well as unprotected pdf, txt and image files. (#2673, #2633)
       Resolution : Desktop Client has been changed to ensure that these files open as expected when opened from within 7Zip tool.
   5. Issue : It was observed that Desktop Client did not remove some shortcuts when uninstalled.(#2657)
       Resolution : Desktop Client has been changed to ensure that it removes all it's shortcuts when uninstalled. 
   6. Issue : Component configuration file can be added on the Policy Server to set certain FileSecure related registry entries on all Desktop Clients registered with this Policy Server. It was observed that the registry entries on the Desktop Client were not getting updated when Component configuration file was deleted from the Policy Server and then re-added again later. (#2679)
       Resolution : This issue was fixed by making sure that the registry entries on the Desktop Client get updated in the above scenario.
   7. Issue :  PATH environment variable contains too many %FSDCCore%. It is added every time Desktop Client is re-installed. (#2767, #2778)
       Resolution: Desktop Client has been changed to remove redundant %FSDCCore% from PATH environment variable. PATH environment variable is updated with correct value in Detect and Repair and when machine is restarted, if it does not contain required folder paths.
   8. Other fixes : #2728

------------------------------
FileSecure 2.48.0.0
FileSecure Desktop Client 2.32.0.0
Aug 05, 2013

   Features:

   1. Support for Microsoft Office 2013 (32-bit only). (#2488)

   Bug Fixes:

   1. Protected files does not open in MS Office 2010 (64-bit) in German Desktop Client. (#2764)

   Known Issues:

   1. User is prompted to manually save unsaved protected and unprotected document before close in Microsoft Office 2013. Also, he/she has to close all documents one by one.
   2. Protected ODT/ODS/ODP files cannot be opened or saved in Microsoft Office 2013.
   3. User is not shown appropriate FileSecure error on print if he/she does not have PRINT permissions in Microsoft Office 2013.
   4. Access Permission window is not shown on top when user opens multiple DOC/DOCX files in Microsoft Office 2013.
   5. Overwriting protected file on mapped location in Microsoft Office 2013 shows unnecessary errors.
   6. Saving protected XLS/XLSX/XLSM/XLSB file in CSV/TXT does not inform that only first sheet will be saved to CSV/TXT file.
   7. Protected PPT/PPTX file with open or/and modify password does not open in Microsoft Office 2013.
   8. FileSecure Event Framework does not generate event for Read-only files in Microsoft Office 2013.
   9. Default 'Save As' tab is replaced with 'Save As' button in File menu in Microsoft Office 2013, once Desktop Client is installed. Default 'Save As' tab has option to save file in SkyDrive, SharePoint or in Recent Folders.
   10. 'Change File Type' option is removed from 'Export' tab in Microsoft Office 2013, once Desktop Client is installed. 'Change File Type' provides option to save file in pre-selected formats. User can use 'Save As' button to change type of the file.

   Known Behavior: 

   1. Multiple Microsoft Word 2013 instances start on opening multiple DOC/DOCX files simultaneously. User may be asked to save Normal.dot/Normal.dotm on exit. This behavior is also observed for unprotected files without Desktop Client. 
   2. Embedding XLS/XLSX file inside XLS/XLSX may crash Microsoft Excel 2013 on save and exit. This behavior is also observed for unprotected files without Desktop Client.
   3. Some features may not be available in Microsoft Office 2013 for files of older format like DOC/XLS/PPT and DOCX/XLSX/PPTX files created in Microsoft Office 2007. This behavior is also observed for unprotected files without Desktop Client when files are opened in 'Compatibility Mode'.

------------------------------
FileSecure 2.47.0.0
FileSecure Desktop Client 2.31.0.0
July 26, 2013

   Features:

   1. Support for Microsoft Office 2010 64 bit. (#2635)

   Bug Fixes:

   1. Workbook sharing option is enabled only if user has FULL CONTROL permission. It will be enabled if user has EDIT and EXECUTE MACRO permissions. (#2647)
   2. User is not allowed to save file in different format (using Save As feature) in Microsoft Office if language of Microsoft Office and Desktop Client does not match, like MS Office language is Italian and Desktop Client language is English. (#2658)
   3. Incomplete Credential name is shown on File Protection window. (#2659, #2660, #2564)
      This issue has been fixed along with the following changes -  
         a. Removed accumulator to select Credentials and replaced with single list with check-box to select Credentials. 
         b. Credential list can be filtered. 
         c. Option to see only selected Credentials. 
         d. Select Owner button is removed. 
         e. Protector information is removed.
         f. Renamed label of create Credential option from 'Add New' to 'Create'.
   4. Office files which require repairing while opening, does not open in Microsoft Office after protection.(#2661, #1915)
   5. Warn user that he/she will not be allowed to save changes made to the document, if he/she does not have EDIT permission. By default, this warning is not shown to user. To turn on this warning, set 'ShowEditWarning' parameter of Desktop Client to '1' in Component Configuration in Policy Server. (#2665)
   6. Multiple error messages are shown to user while opening and closing file in Microsoft Office if user does not have any access. (#2616, #2727)
   7. Internet Explorer 8.x crashes on close/exit on Windows 7 (64-bit) and Protected Mode is enabled in IE. (#2698)
   8. User is not able to print a protected file using printer Canon ImageCLASS 2200. (#2712)
   9. Desktop Client shows invalid SSL certificate error if proxy username/password are not set in Proxy Settings and proxy server requires authentication. (#2725)
   10. Other fixes: #2722
   
   Known Issues:

   1. User may see File Protection window in mixed language if he/she has German Desktop Client installed.

------------------------------
FileSecure 2.46.0.0
FileSecure Desktop Client 2.30.0.0
June 17, 2013

   Features:

   1. Introduction of Client Component Configuration in Policy Server. (#2523)
      a. Component Configuration provides mechanism to configure any client component like Desktop Client, Automatic Data Classification etc. Some example of configuration are 'Enable/Disable One-Click feature', 'Make Automatic Data Classification mandatory or optional'. Component Configuration is maintained in Policy Server and client component retrieves this configuration from Policy Server and starts behaving accordingly.
      b. Desktop Client 2.30.0.0 and Policy Server 2.32.0.0 is mandatory to use this framework.

      * As of now, this framework is used by Automatic Data Classification only to make classification mandatory or optional.

   Bug Fixes:

   1. Default selection to "No, this is not my machine" on the authentication window. (#2484)
   2. User is not allowed to embed objects even if he/she has FULL CONTROL permission. (#2522)
   3. Only last patch of Language Pack (or sub-component) is applied. (#2521)
   4. Application crashes on exit when FileSecure Event framework is enabled and debug logging is enabled. (#2520)
   5. Erratic event generation for FileSecure Event Framework. (#2477)
   6. User is not allowed to classify a file if he forgets to select 'Yes, I am working on my machine' during authentication. (#2622)

------------------------------
FileSecure 2.45.0.0
FileSecure Desktop Client 2.29.0.0
Apr 29, 2013

   Features:

   1. FileSecure Desktop Client is compatible with McAfee DLP 9.3 and later.

   Bug Fixes:

   1. FileSecure Desktop Client does not support automatic detection of proxy settings. (#850)
   2. FileSecure Desktop Client does not support detection of proxy using proxy script. (#1579, #2150)
   3. FileSecure Desktop Client does not support separate proxy server for different protocols.
   4. FileSecure Desktop Client does not fallback to 'No Proxy' mode is some cases. (#2145)
   5. FileSecure Desktop Client does not upgrade if proxy server requires username/password based authentication. (#1327, #2392)
   6. FileSecure Desktop Client does not upgrade if System account does not have DELETE permissions on TEMP folder. (#2148)
   7. FileSecure Desktop Client does not upgrade if value of 'WaitToKillServiceTime' registry has non-numeric characters. (#2390)
   8. User is not warned that FileSecure Desktop Client will not upgrade if he/she is shutting down Windows XP remotely. (#2391)
   9. Microsoft Office files downloaded from Microsoft Outlook are marked as Read Only. (#1710)
   10. Error 'No permissions defined to send protected mail' is shown on sending protected mail (Secure Send) on Windows Vista if Protected Mode is enabled in Internet Explorer 7.x. (#2204)
   11. Corrected spelling mistakes in messages. (#2341)
   12. Many error messages are not shown in Microsoft Office when user performs un-authorized activity like Print when he/she does not have PRINT permission. (#2349, #2363)
   13. DOCX/XLSX/PPTX format is selected by default and not the format of original file, in Save As window in Microsoft Office 2007/2010. (#2403)
   14. Other issues: #1978

   Known Issues:

   1. FileSecure Desktop Client does not upgrade if proxy server requires domain user authentication.
   2. FileSecure Desktop Client uses first proxy server only if multiple proxy servers are provided.

------------------------------
FileSecure 2.44.1.0
FileSecure Desktop Client 2.28.1.0
Apr 12, 2013

   Bug Fixes:
   
   1. Protected PDF/FDF file open in Foxit Reader even if Adobe Reader XI is installed. (#2398)
   2. Unprotected PDF/FDF file does not open in Adobe Acrobat even if user chooses so and Adobe Reader XI and Adobe Acrobat is installed. (#2399)

------------------------------
FileSecure 2.44.0.0
FileSecure Desktop Client 2.28.0.0
Mar 25, 2013

   Features:
   
   1. Support for Adobe Reader XI. (#1936)

   Bug Fixes:
   
   1. Access Permissions window not shown on top of Adobe Reader 9 application window. (#1906)
   2. User cannot open protected file without MACRO permissions in Microsoft Word if only declaration (like Option Explicit) is present in code. (#1946, #2143, #2248)
   3. User cannot unprotect/package/unpackage file if he does not have NTFS permission to create directory on any of the directory in path. (#2212)
   4. Protected PDF file from Lotus Notes does not open in Adobe Reader (or supported application) if Adobe Professional is installed on the machine. (#2214)
   5. Protected PDF file from Internet Explorer does not open in Adobe Reader (or supported application) if Adobe Professional is installed on the machine. (#2215)
   6. Protected PDF files does not open in Adobe Reader (or supported application) if Adobe Reader X and later and Adobe Professional is installed on the machine. (#2124)
   7. Desktop Client cannot connect to Policy Server if proxy server includes scheme/protocol (e.g. http://myproxy.com:80). (#2228)
   8. Primary Policy Server Profile is not downloaded on laptop users (or wireless users) because System Tray starts before system is connected to wireless network. (#2247)
   9. User cannot save file in Microsoft Office if locale (language) of Microsoft Office is German and Desktop Client is English or vice-versa. (#2218)

------------------------------
FileSecure 2.42.3.0
FileSecure Desktop Client 2.27.3.0
Mar 01, 2013

   Bug Fixes:
   
   1. Complete Policy Server name is not seen in Select Profile window. (#2137)
   2. Profile with junk values is added to User Preferences when Profile of Policy Server is not present and Desktop Client falls back to No Proxy mode to connect to Policy Server. (#2102, #1829, #1830)
   3. By default, disabled opening protected document directly from Internet Explorer. (#2206)

------------------------------
FileSecure 2.42.2.0
FileSecure Desktop Client 2.27.2.0
Feb 22, 2013

   Issues marked as fixed in Desktop Client 2.27.1.0 (FileSecure 2.42.1.0) are actually fixed in this release.

------------------------------
FileSecure 2.42.1.0
FileSecure Desktop Client 2.27.1.0
Feb 21, 2013

   Bug Fixes:
   
   1. Microsoft Office hangs randomly. (#1945, #1975)
   2. Outlook hangs randomly. (#2102)

------------------------------
FileSecure 2.42.0.0
FileSecure Desktop Client 2.27.0.0
Jan 31, 2013

   Features:

   1. Support for Data Classification. (#1714, #1720)
      a. Files with following extensions are supported for classification: doc, xls, ppt, docx, xlsx, pptx, odt, ods, odp, pdf
      b. User can classify file using Primary Policy Server only.
      c. Option to classify is available on right click of file, within FileSecure menu.
      d. There is an option to classify files in offline mode for a limited period of time.
      e. Files protected with Open/Edit password cannot be classified.
      f. Digitally signed files cannot be classified.
      g. Classified documents when saved in a different format may not carry the classification. This is an application dependant behaviour.
   2. Support for viewing Visio drawing files. (#1721)
      a. Protected files with following extensions are supported for viewing: vsd, vdx, vss, vsx
      b. To view protected files in FileSecure Viewer pre-requisite is to have one of the following applications on the machine - 
         i. Visio OR Visio Viewer 2013 
         ii. Visio OR Visio Viewer 2010
      c. User needs to use FileSecure -> Open option to open protected Visio files.

   Bug Fixes:
   
   1. Content of protected PDF file is lost when user opens file in Adobe Pro and saves it when prompted. (#1819)
   2. Machine performance degrades if PrintScreenMonitor.exe is not running. (#1823)
   3. Incorrect error message is shown when user saves protected file as PDF in Office 2010. (#2006)
   4. Event for new file in not generated in OpenOffice after user saves it on disk. (#2007)
   5. Provision to specify timeout for connecting to Policy Server. (#2008)
   6. Read-Only attribute is lost after protecting or unprotecting file. (#2010)
   7. Event for file is not generated when modified file is saved and closed. (#2064)
   8. Part of classification name is shown for classification with longer name in file protection window. (#1948)
   9. Desktop Client takes long time to respond if Policy Server is not reachable. (#1639)
   10. Other issues: #1821

------------------------------
FileSecure 2.41.0.0
FileSecure Desktop Client 2.26.0.0
Dec 31, 2012

   Features:

   1. Open protected documents directly from Internet Explorer in application. (#1148)
      a. This supports following extensions only: doc, docx, rxls, xlsx, ppt, pptx, odt, ods, odp, odg, odf, pdf.
      b. Only Internet Explorer 7, 8, 9, 10 (32-bit and 64-bit) is supported.
      c. All file formats which are supported opens in native application irrespective of the whether file is protected or unprotected.
      d. FileSecure Internet Explorer Extension does not intercept default flow in following cases: 
        i.  Any Browser Helper Object is registered with IE.
        ii. PDF file is opened from 64-bit IE.
        iii. File is opened from SharePoint Explorer view.
        iv. Any other ActiveX is installed on the machine to open/show files from a URL eg. SharePoint Open Document ActiveX.
           ** File from SharePoint does not open in applications if SharePoint Open Document ActiveX is enabled in Internet Explorer. SharePoint Open Document ActiveX needs to be disabled to open files in application from SharePoint. By default, SharePoint Open Document ActiveX is not disabled. It is configurable whether Desktop Client should disable SharePoint Open Document ActiveX or not. Customer wanting to open files in application from SharePoint will require customization patch to change the default configuration.         

   Bug Fixes:

   1. Pivot option is disabled if one protected file with FC and unprotected is open in Excel. (#1835)
   2. 'Error reading file' is shown as error message instead of 'File is already unprotected' for unprotected file when multiple files are unprotected. (#1864)   
   3. 'Convert to' window pops up when protected .doc file is opened in Microsoft Office XP/2003/2007/2010. (#1701)
   4. 'Error reading User Preferences' is shown on system startup OR Policy Server Profile with junk values are added to User Preferences randomly. (#1829, #1830)
   5. Do not open protected PDF files in Foxit Reader inside Internet Explorer. (#1874)
   6. Buffer file of first file is used if multiple files with same path length protected together. (#1822)
   7. Print Screen Monitor does not stop when service is stopped. (#1820)
   8. File HANDLE is not released in IDCIsFileProtected() API in Desktop Client APIs. (#1875)
   
------------------------------
FileSecure 2.40.1.0
FileSecure Desktop Client 2.25.1.0
Nov 22, 2012

   Bug Fixes:

   1. Microsoft Office hangs when unprotected file is opened. (#1779, #1783, #1785, #1789, #1791)
   2. FileSecure Event Framework triggers event for all file formats instead of only supported file formats. (#1793)

------------------------------
FileSecure 2.40.0.0
FileSecure Desktop Client 2.25.0.0
Nov 5, 2012

   Features:

   1. Introduction of Primary Policy Server. (#1636)
      a. Upgrade URL is considered as Primary Policy Server for new installation and existing installation. Demo Seclore Policy Server is set as Primary Policy Server for machines using https://upgrade.seclore.com/filsecure as upgrade server.
      b. Profile of Primary Policy Server is automatically downloaded and added to User Preferences. This eliminates requirement of customization patch for Primary Server Profile.
      c. Primary Policy Server is defined at machine level and different User can not have different Primary Policy Server.
      d. Concept of Default Profile is deprecated. Instead of Default Policy Server, Primary Policy Server is shown selected on Profile selection window.
      e. User is not allowed to edit Profile of Primary Policy Server. User can modify 'Trusted' flag only.
   2. Desktop Client APIs are available to protect files using Desktop Client infrastructure. (#1638)
      a. Primary Policy Server must be defined to use Desktop Client APIs.
      b. Desktop Client APIs work with Primary Policy Server only. eg. Files can be protected with Primary Policy Server only.
      c. Only 32-bit version of library is available.
   3. Introduction of FileSecure Event Framework. (#1637)
      a. This framework triggers events whenever file is closed in an application. There can be third-party component registered to handle events triggered by this framework. This third-party component can protect files using Desktop Client APIs.
      b. Supported Applications:
         1. All applications supported by FileSecure Desktop Client
         2. Notepad
         3. Wordpad
         4. EditPlus
      c. Supported File Formats
         1. All file formats supported by FileSecure Desktop Client
      d. Only 32-bit applications are supported.

   Bug Fixes:

   1. Protected excel file does not open in Office 2010 if file is opened when Microsoft Excel is not running. (#1604, #1689)
   2. User cannot create Offline Package for multiple users. (#1675)
      a. Policy Server 2.29.0.0 (FileSecure 2.39.0.0) is required to select multiple users while creating Offline Package.
   3. Offline Identity Establishment Component's registration is not validated before user selects Offline Users. (#1678)
   4. Other issues: #1738

------------------------------
FileSecure 2.37.0.0
FileSecure Desktop Client 2.24.0.0
Sept 21, 2012

   Features:

   1. Support for OpenOffice 2.4.3. (#1585)
      a. OpenOffice 2.4.3 requires separate license to open protected documents.
      b. OpenOffice shows warning to user to upgrade OpenOffice if file protected using pervious version of Desktop Client is opened in OpenOffice 2.4.3. User can ignore this warning to proceed further. Customers who have customized buffer files will face this issue until they are provided buffer files created in OpenOffice 2.4.3 for OpenOffice file formats.
   2. Support to plug in components to establish user identity in offline mode. (#1600)
      a. User can create 'Offline Package' and distribute to users who do not have connectivity to Policy Server to use protected documents if they have such component plugged into Desktop Client.
      b. Minimum Policy Server version required to use this feature is Policy Server 2.36.0.0 (FileSecure 2.33.0.0).

   Bug Fixes:

   1. Desktop Client does not connect to Policy Server having SSL certificate issued by CA 'Staat der Nederlanden Root CA - G2'. (#1552)
   2. User can not insert or edit hyperlink in Microsoft Office XP/2003/2007/2010. (#354)
   3. PowerPoint 2003 crashes on exit after copying OLE object from file. (#1584)
   4. Show icon for protected file only in Windows Explorer to improve performance. (#1617)
   5. Pivot Table options are disabled even if protected document is not open. (#1615, #1627)
   6. Other issues: #356, #1172, #1583, #1602, #1612, #1620

   Note:

   1. Clipboard is cleared whenever any Office application exits.
   2. Offline Licenses generated by previous version of Desktop Client are ignored by this version of Desktop Client so user needs to again open the file in Online mode after upgrading to this version of Desktop Client to open the file in offline mode.
   3. User cannot create Offline Package for multiple users.
   4. Offline permissions are not shown in FileSecure file Properties page on 64-bit Operating System if Offline License is created using third party Offline Identity Establishment component.
   5. Files cannot be opened in Offline mode in 64-bit applications if Offline License is created using third party Offline Identity Establishment component.

------------------------------
FileSecure 2.35.1.0
FileSecure Desktop Client 2.23.1.0
Aug 17, 2012

   Bug Fixes:

   1. User is not allowed to edit password protected and FileSecure protected Office documents in Microsoft Office 2007 and Microsoft Office 2010. (#1581, #1063, #973)
   2. Unprotected file with open and modify password opens with error if protected file is open and user choose to open the unprotected file in Read-Only mode when reloaded. (#1312)

   Note:

   1. User must have Microsoft Office 2007 SP3 and above installed to edit password protected and FileSecure Protected files.
   2. There are compatibility issue with password protected files created in newer version of Microsoft Office and accessed in older version of Microsoft Office. Following are some scenarios:
      a. User is not prompted for password if xslx/docx/pptx file created in Microsoft Office 2010 is opened in Microsoft Office 2007 without SP3.

------------------------------
FileSecure 2.34.0.0
FileSecure Desktop Client 2.23.0.0
July 12, 2012

   Features:

   1. Support for TrueView 2012 to view AutoCAD Drawings. (#1352)
   2. COPY DATA permission allows user to extract data to protected files only, making content copy secure. (#1453)
      Clipboard: 
         a. User can copy content from the protected file to any file if user has FULL CONTROL permission on the protected file.
         b. User can copy content from the protected file to another protected file if user has COPY DATA permission on the protected file and user has lesser permissions than the protected file on target file. Files must be protected with same Policy Server and same user must be accessing the file.
         c. User can copy content from the protected file to another protected file if user does not have COPY DATA permission on the protected file but files are protected with same File Identifier. Files must be protected with same Policy Server and same user must be accessing the file.
      Formulas:
         a. User can refer to the protected file from any file if user has FULL CONTROL on the protected file.
         b. User can refer to the protected file from another protected file if user has COPY DATA permission on the protected file and user has lesser permission than the protected file on referring file. Files must be protected with same Policy Server and same user must be accessing the file.
         c. User can refer to the protected file from another protected file if user does not have COPY DATA permission on the protected file but files are protected with same File Identifier. Files must be protected with same Policy Server and same user must be accessing the file.
      Pivot Table:
         a. User can use Pivot Table if one file is open and the file is protected.
         b. User can use Pivot Table when unprotected file is open or user has FULL CONTROL permission on one protected file, only if user has FULL CONTROL permission on all protected files.
         c. User can use Pivot Table when user does not have FULL CONTROL permission on any protected file but COPY DATA permission on one protected file, only if user has same permissions on all protected files. Files must be protected with same Policy Server and same user must be accessing the file.
         d. User can use Pivot Table when user does not have FULL CONTROL or COPY DATA permission on any protected file only if all protected files are protected with same File Identifier. Files must be protected with same Policy Server and same user must be accessing the file.
      Others:
         a. User can Move/Copy sheet from the protected file to any file only if user has FULL CONTROL permission on the protected file. User can not Move/Copy sheet to any file in Microsoft Excel 2003 or XP on Windows Vista, Windows 7 and Windows Server 2008 and later.
         b. User can Drag & Drop object from the protected file to any file only if user has FULL CONTROL permission on the protected file.

      Known Issues:
         a. Clipboard is cleared when user switches to document on which user does not have permission to paste the copied content from the protected file. This is only applicable when switching within an application.
         b. Microsoft Office Clipboard can not be used once Desktop Client is installed.
         c. File Activity for Copy/Paste is not logged.

   3. Support for MS Paint on Windows XP SP3. (#1396)

   Bug Fixes:

   1. User is not informed about why Pivot Table feature is not allowed, if certain combination of protected files are open. (#1454)
   2. 'Show Markup' and 'Reviewing Pane' options are disabled when user has EDIT rights on the protected file. (#1424)
   3. Part of Authentication dialog can not be seen on Tablet PC. (#1462)
   4. Microsoft Excel crashes when embedded object is pasted from Microsoft PowerPoint or Microsoft Excel. (#1528)
   5. Microsoft PowerPoint crashes when user switches multiple times between documents. (#1527)
   6. Users are not able to connect to Policy Server if proxy needs to be bypassed and proxy bypass list is longer than 1024 characters. (#1515)
   7. User without COPY DATA permission cannot copy/paste contents of any cell within the protected excel file. (#320, #1373)
   8. User without COPY DATA permission cannot copy/paste content within protected documents even if files are protected with same File Identifier. (#1276)
   9. User with EDIT rights is unable to copy-paste objects/clip-art within PowerPoint. (#453)
   10. Other issues: #1330, #1519

   Known Issues:

   a. User can not open the protected file containing macro if user does not have EXECUTE MACRO permission.
   b. User can not Move/Copy sheet to any file in Microsoft Excel 2003 or XP on Windows Vista, Windows 7 and Windows Server 2008 and later.

------------------------------
FileSecure 2.33.2.0
FileSecure Desktop Client 2.22.6.0
June 29, 2012

   Bug Fixes:

   1. Microsoft Office (Excel) file takes long time to open if HPBPRO.EXE is installed on the machine. (#1485)
   2. Other fixes: #1362, #1445, #1516

------------------------------
FileSecure 2.32.5.0
FileSecure Desktop Client 2.22.5.0
Apr 24, 2012

   Bug Fixes:

   1. Opening and saving of large protected excel and csv format, takes time. (#827, #1329, #1354, #1356, #1358, #1374)
   2. Working with large excel files with formula(s), takes time. (#1357)
   3. Other fixes: #1372

------------------------------
FileSecure 2.32.4.0
FileSecure Desktop Client 2.22.4.0
Apr 19, 2012

   Bug Fixes:

   1. Added 'StartCom Certification Authority' to list of trusted root CAs. (#1389)
   2. At times, buffer files is pasted if user copies image from the protected file and pastes in another file. (#1223)
   3. Saving protected MS Office files corrupts file on Windows 7 when application terminates abruptly during save operation. (#1392)
   4. Other fixes: #1369

------------------------------
FileSecure 2.32.3.0
FileSecure Desktop Client 2.22.3.0
Mar 05, 2012

   Features:

   1. User can use Pivot Table feature if there is only one (protected) document open and even if he/she does not have COPY DATA permission. (#1316)

   Bug Fixes:

   1. User cannot print Excel document if document is updated while opening by application and user does not have EDIT permission. (#450)
   2. Print custom page range option is disabled in Office 2010 even if user has PRINT permission. (#1098)
   3. Protected PDF files does not open in Adobe Reader if Adobe Professional is also installed. (#1326)
   4. Office 2010 crashes if document becomes dirty while printing and user does not have EDIT permission on the document. (#1071, #1281)
   5. Multiple patches not applied on restart of Windows 7. (#1335)
   6. MS Office hangs while printing if there is no physical printer is installed. (#1365)
   7. Other fixes: #1299, #1321

------------------------------
FileSecure 2.32.2.0
FileSecure Desktop Client 2.22.2.0
Feb 06, 2012

   Bug Fixes:

   1. Protected file does not open on 32-bit OS if DC is upgraded from 2.16.1.0 to 2.22.0.0. (#1318)

------------------------------
FileSecure 2.32.1.0
FileSecure Desktop Client 2.22.1.0
Jan 24, 2012

   Bug Fixes:

   1. Multiple Excel files with large data hang MS Excel while opening. (#1236)
   2. IE 8 crashes randomly when closed. (#1216)
   3. Windows Update KB2585542 conflicts with Seclore FileSecure Desktop Client. (#1294, #1295)
   4. Unprotected password protected files does not open in Office if FileSecure protected file is open. (#1264)
   5. User can not protect file the after user opens File Properties (Right Click -> Properties). (#1300)
   6. Other fixes: #1306

------------------------------
FileSecure 2.32.0.0
FileSecure Desktop Client 2.22.0.0
Dec 09, 2011

   Features:

   1. Support for Windows Server 2008 64-bit Operating System. (#1206)
   2. Support for Lotus Notes (Domino Server and Lotus Notes 8.5.3) for sending secure e-mails. (#390, #965, #1187)
   3. Provision to see basic file details in file properties. (#882, #1149)
   4. Provision to configure whether to open PDF files in Foxit Reader within Internet Explorer or not. (#1211)

   Bug Fixes:

   1. User can not send secure e-mail if one the attachment name contains &. (#1220)
   2. Desktop Client crashes when connecting to Policy Server running with Apache Server. (#1219)
   3. Protected file are considered corrupt if size of buffer file is 60K, 124K, 252K, 508K, 1020K. (#1213)
   4. D&R crashes when executed after uninstalling Adobe Reader X. (#1243)
   5. Desktop Client crashes while unprotecting multiple files if one of the file is already open. (#1235)
   6. Other fixes: #1217, #1245, #1162

------------------------------
FileSecure 2.31.0.0
FileSecure Desktop Client 2.21.0.0
Oct 17, 2011

   Features:

   1. Support for Power Point Viewer 2010. (#1141)
   2. Support for MS Office 2010 on Windows XP is back. It was deprecated in the last release.

   Bug Fixes:

   1. Chart is not shown properly in Excel 2007 if user does not have SCREEN CAPTURE permission. (#1143)
   2. Desktop Client conflicts with McAfee DLP and other screen capturing tools. (#1175)
   3. Incorrect icon for images file are shown after installing Desktop Client. (#975)
   5. Microsoft Outlook crashes randomly on exit. (#1084)
   6. Unsupported OpenOffice is shown in Open With list of application for Microsoft Office files. (#1194)
   7. PPTX file opens in read-only mode if it is opened twice in same session of Microsoft PowerPoint 2010. (#1190)
   8. Desktop Client does not show appropriate error when SSL certificate of Policy Server is expired. (#788)
   9. Unprotected file are treated as protected when size of the file is exactly 61K. (#1200, #1192)
   10. Other fixes: #1162, #1195

------------------------------
FileSecure 2.30.0.0
FileSecure Desktop Client 2.20.0.0
Sept 21, 2011

   Features:

   1. Support for Adobe Reader X on all supported Operating Systems. (#911, #1101)
   2. Support for Adobe Reader 8/9/X on Windows 7. (#1072)
   3. Deprecated support for Adobe Reader 6/7 and Adobe Professional 6/7/8/9 on all Operating Systems.
   4. Deprecated support for Office 2010 on Microsoft XP. (#1113)

   Bug Fixes:

   1. User has trouble viewing network folder in Windows Explorer if network speed is slow and if the folder contains many files, specially unprotected. (#1116)
   2. Icons for the image attachment in not shown in Outlook. (#975)
   3. Copy/Move Sheet is not allowed even if user has COPY_DATA permission. (#999)
   4. Content of protected DOC file are lost when uploaded to Non-IRMed Document Library in SharePoint. (#1127)
   5. Error messages are updated to inform user to execute 'Detect and Repair'. (#1093)
   6. Protected file gets corrupted on save if buffer file is more than 57K. (#1145)
   7. Adobe X crashes if user prints, when default printer is virtual printer.

------------------------------
FileSecure 2.27.0.0
FileSecure Desktop Client 2.19.0.0
July 15, 2011

   Features:

   1. Support for automatic upgrade without user interaction. (#957, #729, #726, #326)

   Bug Fixes:

   1. Foxit language not set to default (English) when German version of DC is uninstalled and default locale is installed. (#1076)

------------------------------
FileSecure 2.26.1.0
FileSecure Desktop Client 2.18.3.0
July 11, 2011

   Bug Fixes:

   1. In case patch required restart of machine, it does not skip remaining patches of other components.(#1096)

------------------------------
FileSecure 2.25.3.0
FileSecure Desktop Client 2.18.2.0
May 27, 2011

   Bug Fixes:

   1. Protected files can not be opened using any other network adapter when wired LAN is disabled. (#696, #1038)
   2. Drawing objects can not be viewed properly in PowerPoint XP/2003 when protected document is open. (#1009)
   3. Access Permissions dialog is not shown in background and does not blink in Foxit Reader. (#1010)
   4. "Word Options" button does not show Options dialog in Word 2007. (#1039)
   5. Multiple options in MS Word XP/2003 are disabled even after closing all protected documents. (#1046)
   6. Save As/Open dialogs (File selection dialog) takes lot of time to open on Windows 7. (#1059)
   7. 'No User Preferences configured' message is shown when there is no enabled Profile configured in User Preferences. (#1055)
   8. Other bug fixes: #493, #631, #1066

------------------------------
FileSecure 2.25.1.0
FileSecure Desktop Client 2.18.1.0
May 13, 2011

   Bug Fixes:

   1. Various buttons (like Print, Save, Save As, Reply, Reply All, Word/Excel/PowerPoint Options) in Microsoft Office does not respond on Windows Vista/7 when user has admin privileges. Also Outlook Plugin does not load in same case. (#1040)

------------------------------
FileSecure 2.25.0.0
FileSecure Desktop Client 2.18.0.0
Apr 15, 2011

   Features:
   
   1. FileSecure Desktop Client installer is available in all supported languages (English and German). (#885) 
   2. At the time of opening a protected file, if Policy Server Profile associated with the file is not present in User Preferences, every time it prompts user to agree to send details to Policy Server. Profile will now be automatically added. This newly added Profile is not available for protection, but user can enable it for protection in Desktop Client Tray. (#937)
   3. Import Profiles from .fsp files on double-click. This only adds Profile, if does not exist. Profile is enabled, if it is disabled. (#958)
   4. Automatically configure Desktop Client when machine starts. (#936)

   Bug Fixes:

   1. Inappropriate error messages are shown in Detect and Repair in case user does not have admin privileges. (#979)
   2. Protected PPT file gets corrupted on save, in remote cases. (#874, #925)
   3. Installation fails if registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run' is not present. (#978)
   4. Detect and Repair shows error even if it successfully enables Microsoft Office Plugin(s). It also does not reset registry values. (#980)
   5. MS Excel 2007 crashes when user clicks on Excel Options -> Addins and MS Excel 2003 and MS Excel 2007 are installed. (#960)
   6. Open Office plugin fails to register if Quick Starter is running. (#891)
   7. Extra Open (Default) options are shown on right-click of file after installing Desktop Client, specially PDF and image files. (#921)
   8. Lock icon is shown for unprotected files attached in e-mail in Outlook and Windows Explorer. (#975, #988)
   9. AutoCAD Std/Map 3D 2011 hangs when user publishes protected DWG file to DWF/DWFx on Windows 7. (#977)
   10. Other bug fixes: #474, #930

------------------------------
FileSecure 2.23.1.0
FileSecure Desktop Client 2.17.1.0
March 28, 2011

   Bug Fixes:

   1. Fix in the language and grammar of the English Resource Collection.
   2. Other bug fixes: #401, #922, #964.

------------------------------
FileSecure 2.23.0.0
FileSecure Desktop Client 2.17.0.0
Feb 18, 2011

   Features:
   
   1. Support for Microsoft Office 2010. This includes E-mail (Secure Send) support for Outlook 2010. (#707)
   2. Framework support for 64 bit applications on 64 bit Win7. (#886, #901)

   Bug Fixes:

   1. Protected PDF shows blank file when directly viewed from Microsoft SharePoint. (#862)
   2. Unable to send protected e-mails through Secure Send if browser is IE9. (#909)
   3. Error message is displayed when adding/opening pdf files with comments in Foxit Reader. (#872)
   4. PDF files open in Foxit Reader even after uninstalling Desktop Client. (#878)

   Known Issue:
   
   1. In MS Office PowerPoint 2010, pptx files from network can only open in read-only mode, in spite of the FileSecure access right on the file. This is only applicable for non-mapped network drive.

------------------------------
FileSecure 2.22.1.0
FileSecure Desktop Client 2.16.1.0
Jan 21, 2011

   Bug Fixes:

   1. Word/Excel/PPT and Foxit takes long time to start when Microsoft Firewall Client for ISA Server is installed. (#866, #867)
   2. Other bug fixes: #902, #912.

------------------------------
FileSecure 2.22.0.0
FileSecure Desktop Client 2.16.0.0
Jan 04, 2011

   Features:

   1. Support for multi-lingual Desktop Client. (#743)
      a. This version of Desktop Client only supports German (de-DE) language other than English (en-US).
      b. There is a single installer for German and English support. All the screens of Desktop Client Installer are in English. User can choose preferred language on first screen of Installer.
      c. Support of only one language can be installed on the machine at a time. Different users on the machine do not have option to install Desktop Client with different language support, as Desktop Client is installed at machine level. To change the language, user need to re-install the Desktop Client.
      d. Existing installation of Desktop Client will be upgraded to support only English language.
      e. Additional components like AutoCAD Plugins etc do not support multiple languages hence messages shown by these components are shown in English, but whenever these component will start supporting Desktop Client language, they will be automatically upgraded to support same language as DC.
      f. User will see Policy Server pages as per the locale set in the browser. User may see Policy Server pages in English or language other than Desktop Client if his browser language is different than Desktop Client.
      g. User may see some messages in English if Desktop Client is connecting to older version (previous to FileSecure 2.22.0.0) of Policy Server.
      h. User may see some messages in English if Desktop Client language is not supported by Policy Server he is connecting to.
      i. SciTE supports only English language. Files with special characters (non-ASCII) in file name or file path cannot be opened in SciTE. It can open files with content in languages other than English.
      j. User may see OK/Cancel/Retry/Continue/Ignore etc. buttons in message box as per the Language Interface Pack installed on the base Operating System. Similarly, dialogs like Print Page Setup, Printer Preferences and few other windows may be seen as per the Language Interface Pack of the base Operating System.

   Bug Fixes:

   1. Protected files with special (non-ASCII) characters in file does not open in OpenOffice. (#818)
   2. Internet Explorer proxy settings are not reset (if different than System Tray proxy settings) if user tries to login using System Tray and closes the authentication window by pressing ESC key. (#879)

------------------------------
FileSecure 2.21.0.0
FileSecure Desktop Client 2.15.0.0
Dec 10, 2010

   Features:

   1. Support for 64-bit Windows 7 operating system. This release does not include support for opening protected document in 64-bit version of existing applications. (#397)
   2. Provide an option to show/hide Access Permission window, shown after opening document. (#717, #764)
   3. Migrated installer to InstallShield 2011 from InstallShield 2010. (#740)
   4. Apply upgrade patches if proxy is set in User Preferences but proxy is not required to connect to upgrade server. (#817)

   Bug Fixes:

   1. Starting a new instance of MS Word/Excel/PowerPoint takes long time. (#612)
   2. Switching between documents in Office XP/2003 takes long time. (#778)
   3. Remove prompt to remember user session with Policy Server and download offline license while opening file. Instead of these prompts, an option is provided on authentication window where user can select whether user is working on his machine or not. (#742, #802)
   4. Extra files added using upgrade patch do not get removed on uninstallation of FileSecure Desktop Client. (#763)
   5. Foxit application becomes default PDF file editor for all PDFs after installing FileSecure Desktop Client hence unprotected PDF files also opens in Foxit. (#757, #790)
   6. Grammar and sequence of messages are incorrect in Detect and Repair report. (#725)
   7. Clicking on button added by FileSecure extension in OpenOffice shows error message. (#811)
   8. Access Permission window in not displayed to user when PDF file is opened in IE 8. (#812)
   9. Protected BLANK (0 size) MS Word 2007 document (docx) does not open. (#836)   
   10. Application hangs when user tries to capture screen or initiate RDP session and protected document is open on Windows 7. (#760)
   11. Unprotected PDF file is saved as protected when user opens one or more protected and one unprotected document, edits unprotected document and closes all documents. (#848)
   12. Show error message before disconnecting RDP session when protected document without SCREEN CAPTURE permission is open on host machine. (#546)
   13. User can capture screen of remote machine in between RDP session is started by user and disconnected by FileSecure Desktop Client when protected document without SCREEN CAPTURE permission is open on remote machine. (#808)
   14. Dameware hangs while connecting to remote machine after remote connection is disconnected by Desktop Client because protected document without SCREEN CAPTURE permission is open on remote machine. (#849)
   15. Desktop Client tray icon vanishes when explorer in terminated and restarted. (#797)
   16. Remove all confirmation messages in Desktop Client Tray. (#803)
   17. Lock icon in not shown for protected file in explorer when more then 10 Icon Overlay are registered. (#805)
   18. Shortcuts for FIEdi and Foxit are missing when upgraded through patch. (#847)
   19. Normal.dot and other templates do not get renamed after executing Detect and Repair. (#845)
   20. Print Screen Monitor, Desktop Client Tray, FileSecure Assistant exe and Upgrade Client does not start on executing Detect and Repair if instance of this exe is already running in another session. (#846)
   21. Other issues fixed in this release are #267, #795, #808, 

------------------------------
FileSecure 2.20.2.0
FileSecure Desktop Client 2.14.2.0
Nov 01, 2010

   Features:

   1. Provided following options in Context Menu: Activate File, Inactivate File, Transfer Ownership. (#454)
   2. Facility to have buffer file more than 60K. Max. allowed buffer file size is 1020K. (#759)

   Bug Fixes:

   1. User is not able to edit User Preferences if User Preferences file is Read-Only (Read-Only attribute is set). (#787)
   2. System Tray crashes if common User Preferences and user's User Preferences file does not exist. (#787)

------------------------------
FileSecure 2.20.1.0
FileSecure Desktop Client 2.14.1.0
Sept 29, 2010

   Bug Fixes:

   1. If two Policy Server profiles are present on a user's machine, one which requires proxy and other does not, it requires a change in Proxy Setting in System Tray. (#741)
   2. Change in IE proxy settings (in IE browser) is not automatically reflected, whenever Desktop Client uses IE settings to connect to the Policy Server. (#571, #738, #754)
   3. Foxit Reader is not digitally signed hence issues warning at times, on Windows 7 machine.(#773)
   4. Opening large files takes a lot of time. (#691, #694)
   5. Foxit Reader hangs in case user have IE8 and Win XP and trying to open file while not logged on domain (when it requires explicit authentication).(#776, #779)

------------------------------
FileSecure 2.20.0.0
FileSecure Desktop Client 2.14.0.0
Sept 03, 2010

   Features:

   1. Support For Windows7. This includes support for the following application on Windows7 - 
         a. MS Office 2007 - Office 2007 and 2003 file formats
         b. MS Office 2003 - Office 2003 file formats
         c. Open Office    - Open Office, Office 2007 and 2003 file formats
         d. Foxit Reader   - pdf format. (#362, #391, #392, #425, #616)
                           - Rich annotation features.
                           - Support for opening links to protected/unprotected files. 
                           - Support for opening protected pdfs within Internet Explorer. 
         e. FIEdi          - Supports multi-page tiff file in addition to other supported image file formats.   (#350, #393)
         f. SCiTE          - Text formats

         ** Adobe Reader and MS Paint is not supported on Windows7, though it's support will continue on Win XP in addition to Foxit Reader and FIEdi.
         (#350, #391, #392, #393, #396, #425, #616)
   2. Support for E-mail Plugin - SecureSend as part of the core product. This includes support for Microsoft Outlook 2003 and 2007. (#512, #670, #674, #675, #676, #677, #678, #679)
   3. Smarter Desktop Client Installer which includes -
         a. Proactively validating user desktop environment.
         b. ISScript1050.msi is not a pre-requisite to install Desktop Client. (For installers for any additional components it will still be required).
         (#379, #510, #576, #594)
   4. Detection of conflicting softwares. Desktop Client proactively detects any software on user's desktop which might hinder smooth working of Desktop Client. 
      Conflicts are classified into two categories - 
         - Fatal : In case a conflict is classified as fatal, Desktop Client will stop working i.e. no protected documents will open. 
         - Warning : In case of warning, it just shows a warning. (#576, #680, #692)
   5. Richer and informative message displayed when user does not have access to a file. (#421)
   6. Tool for system analysis for better diagnosis of issue.
   7. Prompts error if required components for upgrade are not running, when "Check for Updates" is clicked. (#659)
   8. All executable code is digitally signed by Seclore to avoid any malicious intrusion.

   Bug Fixes:

   1. User cannot login with valid credentials from System Tray, once an invalid credential is provided or the authentication dialog is cancelled, unless user exits System Tray. (#333)
   2. Authorized PRINT activity is logged instead of unauthorized PRINT when user without PRINT access prints file from MS Paint or Adobe Reader.
   3. Conflict message is shown in MS Office, even if correct Office plugin is registered. (This is the case typically when multiple office versions are present on the machine).
   4. Open Office plugin is not re-registered by Detect and Repair utility.
   5. Incorrect options shown on right click of protected file in "Open With". (#640)
   6. After launching About FileSecure from system tray, Check for Updates and Detect and Repair dialog goes in the background. (#530)
   7. Secure Send button remains (with no action) even after uninstalltion for SecureSend addon (which is now part of the core product).
   8. Profile name is not shown properly in System Tray, when user session expires and Profile is not saved.
   9. User is prompted to close all protected documents in Excel even after closing all protected documents. This happens when user creates a new document and saves it in presence of protected documents.
   10. Macros launched on events like button click are not controlled through macro access right. (#605)
   11. Double click of excel document prompts for "Save as" dialog, when Microsoft convertor is installed on the machine. (#607)
   12. Installation of Desktop Client takes a long time with no feedback to the users, when it is upgrading the patches. (#252)
   13. 'Content has been modified without permission' error is shown when two copies of same excel file are opened. (#372) *

   * Actually fixed in Desktop Client release 2.13.1.0
   
------------------------------
FileSecure 2.19.3.0
FileSecure Desktop Client 2.13.3.0
Aug 05, 2010


   Bug Fixes:

   1. Lotus Notes Client (ver 8.5.0) conflicts with FileSecure Desktop Client at startup. (SUPPORT ID#636)

------------------------------
FileSecure 2.19.2.0
FileSecure Desktop Client 2.13.2.0
July 15, 2010


   Bug Fixes:

   1. Multiple Office files does not open when user opens files by double clicking. (SUPPORT ID#628)


------------------------------
FileSecure 2.19.1.0
FileSecure Desktop Client 2.13.1.0
May 25, 2010

   Features:

   1. Support for Open Office 3.2. (SUPPORT ID#565)
   2. Optimized the check for screen capture rights. (SUPPORT ID#564)

   Bug Fixes:

   1. Unable to open MS Office FileSecure protected files without edit rights, from network. (SUPPORT ID#542, #597, #573)
   2. Protected excel file, with edit rights, when opened from the network, resulted in file header being corrupt in remote cases. (SUPPORT ID#570)
   3. User is not able to open MS Office files after executing Detect and Repair tool in MS Office 2007. (SUPPORT ID#572)
   4. Buffer file is shown, when second protected file is opened in Open Office. (SUPPORT ID#601)

------------------------------
FileSecure 2.19.0.0
FileSecure Desktop Client 2.13.0.0
Apr 30, 2010

   Features:

   1. Support for viewer application to view AutoCAD files. (Prerequisite: AutoCAD Design Review 2010 must be installed) 
   2. Provided a framework for smoother integration of new applications with Desktop Client. (SUPPORT ID#561)
   3. End user will get an option to open protected file in any of  available editors supported by FileSecure (Right click - FileSecure Open With will be available).
   4. At the time of installation, there is an option to specify the default editor for a group of file type like txt, MS Office, OpenOffice, image and pdf. This will override the default behavior of file association with editors.

   Bug Fixes:

   1. After installing FileSecure Desktop Client, unprotected text files open in SciTE and not the application which user has chosen.
   2. After installing FileSecure Desktop Client, unprotected PDF files open in Adobe Reader and not the application which user has chosen.
   3. User level association of text and PDF files are reset once user logs off and login.
   4. Second excel file gets corrupted when two copies of protected file (two protected files with same file identifier) without EDIT permission are opened one by one in Microsoft Excel. (SUPPORT ID#547)
   5. Hidden logs files generated for each application (process).
   6. User is not able to Open File as different user after executing Detect and Repair. (SUPPORT ID#568)
   7. If proxy details are changed on the machine, it does not automatically get reflected in Upgrade Client till
      user logs in again.

------------------------------
FileSecure 2.18.0.0
FileSecure Desktop Client 2.12.0.0
Mar 19, 2010

   Features:

   1. Provided a framework for dependent components of Desktop Client to be installed, repaired and uninstalled neatly. (SUPPORT ID #500)
   2. Richer 'About' information of FileSecure and Desktop Client in a window based dialog.
   3. Improved Detect and Repair, which takes care of repairing dependant components.

   Bug Fixes:

   1. Unable to upgrade Desktop Client, in case proxy is required to connect to the portal having patches. This is in case user has asked to use IE settings.(SUPPORT ID #422)
   2. Unable to open IE browser control from Open Office. (SUPPORT ID #472)
   3. Changed default port of Desktop Client Service to 5002.
   4. Issue resolved for punctuation mark. (SUPPORT ID #263)

------------------------------
FileSecure 2.16.0.0
FileSecure Desktop Client 2.11.0.0
Jan 22, 2010

   Features:

   1. Support of Microsoft Office XP file format. Note :: Office XP with Service Pack 2 should be installed on the machine, to 
   open PPT files in XP).
   2. Open office plugin installation is done as a part of the core installer. No separate installer is available for it, from this release onwards.
   Application(s) supported by Desktop Client is based on the License deployed at the server end. By default supported applications 
   are - Acrobat Reader, Acrobat Professional, MS Paint, Microsoft Office 2k3 and 2k7. All other supported applications require explicit license.

   Bug Fixes:

   1. Print Screen is enabled during remote session using Mini Control DameWare. (SUPPORT ID #267)
   2. Buffer file is shown in excel, if already open protected file is again dropped inside excel.
   3. Invalid activity comments are being sent to Policy Server, while opening a file on remote system.
   4. User can extract protected data by choosing option File->New and create from existing. (SUPPORT ID #346)
   5. User can Drag & Drop/insert object protected document inside unprotected documents and extract data.
   6. Files protected by Desktop Client cannot be opened by Web Services - To make Desktop Client compatible with Web Services Client, 
   encryption key length has been changed. Note :: Files protected using this DC release (onwards) cannot be opened by DC release 
   prior to 2.9.0.0.

------------------------------
FileSecure 2.15.0.0
FileSecure Desktop Client 2.10.0.0
Dec 24, 2009

   Features:

   1. User has an option to have more granular control over the file, while defining credentials. The new access rights which
      are part of this release are (#184) - 
         a. Screen Capture - This allows the FileSecure protected file to be opened on VM, RDP Or any other software which allows remote session. 
            This allows to capture screen through Print Screen key.
         b. Copy Data - Allows data of FileSecure protected file to be copied outside.
         c. Allow Macro - Allows to define and run macro for a FileSecure protected file.

   Bug Fixes:

   1. Desktop Client Service is not able to start if the default port (5000) is not available on a certain machine. To take care of this 
      now it tries to start itself on next 1000 ports till 6000.
   2. SciTE opens all text files in the folder, if it encounters any special un-readable character in the filename like Japanese character.
   3. Print Screen Monitor stops when Desktop Client service is stopped. This also stops the directory watcher on system for
      outlook folder to make protected files, Read-Only. To avoid this a new component has been added as - FileSecureAssist.
   4. Application hangs if protected document is open and Desktop Client Service is stopped.
   5. MS Office application crashes when last dirty document is closed and file path is very long.
   6. Disable CloseAll option and MailMerge related options in MS Office plugins.

------------------------------
FileSecure 2.14.1.0
FileSecure Desktop Client 2.9.6.0
Nov 30, 2009

   Bug Fixes:

   1. Opened shared file in READ-ONLY mode, which is opened(locked) by another user for editing. This solves multiple issues related to 
   opening files on the network like able to save file as unprotected and even application hanging.
   2. Opening and editing protected network file through complete Universal path unprotects files in office and all applications, if the network drive is mapped.
   3. Calling SaveAs instead of Save in SaveALL, when user has opened a Read-Only file with FileSecure edit access.
   4. Right click and performing Ctrl+C crashes the xls, doc files at times.
   5. Office 2007 documents were crashes in full mode.
   6. Installer - User unable to install Desktop Client, without addon option, in an interactive mode.
   7. Installer - Setup.exe prompts for upgrading the Desktop Client and then make the installation corrupt, when DC already installed.

------------------------------
FileSecure 2.14.0.0
FileSecure Desktop Client 2.9.5.0
Nov 20, 2009

   Features:
 
   1. User is allowed to lock a protected file to a machine, on first time use.

   Bug Fixes:

   1. Upgraded Detect and Repair Utility to 
         a. Register Upgrade Service. 
         b. Register Upgrade Client. 
         c. Change name of Desktop Client Service. 
         d. Register System Tray. 
         e. Enable Office Plugin.
   2. Second URL is not saved if three URL(s) are specified while adding/editing Profile, in System Tray. (SUPPORT ID: #279)
   3. Dialogs and messages displayed from FileSecure Desktop Client are not focused by default. They appear in the background. (SUPPORT ID: #274)
   4. Access Permission Dialog, during file opening is showing incorrect offline validity date. (SUPPORT ID: #286)
   5. Activities performed on the protected file in offline mode are not logged in the Activity Log. (SUPPORT ID: #288)
   6. Upgrade service takes 100% CPU and crashes while multiple instance of upgrade client running.  (SUPPORT ID: #266)
   7. When a URL is accessed from a protected excel document, it hung the application and later on crashed. Same is the case when unprotected excel is accessed 
   from a protected word document. (#339)
   8. Password protected office files are getting corrupt when edited and saved in Office 2007. This release does not allow to save password protected file. 
   9. Template files have been changed to show Anonymous user instead of Abhijit Tannu in case opened on shared folder, by multiple users.(SUPPORT ID: #316)
   10. Some machines hang after reboot if FileSecure Desktop Client is installed. Upgraded madCHook library for this. (SUPPORT ID: #262)
   11. On some of the machine Xerces.dll is not found compatible with MSVCR80.dll and due to this FileSecure executables are not able to start. This is fixed by embedding manifest file in Xerces itself. (SUPPORT ID: #289)
   12. Excel crashes if base file is closed after opening embedded excel file, w/o closing embedded excel file. This is happening for unprotected documents. (SUPPORT ID: #329)

------------------------------

FileSecure 2.13.1.0
FileSecure Desktop Client 2.9.4.0
Oct 26, 2009

   Bug Fixes:

   1. Unprotected files get protected when unsaved unprotected file and 
   protected file is open and user quits Excel 2003 and saves unprotected file 
   when asked.
   2. Disable following options in Office2003: Send E-mail, Move or Copy Sheet, Insert Hyperlink etc.

------------------------------
FileSecure 2.13.0.0
FileSecure Desktop Client 2.9.3.0
Oct 9, 2009

   Features:
 
   1. Allow documents with FULL_CONTROL to execute macros, mail merge feature and VBA environment.
   2. At repository level, there is an option to specify whether user session is to be preserved or not, in the System Tray.

   Bug Fixes:

   1. Bug in creating logger. Also write FFFE as first two bytes so log file can be recognized as UNICODE files.
   2. Installer waits for starting the DC service infinitely, which hangs the installation process, in case DC service 
   is not able to start.
   3. When the same installer is used to install DC (on an already installed system), it corrupts the DC installation.
   4. Only buffer file is received if protected file stored on network is sent as attachment of mail using MS Outlook 2003.

------------------------------

FileSecure 2.12.2.0
FileSecure Desktop Client 2.9.2.0
Oct 1, 2009

   Bug Fixes:

   1. Read-Only XLSX files does not open in Microsoft Excel.

------------------------------

FileSecure 2.12.1.0
FileSecure Desktop Client 2.9.1.0
Sept 29, 2009

   Bug Fixes:

   1. Attachment when directly opened from outlook mail client gives an error, when opening file in an exclusive mode. Also at startup, even if system wide injection fails, Print Screen Monitor starts up.
   2. After registering FileSecure Microsoft Office plugin with word application, it stops even starting up. The error says that the user needs to install office.
   3. Policy Server API is not using bypass proxy settings set by Internet explorer.
   4. Adding functions to get current version of word, excel, PPT and outlook from registry.

------------------------------

FileSecure 2.12.0.0
FileSecure Desktop Client 2.9.0.0
Sept 18, 2009

   Features:
   1. Use browser dialog for authentication on portal.

   Bug Fixes:
   1. After opening a view-only office document, Ctrl+C and Ctrl+V command gets disabled on the windows explorer window.
   2. In Microsoft excel sheets, copy from a cell and pasting into another cell of a different excel sheet is not possible, even with full control rights of the excel files.
   3. User is not able to change print area using Drag & Drop feature.
   4. Microsoft Office plugin is getting disabled, if the user opens any office file, after DC installation and before re-start of the machine.
   5. Protected document opens from remote session if remote session is started after starting application.
   6. In SciTE, even the unprotected do not open, if remote session is running.
   7. FSDCTray gives error(-3) on first time system re-start, after installation.
   8. FSDCTray crashes when deleting a profile and while importing same profile to replace existing profile.
   9. Print Screen is enabled while remote session using Ultra VNC.

------------------------------

FileSecure 2.11.0.0
FileSecure Desktop Client 2.8.0.0
Aug 14, 2009

   Features:
      - Display File Name, File Identifier, Classification, Owner in Access 
      Permission Dialog.
      - System Tray component added to Desktop Client. FileSecure Desktop Client(FSDC) 
      System Tray is a utility which is used configure connection settings to connect to 
      different Policy Servers for protecting and opening files. Removed utility to 
      configure User Preferences.
      - Added feature to upgrade FileSecure Desktop Client components automatically. Even at the time of
      installation components are upgraded to the latest version. User also has an option to update on
      demand.

   Bug Fixes:
      - Stored expiry of Evaluation release in a separate file. 
      - User Preferences does not allow user to enter proxy username and password,  
      if user chooses to use proxy settings from Internet Explorer.
      - User is not able to capture screen in EVAL release even after setting 
      correct registry value.
      - Excel sets Read-Only flag of file if file is opened in MS Excel and 
      user does not have EDIT permission.
      - MS Paint deletes the file if user does not have EDIT permission and 
      overwrites the file in SaveAs operation.
      - Creates offline license file only if user has offline permissions.
      - Microsoft Excel hangs while opening protected xls file with macro.
      - User Preferences file gets corrupted after removing a Profile.
      - Shows 'abhijit.tannu' as author of protected PDF file in explorer.
      - Word documents give access permission error, in case, the document is dirty while saving.

------------------------------

FileSecure 2.10.3.0
FileSecure Desktop Client 2.7.4.0
July 28, 2009

   Bug Fixes:
      - 'Desktop Client Service' does not stop gracefully.
      - User is not able capture screen if 'Print Screen Monitor' is not running.
      - Print Screen Monitor was not able to start on certain machines, which was slowing down the full system.
      - Microsoft Excel 2003 and 2007 shows error if user exits Excel after opening protected 
      document and closing all protected documents.
      - Microsoft Office 2003 and 2007 plugin does not reset the menu controls even when no protected
      document is opened.
      - Microsoft Office 2003 and 2007 plugin does not re-authenticate, if the last document is a protected
      document and it is re-opened again.

------------------------------

FileSecure 2.10.2.0
FileSecure Desktop Client 2.7.3.0
July 17, 2009

   Bug Fixes:
      - Protected .doc and .ppt files get truncated when sent as attachment using Microsoft Outlook.
      - Processes crash when FileSecure Desktop Client is installed.

------------------------------

FileSecure 2.9.1.0
FileSecure Desktop Client 2.7.1.0
Jun 08, 2009

   Bug Fixes:
      - SAP application runs slow if FileSecure Desktop Client is installed.

------------------------------
FileSecure 2.9.0.0
FileSecure Desktop Client 2.7.0.0
May 25, 2009

   Features:
      - Support for HotFolder Server.
      - Support for OpenOffice file formats.
      - Allow user to print unsaved document if user has EDIT permission.
      - 'Detect and Repair' utility displays list of activities performed.

   Bug Fixes:
      - If Classification identifier contains multiple characters, it sends only first character to Policy Server while protecting file.
      - User can not convert unprotected MS Office file to PDF using Adobe Profession Pro.
      - Displays console windows when 'Detect and Repair' utility is run.
      - User is not able to capture screen after closing all protected Word documents.
      - Microsoft Word does not quit when user chooses File -> Exits or exits Word using Top-Right cross button.

------------------------------

FileSecure 2.8.0.0
FileSecure Desktop Client 2.6.2.0
Apr 15, 2009

   Features:
      - Added feature to import Profile(s) from User Preferences (.fsp) file to Preferences files for the that user on a particular machine.

   Bug Fixes:
      - Protected files stored on network does not open in Microsoft Office 2007.
      - Prints junk data when protected Microsoft Office files are printed with spooling.
      - Protected Open Office file are treated as corrupt files.
      - Send activity logs when application exits.
      - File content are lost when file stored on network is protected.
      - Microsoft Word quits when user closes last document.

------------------------------

FileSecure 2.7.0.0
FileSecure Desktop Client 2.6.1.0
Mar 16, 2009

   Bug Fixes:

      - The system was hanging a couple of time for Microsoft Office documents (2003 & 2007).
      - For Microsoft Office documents, SaveAs option saved file in in-correct format.
      - Changed Microsoft Office 2003 Plugin for 
         - Disabled 'Research' functionality in Word, PowerPoint.
         - BUG: Save PPT file as 'Presentation for Review' and save as 'Design Template', 'Design Template' file becomes unprotected and original file becomes corrupt.
         - BUG: Save PPT file as 'Outline/RTF' and save as any other format, new file becomes unprotected.
         - Disabled Compare functionality, if any protected document is open.
         - If file does exist, do nothing in BeforeClose and AfterOpen.
         - Size of PPT file increases after saved as copy.
      - Changed Microsoft Office 2007 Plugin for
         - Disabled AutoRecovery.
         - Disabled Compare functionality, if any protected document is open.
         - Controls do not get enabled when last protected document is closed.
         - Enabled 'Create Handout' for FULL CONTROL access only.
         - If file does exist, do nothing in BeforeClose and AfterOpen.
         - Size of PPT file increases after saved as copy.
   
------------------------------

FileSecure 2.6.0.0
FileSecure Desktop Client 2.6.0.0
Feb 27, 2009

   Features:
      - Support for Microsoft Office 2007 file formats.
      - De-support for Office Template, Office Add-In, WK, dBASE, log, PostScript files.

   Bug Fixes:
      - Shows error while protecting file, if 'Supported File Extension List' file is not multiple of 2.
      - Renamed 'Diagnosis Utility' to 'Detect And Repair'.
      - Changed 'Detect And Repair' utility register correct office plugin depending on installed office version.
      - Changed 'Print Screen Monitor' to remove association of files.
      - Changed 'Detect And Repair' to remove association of files.
      - Changed 'Detect And Repair' to delete Office 2007 global template.
      - Changed 'Installer' to register correct office plugin depending on installed office version.
      - Changed name of shortcut to 'Detect And Repair' utility.
      - Disabled required controls in Microsoft Office 2003
      - If protected document is opened in PowerPoint, menus become non clickable.
      - Error '2' is shown when linked file is opened.

------------------------------

FileSecure 2.5.6.0
FileSecure Desktop Client 2.5.5.0
Feb 16, 2009

   Features:
      - Changed date format in 'Access Permissions' dialog.
      - Changed 'Diagnosis Utility' to take care of following: 1) Renaming 'Normal.dot' 2) Set value of 'ToolbarConfigSaved' to '0'.

   Bug Fixes:
      - User name is not displayed on 'Access Permission' dialog.

------------------------------

FileSecure 2.5.5.0
FileSecure Desktop Client 2.5.4.0
Feb 10, 2009

   Bug Fixes:
      - System crashes while showing 'Access Permission' dialog, if logged in user in not domain user.
      - After installing FileSecure Desktop Client does not open with currently associated application.

------------------------------

FileSecure 2.5.4.0
FileSecure Desktop Client 2.5.3.0
Feb 09, 2009

   Bug Fixes:
      - Display time for offline access permissions in 'Access Permissions' dialog.
      - Do not protect or unprotect if file is open by another process.

------------------------------

FileSecure 2.5.3.0
FileSecure Desktop Client 2.5.2.0
Feb 09, 2009

   Features:
      - Added facility to edit credential in 'Protection Details' dialog.
      - Removed 'Authentication in Progress' message box while user authentication is used for authentication. In case of other web browser, diff. dialog is shown where user needs click on 'Authenticate' button to start authentication and 'Complete Authentication' when authentication is completed.
      - Display users permission when user opens the document.
      - Image files are not associated with 'Image Editor', so user need to user Context Menu to open protected image files.
      - User is not asked to save offline permissions when user unprotects the file.
      - SciTE remembers 'Wrap' options.
      - User is redirected to help page on Policy Server when he clicks on 'Help' in 'Protection Details' dialog.

   Bug Fixes:
      - Show error is PDF reader in not installed.
      - Read-Only attribute is ignored while protecting or unprotecting the file.
      - Updated Buffer Files to include that if user see the Buffer File, he should user Context Menu to open the file.
      - Changed image to display error message when user captures screen when   protected document is open.
      - Offline activities are not logged.
      - Acrobat Reader hangs when file is saved as Text file.
      - If document is not dirty, user is not shown error when user saves the   document.
      - 'User Preferences' crashes when user click on 'Test Connection' and Application Name is missing in URL. 
      - User is not able to see protected file in Acrobat Reader while scrolling.

------------------------------

FileSecure 2.4.2.0
FileSecure Desktop Client 2.4.2.0
Jan 22, 2009

   Bug Fixes:
      - Icons of text, image and PDF files are retained to original icons.

------------------------------

FileSecure 2.4.1.0
FileSecure Desktop Client 2.4.1.0
Jan 21, 2009

   Bug Fixes:
      - PDF and Image file does not open if authentication takes more than 30-40 seconds.

------------------------------

FileSecure 2.4.0.0
FileSecure Desktop Client 2.4.0.0
Jan 20, 2009

   Features:
      - Provided utility for cleanup.

   Bug Fixes:
      - Converted 'PDF Editor' into Win32 Application so it does not show console while opening PDF file.
      - Converted 'Image Editor' into Win32 Application so it does not show console while opening Image file.
      - Converted 'Print Screen Monitor' into Win32 Application so it does not show console.
      - Converted 'Desktop Client Executable' into Win32 Application so it does not show console.
      - 'Print Screen Monitor' wait to complete injection of 'Common Library'. 
      - Removed various options from 'Options' and 'About' menu from SciTE.
      - Validate URL before preparing 'ServerInfo' in 'Interface Library'.
      - Display proper error message if user does not have permissions to unprotect file in offline mode.
      - Disable 'Refresh' button on 'Protection Details Dialog' once user click the button.
      - Removed 'Buffer File' for .ico as we are not supporting .ico files.
      - Update 'Buffer Files' to include various reasons why user will see the content of 'Buffer File'.
      - Enable 'Screen Capture' if 'Remote Connection' is enabled.
      - While checking for system wide injection, not checking for 'DiCryptoSys' and 'Xerces' library.
      - Display standard title in message if title is not specified.
      - Validate URL before adding 'Profile' in 'User Preferences'.
      - Ignore error while injection 'Common Library' if DLL initialization is failed.
      - If 'Common Library' is detached from process and process is still running, do not terminate the process.
      - Release API lock before calling clipboard and printing related system APIs and acquire after API returns.
      - Return error if fails to get file information in 'IDocumentOpened'.
      - Not hooking 'OpenPrinterW' and 'OleSetClipboard' APIs.
      - Delete installation folder while uninstalling.
      - Display proper error message if user opens protected file and 'Service' has not run once on the machine.
      - Validate content of file while unprotecting only if 'Content Validity Flag' is set.
      - Do not calculate padded count in 'IDocumentOpened' if 'Content Validity Flag' is set.
      - Changed icons for Text, PDF and Zipped Log files.
      - Optimized and revamped Microsoft Office 2003 plugin.

------------------------------

FileSecure 2.3.0.0
FileSecure Desktop Client 2.3.0.0
Jan 02, 2009

   Features:
      - User can test profile while adding using 'User Preferences'.
      - User can connect to Profile using 'User Preferences'.
      - Log files are zipped daily. Also provided utility to unzip zipped logs.
      - Associated text files with SciTE.
      - Deprecated support for .ico file as 'MS Paint' does not support it.

   Bug Fixes:
      - Protected PDF and Image file are associated with new editors so they open from Outlook etc.
      - Issue in logging activity because of invalid date.


------------------------------

Dec 26, 2008
FileSecure Desktop Client 2.2.0.0

   Bug Fixes:
      - Compatibility no. is included in offline license file.
      - User Preferences crashes if user clicks 'Cancel' first time without doing anything and runs second time.

------------------------------

Dec 23, 2008
FileSecure Desktop Client 2.1.0.0

   This is first release of FileSecure as well as Desktop Client.