Release Notes - MIKE OPERATIONS 2026 Update 1¶
Release date¶
June 2026
Welcome¶
Welcome to MIKE OPERATIONS 2026 Update 1
In this Release Note, you will find information about new features of MIKE OPERATIONS and what you need to know to install and get started with Release 2026 Update 1.
MIKE OPERATIONS is a software product designed for data management and model-based forecast services for online operational control of river systems, water collection systems and water distribution systems. MIKE OPERATIONS empowers you to build real-time systems by offering flexible tools that help you deal with complexities such as acquiring and combining online data sources in preparation for real-time modelling.
MIKE OPERATIONS is a product consolidation of software tools developed and applied in projects since 2012. Hence, although MIKE OPERATIONS is a relatively new member of the MIKE product family it builds on proven software products that already serve many customers worldwide.
System requirements¶
The table below shows the fully supported operating systems. Those are systems that have been tested in accordance with MIKE's Quality Assurance procedures and where warranty and software maintenance agreement conditions apply.
| Supported Operating Systems |
|---|
| Windows 11 version 25H2 (64 bit) |
| Windows Server 2025 |
| windows server 2022 |
Note
When running a fully supported operating system as a 'guest operating system' on a virtualization platform, it is automatically downgraded to a non-supported operating system under the conditions provided above.
| Minimum hardware/software requirements | |
|---|---|
| Processor | Compatible with x64 instruction set, 2.2 GHz or higher |
| Memory (RAM) | 16 GB or higher * |
| Storage | 64 GB or higher * |
| Display | Resolution 1024 x 720 (High-Definition) or higher, 24-bit color (true color) |
| Graphics adapter | 64 MB RAM (256 MB RAM or higher recommended), 32-bit true color |
| Software requirements | Microsoft .NET Framework 4.7.2 or higher |
(*) The actual required amount of memory and disk space depend on the usage (application, model setup, size of data files etc.)
Installation and Prerequisites¶
Depending on your particular use case, several guides are available:
- Install MIKE OPERATIONS on a new Server, please follow this Installation Guide
- Install MIKE Modelling Workbench, please follow this Getting Started
- Upgrade MIKE OPERATIONS to a newer version (e.g. from version 2026.1 to 2026.2), please follow this Upgrade guide
License file and dongle¶
DHI License Management is used to configure the MIKE OPERATIONS licenses and visualise the modules available. The table below summarizes how the DHI License Mangement modules correspond to MIKE OPERATIONS Managers and User Interfaces.
| Licensed module | MIKE OPERATIONS User Interface/Manager |
|---|---|
| MO_DBase (*) | PostgreSQL and Microsoft SQL Server |
| MO_WorkbenchUI | MIKE Workbench MIKE Modelling Workbench |
| MO_Web_Operatior_View | MIKE OPERATIONS Web |
| MO_Desktop_Operatior_View | MIKE OPERATIONS (aka MIKE OPERATIONS Desktop) |
| MO_Data | Document Manager Favorite Manager GIS Manager Places Manager Report Manager Script Manager Spreadsheet Manager System Manager Time serie Manager Workflow Manager |
| MO_Planning | Analysis Manager |
| MO_RealTime | Job Manager Operations Manager |
| MO_Scenario | Scenario Manager Indicator Manager |
MOPY
(*) If this module is not licensed, only a single user SQLite database is enabled.
Product invocation¶
Launch MIKE OPERATIONS 2026, MIKE Workbench 2026, MIKE Modelling Workbench 2026 or Database Management Utily 2026 from the Windows Start menu.
Support¶
For general support, please refer to our FAQ or the MIKE OPERATIONS Online Help.
If you experience any difficulties, or if you have questions, please contact our Customer Care team.
You can also contact your local Customer Care team for support in your local language.
Breaking Changes¶
In an effort to improve the cyber-security of MIKE OPERAIOTNS, the encryption algothirm has been changed. This means that all databases must be updated.
New features¶
Every new release of MIKE OPERATIONS consists of new modules, new features and/or corrections to problems or significant inconsistencies discovered in previous releases.
| Tags | Title | ID | State |
|---|---|---|---|
| Job | New logs to investigate how jobs are triggered (see here) | 124474 | Closed |
| Scenario | MIKE+ - simplified model registration wizzard (see here) | 137878 | Approved |
| Scenario | MIKE HYDRO Basin - New polygons output model objects (see here) | 128459 | Closed |
| Scenario | FEFLOW - Support steady state models (see here) | 133354 | Closed |
| Scenario | Performance - faster import of res1d simulation results | 135489 | Closed |
| Scenario | Performance - faster deletion of simulations with many time series | 134481 | Closed |
| Desktop | Removed limitation of 200 station per layer | 137322 | Closed |
| Web | Assign different colour for each timeseries when using multi-select | 136994 | Approved |
| Web | Re-organise the columns in the Places configuration page | 138418 | Closed |
| Web | Automatic configuration does not work for my model | 122745 | Closed |
| Web | if a simulation has a SpatialOutputTimeseriesType.FeatureClass defined in the list of outputs, it should be loaded with the "View 2D results" control | 125446 | Closed |
| Web | Improve the error messages when connection creation fails | 132613 | Closed |
| WebAPIs | Show model, scenario and similation Ids in MIKE Workbench to simplify usage of Scenario End points | 137000 | Closed |
| WebAPIs | Create an installer to deploy the Web APIs on IIS | 137004 | Approved |
| WebAPIs | When clone a scenario, the end point requires both a Simulation and a scenario. Simplify but only requiring Simulation since this is how the cloning is implemented | 137852 | Approved |
| WebAPIs | Include the DHI.Services.OpenXML repository to the WebAPIs to work with spreadsheets outside of the database | 137831 | Closed |
Fixed issues¶
MIKE Workbench¶
| Module | Description | ID | State |
|---|---|---|---|
| Scenario | MIKE+'s new flood extent output (i.e. feature class) get created for each member when running ensemble simulation, instead of one per simulation | 129097 | Approved |
| Scenario | MIKE+ uses wrong 2D hotstart path | 133219 | Approved |
| Scenario | MIKE+ mesh file bug is not created in the correct folder | 133038 | Closed |
| Scenario | MIKE+ mesh file bug is not exported at all | 132645 | In Review |
| Scenario | MIKE+ does not generate a feature class when registering a global boundary conditions (e.g. rainfall), preventing it from being used in Places Manager | 138498 | In Review |
| Scenario | MIKE+ has misleading error message when trying to register model which is already open in MIKE+ | 133070 | Resolved |
| Scenario | FEFLOW postprocessing gets stuck when creating contours | 133540 | Closed |
| Scenario | MIKE1D fails to read GateLevel and ControlStrategy output timeseries because of mismatching description strings | 128983 | Closed |
| Event | Service becomes unresponsive after 12–14 hours because the subscriber leaks and shutdown deadlock | 138734 | In Review |
| GIS | The dfsu files generated by a MIKE 21FM PT model do not import | 139195 | Approved |
| GIS | Run the Cloud spatial tool fails if "Destination Root Path" is left empty | 125192 | In Review |
| Operations | Extensions - Chart - Legend item text overruns each other | 138540 | Approved |
| Operations | Extensions - Chart - Incorrect Column Width for Column Charts | 138703 | Approved |
| Operations | Extensions - Chart - Cannot Select None for Hatching Option | 138704 | In Review |
| Operations | Extensions - Chart - Now line not appearing | 138539 | Test |
| Operations | Viewsettings of one chart above another can cause the shell to crash | 138542 | In Review |
| Operations | Crash when loading a map view and associated time series | 138541 | New |
| Operations | Operations Manager Full Tree Export and Import Bug | 137474 | Test |
| Operations | SetState only works with basic accounts | 138533 | Test |
| Operations | State job task not displaying progress on the operations node | 138535 | Test |
| Operations | Right clicking a node causes the node to be immediately loaded | 138536 | Test |
| Operations | All calls to refresh the UI tree cause all nodes to be collapsed | 138537 | Test |
| Operations | Operations node is missing tooltip message on icon hover | 139344 | Active |
| TS | Timeseries cannot be saved when unit contains special characters | 139109 | Approved |
| TS | Time serie calculator cannot filer values below 0.01 | 139180 | Approved |
| TS | Time series import tool creates time series with the wrong names when using the batch option | 135025 | Closed |
| TS | MIKE Cloud updload tools should not renames time series (i.e. replace ':' by '-') | 135368 | Closed |
| TS | Registering a MIKE Cloud time series throw the error "The given key was not present in the dictionary" | 125341 | Closed |
| TS | The import from dfs0 tool is not backward compatible, by default, only the first time series item is imported instead of all items | 138497 | In Review |
| Other | MIKE 2026 has a new License Manager but the links in the trouble shooting wizzard point to the old one | 139090 | Approved |
| Other | Extending the Login window should not move the Workspace field | 128205 | Closed |
| Other | In the connection manager windows, clicking on Edit opens the wrong connection | 128208 | Closed |
| Other | Progress Bar is not anymore | 138546 | In Review |
| Other | Progress Bar updates slowly when script not run on separate thread | 139343 | Active |
MIKE OPERATIONS Desktop¶
| Description | ID | State |
|---|---|---|
| When re-loading a set up, all the stations are stations duplicated | 138523 | Approved |
| Mouse-over label is not available anymore in the charts | 129500 | Resolved |
| Hide/Show empty timesteps not available anymore | 136988 | Resolved |
| Chart x-axis shows the wrong date format | 136989 | Resolved |
| Threshold shown for wrong axis | 136991 | Resolved |
| The time of forecast line should not move | 136992 | Resolved |
| Null values in times series should not be used by line | 139021 | Resolved |
MIKE OPERATIONS Web¶
| Description | ID | State |
|---|---|---|
| Filtering places does not work | 137157 | Closed |
| Places dont load properly | 134339 | Closed |
| A place does not load properly | 137158 | Closed |
| Places do not load because auto-configuration does not handle polygons properly | 137159 | Closed |
| When an error occurs in the scenario cloning, the front end does not handle error properly | 137573 | Closed |
| Thresholds dont show propertly | 132390 | Closed |
| Cannot multi-selecting similar variables for different stations | 138417 | On Hold |
Web APIs¶
| Description | ID | State |
|---|---|---|
| When cloning a scenario with the WebAPIs, the execution parameters are not cloned | 138887 | Approved |
| When cloning a scenario with the WebAPIs, if the output model object has more then 1 time series, only the first one is copied | 138887 | Approved |