For optimal performance of the Logix Designer application, the personal computer should meet or exceed these hardware and software requirements.

• Minimum:
  • CPU with 4 logical cores
  • 8 GB of RAM memory
  • 30 GB free hard disk space
• Recommended:
  • CPU with 8 logical cores
  • 16 GB of RAM memory

• These operating systems are supported and recommended. Recommended operating systems have priority for Microsoft Patch Qualifications with Rockwell Automation software.

• Windows® 11 Enterprise (Recommended)
• Windows 11 Professional
• Windows 11 IoT Enterprise LTSC 2024 (v24H2)
• Windows 10 Enterprise 64-bit
• Windows 10 Professional 64-bit
• Windows 10 Enterprise 2021 LTSC 64-bit (v21H2) (Recommended)
• Windows 10 Enterprise 2019 LTSC 64-bit (v1809)
• Windows Server® 2025 Standard (Recommended)
• Windows Server 2022 Standard (Recommended)
• Windows Server 2022 Datacenter

• Universal C Runtime (CRT) is a Windows operating system component that enables core functionality on the Windows operating system. It was introduced in Windows 10 and distributed to most computers running earlier supported operating systems. This component is present on computers that have been kept up to date.

• While the Windows 8.1 and later operating systems run on many touch-enabled devices, various features of the Logix Designer application may not be touch-enabled. Most functions are expected to work with touch, but the software has only been tested with a keyboard and mouse.
• Logix Designer was tested with UAC set to the most restrictive level (Always notify). This version of the Logix Designer application is also expected to operate correctly when UAC is configured for any less restrictive setting.
• Microsoft .NET Framework 4.8
• This version of the Logix Designer application is expected to operate correctly on all other editions and service packs of these operating systems, but has not been tested:
  • Windows 8
  • Windows Server 2019
  • Windows Server 2016
• This is a list of the prerequisite software installed with this version of the Logix Designer application:
  • FactoryTalk® Services Platform v6.60
  • FactoryTalk® Activation Manager v5.02
  • FactoryTalk® Linx v6.60

Preferred operating systems

• Windows 11 Professional (64-bit)
• Windows Server 2022 Standard (64-bit)

High Resolution Display support

If running this software with a 2K or 4K High Resolution Display with scaling up to 125% you can expect acceptable results.

FactoryTalk Updater Server:

• Communicates with online FactoryTalk Updater Agents to receive collected data.
• Connects to the Product Compatibility and Download Center to retrieve the latest software information.
• Responds to requests from the FactoryTalk Updater Client.
• Supports ~100 online Agents.

Firmware requirements

