Change Control 8.x Known Issues

Product release information

To review the release notes, visit the Product Documentation site.

Version	Build Number	General Availability
8.3.2 (GA)	133.2	October 13, 2020
8.3.1 (GA)	124.2	August 25, 2020
8.3.0 (GA)	303.2	March 24, 2020

8.2.6 (GA)	141.3	March 24, 2020
8.2.1.435 (Repost)		September 25, 2019
8.2.1.114		October 2, 2018
8.2.0		August 14, 2018

8.1.0		April 24, 2018
8.0.0		December 12, 2016

Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.

Change Control 8.3.x known issues

CRITICAL: There are currently no known critical issues.

Non-critical

Reference	Related Article	Found in Version	Resolved in Version	Description
MACC-10318	-	8.3.2	-	Issue: Windows version 20H2 installation fails when the Application control is in the Enable Mode. Workaround: Add the updater rule from ePolicy Orchestrator (ePO) or the client, and then install Windows. sadmin updaters add -p services.exe “\Program Files\Common Files\microsoft shared\ClickToRun\OfficeClickToRun.exe”
MACC-10313	-	8.3.2	-	Issue: When Change Control is upgraded from version 8.0.2 to 8.3.x and rebooted, the client upgrade status remains as reboot needed.
MACC-10311	-	8.3.2	-	Issue: In rare cases, the installation of binaries stops for an indefinite period when Package Control and the antivirus service are enabled on the system. Workaround: From the ePO or client, configure the passthrough process for Antivirus Service in Solidcore. Example: In Windows Defender, add the rule below: sadmin attr add -p MsMpEng.exe After the passthrough process for antivirus is configured, reboot and run the installer again.
MACC-10327	-	8.3.2	-	Issue: Incorrect offset calculation can sometimes lead to a bugcheck on Windows 8.1 and Windows 10 x86 systems.
MACC-10295	-	8.3.2	-	Issue: When a client task for enable is triggered from ePO, the Solidcore client doesn't receive the enable task from McAfee Agent (MA). Also, sometimes, the command-line interface stops. Workaround: To resolve the issue, set the "MaplErrorHandlerEnabled=0" configuration from ePO or on client, and restart the enable task.
MACC-9939	-	8.3.1	-	Issue: One of the Solidcore.log files is displayed as "soli.log" in the %programdata%/McAfee/Solidcore path.
MACC-10041	-	8.3.1	-	Issue: The "Access Denied" message is displayed at the first attempt when you try to move the bat script file from a removable or unremovable drive that has skiplist -v applied. Workaround: Second attempt allows moving of the bat script.
MACC-10035	-	8.3.1	-	Issue: In Windows 7, when Change Control is upgraded from 8.0.2 to 8.3.1, the reboot process takes more than 3 minutes.
MACC-8746		8.3.0.225	-	Issue: Wrong copyright string for Extension build 8.3.0.225.
MACC-8891		8.3.0.225	-	Issue: After the Solidcore standalone installer (InstallShield) is run, the End User License Agreement (EULA) page in the InstallShield wizard displays "EULA (April 2017)".
MACC-8574		8.3.0.225	-	Issue: In the Inventory mode, when the "SC Begin Update mode" and "SC Observe mode" ePO client tasks are executed, the task takes some time to complete. The reason is because the inventory reconciliation is automatically executed in advance and the time taken is based on the number of files with mismatches, such as checksum, types, etc. Recommendation: Check that the Begin Update or Observe mode tasks are completed before the reboot.

Change Control 8.2.x known issues

CRITICAL: There are currently no known critical issues.

Non-critical

Reference	Related Article	Found in Version	Resolved in Version	Description
	KB92081	8.2.1.435		Issue: Application Control reports 8.2.1.407 on Swin.sys when 8.2.1.435 (Update 5 Repost) is installed.
