Информация о выпуске опубликованных версий
Created: ноября 01, 2024 | Updated: декабря 03, 2025
This page lists the release notes for publicly released versions of Altium Designer 26, Altium Designer Develop 26 and Altium Designer Agile 26.
Version 26.1.1
Altium Designer Develop – Released: 3 December 2025, Version 26.1.1 (build 6)
Altium Designer Agile – Released: 3 December 2025, Version 26.1.1 (build 13)
Altium Designer – Released: 3 December 2025, Version 26.1.1 (build 7)
Schematic
| 62751 | Added a new advanced settings option 'WSM.DotNetECOImplementation' that, when enabled, optimizes and accelerates ECO processing functionality. |
| 66529 | Double-clicking on a placed component would correctly access the Properties panel with the Designator text selected, ready for change. However, double-clicking on a subsequent component would not result in the designator text being selected, but rather the cursor placed at the start of the field. (BC:25802) |
| 67151 | In some cases when working with a schematic document, crossing of signal harnesses under a compile mask (with the 'Display Cross-Overs' option enabled on the Schematic - General page of Preferences), would result in the error "EOleException: Index was outside the bounds of the array" being encountered. |
| 67186 | There was a noticeable delay in the loading of properties into the Properties panel when switching between symbols in a schematic library (.SchLib). (BC:25112) |
| 67514 | In some cases when switching between comments in a schematic, the error "Cannot set Visibility or call Show, ShowDialog, or WindowInteropHelper.EnsureHandle after a Window has closed" would be encountered. |
| 67618 | After making the name of a parameter visible in the design space, it would display twice while dragging that parameter to a different location. |
PCB
| 52067 | With Violation Overlay Style set to 'None (Layer Color)' and Overlay Zoom Out Behaviour set to 'Base Pattern Scales' (on the PCB Editor - DRC Violations Display page of the Preferences), opening or creating a PCB would result in an Access Violation (in module 'ADVPCB.DLL') being encountered. (BC:19367) |
| 58670 | Added option (PCB.Performance.PadViaTemplate.LoadingOptimization) to store Pad Via templates not linked to an external Pad Via Library, inside the PCB document, enabling faster load times. |
| 61493 | Added an Advanced Settings option (PCB.ViaInstancing) that when enabled, enhances performance when building the geometry of an instance of a via, reducing both memory consumption and scene building time. |
| 63635 | There was a noticeable delay when starting to pan within the design space, when an interactive command (e.g. Move Object, Interactive Routing, etc...) was running. |
| 65474 | Observing the IPC-7351B standard in relation to padstack defaults, where the solder mask openings are typically a 1:1 ratio of the land size, default values for the Solder Mask Expansion rule (in PCB documents) and rule-driven solder mask expansion (in PCB library documents) are now set to 0 mil (previously 4 mil). |
| 65539 | After adding comments to a PCB, switching to 3D viewing mode, changing to orthographic projection and rotating the PCB, would result in PCB artifacts being displayed. |
| 65636 | Added a new advanced settings option 'PCB.SimbeorVersion' to control the version of Simbeor used in the calculation of delay and impedance (Simbeor 2020.3 (option '0') or Simbeor 2023.1 (option '1')). |
| 65828 | With a polygonal-shaped object selected on a PCB and when using the Paste command from the right-click context menu in free space within the Outline Vertices section of the Properties panel, the error "Exception has been thrown by the target of an invocation..." would be encountered. |
| 65866 | As part of the PCB.Performance.InteractivePropertyPanel.Optimization option (Advanced Settings), the Properties panel has been further enhanced when working with the Interactive Routing/Differential Pair Routing/Multi-Routing, Quick Routing, Interactive Sliding and Interactive Via Dragging features, to increase performance and optimize access to properties, especially with larger designs. |
| 65971 | Placing (or copying/pasting) from a PCBLIB to a PCB document did not follow the physical order of the layers, resulting in primitives being placed on the wrong layers on the PCB document. Note that as part of the fix for this issue, you must resave your PCB libraries using Altium Designer 22.11 or later. |
| 66010 | When routing to a pad that was previously impacted by running the 'Remove Unused Pad Shapes' feature, the missing annular ring was no longer being detected by DRC. (BC:24704) |
| 66318 | When using the PCB Library panel's 'Select All' command (on the right-click context menu), all footprints in the list would only be selected if the command was used on the first (top) footprint in the list. |
| 66319 | Design Rule Check (DRC) would incorrectly report Un-Routed Net violations on multiple SMT pads thermally connected to a polygon pour, when Thermal Relief was set to 'Auto' and overlapping Polygon Connect Style rules were present. |
| 66678 | In some cases when using the automatic diff pair length tuning tool to phase match between the sides of a differential pair, the actual measured Tooth Width of the generated sawtooth-based pattern differed from that specified in the Auto Tuning Process dialog. (BC:25941) |
| 66726 | With the PCB.Performance.InteractivePropertyPanel.Optimization option disabled (Advanced Settings) and multiple parameters (component designators and/or comments) selected in the design space (or multiple components selected and clicking through to child Designator or Comment in the Properties panel), the Autoposition property and Value visibility control ('eye' button) were missing from the Properties panel. (BC:26018) |
| 66879 | Delay values for nets and xSignals that included a length tuning pattern were not being calculated and were incorrectly displayed as 0 ps in both the Properties and PCB panels. (BC:26054) |
| 66948 | For a Clearance design rule defined through the PCB Rules and Constraints Editor dialog and where the clearance matrix contains differing values for primitive combinations, the Gap value in the Applicable Binary Rules dialog did not correctly reflect the clearance value defined for the selected primitives in the rule's clearance matrix. |
| 67027 | In some cases, copying-pasting a rectangle and then attempting to change that pasted rectangle's size, would lead to an Access Violation (in module 'ADVPCB.DLL') being encountered. (BC:26086) |
| 67094 | With the PCB.DRC.OnlineOptimization option enabled (Advanced Settings), running a DRC for a rule class from within the PCB Rules And Violations panel would result in the violations for other rule classes becoming cleared. |
| 67123 | When exporting a PCB as a Specctra design file, the export process had, in some cases, become considerably slower. |
| 67161 | In some cases when working with a selected polygon pour, the error "Object accessed after being destroyed" would be encountered. |
| 67207 | When modifying the assigned layer numbers of existing Component Layer pairs in the PCB Library or PCB editors, Altium Designer new mechanical layers would be incorrectly generated. Deleting these layers would result in the associated Layer Type being lost, reverting to 'N/A'. |
| 67224 | It was not possible to gloss differential pairs with rounded corners (Hugging Style = Rounded) when the glossing Effort was set to Weak. (BC:26265) |
| 67238 | The 'PCB Properties Panel Optimizations' feature, delivered by the PCB.Performance.InteractivePropertyPanel.Optimization option (Advanced Settings), is now officially made Public with this release (ON by default). |
| 67466 | Added a 'hand' cursor when panning (Right-Click, Hold&Drag) during an interactive process within a PCB document. |
| 67534 | For a rigid-flex design with coverlay layers defined and added to a board region with assigned flex stack, setting the Active Layer field to a coverlay layer (on the Layers & Colors tab of the View Configuration panel) would result in Altium Designer becoming unresponsive. (BC:26402) |
| 67894 | In some cases when working within the Properties panel, the error "Object reference not set to an instance of an object" would be encountered. |
PCB CoDesign
| 64925 | For a specific PCB design, attempting to run the PCB Comparison feature would result in the error "System.NullReferenceException: Object reference not set to an instance of an object" being encountered. |
| 67414 | In some cases when running a comparison, the error "Object reference not set to an instance of an object" would be encountered. |
Constraint Manager
| 64463 | Introduced a ‘Class Filtering’ capability when working with the Clearances view. This enables the construction of filters (or groupings) of classes to allow switching between, and working with, focused sub-sets of the clearances matrix. |
| 65702 | When working with a Workspace project that uses Constraint Management, if the project's constraints.xml file was deleted locally (through Windows File Explorer), the Save to Server dialog would no longer appear when using the control (Save to Server) to save the project back to the Workspace. |
| 65937 | It is now possible to set/edit a Creepage value when multiple cells are selected in the Clearances Matrix. Changes made are reflected by the Creepage rule(s) being created/updated in the All Rules view (when the Constraint Manager is accessed from the PCB). |
| 66146 | For a parameter set associated to a signal harness whose directives have already been imported to the Constraint Manager, subsequent selection of the parameter set object on the schematic would result in the error "Exception has been thrown by the target of an invocation..." being encountered. (BC:25707) |
| 66590 | Enhanced handling of clearance rules with custom query expressions when migrating from the older design rules system to the Constraint Manager. This includes better handling of rules with scope expressions targeting inner (mid) layers and ensuring such rules are made Advanced Rules (and not Basic Rules). |
| 66788 | For a specific design, attempting to access the Constraint Manager from a schematic document would result in the error "An item with the same key has already been added..." being encountered and subsequently all views becoming empty. |
| 67392 | After creating a new clearance rule in the Clearance view of the Constraint Manager, the interactive multi-routing tool did not respect the minimum clearance boundary during routing. |
Draftsman
| 49410 | For a specific project, the software would crash when updating the Draftsman document with changes from the PCB, then selecting a placed Ordinate dimension. |
| 63602 | When editing a Workspace Draftsman Document Template, placing a drill drawing view or a transmission line table would result in the error "Object reference not set to an instance of an object" being encountered. (BC:24492) |
| 65704 | Added support for importing DXF files (version R12 and later) into a manufacturing drawing document (.PCBDwf/.HarDwf/.MbDwf). |
Wire Bonding
| 63827 | In the primitives region of the PCB panel (with a selected component in Components mode) and PCB Library panel (with a selected footprint), bond wires are now presented with the correct type (Bond Wire). Selecting a bond wire primitive will select/highlight that bond wire within the main design space. In addition, a corresponding "Show Bond Wires" option is now available on a region's right-click context menu, for toggling bond wire visibility. |
| 63869 | After running a DRC and browsing length violations for bond wires in the PCB Rules And Violations panel, those violations would unexpectedly have changed after saving-closing-reopening the PCB document. |
3D-MID Design
| 65950 | For a selected track, it was possible to type a new value into the Length field (in the Properties panel) which did not change the actual length. Resolving this, the Length field has been made non-editable. |
| 67570 | Added a new advanced settings option '3DLayout.DRC' that, when enabled, provides batch Design Rule Checking (DRC) for Width, Clearance, Length and Matched Lengths rule violations, in respect to routed tracks on your 3D substrate. Note that while a generated DRC report will provide information for all of these checks, only clearance violations will be highlighted within the main design space. |
Multi-board Design
| 64949 | Added the ability to define the 'Termination Type' for a selected harness entry on a multi-board schematic. Choose from 'Connector', 'Crimps/Ferrules' and 'Wire termination'. The information is reflected in the properties for the selected harness itself and in the properties for the selected corresponding module entry. |
| 67391 | When using custom parts in a multi-board schematic, it was possible for the data to become corrupted, leading to data loss and experiencing one of various errors/crashes, depending on the nature and extent of the corruption. |
Harness Design
| 61571 | Added the ability to generate, through an OutputJob, a single Excel Workbook containing data for use by harness manufacturers. The generated Workbook includes sheets for ‘Bill of Materials’ (useful for quick quote generation), ‘Wiring List’ (for use with wire processing machines), ‘Labels’ (a summary of the physical labels to be printed for harness bundles, for use with Zebra or other printers) and ‘Coverings’ (a summary of the coverings to be applied over harness bundles). |
| 63973 | Harness wires connected with a wire break are now recognized even if they have different Design Item IDs. In addition, all wire segments with the same designator and connected by the same wire break are now compared (for part number, comment, color and all parameters) and, if any differences are found, a new 'Mismatched parameters in connected wire segments' violation will be reported. In conjunction, a conflict banner will appear in the Properties panel, offering the ability to synchronize all wire segments to use the same parameters as those of the chosen wire. |
| 65569 | Added the ability to apply/extend a covering over a junction point (a connection point in the layout drawing where two or more bundles come together). In addition, the start of a covering is now taken as the left-most, top-most point of its path, and that path now includes only the bundles the covering lays on. (I:24932) |
| 66016 | For a harness component with a defined crimp cavity whose part contained no symbol and one or more parameters with empty values, using the 'Update From Libraries' command would result in the error "System.ArgumentNullException: Value cannot be null. (Parameter "value")" being encountered. |
| 66323 | For wire, cable and covering entries in the ActiveBOM or a BOM Table in a manufacturing drawing document (*.HarDwf), the entry in the Quantity field is now 'As Required'. |
| 66740 | Enhanced the pin ordering for a wiring list placed in a harness manufacturing document. Now, for the connector with the most wires, automatic grouping is applied and all of its cavities are correctly grouped in the From column. |
| 66741 | After placing and configuring a connection table or wiring list in a harness manufacturing drawing document (*.HarDwf), a subsequent copy-paste of the object would result in the columns and other configured parameters being reset to their defaults. |
| 67130 | For a wire break with a defined Wire Designator, the designator was not preserved when connecting a wire to that break. |
| 67214 | After locking the Length parameter for a selected bundle on a layout drawing, it was not possible to then unlock it again. (BC:26239) |
Platform
| 60238 | Added a new advanced settings option 'System.UseWebView2' to enable use of WebView2 for browser-related elements within Altium Designer (e.g., the Home page). This delivers access to the latest web browser engine within Altium Designer, just by updating Windows. Note that when disabled or if a connected Workspace does not support WebView2, CefSharp v.126 will automatically be used. |
| 65737 | With this release, Altium Designer switches from using .NET 6 to .NET 8. |
| 65961 | Whenever required to sign in to your Altium account through your default Web browser (driven by the 'Unified Login' feature), Altium Designer will now automatically be presented (given focus) once the log-in process completes. |
Data Management
| 59401 | When a comment is added as part of a design review, a link to that review ('From <DesignReviewName>') is now presented in the contextual commenting window for that comment (within the design space). |
| 63542 | Cross-selection between a selected part on a schematic and the corresponding line in the project's ActiveBOM document, was not working. (BC:24441) |
| 63990 | For a specific component, it was not possible to open its associated data sheet from within the Manufacturer Part Search panel or Add Part Choices dialog. |
| 64571 | In some cases during poor internet connectivity, the warning "Push notifications service was not properly initialized. Connection Timeout" would appear and Altium Designer would become unresponsive, requiring termination through the Task Manager. (BC:24707) |
| 64777 | After adding a new column for a component type to the Manufacturer Part Search panel, that column was not visible until switching to another component type and back again. |
| 64783 | Added the ability to define and sync part choice information using the Components Synchronization feature and its related Components Synchronization Configuration document (*.CmpSync). |
| 65063 | In some cases when working with the Project Releaser, an Access Violation (in module "ProjectReleaser.dll") would be encountered. |
| 65126 | In some cases when generating a BOM report from an ActiveBOM, adding data columns from the source PCB would lead to the error "The method or operation is not implemented" being encountered. |
| 65397 | A new control "Refresh VCS Statuses" (with associated tool-tip warning) is now presented next to a project’s entry in the Projects panel if there is an issue connecting to a Workspace and the latest VCS states of project documents are not able to be refreshed. Once connection resumes, click the control to bring the VCS states back into sync and to see the latest changes. |
| 65690 | After changing the name of a connected Workspace, a PCB design's project file (*.PrjPcb) would still refer to the old Workspace name in any alternate parts defined for variants. The Variant Manager and the Item Manager would therefore incorrectly present the old naming. |
| 65696 | Added a new advanced settings option 'VCS.HideProjectExternalRepositoriesLinks' that, when enabled, hides links to external VCS repositories (created automatically when making a project under external VCS available to a connected Workspace). |
| 66071 | Added support for making a copy of a Workspace project (from the Projects panel's right-click context menu) using defined (and enabled) process workflows. |
| 66123 | In a specific case and when getting advanced part data from SiliconExpert for a selected part in the Manufacturer Part Search panel, the error "Object reference not set to an instance of an object" would be encountered. (BC:25701) |
| 66241 | After batch-updating the lifecycle state for all components in a design project, the first component's lifecycle was not updated at all. In addition, the display of the new lifecycle state for all other components was not refreshed until after a restart of the software. |
| 66273 | Where the Explorer panel is configured to present the Altium Content Vault ('Explorer.ShowContentVault' option enabled in the Advanced Settings dialog), the Library Health entry (in the listing of server folders) is no longer displayed. |
| 66293 | For a specific project, attempting to access its history would result in the catastrophic error "Object reference not set to an instance of an object..." being encountered. (BC:25786) |
| 66358 | Attempting to add a solution from a custom part provider source (defined in a connected Enterprise Server Workspace) to a component in an ActiveBom, using the 'Add Solution » Create/Edit Manufacturer Links' feature, would lead to the error "Failed to pull data" and result in the solution not being displayed for the component. |
| 66419 | When attempting to export the active Project History view for a project to PDF using the Smart PDF feature (choosing 'Current Document' as the export target), an Access Violation (in module 'WorkspaceManager.DLL') would be encountered. |
| 66445 | When attempting to create a harness template document in a connected Workspace without rights to create a folder, a crash would be encountered. |
| 66510 | In a specific case, trying to detach a project folder that did not have permissions inheritance enabled, when that folder was inside of a folder with inherit permissions enabled, resulted in an Access Violation being encountered. |
| 66532 | When saving the active PCB Library, with a single footprint, to a connected Workspace, the subsequent dialog had a typo for the intended word 'Planned' in its header ("Choose Planed Item Revision"). (BC:25864) |
| 66683 | After creating a component with a part choice through use of the Database to Workspace component synchronization (.CmpSync) feature, when editing that component in the Component editor (in its Single or Batch Component Editing modes), data for its part choice was not being displayed (description, associated supplier solutions (SPNs) and pricing). |
| 66701 | Added ability (for those with assigned operational permission) to preserve a model's current lifecycle state when releasing into a new revision. |
| 66910 | For multiple instances of a component being used in a design, changing the component to a different one, through the ActiveBOM, would not apply that change to all instances in the subsequent ECO. (BC:26132) |
| 66964 | In some cases when attempting to create a new Workspace Library component (via File » New » Component), the error "EOleException: Object reference not set to an instance of an object" would be encountered. |
| 66995 | Improved the performance of the Open Project dialog when loading the project folder view for projects in a connected Workspace and the user has access to many projects. |
| 67009 | Since nested reuse blocks are not supported, commands to place a reuse block have been removed from menus and the Active Bar in both the Schematic and PCB editors, after having created a new reuse block or when editing an existing one. |
| 67074 | When editing a component in the Component editor (in its Single or Batch Component Editing modes) and adding a part choice from a Custom Parts Provider, data for that part choice was not being displayed (description, associated supplier solutions (SPNs) and pricing). |
| 67195 | When a comment is added as part of a design review, a link to that review ('From <DesignReviewName>') is now presented within its corresponding entry in the Comments and Tasks panel. |
| 67357 | Added a new advanced settings option 'BOM.CoDesign.Comparison.IncludeSupplierData' that gives you control over whether or not supplier-related data is included in results when comparing an ActiveBOM with a selected Managed BOM, using the BOM CoDesign feature. When disabled, supplier-related data is excluded from the Differences section (on the Related BOMs tab of the Properties panel, when accessed from a project’s ActiveBOM document) and also in the generated comparison in the Altium Platform’s Web Viewer interface. |
| 67410 | Added support for additional unit-aware data types – Area (mm2), Bar (bar), Bit, Candela (cd), Decimal, Integer, Joule (J), Lumen (lm), Millimetre (mm), Pascal (Pa), Pounds per square inch (psi), Rotations per minute (rpm), Siemens (S), Tesla (T) – when defining a user parameter as part of a component template in a connected Workspace on the Altium Platform. |
| 67803 | Attempting to generate PDF data from a specific Output Job configuration file would result in Altium Designer freezing and needing to be terminated using the Windows Task Manager. |
| 67948 | For non-Workspace Library parts, after creation of a solution for a component in an ActiveBOM, SPNs relating to DigiKey were not being presented in the solutions region. |
Import/Export
| 57602 | When importing a specific, hierarchical KiCad design, components were missing from an imported child schematic sheet in the hierarchy. |
| 61888 | When importing a KiCad v.8 design, arc primitives were not being imported on the generated schematic documents. |
| 61963 | When importing a KiCad design, curved tracks were being imported incorrectly, with start and end angles for associated arcs inverted. (BC:20658) |
| 63187 | When importing a specific v8.x KiCad design, polygons were not being imported. |
| 63467 | When importing a KiCad design, the view of the PCB Documents (on the General Import Options page of the Import Wizard) was clipped and could not be adjusted, meaning it was not possible to review the output project structure. |
| 63776 | When importing a version 8.x KiCad design, net classes were not being imported. |
| 65163 | Alternate view modes for components are now supported, in both generated schematic and schematic library documents, when importing an xDX Designer design. |
| 65451 | When importing a specific xDX Designer design, designators were being imported incorrectly. |
| 65907 | When importing a specific Allegro design, package geometry silkscreen objects were missing from the generated Top Overlay and Bottom Overlay layers. |
| 65913 | When importing a specific Allegro design, pads with slot holes were not being imported correctly into the generated Altium Designer PCB document, both in terms of their shape and their coordinates. (Requires the Importer.Allegro.ReadPadLayers advanced settings option to be enabled). |
| 65925 | In some cases when importing an xDX Designer design, images were not being imported/displayed on a generated schematic document. |
| 66138 | When importing a specific Allegro design, the footprint pads of some components were not being imported correctly. |
| 66139 | When importing a specific Allegro design, board outline geometry was not being imported correctly into the generated PCB document. |
| 66664 | When importing an OrCAD design, Japanese (shift_jis charset) and Korean (hangeul charset) symbols in text were not being faithfully imported. |
| 66961 | When importing a specific OrCAD design, power port names would be incorrectly placed to overlap their associated symbol graphics, in the generated schematic documents. |
| 67038 | The Allegro2Altium.bat file, a batch file included in your Altium Designer installation and used to convert an Allegro binary (*.brd or *.dra) file to ASCII format (when such a design/library is not on the same PC as Altium Designer), has been improved to include all configuration files necessary for its use. |
| 67084 | In some cases when importing an Allegro design, text on a Silkscreen layer would be imported incorrectly. |
| 67101 | When importing a specific OrCAD design, some custom ports were appearing rotated in the generated schematic document and not visually connected to wires (even though they were actually connected to their relevant nets). |
| 67106 | In some cases when importing an OrCAD design, the designator and parameter for some components were being incorrectly placed overlapping on a generated schematic document. |
| 67139 | When importing an Allegro design containing a mechanical component with identical geometry defined on both top and bottom Silkscreen layers (at the library level), text on the Bottom Silkscreen layer would be incorrectly duplicated. |
| 67143 | The 'Import Detailed Allegro Pad Stack' feature, delivered by the Importer.Allegro.ReadPadLayers option (Advanced Settings), is now officially made Public with this release (ON by default). |
| 67176 | When importing a specific OrCAD design, a hidden parameter for a component was being incorrectly displayed on a generated schematic document. |
| 67182 | When importing an Allegro design, component values were incorrectly being displayed on silkscreen layers of the generated PCB document, even though visibility on these layers (for the 'Layers - Components - Comp value' sub-class) was disabled in the original design. |
| 67585 | When attempting to export a PCB to the Protel PCB 2.8 ASCII file format, an Access Violation "Object accessed after being destroyed" (in module 'ADVPCB.DLL') would be encountered. |
Power Analyzer by Keysight
| 65355 | When viewing the details for any network in an analysis report, the value presented for the 'Power Consumption for This Network' field was always displayed as "0 Watts", instead of the actual power consumption. |
| 66130 | When increasing the Work Temperature, the resulting Voltage Drop was incorrectly decreasing rather than also increasing. (BC:20248) |