• To check and download the firmware compatible with this version of the Logix Designer application, use the PCDC (https:// compatibility.rockwellautomation.com/Pages/home.aspx).
• Logix 5000 controllers and ControlLogix Motion modules must contain a revision of firmware that is compatible with this version of the Logix Designer application. The firmware images for most of the supported modules are contained on a DVD-ROM shipped with Rockwell Software Studio 5000 Automation Engineering & Design Environment™.

Rockwell Automation test environment

New features

• Support for ControlLogix 5590 controllers

• Synchronize EPLAN projects with Logix Designer projects

• Saves repetitive editing--make updates in one project and synchronize them in others.
• Minimizes human error when working across multiple systems.
• Helps keep your device data consistent and up-to-date across your software tools. The Synchronize feature also expands the number of supported devices.

See the Logix Designer online help for more information:

• Generate Safety Signatures in Run mode

• Front-port crossloading redundancy on ControlLogix 5590 controllers

Enhanced features

• New Timer_T data type

This version of the Logix Designer application includes the TIMER_T data type. The TIMER_T data type:

• Further integrates the DateTime feature into the Logix Designer instruction set. You can set the Timer operand as TIMER or TIMER_T in the Timer On Delay (TON), Timer Off Delay (TOF), and Retentive Timer On (RTO) instructions. The TIMER_T data type has Accumulated (ACC) and Preset (PRE) members whose data type is TIME.
• Clarifies elapsed time by displaying values in units of time: days (d), hours (h), minutes (m), seconds (s), milliseconds (ms), and microseconds (us). You no longer need to derive ACC or PRE values from a DINT that represents milliseconds.

• You import a signed Add-on Instruction (AOI) with a signature history.
• The option to overwrite an existing AOI without a signature history is enabled.
• The existing AOI’s signature history is blank.

Download errors in applications with ODOMETER or SIGNED_ODOMETER data types (5108058, 5201311)

When you upgrade the Studio 5000 Logix Designer application from an earlier release and the application includes tags with ODOMETER or SIGNED_ODOMETER data types, the download process may fail and display errors:  

• Error: Invalid attribute value.
• Error: Failed to download tags.

Workarounds:

• Delete and recreate the tags with ODOMETER and SIGNED_ODOMETER data types.
• Export the application to an L5K file and then import it back into the Logix Designer application.

For additional information, refer to technote ID: BF32566.

This anomaly corrected in version 37.03, 38.00.

This issue first identified in version 37.00.

Error 16#FF00: Connection Request Error - No Connection Instance (5087417)

When using the Enhanced Rack Optimization feature, Error 16#FF00 can occur with one or more modules in a 1734-AENT(R) chassis. 

To resolve this issue, disable the Enhanced Rack Optimization feature and use the standard Rack Optimization feature.

This anomaly corrected in version 38.00.

This issue first identified in version 37.00.

Unable to upload from a GuardLogix Controller (3870572, 3911842, 4039431)

Uploading from a GuardLogix SIL 2 or SIL 3 controller will result in errors if the application contains safety tags that use standard Add-on Instruction (AOI) datatypes. Mapping standard AOI data into the safety task is a use case for having safety tags of a standard AOI data type.

There are two different upload errors for two different scenarios.

• Scenario #1: The upload is performed with an application that is Safety Signed and/or Safety Locked.
  • In the Logix Designer Error Pane:
    "Error: <Name of AOI> Access Denied - Action not permitted when controller is Safety-locked or has signature."
    "Error: Failed to upload add-on instructions(s)."
  • If no safety signature or safety lock is applied, the upload completes without error.
    Note: It is not recommended to run without a safety signature in a production environment.

• Scenario #2: The upload is being performed with a Standard Edition activation.

  • In the Logix Designer Error Pane:
    "Error: <Name of AOI> Access Denied - This edition of Logix Designer does not permit this action."
    "Error: Failed to upload add-on instructions(s)."
    
  • If uploading with Professional Edition or a GuardLogix Safety Editor activation (9324-RLDGLXE) and Scenario #1 does not apply, the upload completes without error.

If it is not possible to correlate and go online with the controller, a download will have to be performed to reconnect to the controller.

Workaround:

To modify an application to work around this anomaly, use User Defined Datatypes (UDTs) for safety tag mapping instead of Add-on Instructions (AOIs). Editing the application requires a Professional Edition or GuardLogix Safety Editor license. After completing the edits, the Standard Edition can be used for ongoing tasks, if desired.

1. Create a User Defined Datatype (UDT) that matches the structure of the AOI tag.
2. Create standard and safety tags using the UDT datatype.
3. Copy the AOI tag data into the standard UDT tag.
4. Map the standard UDT tag to the corresponding safety UDT tag.
5. Repeat these steps for each AOI that requires safety tag mapping.
6. Remove all safety tags with a standard AOI datatype to ensure the upload succeeds.

This anomaly first identified in version 36.00.

This anomaly corrected in version 36.05, 37.04, and 38.00.

Add-on Instruction InOut BOOL Passes Incorrect Value (5107200)

If an Add-on Instruction (AOI) includes a BOOL InOut parameter defined with an element from a LINT or ULINT tag, the value of the tag does not pass into the instruction. For more information, please see technote BF33093 - AOI InOut BOOL Parameter Passing Incorrect Value.

This anomaly first identified in Studio 5000 Logix Designer version 37.00.

This anomaly corrected in Studio 5000 Logix Designer version 38.00.

• FactoryTalk Directory clients are losing communication with the FactoryTalk Directory Server which disrupts other Rockwell Automation software products that rely on the FactoryTalk Directory, such as Studio 5000 Logix Designer or FactoryTalk View Site Edition. The root cause is an anomaly with leap year handling in a FactoryTalk Alarms and Events service causing high CPU and memory usage when the system date is February 28 in non-leap years. For more information, see Product Notice 2025-03-001 – FactoryTalk® Alarms and Events anomaly causes High CPU and Memory usage preventing a FactoryTalk® Directory Client from communicating with the FactoryTalk® Directory Server. First identified in FactoryTalk Services Platform version 6.40.00. [Jira 4180731]
Corrected in FactoryTalk Services Platform version 6.60.00.

Warning on Timer Preset and Accum tags (5337418)

The following verification warning could appear for Timer Preset (.PRE) and Accum (.ACC) tags if these tags are used as destination elements in Logix instructions:

"Tag Member overwrites may cause unexpected errors/behaviors."

Members of a structure operand should not be overwritten. However, .PRE and .ACC are pseudo-operands and are permitted to be written to in logic.

For more information about pseudo-operands, see Logix 5000 Controllers General Instruction Manual, 1756-RM003.

This anomaly first identified in Studio 5000 Logix Designer version 38.00.

Logix Designer is unresponsive after finalizing an online edit (5218346, 5496825)

After finalizing an online edit of multiple rungs in a Ladder Routine while in Remote Run mode, the Studio 5000 Logix Designer software becomes unresponsive. End the process in Task Manager and reopen the software to recover.

To minimize the likelihood of occurrence, use any of the following mitigations:

• Instead of selecting Finalize, perform each step of the online edit procedure: Accept, Test, and Assemble.

• Perform and finalize edits in Rem Prog mode.

• Edit and finalize 1-2 rungs at a time.

Note: Utilizing multiple mitigations steps reduces the likelihood further.

For more information, see technote BF33049 - Studio 5000 Logix Designer V38 Freezes with online Finalize All Edits.

This anomaly corrected in version 36.06, 37.05, 38.02.

This anomaly first identified in version 38.00.

Online editing of CMP or CPT instructions takes the application offline (5410979, 5505436, 5767841)

Online editing of Compare (CMP) or Compute (CPT) instructions causes the application to go offline with the following error:

Failed to correlate the project with a change in the controller. Logix Designer has been taken offline. Error 727-0.

The anomaly occurs if the instruction expression includes:

1. A tag of a user-defined data type (UDT) array using indirect addressing.

2. A large, nested UDT array member.

3. A comparison or compute to a tag or tag expression.

For more information, see technote BF33114 - Studio 5000 Logix Designer: Communication Error 727-0 when online editing of Compare (CMP) or Compute (CPT)

This anomaly corrected in version 37.05, 38.02.

This anomaly first identified in version 38.00.

• Chinese
• Italian
• Korean

Unable to Access CAM Editor or PID Configuration (5323751)

When launching a CAM Editor from an instruction, the following error can occur:
Failed to retrieve all information about tag.
Invalid member specifier
Error 23084-80042C09
When launching a PID configuration interface, the following error can occur:
Failed to retrieve all information about tag. One or more arguments invalid.
Error 23084-80070057
The errors occur when a tag is created with a data type set to a UDT (User-Defined Data Type) that contains nested tags of type CAM_PROFILE, CAM, or PID. If this tag is defined as an array and used as an operand in either a predefined instruction or an AOI (Add-On Instruction) that references CAM_PROFILE, CAM or PID tags, attempting to launch the editor or configuration interface via the ellipsis (...) next to the tag will result in one of the above errors.
The issue does not occur if the UDT tag is defined as a single tag instance (not an array).
Workaround:
To access the CAM Editor or PID configuration interface, locate the tag in the Controller or Program Scope Tag Editor, right-click on the CAM_PROFILE, CAM, or PID member and select Configure “TagName”.

This anomaly first identified in version 37.00.

Slow online performance of Logix Designer (5518773, 5604259, 5604261)

Studio 5000 Logix Designer software may experience delays in response or go completely unresponsive as more routines are open. This is more likely to occur with routines that reference a large number of tags in 5370 and 5570 Controller applications.

This anomaly corrected in version 37.03, and 38.02.

This anomaly first identified in version 37.00

NRGC-EIP end devices showing as not configured in Studio 5000 Logix Designer (5345286)

When configuring a NRGC-EIP device (manufactured by Carlo Gavazzi) and its NRG solid state relay end devices in Studio 5000 Logix Designer, the status of the NRGC-EIP end devices can show configuration errors in the End Device XX – Configuration and Communication Status tags, despite the physical LED status on the end devices not showing any indication of error. Additionally, data may not be accurately passed between the Logix Controller and the NRGC-EIP device.

This anomaly first identified in Studio 5000 Logix Designer V34.00.

Incorrect Warning Returned when Verifying a Function Block Diagram Routine (5277044)

When verifying a Function Block Diagram routine, where an immediate tag value is input into a Function Block Instruction member of a smaller datatype, the following error is reported:
Using 64-bit input with FBD Blocks having 32 bit backing tag members can produce unexpected result.
This warning appears, even if the FBD instruction member is not a 64-bit data type.
The warning should read as follows:
Using input values outside the range that FBD block members can hold could produce unexpected results.
Immediate values are stored as a 32-bit value by default, so if they are input to any datatype smaller than 32-bit, a warning is expected.

This anomaly first identified in Studio 5000 Logix Designer V37.00.

Web-based profiles launch as blank or empty windows with multiple instances of Logix Designer running on one PC (5582938)

If a space exists in a Windows username and/or the user shell folder path, and multiple Logix Designer projects are open, web-based user interface profiles will launch as an empty window.

The profiles will launch correctly in a single instance of Logix Designer or in one of the opened projects but trying to launch profiles from additional open projects will display the anomaly.

To work around the anomaly

• Work in one project of Logix Designer at a time.

• Log in as a user with no spaces in the username.

This anomaly will be resolved in an upcoming release of Logix Designer Add-on Profiles.

This anomaly first identified in version 20.00

Safety I/O modules can be added after a module type change in a redundant project (3806306)

In a redundant project, changing a 1756-EN2TP module to a 1756-EN4TR module can allow unsupported 5094 safety I/O modules under a non-concurrent configuration. If this occurs, remove unsupported modules and create the 1756-EN4TR module directly instead of changing module type.

This anomaly first identified in version 37.00.

Sequence Manager parameter values and descriptions are lost after project upgrade (5803385, 5837550, 5837546, 5837547)

Fatal error 0x8004203b when uploading specific project (5593747, 5662443, 5662447, 5662441)

A fatal error 0x8004203b occurs when uploading a specific project file that contained a Structured Text routine with an inline comment that was not placed on its own dedicated line. For example, uploading the file V39_ST_Fatal_23.ACD results in a fatal error instead of completing successfully. To resolve this, place the comment '//HYF 20250617' on its own line in the affected project file.

This anomaly corrected in version 36.06, 37.05, 38.03.

This anomaly first identified in version 36.03.

Axis scaling error in Windows 11 with Logix Designer (5627266, 5671237, 5671238, 5671236)

An error occurs when changing axis scaling parameters in Studio 5000 Logix Designer on Windows 11. For example, changing the Scaling Position Numerator value results in error 16427-80042FD2. This error does not occur on Windows 10.

To mitigate, export the project to L5K format, edit the scaling parameters, and re-import, or set Scaling Source to Direct Scaling Factor Entry before applying changes.

This anomaly corrected in version 36.06.

This anomaly first identified in version 32.00

Upload failure (1024944)

When attempting to upload a project, the Logix Designer application generates these errors and the upload fails:

• Error code: 731-0

• Error: [Routine Name]: Logic reconstruction data may be corrupted (displays in Error pane).

To work around this issue, remove long names from the project.

This anomaly first identified in version 32.00.

Tag based alarm does not create on import (1093641)

If Logix based alarms are not verified or created when importing a User-defined Data Type (UDT) that references them, users will experience a controller major non-recoverable fault (MNRF) after download.

This anomaly first identified in version 33.00.

The Logix Designer stops responding when copying motion axes (1170662)

When copying and pasting motion axes between motion groups, the Logix Designer stops responding.

This anomaly first identified in version 32.00.

The Tag Browser may disappear behind the Watch view preventing the user from selecting a tag. This can happen when the Watch view is in Auto Hide mode, the user opens the Tag Browser from the Watch view, and the Tag Browser appears outside the Watch view.

This anomaly first identified in version 32.00.

Use one of these steps to work around the issue:

• Dock the Watch view by selecting in the Watch title bar.
• Float the Watch view by selecting in the Watch title bar and selecting Float.

Size the Watch view so the Tag Browser fits inside the Watch view.

Some browsers (particularly the Microsoft Edge browser) may not launch the hyperlinks in the Sample Projects.pdf file when the hyperlinks are configured to open PDF files.   

This anomaly first identified in version 32.00

To work around this issue, open the PDF file with Adobe Acrobat Reader:

• Right-click the Vendor Sample Projects.pdf file and select Open with Adobe Acrobat Reader.

The Accelerate 3D Graphics setting in VMware sometimes causes the Logix Designer application to run out of memory.

This anomaly first identified in version 32.00.

Use one of these steps to work around this issue:

• In VMware, turn off the Accelerate 3D Graphics setting.
• Modify VMware Tools and remove the offending VMware SVGA 3D. This causes the display adapter to revert to Microsoft Basic Display Adapter mode.
• Upgrade VMware Workstation to version 15, which uses VMware SVGA 3D driver v8.16.1.1.

In the Tag Editor with Show: Consumed tags displayed, selecting all the consumed tags can cause the Logic Designer application to freeze.

This anomaly first identified in version 32.00.

• To work around this issue, press Esc. When an error message window appears that asks Do you want to abort the operation, select Yes.

Leaving multiple routines open for over two days while online with the controller can cause the Logix Designer application to crash.

This anomaly first identified in version 32.00.

Subroutine called by locked routine through JSR instruction might not show energized power rail (Lgx00218331)

When a locked routine uses a JSR instruction to call a subroutine, Logix Designer sometimes fails to display the power rails in the subroutine as energized. The problem is limited to the incorrect display; the execution flow in the controller is still correct.

This anomaly first identified in version 32.00.

Labels are cut off and dislocated in BOOTP-DHCP Server applications (Lgx00152848)

When the font size in Windows 7 is set to 125%, the labels in the Network Settings and DHCP properties of BOOTP-DHCP Server application are cut off, making them unreadable. They are also dislocated, where they do not match with the proper input fields.

This anomaly first identified in version 23.00.

Error in the content of Studio 5000 Logix Designer application generated reports (1421415)

"ACD filename - Label does not exist" appears at the top of the page instead of "ACD filename - Controller Organizer Listing" when using the Generate Report menu option. 

This anomaly first identified in version 33.00.

Editing Operand Description sometimes results in unexpected display behavior (1354684)

When the same tag description exists on many branches that span an area that extends beyond what is visible on a display and the tag description is edited, the content on the display sometimes jumps upon acceptance of the tag description edit. 

Using the left or right arrow keys causes the screen to focus on the tag description that was just edited.

The anomaly does not occur when the tag description is edited for the rung where the contacts are unique because the tag description only exists in one location.

This anomaly first identified in version 20.00.

Storing Firmware Supervisor files from PowerFlex 755T causes the <ST5LD>  application to stop responding (1518416)

Attempting to store Firmware Supervision files for PowerFlex 755T devices causes the <ST5LD> application to stop responding. The application must be closed using Task Manager.

This anomaly was first identified in version 33.00.

Can create safety I/O module successfully when Safety Modify Component set to deny (1787414)

You can successfully create an Add-On Profile based safety I/O module without errors when FactoryTalk Security user privileges's Safety Modify Component is set to Deny.

This anomaly first identified in version 35.00.

Direct Add-on-Profile-to-Device Communication Could Result in Time Out Errors or Communication Routing to the Wrong Device (1927272)

Direct Add-on-Profile-to-device communication could result in time out errors or routing the communication to the wrong device in circumstances where all of the following conditions are met:

• I/O must exist on a different subnet from the controller.
• Layer 3 switches used to separate and manage the routing of communication from the controller network to the network with the I/O.

This applies to configuration data that goes through unconnected communication to the target I/O device (for instance, uploading/downloading device parameters).

This does not apply to I/O data.

This does not apply to commands from the controller (for instance, inhibiting/uninhibiting a device).

Please see technote BF28941 for additional details.

This anomaly first identified in version 20.00.

Removed KNOptimassMfc400 profile (2106380)

The KN profile no longer has a license in the Logix Designer application.

This anomaly first identified in version 32.02.

Some Catalog numbers not displaying correctly in Module Discovery (2001084)

After creating a new L85E v35 project with a 5032 I/O-Link bridge device connected to the Ethernet bus and enabling at least one channel for the I/O-Link, connect Siemens-K20-4DI IO-Link device with the 5032 I/O-Link bridge module, and download the project. Launching Module Discovery from the I/O-Link bus shows some Catalog numbers do not display correctly.

This anomaly first identified in version 35.00.

I/O-Link Module Discovery displays 17.00 (100,1.1001) (1848106)

When creating an L85E project and adding a 5032-Master, after configuring some channels to I/O-Link and downloading the project, launch Module Discovery from the I/O-Link bus. The Revision column shows 17.000 for the I/O-Link devices instead of the expected 1.1 or 1.0.

This anomaly first identified in version 35.00.

L5K file with I/O Device cannot be imported (2047005)

When creating an L85E project using a 5032 master profile on the Ethernet bus and adding the I/O-Link device 42AF-R1MAB1-xx[209] with default setting on the I/O-Link bus, the error Unexpected end of file encountered occurs and the import is not successful.

This anomaly first identified in version 35.00.

Mismatching display resolution and scaling may result in overlapping SFC elements (2122642)

Editing a Sequential Function Chart (SFC)) using a display with a given resolution (for example, 1920 x 1200) and Windows scale setting (for example, 100%), closing the ACD, and then opening the same ACD in another resolution (for example, 3840 x 2160) and Windows scale setting (for example, 150%) may result in overlapping SFC elements.