1250277		8.2.0		Issue: Enabling the Application Control license with limited activation or the Change Control license results in a crash after upgrading from 8.1.0.179 to 8.2.0.140.
1256220		8.2.1		Issue: The Solidcore installation folder isn't removed after the Uninstall Task.
1256249		8.2.0		Issue: Some Tasks in the Server Task Log remain in Waiting status indefinitely after executing different operations. This action causes all other tasks executed after that to remain in Waiting status as well. Workaround: To be allowed to perform Server Tasks, restart ePolicy Orchestrator services using these steps: Stop the ePO services: Click Start, Run, type services.msc, and click OK. Right-click the following services and select Stop: McAfee ePolicy Orchestrator x.x.x Application Server McAfee ePolicy Orchestrator x.x.x Server McAfee ePolicy Orchestrator x.x.x Event Parser Start the ePO services: Click Start, Run, type services.msc, and click OK. Right-click the following services and click Start: McAfee ePolicy Orchestrator x.x.x Application Server McAfee ePolicy Orchestrator x.x.x Server McAfee ePolicy Orchestrator x.x.x Event Parser
1257561		8.0.0		Issue: When trying to import a group of rules on the Solidcore Rules page, the task fails and shows the message "Data with same key already exists in Database."
1259241		8.0.0		Issue: There's high memory usage of Tomcat after upgrading the Change Control ePO extension to version 8.2.1.
1259925		8.2.1		Issue: Files added to the 'my updater' process remain unsolidified after an upgrade to 7.0.1.462.
1260315		8.2.0		Issue: When adding a rule for executable files in an Application Control Rules policy for Windows, the rule can be created with three different rule types: Name, SHA-1, and SHA-256. After saving the rule with one of these types, you can no longer change the rule type. Workaround: Delete the rule and create it again with the other rule type.
1262809		8.0.0		Issue: After removing a user who is the owner of one or more Solidcore rules, if anyone tries to access the Solidcore Rules page, the message "An unexpected error occurred" is displayed.

Solidcore Extension

Reference	Related Article	Found in Version	Resolved in Version	Description
MACC-8694		8.2.6	-	Issue: Write-denied events are seen for .js files after the Windows upgrade.
MACC-9053		8.2.6	-	Issue: Copyright version for Change Control binaries is marked as 2019.
MACC-8695		8.2.6	-	Issue: After Solidcore is upgraded to version 8.2.6 in the "disable" mode and Change Control is enabled, the Solidcore upgrade property in ePO doesn't get updated. It shows the status as "reboot required" even after multiple reboots. NOTE: The issue occurs only if the upgrade is performed in the "Disable" mode.
MACC-8700		8.2.6	-	Issue: When Solidcore is upgraded to 8.2.6 and rebooted, the ePO Solidcore product version under system "Properties" doesn't display the upgraded product version. This issue is intermittent.
1239874		8.1.0	8.2.0	Issue: Default rule groups are removed after upgrading to Solidcore ePO Extension 8.1.0. Solution: Upgrade to Change Control 8.2.0 or later.
1241551		8.1.0	8.2.0	Issue: Policy Discovery events aren't displayed on the Policy Discovery page after events are sent from Endpoint. Solution: Upgrade to Change Control 8.2.0 or later.
1245623		8.0.0	8.2.0	Issue: When trying to import the inventory created as an XML file, the following error is displayed: "Inventory could not be imported." Solution: Upgrade to Change Control 8.2.0 or later.
1247758		8.1.1	8.2.1	Issue: An extension upgrade from Change Control 8.1.1 to another Change Control version fails in step 6. Solution: Upgrade to Change Control 8.2.1 or later.
1254921		8.2.0		Issue: When adding two or more Solidcore rules to an Integrity Monitoring policy for Windows, after saving the policy, only one Solidcore Rule is saved.
1255177		8.0.0		Issue: When Solidcore Client is enabled with Limited Activation in Observe Mode, the Solidcore Client Status is shown as "Observe" instead of "Observe (Limited)" in the Solidcore Client Status column from System Tree.
1255936		8.2.0		Issue: When adding a rule for updaters in an Application Control Rules policy for Windows or UNIX, the rule can be created with three different conditions: None, Library, or Parent. After saving the updater rule with one of the conditions (different to None), if the user tries to edit the rule, the None condition becomes selected by default. If it's saved again, it's saved as None. Workaround: When editing a rule, change the condition to the one selected originally before saving the policy.

Windows (all versions)

