Software Status Bulletin
Agilent ICF Support Layer for Waters CDS WICF
Known Problem Report as of Dec 8 2025 4:00AM
Preface
-------------------------
This Software Status Bulletin (SSB) documents all known problems in the software
product designated above. The SSB is derived from Known Problem Reports (KPR)
which result from user problems that have been classified as documentation
problems or software defects. When a KPR is written, an identifying number is
assigned to it, and the KPR is added to the next edition of the SSB.
User inputs that have been classified as Enhancement Requests are not documented
in the SSB. User problems that have been submitted, but that have not been
classified by the time the SSB is generated are not included in the SSB.
How to use the SSB
-------------------------
When you experience a problem with a product, first check this SSB to see if the
problem has been reported already, and if there is a temporary workaround
available for the problem, or if the problem has already been fixed by a new
revision. If the problem is not listed in this SSB then you may wish to report
it to the Response Center or to your field support representative.
To determine if your problem is documented in this SSB, first look in the
Keyword Index section of the SSB. Under each keyword is a listing of one-line
descriptions of related KPRs. If any of these sound like yours, locate the KPR
# in the Known Problem Reports section of the SSB, and read the full KPR. The
KPRs in the Known Problem Reports section are sorted by KPR #.
There are two sections in the SSB:
Keyword Index: This index is categorized by keyword. For each KPR there is a
brief description and a KPR #. A KPR may be associated with more than one
keyword.
Known Problem Reports: This section contains KPRs, with all the available
information relevant to the problem. KPRs in this section are sorted by KPR #.
Keyword Glossary
Keyword Index
KPR#:718626
Skip function for GC ALS/HS errors aborts the Sample Set
KPR#:746194
Non-inject functions with a Postrun time in method cause an abort
KPR#:804562
Sample set does not abort upon GC ALS/HS failure
KPR#:1209321
No dashboard, Node Properties>Scan Instruments shows "No", and slow performance without internet connection
KPR#:1329005
No signal for acquisition leads to "Run cannot be stopped because the instrument is in idle state"
KPR#:783237
Unhandled Exception when (Re-)Configuring the G1888 HS in Empower
KPR#:783402
DHCP Configuration details not in System Audit Trail
KPR#:805851
(Re-)Configuration of a HS can maintain the previous HS config
KPR#:1289930
Agilent PreConfiguration fails to launch if Empower is not installed in the default path (C:\Empower).
KPR#:1320597
Co-Existence of WICF and native GC ICS A7890 driver leads to failing SVT
KPR#:933792
No data from back only injections in dual tower mode
KPR#:937729
Multiple Injections in Dual Tower mode do not work
KPR#:965886
Signal assignment for Dual Tower injections do not match the method
KPR#:1031138
Overlapped Injection and Abort after Injection/Vial is complete does not work
KPR#:1034481
Manual GC injection stays in Injection Running
KPR#:1215516
GC/HS stays in Monitor after reboot
KPR#:1247908
Methods with Prep Run on Manual Request enabled cannot be migrated
KPR#:1225460
Liner selection not possible
KPR#:940321
GC-HS MHE aborts when queueing Sample Sets
KPR#:979714
Unexpected Instrument Failure for GC+ HS G1888
KPR#:1027680
Multiple Headspace Extraction (MHE) is ignored on Japanese and Chinese systems
KPR#:1030774
Multiple Headspace Extraction (MHE) only works with # of Injs
KPR#:1050700
Issues when uninstalling Waters Driver Pack
KPR#:1070724
Non-Agilent RC.NET drivers not displayed in SVT
KPR#:1283085
Disabling Dual Tower leads to failing SVT
KPR#:938364
Direct control issues in ICF SL 3.6 and 3.6.1 Interoperability scenarios
KPR#:955472
Interoperability issues with ICF SL versions lower than 3.6 when using a GC barcode reader
KPR#:543734
Column configuration changes are not visible
KPR#:980175
Fraction Collection does not work with ICF SL 3.7.01
KPR#:980181
Open-bed Sampler (G7158B and G7169B) does not work in a cluster
KPR#:1057254
Antec/Waters 3465 ECD Instrument Failure when both cells are turned off
KPR#:1089437
No data available for Fraction Collector when Temp Aux channel is enabled
KPR#:1142013
InfinityLab Assist Hub can start a task during a monitor run in Empower
Keyword: Localization (Chinese),Localization (Japanese)
KPR#:1027682
Multiple Injection for GC ALS is ignored on Japanese and Chinese systems
KPR#:1030362
Injector Preference GC Front or Back is ignored on Japanese and Chinese systems
KPR#:745702
Method resolution resets the Options for GC/HS
KPR#:936794
Two empty Options tabs for GC methods in Empower 3.8.0
KPR#:1197338
">" and "<" symbols display as "gt;" and "lt;" in the method report
KPR#:717268
Column information refresh does not work
KPR#:742695
Run Samples window becomes unresponsive
Keyword:
One-line Description:
Exception while configuring the HS G1888
Problem:
During the PreConfiguration, the G1888 can throw an exception "Exception has been thrown by the target of an invocation". The Windows Event Logs show a missing dependency on Microsoft VC90 which is part of the Microsoft Visual C++ 2008 (x86) redistributable package which is not installed anymore by the Empower installer starting with version 3.8.1.
Temporary Solution:
Download and install Microsoft Visual C++ 2008 Redistributable package (vcredist_x86) from Microsoft.
Fix Information:
n/a
Keyword:
One-line Description:
Exception while configuring the HS G1888
Problem:
During the PreConfiguration, the G1888 can throw an exception "Exception has been thrown by the target of an invocation". The Windows Event Logs show a missing dependency to Microsoft VC90 which part of the Microsoft Visual C++ 2008 (x86) redistributable package which is not installed anymore by the Empower installer starting with version 3.8.1.
Temporary Solution:
Download and install Microsoft Visual C++ 2008 Redistributable package (vcredist_x86) from Microsoft.
Fix Information:
n/a
Keyword:
One-line Description:
CTC Module Tile is empty on a client
Problem:
Having configured a CTC PAL3 and opening on a client for the first time. The module tile is empty for the PAL3 only.
Temporary Solution:
Close and open the Run Samples window. When Run Samples is opened a second time the dashboard tile loads correctly.
Fix Information:
Fixed in WICF 4.2
Keyword: Acquisition
One-line Description:
Skip function for GC ALS/HS errors aborts the Sample Set
Problem:
Using the Skip function to skip the current injection and proceed with the sample set upon ALS or Headspace errors, for example, missing vial, incorrect vial size, etc., aborts the entire sample set.
Temporary Solution:
n/a
Fix Information:
Must be fixed in Empower as Skip functions can currently not be handled.
Keyword: Acquisition
One-line Description:
Non-inject functions with a Postrun time in method cause an abort
Problem:
Using non-inject (Equilibrate, Condition Columns, etc.) or monitor functions with instrument methods having set a Postrun time, can cause an abort showing an instrument failure.
Temporary Solution:
Use a separate instrument method without Postrun time for the Non-inject functions.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Sample set does not abort upon GC ALS/HS failure
Problem:
The abort or skip function upon ALS/HS failure does abort the instrument run but remains in Run mode in Empower and states 'Run cannot be stopped because the instrument is in idle state' in the instrument log.
Temporary Solution:
Sample set must be aborted manually after a GC ALS/HS failure by using the red Stop button in Empower.
Fix Information:
Fixed in WICF 4.2. Using abort or skip upon ALS/HS failure aborts the Empower sample set.
Keyword: Acquisition
One-line Description:
No dashboard, Node Properties>Scan Instruments shows "No", and slow performance without internet connection
Problem:
Starting with WICF 4.1, the executables contain a digital signature. For setups without internet connection, the revoking mechanism of the certificate can lead to timeouts of the PluginRunner process resulting in an empty instrument dashboard, scan instruments in the node properties showing "OK? No", and >30s loading times of the method UI.
Temporary Solution:
n/a
Fix Information:
Workaround implemented in WICF 4.2 to prevent a timeout of the PluginRunner process. Slow Performance to be fixed by one of the following options: - Set the default retrieval timeout to 1 under Local Security Policy > Security Settings > Public Key Policies > Certificate Path Validation Settings > Network Retrieval tab. - Uncheck the certificate revocation checks under Internet Options>Advanced>Security, - Configure the firewall to allow accessing the DigiCert CRL Distribution Points, OCSP Servers and Services with the related ports including DNS resolution for the DigiCert URLs.
Keyword: Acquisition
One-line Description:
No signal for acquisition leads to "Run cannot be stopped because the instrument is in idle state"
Problem:
Starting with ICF SL 3.7.01 and higher, if no signal is configured for acquisition in the instrument method, the system will immediately abort the run and generate the following error messages: "Run cannot be stopped because the instrument is in idle state" and "failed to get ready to run an acquisition"
Temporary Solution:
Select at least one signal to be acquired in the instrument method.
Fix Information:
n/a
Keyword: Configuration
One-line Description:
Unhandled Exception when (Re-)Configuring the G1888 HS in Empower
Problem:
Configuring the G1888 (for example, to change the vial size) when having already an active connection (for example, in Empower after a session was opened once) clicking "Upload from Instrument" will lead to an unhandled exception error. This is a hardware limitation as the G1888 only allows one communication channel at a time.
Temporary Solution:
Possible Workarounds: - Reboot the LACE and directly upload the config again - Do a soft-config via Status UI -> Advance Options -> Module Options - Use the Terminate connection button (introduced with Water SL 3.6) before uploading the config
Fix Information:
n/a
Keyword: Configuration
One-line Description:
DHCP Configuration details not in System Audit Trail
Problem:
Configuring a new instrument via Agilent PreConfiguration and Waters DHCP configuration does not create an entry with instrument details in the Empower System Audit Trail.
Temporary Solution:
Remove and add the DHCP configuration again without closing the node properties window. Alternatively, use the Details column in the Node Properties window to report the configuration details.
Fix Information:
To be fixed in Empower (INFEMP-33741)
Keyword: Configuration
One-line Description:
(Re-)Configuration of a HS can maintain the previous HS config
Problem:
When the instrument controller (LAC/E or Workstation) is not rebooted, the Headspace configuration is read from a file which is not updated by uploading the Config from instrument in the Pre-Configuration. Thus, the most recent configuration of the same or another HS connected to this instrument controller will apply, potentially leading to config mismatches or mixed systems.
Temporary Solution:
To ensure using the proper HS configuration you must follow these steps: - Only configure a Headspace directly on the instrument controller (LAC/E or Workstation). - Always reboot the instrument controller before a Headspace configuration. - Optional alternative: Before configuring the instrument delete C:\Empower\Instruments\AgilentLC\HSConfig.xml if present.
Fix Information:
Fixed in WICF 4.0
Keyword: Configuration
One-line Description:
Agilent PreConfiguration fails to launch if Empower is not installed in the default path (C:\Empower).
Problem:
Installing WICF sets a fixed path for launching Agilent PreConfiguration from the Empower Configuration Manager menu. If Empower is not installed on the default path (C:\Empower), the tool fails to open and "Could not start custom program" is displayed.
Temporary Solution:
Manually update the following registry entry to point to the correct installation path of PreConfigClient.exe: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Waters\Empower\Toolkit\CustomPrograms\ConfigurationManager\Program1
Fix Information:
n/a
Keyword: Configuration
One-line Description:
Co-Existence of WICF and native GC ICS A7890 driver leads to failing SVT
Problem:
Installing WICF on a system with an already existing native ICS A7890 driver, leads to a failure in the Agilent SVT report because the following registry value is not found HKEY_LOCAL_MACHINE\SOFTWARE\Waters\Instruments\A7890\Scanable Starting with ICF SL 3.7.01, Dual Tower is activated by default during installation. As a result, legacy methods created with the ICS A7890 driver cannot be opened.
Temporary Solution:
- If ICS A7890 is not required, uninstall it and reinstall WICF. - If Dual Tower is not used and legacy methods must remain accessible, disable Dual Tower and re-install ICS A7890, leading to A failing Agilent SVT with registry value not found for "EditorHTML" and "Scanable" in HKEY_LOCAL_MACHINE\SOFTWARE\Waters\Instruments\A7890\
Fix Information:
n/a
Keyword: GC Control
One-line Description:
No data from back only injections in dual tower mode
Problem:
In all WICF and ICF SL versions, if the Dual Tower is enabled and only the back injector is used for injections (injector preference GC0:Back) no data is acquired, and the chromatogram plot appears blank.
Temporary Solution:
To run acquisitions with back injector only, disable the Dual Tower mode and run as an individual back tower acquisition.
Fix Information:
To be fixed in Empower.
Keyword: GC Control
One-line Description:
Multiple Injections in Dual Tower mode do not work
Problem:
Multiple Injection mode is ignored when performing Dual Tower injections and the ALS towers only inject once.
Temporary Solution:
Do not use Multiple Injections in Dual Tower mode. To perform Multiple Injections for a GC configured as dual tower, perform a front or back injection.
Fix Information:
n/a
Keyword: GC Control
One-line Description:
Signal assignment for Dual Tower injections do not match the method
Problem:
Using the slider to set dual injection signal assignments in the Signals tab of the method is ignored. Empower is using its own assignment pattern instead.
Temporary Solution:
n/a
Fix Information:
To be fixed in Empower
Keyword: GC Control
One-line Description:
Overlapped Injection and Abort after Injection/Vial is complete does not work
Problem:
Using overlapped injections and the Sample Set functions "Abort after Injection is complete" or "Abort after Vial is complete" will not abort preparing the next sample and the ALS is waiting for injection trigger.
Temporary Solution:
Use "Abort Now" to abort the Sample Set again. If not possible, use Terminate and Initialize to recover the GC.
Fix Information:
n/a
Keyword: GC Control
One-line Description:
Manual GC injection stays in Injection Running
Problem:
Restarting the instrument controller and starting a run within a short timeframe can lead to a not ending run remaining in the Injection Running state.
Temporary Solution:
After restarting the instrument controller, reboot the GC or wait >15min until the connection is reset.
Fix Information:
Planned to be fixed in GC firmware
Keyword: GC Control
One-line Description:
GC/HS stays in Monitor after reboot
Problem:
Rebooting the instrument controller and immediately opening Run Samples after the startup can lead to GC or HS being displayed in Monitor mode and diagnostic log messages "Can't gain ownership of the instrument" and "..already controlled by" the own instrument controller.
Temporary Solution:
Terminate the instrument connection before restarting, restart the GC/HS hardware, or wait >15min until the old connection is reset from the hardware side.
Fix Information:
Planned to be fixed in GC/HS firmware
Keyword: GC Control
One-line Description:
Methods with Prep Run on Manual Request enabled cannot be migrated
Problem:
If the "Prep Run on Manual Request" button is enabled in the method for a GC 8890 (firmware ≥ 3.1), Intuvo 9000 (firmware ≥ 2.9.0), or GC 7890B (firmware ≥ B.02.07), methods created with ICF SL ≤ 3.7.01 cannot be migrated to WICF 4.2.
Temporary Solution:
Possible workarounds: - Downgrade the GC firmware - Re-create the method - Use the Prep Run button on the GC Front Panel for manual injection
Fix Information:
Planned for WICF 4.3
Keyword: GC Control,Method
One-line Description:
Liner selection not possible
Problem:
Currently it is not possible to select a liner in the GC instrument method. This has no effect on chromatographic results. The limitation is that reporting the liner is currently not possible.
Temporary Solution:
Liner information is removed from the method report for WICF 4.2.
Fix Information:
Planned to be fixed in WICF 4.3.
Keyword: HS Control
One-line Description:
GC-HS MHE aborts when queueing Sample Sets
Problem:
Using Multiple Headspace Extraction (MHE) in the GC-HS method can lead to aborts ("Instrument failure") in case additional sample sets are submitted to the run queue during a running sample set with MHE.
Temporary Solution:
Do not submit additional sample sets when one is running using MHE.
Fix Information:
Fixed in WICF 4.0
Keyword: HS Control
One-line Description:
Unexpected Instrument Failure for GC+ HS G1888
Problem:
Using a GC with G1888 HS in ICF SL 3.7 without having terminated and initialized the connection, unexpected instrument failures ("Object reference not set to an instance of an object.") can be observed for a sample set after any interaction with the instrument was performed upfront (for example, using monitor, starting a run, re-opening acquisition).
Temporary Solution:
Terminate and Initialize the instrument connection via Advance Options after starting the Acquisition window.
Fix Information:
Fixed in WICF 4.0
Keyword: HS Control
One-line Description:
Multiple Headspace Extraction (MHE) is ignored on Japanese and Chinese systems
Problem:
On Empower systems localized in Japanese or Chinese, the method setting to perform Multiple Headspace Extractions (MHE) is ignored. Only standard injections are performed instead.
Temporary Solution:
n/a
Fix Information:
Fixed in WICF 4.0
Keyword: HS Control
One-line Description:
Multiple Headspace Extraction (MHE) only works with # of Injs
Problem:
MHE does not work for consecutive lines in the sequence using the same vial. The vial will be equilibrated and punctured again.
Temporary Solution:
Specify the number of injections ("# of Injs column") per vial in the Sample Set to use MHE.
Fix Information:
n/a
Keyword: Installation
One-line Description:
Issues when uninstalling Waters Driver Pack
Problem:
Uninstalling the Waters Driver Pack leads to issues as shared components will be removed (InstrIDL.dll in C:\Empower\Instruments\Bin) after every restart. As a consequence, the Agilent Software Verification will fail and the instruments will be unusable.
Temporary Solution:
Workarounds are: - Re-install the Waters DP. - Set the Read-only attribute for the InstrIDL.dll before uninstalling Waters DP or after WICF installation, before restarting.
Fix Information:
Must be fixed in the Waters Driver Pack installer
Keyword: Installation
One-line Description:
Non-Agilent RC.NET drivers not displayed in SVT
Problem:
Non-Agilent RC.NET drivers like CTC, Antec or PerkinElmer are not displayed in the Agilent Software Verification Report compared to ICF Support Layer 3.X.
Temporary Solution:
Copy all reference xml files from \Program Files (x86)\Agilent Technologies\IQTool\IQProducts\Agilent ICF to \Program Files (x86)\Agilent Technologies\IQTool\IQProducts\Agilent ICF Support Layer for Waters CDS
Fix Information:
To be fixed in the new versions of the Non-Agilent RC.NET drivers.
Keyword: Installation
One-line Description:
Disabling Dual Tower leads to failing SVT
Problem:
Disabling Dual Tower using the Disable_Dual_Tower script provided on the WICF installation media, leads to a failing Agilent SVT.
Temporary Solution:
Disabling Dual Tower will lead to Registry value not found entries in the Agilent SVT for HKEY_LOCAL_MACHINE\SOFTWARE\Waters\Instruments\A7890\.
Fix Information:
n/a
Keyword: Interoperability
One-line Description:
Direct control issues in ICF SL 3.6 and 3.6.1 Interoperability scenarios
Problem:
When ICF Support Layer 3.6 or 3.6.1 are installed on a LAC/E and ICF Support Layer 3.7 or WICF 4.X are installed on a client, instrument direct control functions (for example, right click on instrument dashboard>control/turn on/etc.) do not work from a Citrix server or acquisition client.
Temporary Solution:
Avoid interoperability setups with ICF SL 3.6 or 3.6.1.
Fix Information:
Fixed in ICF SL 3.7 but interoperability scenarios (for example, rolling client upgrades to higher versions) with ICF SL 3.6 or 3.6.1 involved are still affected.
Keyword: Interoperability
One-line Description:
Interoperability issues with ICF SL versions lower than 3.6 when using a GC barcode reader
Problem:
False barcode reader inconsistency preventing method download for methods interoperating between ICF SL versions higher (client) and lower (instrument controller) than ICF SL 3.6 (ICF 3.0 U3 with GC driver 3.5 SR1).
Temporary Solution:
Avoid interoperability scenarios across ICF SL 3.6 when using GC/HS with barcode reader.
Fix Information:
Fixed for all versions equal or higher than ICF SL 3.6 (ICF 3.0 Update 3, GC driver 3.5 SR1)
Keyword: LC Control
One-line Description:
Column configuration changes are not visible
Problem:
When changing the column configuration, the system does not graphically display the change in the dashboard, nor provides an information about the change.
Temporary Solution:
Perform a reboot and an Auto-Configuration when adding, changing, or deleting a column with a change in plumbing/color code in the Column Assignment screen of the LC Status Dashboard.
Fix Information:
Fixed in WICF 4.0
Keyword: LC Control
One-line Description:
Fraction Collection does not work with ICF SL 3.7.01
Problem:
Using a Fraction Collector with ICF SL 3.7.01 executes the sample set as expected but shows injection status incomplete in Empower Data Analysis and does not upload the fraction results.
Temporary Solution:
Do not use Fraction Collection with ICF SL 3.7.01
Fix Information:
Fixed in WICF 4.0
Keyword: LC Control
One-line Description:
Open-bed Sampler (G7158B and G7169B) does not work in a cluster
Problem:
A Fraction Collector Cluster where G7158B or G7169B are configured as a combined sampler leads to an instrument failure ("Invalid input format") when starting a run.
Temporary Solution:
Do not configure a cluster with a combined sampler and use a separate sampler instead
Fix Information:
n/a
Keyword: LC Control
One-line Description:
Antec/Waters 3465 ECD Instrument Failure when both cells are turned off
Problem:
Running a method with both cells turned off in the Antec/Waters 3465 ECD detector results in an instrument failure.
Temporary Solution:
Do not use instrument methods with both cells turned off.
Fix Information:
n/a
Keyword: LC Control
One-line Description:
No data available for Fraction Collector when Temp Aux channel is enabled
Problem:
Running a method with a Fraction Collector and Aux channel AFC.0.1. Temperature enabled, does not upload the data to Empower. The Sample Set completes successfully but in Data Analysis, the Injection Status stays on Incomplete and the Channel Status on Data Being Acquired.
Temporary Solution:
Do not record the Temperature Aux channel for Fraction Collectors
Fix Information:
Fixed in WICF 4.1
Keyword: LC Control
One-line Description:
InfinityLab Assist Hub can start a task during a monitor run in Empower
Problem:
If a task on the InfinityLab Assist Hub is started during an LC monitor run in Empower, the monitoring and task execution run in parallel.
Temporary Solution:
System must be rebooted to get LC instrument idle again. Alternatively, a sample set can be started to abort the monitoring
Fix Information:
n/a
Keyword: Localization (Chinese),Localization (Japanese)
One-line Description:
Multiple Injection for GC ALS is ignored on Japanese and Chinese systems
Problem:
On Empower systems localized in Japanese or Chinese, the method setting to perform multiple injections with a GC ALS is ignored. Only standard injections are performed instead.
Temporary Solution:
Do not use multiple injection functionality in Japanese or Chinese localizations.
Fix Information:
Fixed in WICF 4.2
Keyword: Localization (Chinese),Localization (Japanese)
One-line Description:
Injector Preference GC Front or Back is ignored on Japanese and Chinese systems
Problem:
On Empower systems localized in Japanese or Chinese, the Injector Preference setting for liquid front or back injections in the Options tab of the method is ignored.
Temporary Solution:
The vial number is decisive which injector is used. Use vial numbers 1-150 for the front and 501-650 for the back injector.
Fix Information:
n/a
Keyword: Method
One-line Description:
Method resolution resets the Options for GC/HS
Problem:
Resolving a method from a different instrument configuration in Empower, resets the settings in the Options tab (for example, Injector preference is set to GC0:Front, High Throughput mode is turned off).
Temporary Solution:
Edit the method after resolution to correct the settings in the Options tab.
Fix Information:
n/a
Keyword: Method
One-line Description:
Two empty Options tabs for GC methods in Empower 3.8.0
Problem:
Creating a new instrument method for an Agilent GC in Empower 3.8.0 will display two empty Options tabs and thus prevent the Injector Preference and High Throughput setting. To edit these settings, the method must be saved and re-opened.
Temporary Solution:
Saving and re-opening the method displays the Options tab in a correct way.
Fix Information:
Fixed in WICF 4.0
Keyword: Reporting
One-line Description:
">" and "<" symbols display as "gt;" and "lt;" in the method report
Problem:
The method report of Agilent instrument methods in Empower displays the symbol "gt;" and "lt;" instead of ">" and "<".
Temporary Solution:
No workaround
Fix Information:
Planned for WICF 4.3
Keyword: User Interface
One-line Description:
Column information refresh does not work
Problem:
The instrument method UI for a multi-column thermostat (MCT) provides a Refresh button to update the visual column information. This button does not work and leads to a stalling interface displaying "updating column information".
Temporary Solution:
Do not use the Refresh button
Fix Information:
n/a
Keyword: User Interface
One-line Description:
Run Samples window becomes unresponsive
Problem:
After clicking a button in Empower like Setup, Develop Methods, Options, etc., and interacting with the instrument dashboard while the button is outlined, causes a "Not Responding" Run Samples window.
Temporary Solution:
Avoid outlined buttons. For example, wait until method setup is complete or click into a text field to remove the button outline before interacting with the instrument dashboard.
Fix Information:
Must be fixed in Empower