The Brovanture team has been testing the April 2026 Oracle Cloud EPM Update and has found that upgrading Oracle EPM Automate on Windows (as reflected in Oracle’s April 2026 update) introduces a change to default folder locations used at runtime. If you run Oracle EPM Automate via Windows scheduled tasks or batch (.bat) scripts, this change can cause jobs to fail when scripts rely on relative paths or previously used working directories.

Oracle now installs the EPM Automate program files by default under:

C:\\Program Files\\Oracle\\EPM Automate.

Separately, log files, encrypted password files, downloaded/upload staging files, user preferences, and other runtime artifacts now default to:

C:\\ProgramData\\Oracle\\EPM Automate

(regardless of whether this is a new installation or an upgrade).

Impact: After an upgrade, the EPM Automate installation folder may remain in its current location (for example, if it was previously installed to a custom path), but runtime files are still resolved from:

C:\\ProgramData\\Oracle\\EPM Automate.

As a result, Windows batch jobs can fail if they assume files will be found next to the script, under the prior installation folder, or in the current working directory.

In particular, please review any scripts that reference the following items using relative paths:

• encrypted password files
• upload/download staging files
• parameter files
• debug/log collection
• post-processing steps that move or archive files after EPM Automate runs

Brovanture recommended customer actions

To reduce risk of disruption, we recommend the following prior to upgrading in any production environment:

1) Test the upgrade in a non-production environment first.
Validate end-to-end scheduling, service accounts, working directories, and any file handoff/archiving logic before rolling the change into production.

2) Pause any automatic upgrade process until testing is complete.
If EPM Automate upgrades are automated in your estate, temporarily disable them to avoid introducing the new path behaviour unexpectedly.

3) Update scripts to use absolute paths for runtime files.
Review usage of:

Login

(encrypted password file)

uploadFile

parameter files, downloads, and any copy/move steps. Where applicable, reference files using fully qualified file names, or ensure they are placed under:

C:\\ProgramData\\Oracle\\EPM Automate

4) Confirm Windows permissions for the service account.
Installation/upgrade typically requires Windows administrator rights (because

C:\\Program Files

is protected). In addition, the account that runs scheduled tasks/batch jobs must have read/write permissions to

C:\\ProgramData\\Oracle\\EPM Automate

for logs, password files, and staging files.

5) Update monitoring and support runbooks.
Ensure operational documentation and monitoring point to the new runtime location for logs and debug output under:

C:\\ProgramData\\Oracle\\EPM Automate.

Summary / required attention
Although this is a folder-location change, it can have a direct impact on automated Windows batch and scheduler processes. Please test the upgraded EPM Automate version and update scripts to use corrected paths, or place required files under

C:\\ProgramData\\Oracle\\EPM Automate)

before upgrading production.

If you need help or have any questions you can get in touch with our support team using the form on the contact page of our website HERE.

The Brovanture Team