Reference	Related Article	Found in Version	Resolved in Version	Description
1247479		8.2.0		Issue: An upgrade from Change Control 8.1.0 to Change Control 8.2.0 in Windows 32-bit is failing Workaround: Disable MP-CASP before you upgrade to the latest version of Change Control.

Windows 8
There are currently no known issues.

Windows 2008 R2 (64-bit)
There are currently no known issues.

Windows 2008 (64-bit)
There are currently no known issues.

Windows 2008/Vista (32-bit and 64-bit), Windows XP/Windows 7/Windows 2008 R2 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
MACC-8375		8.2.1.114	8.2.1.435	Issue: Communication issues with MA 5.0.6 when Change Control 8.2.1.114 and VSE 8.8 are installed on Windows 7 and 2k8R2
1247171		8.2.0	8.2.1	Issue: Windows 7 endpoints turn into limited activation after sending a full activation task. Workaround: To make a full feature activation on Change Control 8.2.0 and later for Windows 7: Send an Enable task as a Limited Feature Activation. Restart the client.

Windows Vista
There are currently no known issues.

Windows 10
There are currently no new known issues.

Change Control 8.1.0 known issues

CRITICAL: There are currently no known critical issues.

Non-critical:

Solidcore Extension

Reference	Related Article	Found in Version	Resolved in Version	Description
607517				Issue: PDF reports have minor data display and formatting issues if more than 50,000 records are reported.
607908				Issue: It's not possible to export more than 50,000 records from any table or report.
607950				Issue: User-defined system variables in policies are resolved at the endpoint only after the endpoint is restarted.
608025				Issue: Reports, tasks, and policies for all SKUs are listed even if the license for that SKU isn't added.
608347				Issue: The Solidcore Policies Applied on Hosts report displays all policies derived from the root, regardless of the SKUs enabled on the platform.
608374				Issue: When you try to enable an already enabled Solidcore Agent, the error displayed isn't translated.
608390				Issue: When viewing an Integrity Monitor policy, the My Rules tab isn't translated.
608618				Issue: You try to upload a Windows Solidcore Agent Deployment Package that's larger than 100 MB to ePO through Microsoft Internet Explorer. But, the file upload times out if the network upload speed is slow. Workaround: Use Internet Explorer 7 or later, and if you encounter further issues, copy the package to a local directory on the ePO server. Then, access the ePO console on the ePO server and upload the file from the local path. This sequence avoids possible network delays.
608753				Issue: Sometimes, using the username field of reported events on the ePO server as a trusted user might not work if the client system is part of an Active Directory (AD) domain. The reason is because the domain name reported in the events isn't the full AD domain. Workaround: Use the environment variable USERDNSDOMAIN as the domain name for AD clients. Or, review the properties of the My Computer icon to identify the complete username to specify as the trusted user.
609304				Issue: It's not possible to export data from the Reporting, Solidcore Events page. Workaround: Use Queries (Reporting, Queries) to export event data.
636769				Issue: If you upgrade from Solidcore 5.1.0 to 5.1.1 or later, existing Solidcore events in the Solidcore Events table aren't migrated to the ePO Events table.
636352				Issue: After removing the Solidcore Extension, all Solidcore-related events are retained in the ePO table. When you view the events in the Threat Event Log, some fields might display erroneous data.
695769				Issue: Under the Content Change Tracking feature, the view file page goes blank for a file size of around 1 MB.
719796				Issue: Global Catalog search for AD groups isn't supported. Workaround: Search for a group in a specific AD server instead of using the Global Catalog. To add a specific group: Log on to the ePO console. Add the AD server containing the group as a registered server. Search for the group by selecting the registered AD server. Make sure that the Global Catalog Search option is deselected. Add the group to a policy as a trusted group.
722045				Issue: Adding new columns, such as Solidcore Status and Solidification Status, for an endpoint by clicking Actions, Choose columns, Non Compliant Solidcore Agent, might not display values for all endpoints. The reason is because the Non Compliant Solidcore Agent section includes only noncompliant agent properties. Workaround: When adding new columns for an endpoint, click Actions, Choose columns, Solidcore Client Properties instead.
800014				Issue: Extra events are reconciled when manual reconciliation is performed from custom queries. Workaround: To perform the manual reconciliation for multiple events by selecting either All in this page or Select All in all pages, open the Solidcore events page directly by clicking Menu, Reporting, Solidcore Events. NOTE: This option doesn't work well if you reach Solidcore Events by drilling down from a Query page.
882821				Issue: Sorting isn't supported on the Last Modification Time column on the Content Change Tracking page.
1043052				Issue: You can't upgrade the Solidcore help extension from previous versions to 6.2 or later. Workaround: Uninstall the old help extension and install the new one.
1107754				Issue: The following queries related to Automatic Reconciliation aren't removed after you upgrade to Solidcore Extension 7.0.0: Systems in Update Window due to TBE History of Update Windows opened by TBE Ticket Manifest Deviation (all Change Events per Object like File or Registry) Ticket Manifest Deviation (only Unique Change Events per Object like File or Registry)
1109570				Issue: The Application Control, Change Control, and IM dashboards are editable after you migrate from ePO 4.6.9 to 5.1.3.
1146143				Issue: Value for property Upgrade Status not getting updated.
1171909				Issue: Improper translation on the message in Solidcore events page.
1227853		8.0.0		Issue: When creating a custom filter on the System Tree page, the application service crashes.
1237773		8.1.0		Issue: Client task for enabling Change Control from ePO fails (second line in progress bar becomes red). Workaround: Using the command-line interface on the client to be solidified, execute (as administrator) the command instaconfig /connect. After executing the command, run the Change Control enable task from ePO again. A restart isn't needed.