Studio 5000 Logix Designer Ladder Diagram routines may stop execution after download (2047296)

Studio 5000 Logix Designer ladder diagram routines may stop execution after download to ControlLogix 5580, GuardLogix 5580, CompactLogix 5380, 5480 and Compact GuardLogix 5380 controllers. See Product Notice ID: PN1620 for the specific sequence of events to experience this anomaly.

This anomaly first identified in version 31.00.

Using specific set of characters in structured text outlining comment, will cause an upload failure into a blank project ACD file (2207451)

Using the ** set of characters with a single-line comment (//) (that is, //**) in a structured text outlining comment (#region\#endregion) causes an upload error into a blank ACD file. The ** characters are used for multi-line comments and using the ** characters with a single-line comment causes this anomaly to occur. 

To work around this issue, put double quotes around the ** characters, such as “**”.

This anomaly first identified in version 31.00.

1. Add a 5015-AENFTXT adapter, firmware revision 3.011, to a Logix Designer application project, version 37.00 or later.
2. On the Connection category, inhibit the connection to the module.
3. Manually change any value except the IP address or Host Name.
4. Attempt to apply the changes. The attempt fails, and an Execution failed message (16#0C) appears.

Project Path setting is ignored (3855364)
The Logix Designer application ignores changes to the directory path in the Project Path setting on the Workstation Options dialog. When you modify the default project path, C:\Users\UserName\Documents\Studio\Studio 5000\Projects, the new path does not appear in the Save As dialog, the Open dialog, and the Location field when you create a new file. Also, project backup files continue to be stored in the same directory as the opened .ACD file.
There is no workaround to this issue.

This anomaly first identified in Logix Designer version 31.00.

Fatal error when trying to create a tag for an undefined program (3907641)

The Logix Designer application experiences a fatal error when attempting to create a tag for an undefined program.

This anomaly corrected in version 36.06.

This anomaly first identified in version 36.00.

• Microsoft .NET Error: System.NullReferenceException: Object reference not set to an instance of an object.
• Fatal Error: 0xe0434352

To work around this anomaly:

• Use an IODD file that supports IO-Link version 1.1.2.
• Configure the connected IO-Link device as a Generic Device.

​Anomalous behavior when editing a large Structured Text routine (3838969)

​When editing a large Structured Text routine with outlining, the following issues might occur:

• ​​The line in focus changes during an edit.
• ​The text regions do not fully expand or collapse when commanded using keyboard shortcuts.
• ​The application encounters a fatal error.

​This anomaly first identified in version 32.00.

When enabling SFC forces, the system displays erroneous information (4041343)

• The controller is a GuardLogix 5580 or 5380 model.
• An SFC routine is present.
• The controller has a safety signature.

Despite these messages, SFC forcing functions as expected.

This anomaly first identified in version 33.00.

For more information on when this anomaly was corrected, see the controller firmware release note When enabling SFC forces, the system displays erroneous information

• 1834-AENTR
• 100-E-INT-D
• 104-E-INT-D
• 100-E-INT-X
• 104-E-INT-X
• 800F-INT
• 800F-INT-L
• 1834-SUP-PWR

To work around the error:

1. In Windows Start, search for and open the Computer Management app.
2. Select Local Users and Groups > Groups.
3. Add a local Windows group and name the group Users.
4. Add the logged in user to that Windows group.
5. Reboot your computer and reattempt the install.

• adding a new EDS AOP module.
• copy/paste of the EDS AOP module.
• import/export of the EDS AOP module.

Mitigation for Microsoft DCOM Hardening patch

To help meet secure system design requirements, review these publications:

• Configure System Security Features User Manual (publication SECURE-UM001)
• System Security Design Guidelines Reference Manual (publication SECURE-RM001)
• Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001)

To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products (publication SECURE-AT001).

Supported Logix controllers

One method to restore or reset Workstation Options is to hold Ctrl + Shift, launch the Logix Designer application, and continue to hold Ctrl

+ Shift until the application is fully launched.

Clicking Yes on the dialog box while continuing to hold Ctrl + Shift, the Workstation Options are not reset. To reset Workstation Options, use one of these workarounds:

• Temporarily set UAC to Never notify.
• Release Ctrl + Shift, click Yes on the dialog box, and then immediately hold down Ctrl + Shift.
• Open the Logix Designer application, click Tools > Options to open the Workstation Options dialog box, and for each Workstation Option category, click Reset Category.

FactoryTalk Linx compatibility and end of support for RSLinx Classic

The devices and profiles listed here are compatible only with RSLinx Classic and are not supported with version 38.00.

• 1305
• 1336
• GuardMaster and GuardLink (440C-CR30-22BBB), versions 3.0100 and earlier
• HIPROM
• 1788-EN2PAR
• 1788-CN2PAR
• 1788-EN2FFR
• 1788-CN2FFR

To get the same SFC layout as in v30.00 and earlier:

1. Select Tools > Options.
2. In the Workstation Option, select Structured Text Editor > Font/Color.
3. In Font, choose Courier New.
4. In Size, choose 8.

• Export the version 11 project file to an .L5K file, and then import the .L5K project file into version 21.00 and later.
• Convert the project from version 11 to version 12.00 through version 20.00 before converting the project to version 21.00 and later.

SequenceManager not available on Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580,

GuardLogix 5580, and ControlLogix 5590 controllers

However, SequenceManager is available on these Process controllers:

• 5069-L320ERP
• 5069-L340ERP
• 1756-L81EP
• 1756-L83EP
• 1756-L85EP
• 1756-L905TPSXT
• 1756-L915TPSXT
• 1756-L950TPSXT
• 1756-L980TPSXT

• When previous versions of Logix Designer are installed after version 30.00, .NET Framework 4.6 may cause installation to fail for these earlier versions of the Logix Designer application.
• When installed on 32-bit Windows operating systems, .NET Framework 4.6 causes versions 23.00 and earlier of the Logix Designer application to fail on startup.

Follow one of these steps to work around the issue:

• Do not install version 30.00 of the Logix Designer application on a 32-bit Windows operating system on which version 23.00 or earlier of the Logix Designer application is installed.
• Contact Rockwell Automation Support for instructions on disabling the Logix Designer Start page on versions 23.00 or earlier.

Disabling the Start page allows the Logix Designer application to start and run.

Signatures break for Add-On Instructions from previous Major Releases

These examples show how to use the installation commands.

• To install the software with no user interface using the default settings during the installation process. (Silent install)

• To install the Chinese language version of the software on the D: drive and display the progress, error, or complete messages during installation and restart the computer if necessary. (Unattended install)

The 1756-EN4TR Add-on Profile takes 10-15 seconds to fully load content while online with a controller if all of the following conditions are true.

• The controller is configured for Redundancy (Redundancy Enabled checkbox is checked in Controller Properties).
• The controller is configured for Obtain IP settings automatically using DHCP and is connected on the network.
• The 1756-EN4TR is configured for Adapter Pair, and either
1. not present
2. present and not connected to a network

The Module Info tab within Module Properties will not return module information when utilizing FactoryTalk Linx

Viewing the Module Info tab of any device in the I/O configuration results in the following error:

Internal direct communications error. Call Technical Support.

This error will occur even when the module is connected and successfully communicating with the controller. The error will only occur when utilizing FactoryTalk Linx as the communication software package for Logix Designer.

This is not an anomaly in Logix Designer.

This anomaly in FactoryTalk Linx was addressed in a Patch Update for FactoryTalk Linx. See technote BF28781 for additional details.