Back to top

Windows (all versions)

Reference	Related Article	Found in Version	Resolved in Version	Description
598002				Issue: Registry key protection doesn't work for all registry key hives; it works only for HKEY_LOCAL_MACHINE.
599240				Issue: A sub-key registry doesn't get added to a protected registry key when using the reg command.
600748				Issue: Multiple deny-write events can be generated for a single deny-write action. For example, on deletion of a file using Windows Explorer, up to eight file-deletion events are reported. When the application denies deletion of a file, Windows Explorer tries multiple methods to delete the file, resulting in an event for each attempt.
600805				Issue: While opening a write-protected network share in Windows Explorer, a few deny-write errors are observed.
601500				Issue: Creating a shortcut within a read-protected directory isn't allowed.
602122				Issue: Any file operation performed on a read-protected file generates deny-read events that correspond to the file even when the file operation is allowed.
603032				Issue: Changes to folder-mounted volumes that don't have an associated drive letter can't be monitored. Workaround: Assign a drive letter to a volume before mounting it on any other folder.
603628				Issue: On 64-bit platforms, ACL modification events aren't generated when the update mechanism supersedes the deny-write policies for registries.
603747				Issue: The trusted, solidified, and write-protect features don't work correctly for folder-mounted volumes. Workaround: Contact Technical Support for assistance if the setup uses folder-mounted volumes.
605371				Issue: When you try to read a read-protected file with certain file flags set through Windows Explorer, read-denied events might not be written to the event viewer. But, the events are logged in the Solidcore Agent log file.
606496				Issue: Only full long names are supported with commands that accept file or folder names. For example, names such as c:\myPackages\SETUP-~1.EXE aren't supported.
606532				Issue: Virtual drive paths aren't supported as path values in Solidcore Agent commands, such as write-protect, read-protect, and monitor.
608036				Issue: Mapped drive names can't be used in commands issued by remote users/ePO.
608418				Issue: The Original Username reported in events is the same as the Username.
691196				Issue: For a file where you're tracking content changes, you receive an unknown error if connectivity issues occur while sending metadata for the file from the endpoint to the ePO console. Workaround: When network connectivity resumes, the next change to the file is reflected accurately on the ePO console.
724796				Issue: Although you can track content changes for a read-protected file, you can't view the actual changes because the read-protection rule prevents the software from fetching file contents from the endpoint.
799559				Issue: If you exclude the .bat extension from monitoring, events for batch-file operations are generated.
812964				Issue: If the Updater flag is removed for a cert rule in ePO, the certificate is listed as an Updater on the endpoint.
876430				Issue: For monitoring and change control rules that contain an asterisk (), the longest path* rule isn't given precedence for conflicting rules.
881480				Issue: Revisions aren't reported for Content Change tracking if user events are filtered using the filter rules. Workaround: Exclude the user from event filtering and apply advanced filters for the user for exclusion of unwanted events for files and directories.
894237				Issue: For a directory-based Content Change Tracking rule, renaming of the directory or its subdirectory generates spurious monitor events.
920568	KB79987			Issue: The product version isn't updated in the ePO server and the McTray About box after an endpoint upgrade. Workaround: See the related article.
940085	KB73484			Issue: There's a known incompatibility between Change Control and SafeNet ProtectFile: File Encryption and Protection software.
1027687	KB84043			Issue: Upgrade to Application Control or Change Control 6.2 (or later) fails for endpoints. Workaround: See the related article.
1146803				Issue: Change Control event REG_KEY_CREATED isn't generated for New Key #1.
1188255		8.0.0		Issue: Change Control is preventing the Windows Defender Update process from running successfully. Workaround: Place in Update mode to update Windows Defender. Place back into Enabled mode after Windows Defender update completes.
1189702		8.0.0		Issue: scsrvc.exe service hangs during restart when in disable mode because Cryptsvc starts after our service. Workaround: Microsoft suggests that you add a dependency in the Solidcore service: sc config scsrvc depend= cryptsvc.
1219284		8.1.0		Issue: Write-protected files are allowed to be deleted from the command line when their name exceeds a certain length (DOS shortname associated).
1221213		8.1.0		Issue: Executable (.exe) files on network drives aren't allowed to be executed when they're in trusted folders.
1223577		8.1.0		Issue: The swin1.sys file isn't deleted after Change Control is set as Enable.
1225038		8.1.0		Issue: There are repeated rows per system and requests made on the Policy Discovery page.
1230980		8.1.0		Issue: The wrong error message "Error1316. The specified account already exists" displays after upgrading Change Control on an x64 system Windows 10 system with an x86 installer. The correct error message is "Installer supports installation only on a 32-bit system. Setup has aborted."
1231217		8.1.0		Issue: Labels are wrong in the Approval status drop list on the Policy Discovery page.
1231583		8.1.0		Issue: "User Comments" is repeated for Observations with Global Prevalence greater than one on the Policy Discovery page.
1232088		8.1.0		Issue: FILE MODIFIED events aren't being generated for files with a "monitor file" rule added. Solution: This issue is resolved in Change Control 8.2.1.

Back to top

Windows 2008 R2 (64-bit)

Reference	Related Article	Found in Version	Resolved in Version	Description
608636				Issue: During manual installation of the Solidcore Agent on Windows 2008 R2 (64-bit), a Windows installer encountered a validation error message displays for the msiexec.exe and kernelbase.dll files. Workaround: To continue installation, click Ignore once or Ignore always on the pop-up message.

Windows 2008 (64-bit)

Reference	Related Article	Found in Version	Resolved in Version	Description
609780				Issue: On Windows 2008 (64-bit), the rundll32.exe file crashes if an application is uninstalled via Add/Remove Programs after the SetupInstallFromInfSection() function is used to install the application.

Windows 7 (64-bit)

Reference	Related Article	Found in Version	Resolved in Version	Description
708226				Issue: Change Control is functionally incompatible with Avecto Privilege guard.

Windows 10

Reference	Related Article	Found in Version	Resolved in Version	Description
1141216				Issue: You upgrade from Windows 7 to Windows 10. If you then uninstall Change Control , the removal is only partially successful. You're then unable to reinstall Change Control. Workaround: Remove all traces of the previous installation using the tool in the related article.

Back to top

Change Control 8.0.0 known issues

CRITICAL: There are currently no known critical issues.

Non-critical:

Solidcore Extension

Reference	Article	Found in Version	Resolved in Version	Description
607517				Issue: PDF reports have minor data display and formatting issues if more than 50,000 records are reported.
607908				Issue: It's not possible to export more than 50,000 records from any table or report.
607950				Issue: User-defined system variables in policies are resolved at the endpoint only after the endpoint is restarted.
608025				Issue: Reports, tasks, and policies for all SKUs are listed even if the license for that SKU isn't added.
608347				Issue: The Solidcore Policies Applied on Hosts report displays all policies derived from the root, regardless of the SKUs enabled on the platform.
608374				Issue: When you try to enable an already enabled Solidcore Agent, the error displayed isn't translated.
608390				Issue: When viewing an Integrity Monitor policy, the My Rules tab isn't translated.
608618				Issue: You try to upload a Windows Solidcore Agent Deployment Package that's larger than 100 MB to ePO through Microsoft Internet Explorer. But, the file upload times out if the network upload speed is slow. Workaround: Use Internet Explorer 7 or later and if you encounter further issues, and copy the package to a local directory on the ePO server. Then, access the ePO console on the ePO server and upload the file from the local path. This sequence avoids possible network delays.
608753				Issue: Sometimes, using the username field of reported events on the ePO server as a trusted user might not work if the client system is part of an AD domain. The reason is because the domain name reported in the events is not the full AD domain. Workaround: Use the environment variable USERDNSDOMAIN as the domain name for AD clients. Or, review the properties of the My Computer icon to identify the complete username to specify as the trusted user.
609304				Issue: It's not possible to export data from the Reporting, Solidcore Events page. Workaround: Use Queries (Reporting, Queries) to export event data.
636352				Issue: After removing the Solidcore Extension, all Solidcore-related events are retained in the ePO table. When you view the events in the Threat Event Log, some fields might display erroneous data.
636769				Issue: If you upgrade from Solidcore 5.1.0 to 5.1.1 or later, existing Solidcore events in the Solidcore Events table aren't migrated to the ePO Events table.
695769				Issue: Under the Content Change Tracking feature, the view file page goes blank for a file size of around 1 MB.
719796				Issue: Global Catalog search for AD groups isn't supported. Workaround: Search for a group in a specific AD server instead of using the Global Catalog. To add a specific group: Log on to the ePO console. Add the AD server containing the group as a registered server. Search for the group by selecting the registered AD server. Make sure that the Global Catalog Search option is deselected. Add the group to a policy as a trusted group.
722045				Issue: Adding new columns, such as Solidcore Status and Solidification Status, for an endpoint by clicking Actions, Choose columns, Non Compliant Solidcore Agent might not display values for all endpoints. The reason is because the Non Compliant Solidcore Agent section includes only noncompliant agent properties. Workaround: When adding new columns for an endpoint, click Actions, Choose columns, Solidcore Client Properties instead of Actions, Choose columns, Non Compliant Solidcore Agent.
800014				Issue: Extra events are reconciled when manual reconciliation is performed from custom queries. Workaround: To perform the manual reconciliation for multiple events by selecting either All in this page or Select All in all pages, open the Solidcore events page directly by clicking Menu, Reporting, Solidcore Events. NOTE: This option doesn't work well if you reach Solidcore Events by drilling down from a Query page.
882821				Issue: Sorting isn't supported on the Last Modification Time column on the Content Change Tracking page.
1043052				Issue: You can't upgrade the Solidcore help extension from previous versions to 6.2 or later. Workaround: Uninstall the old help extension and install the new one.
1109570				Issue: The Application Control, Change Control, and IM dashboards are editable after you migrate from ePO 4.6.9 to 5.1.3.
1107754				Issue: The following queries related to Automatic Reconciliation aren't removed after you upgrade to Solidcore Extension 7.0.0: Systems in Update Window due to TBE History of Update Windows opened by TBE Ticket Manifest Deviation (All Change Events per Object like File or Registry) Ticket Manifest Deviation (Only Unique Change Events per Object like File or Registry)
1146143				Issue: Value for property Upgrade Status not getting updated.
1171909				Issue: Improper translation on the message in Solidcore events page.

Back to top

Windows (all versions)

Reference	Article	Found in Version	Resolved in Version	Description
598002				Issue: Registry key protection doesn't work for all registry key hives, it works only for HKEY_LOCAL_MACHINE.
599240				Issue: A subkey registry doesn't get added to a protected registry key when using the reg command.
600748				Issue: Multiple deny-write events can be generated for a single deny-write action. For example, on deletion of a file using Windows Explorer, up to eight file-deletion events are reported. When the application denies deletion of a file, Windows Explorer tries multiple methods to delete the file, resulting in an event for each attempt.
600805				Issue: While opening a write-protected network share in Windows Explorer, a few deny-write errors are observed.
601500				Issue: Creating a shortcut within a read-protected directory isn't allowed.
602122				Issue: Any file operation performed on a read-protected file generates deny-read events that correspond to the file even when the file operation is allowed.
603032				Issue: Changes to folder-mounted volumes that don't have an associated drive letter can't be monitored. Workaround: Assign a drive letter to a volume before mounting it on any other folder.
603628				Issue: On 64-bit platforms, ACL modification events aren't generated when the update mechanism supersedes the deny-write policies for registries.
603747				Issue: The trusted, solidified, and write-protect features don't work correctly for folder-mounted volumes. Workaround: Contact Technical Support for assistance if the setup uses folder-mounted volumes.
605371				Issue: When you try to read a read-protected file with certain file flags set through Windows Explorer, read-denied events might not be written to the event viewer. But, the events are logged in the Solidcore Agent log file.
606496				Issue: Only full long names are supported with commands that accept file or folder names. For example, names such as c:\myPackages\SETUP-~1.EXE aren't supported.
606532				Issue: Virtual drive paths aren't supported as path values in Solidcore Agent commands, such as write-protect, read-protect, and monitor.
608036				Issue: Mapped drive names can't be used in commands issued by remote users/ePO.
608418				Issue: The Original Username reported in events is the same as the Username.
691196				Issue: For a file where you're tracking content changes, you receive an unknown error if connectivity issues occur while sending metadata for the file from the endpoint to the ePO console. Workaround: When network connectivity resumes, the next change to the file is reflected accurately on the ePO console.
724796				Issue: Although you can track content changes for a read-protected file, you can't view the actual changes because the read-protection rule prevents the software from fetching file contents from the endpoint.
799559				Issue: If you exclude the .bat extension from monitoring, events for batch-file operations are generated.
812964				Issue: If the Updater flag is removed for a cert rule in ePO, the certificate is listed as an Updater on the endpoint.
876430				Issue: For monitoring and change control rules that contain an asterisk (), the longest path* rule isn't given precedence for conflicting rules.
881480				Issue: Revisions aren't reported for Content Change tracking if user events are filtered using the filter rules. Workaround: Exclude the user from event filtering and apply advanced filters for the user for exclusion of unwanted events for files and directories.
894237				Issue: For a directory-based Content Change Tracking rule, renaming of the directory or its subdirectory generates spurious monitor events.
920568	KB79987			Issue: Product version isn't updated in the ePO server and the McTray About field after an endpoint upgrade. Workaround: See the related article.
940085	KB73484			Issue: There's a known incompatibility between Change Control and SafeNet ProtectFile: File Encryption and Protection software.
1027687	KB84043			Issue: Upgrade to Application Control or Change Control 6.2 or later fails for endpoints. Workaround: See the related article.
1146803				Issue: Change Control event REG_KEY_CREATED isn't generated for New Key #1.

Back to top

Windows 2008 R2 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
608636				Issue: During manual installation of the Solidcore Agent on Windows 2008 R2 (64-bit), a Windows installer encountered a validation error message displays for the msiexec.exe and kernelbase.dll files. Workaround: To continue installation, click Ignore once or Ignore always on the pop-up message.

Windows 2008 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
609780				Issue: On Windows 2008 (64-bit), the rundll32.exe file crashes if an application is uninstalled using Add/Remove Programs after the SetupInstallFromInfSection() function is used to install the application.

Windows 7 (64-bit)

Reference	Article	Found in Version	Resolved in Version	Description
708226				Issue: Change Control is functionally incompatible with Avecto Privilege guard.

Windows 10:
There are currently no known issues.

Back to top

Knowledge Center

Change Control 8.x Known Issues

Environment

Summary

Affected Products

Languages:

Title

Title

Knowledge Center

Change Control 8.x Known Issues

Environment

Summary

Affected Products

Languages:

Choose your region

Title

Title