---
title: "Fix Workday Studio SDKProfile and Unsigned Startup Errors"
description: "Fix Workday Studio Profile SDKProfile is not current p2 errors, macOS Gatekeeper quarantine blocks, Windows Program Files write locks, and JDK 17 + JDK 8…"
url: https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors
---

# How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows

Workday Studio throws Profile SDKProfile is not current when Eclipse p2 metadata gets out of sync after an interrupted update or read-only install path, while unsigned warnings stem from macOS quarantine attributes or Eclipse plugin trust prompts. Clear quarantine or reinstall cleanly.

-   **Checked** against Workday on November 13
-   Applies to **Workday Studio**
-   7 min read
-   Published November 13
-   By Kiweely

Workday Studio throws `IllegalStateException: Profile SDKProfile is not current` when its underlying Eclipse Equinox p2 provisioning registry falls out of sync after an interrupted patch, a read-only installation folder on Windows, or an independent Eclipse platform update. Unsigned software blocks happen at two separate layers: macOS Gatekeeper quarantining the downloaded installer or app bundle at launch, and Eclipse p2 prompting you to trust unsigned plugin JARs during `Workday > Update Workday Studio`.

Because Workday allows only one current Workday Studio release to connect to Sandbox or Production tenants, leaving an update half-applied blocks Cloud Explorer deployments until you either clear the OS lock or replace the Studio binary directory cleanly while keeping your workspace intact.

## Which Startup or Update Failure Are You Hitting?

Before wiping your setup, match the exact dialog text to the layer raising it. Mixing up an OS quarantine prompt, an Eclipse p2 registry lock, and a missing Java 8 runtime wastes hours on the wrong fix.

| Error or Symptom | Layer Raising It | Root Cause | Direct Fix |
| --- | --- | --- | --- |
| `Profile SDKProfile is not current. Expected timestamp ...` | Eclipse Equinox p2 (`p2/org.eclipse.equinox.p2.engine`) | Concurrent Studio process, aborted in-place update, Windows UAC write virtualization under `C:\Program Files`, or running Eclipse’s generic `Check for Updates` | Close all Studio/Java processes, run once with `-clean` (and elevated rights if installed in `Program Files`), or do a clean Studio binary reinstall |
| `"Workday Studio" is damaged and can't be opened` or `"cannot be opened because the developer cannot be verified"` | macOS Gatekeeper (`com.apple.quarantine`) | Browser download attached a quarantine extended attribute to the `.dmg`, installer `.jar`, or extracted `.app` bundle | Inspect and clear the quarantine attribute on the official download or approve via **System Settings > Privacy & Security** |
| `Trust Authorities` / `Unsigned Content` dialog during update or BIRT Report Designer install | Eclipse p2 artifact verifier | Studio update site or plugin bundle includes JARs without an Eclipse PGP/jar-signer chain in the local trust store | Verify you used **Workday > Update Workday Studio** (not an external update URL), review the listed `com.workday.*` / BIRT bundles, and explicitly select and trust them |
| Studio IDE opens, but AUnit or local debug fails with `JavaSE-1.8 JDK is required` | Workday Studio local runtime | Eclipse started on JDK 17, but no JDK 8 is bound to the `JavaSE-1.8` Execution Environment in workspace preferences | Install JDK 8 (ARM64 on Apple Silicon) and bind it under **Preferences > Java > Installed JREs > Execution Environments** |
| Workspace fails to open right after upgrading from an older Studio release | Eclipse workspace metadata | A workspace created under an older Java 8 Eclipse shell has not been upgraded, or you opened an upgraded Java 17 workspace in an older Studio build | Let the new Studio migrate a backup copy of the workspace forward, and keep workspace paths free of spaces |

## Why Does `Profile SDKProfile is not current` Happen During Studio Updates?

Workday Studio packages more than 150 Eclipse plugins plus the local Workday Cloud runtime on top of Eclipse’s p2 provisioning engine. Inside your Studio installation directory, `p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile/` stores sequential `.profile.gz` snapshots. Every time you run **Workday > Update Workday Studio** or add the Report Designer (BIRT) pack, p2 reads the latest timestamped snapshot in memory, downloads the delta bundles, and attempts to commit a new timestamped snapshot to disk.

Three things break that commit and trigger `Profile SDKProfile is not current`:

1.  **Windows `C:\Program Files` write virtualization:** If Studio was installed under `C:\Program Files\Workday Studio` without administrator rights during a later in-app update, Windows redirects partial writes into the user’s `VirtualStore` folder while leaving the base `SDKProfile.profile` directory stale.
2.  **Background or zombie Studio processes:** If a hung debug runtime or second Studio instance still holds a lock on the installation directory (or if Studio’s background runtime check under **Window > Preferences > Runtime > Automatic Updates** collides with a manual update), the on-disk profile timestamp advances behind the UI’s back.
3.  **Updating Eclipse directly instead of Studio:** Running Eclipse’s built-in **Help > Check for Updates** pulls upstream Eclipse SDK metadata that conflicts with Workday’s pinned plugin graph. Workday explicitly warns never to update the underlying Eclipse platform independently of the Studio update schedule.

### Step-by-step recovery for `SDKProfile is not current`

First, try a clean cache rebuild without touching your projects:

1.  Quit Workday Studio completely and verify no stray `eclipse` or `java` child process from Studio is still running in Activity Monitor (macOS) or Task Manager (Windows).
2.  Check `.lock` files: make sure your workspace folder is **outside** the Studio installation directory (for example, `$HOME/studio-workspace` on macOS or `C:\workday\studio-workspace` on Windows, with **no spaces** anywhere in the path so the Studio debugger works).
3.  Launch Studio once from a terminal with the `-clean` flag so Equinox rebuilds cached bundle wiring:

text

```
# macOS (launch the Eclipse binary inside the app bundle directly)
"/Applications/Workday Studio.app/Contents/MacOS/eclipse" -clean

# Windows (run Command Prompt as Administrator if installed under Program Files)
"C:\WorkdayStudio\eclipse.exe" -clean
```

1.  Once Studio opens, use **Workday > Update Workday Studio** from the top menu bar rather than Eclipse’s Help menu.

When an in-place Studio update still fails, stop patching it

Workday’s own Studio update guidance is explicit: if `Update Workday Studio` fails repeatedly, uninstall the current Studio installation completely and install the latest full release from Workday Community. Because your projects live in your separate workspace directory (and can also be exported via **Export > CLAR file**), replacing the Studio binary folder takes five minutes and leaves your assemblies untouched.

## How to Resolve macOS Gatekeeper and Unsigned Plugin Errors Safely

On macOS, developers run into two very different “unsigned” warnings when installing or updating Workday Studio.

### 1\. macOS Gatekeeper blocking the `.jar` installer or `Workday Studio.app`

Workday distributes macOS installers separately for **Apple Silicon** (`aarch64`) and **Intel** (`x86_64`), launched via an installation `.jar` file on JDK 17. When downloaded through a browser, macOS attaches the `com.apple.quarantine` extended attribute to the archive and anything extracted from it. Depending on your corporate MDM policy, macOS may block the installer `.jar` or report that `Workday Studio.app` cannot be verified or is damaged.

Verify you downloaded the matching architecture package from Workday’s official Studio download link first. Then either approve the launch in **System Settings > Privacy & Security > Open Anyway**, or inspect and clear the browser quarantine attribute in Terminal on that verified installation:

bash

```
# Check whether browser quarantine is attached to the Studio app bundle
xattr "/Applications/Workday Studio.app"

# Remove the com.apple.quarantine flag after verifying your official Workday download
xattr -dr com.apple.quarantine "/Applications/Workday Studio.app"
```

### 2\. Eclipse `Trust Authorities` / `Unsigned Content` prompt inside Studio

Modern Eclipse 4.x builds (running on Java 17) enforce stricter p2 signature verification than legacy Java 8 Studio builds did. When you run **Workday > Update Workday Studio** or install optional Studio packs, Eclipse may pause near the end of installation with a **Trust** dialog listing unsigned artifacts.

Do not click **Finish** blindly without selecting the rows—if you leave an unsigned Studio bundle unchecked in Eclipse’s trust table, p2 cancels the transaction and rolls back the update. Confirm that the update came strictly from Studio’s built-in Workday updater (never a third-party Eclipse marketplace URL), select the listed Workday/Report Designer artifacts in the trust prompt, and complete the restart.

## Fixing the Dual-JDK Trap (JDK 17 + JDK 8) That Looks Like a Broken Install

Even after `SDKProfile` and Gatekeeper errors are cleared, Studio startups and [AUnit tests](https://kiweely.com/guides/workday-studio-aunit-testing) routinely fail if only one Java version is installed. Current Workday Studio releases require **two exact JDK versions** side by side:

-   **JDK 17 (not Java 21 or Java 23):** Required to start the Eclipse IDE itself (`-vm` in `Workday Studio.ini` / `eclipse.ini`).
-   **JDK 8 (1.8):** Required by the local Workday Studio runtime to compile assemblies, run AUnit tests, and launch the [Studio assembly debugger](https://kiweely.com/guides/debug-workday-studio-integration).
-   **Architecture match on Macs:** On Apple Silicon Macs, **both** OpenJDK 17 and OpenJDK 8 (for example, Azul Zulu OpenJDK builds) must be native `aarch64` / ARM64 packages. Mixing an ARM64 Studio app with an `x86_64` JDK causes immediate JVM load errors on startup.

After every fresh Studio installation, confirm these three preferences before building an assembly:

1.  Open **Workday Studio > Preferences** (macOS) or **Window > Preferences** (Windows) and go to **Java > Installed JREs**. Add your JDK 8 `Home` directory as a *Standard VM* and check the box beside it.
2.  Expand **Java > Installed JREs > Execution Environments**, click **JavaSE-1.8**, and select the JDK 8 entry marked `(perfect match)`.
3.  Go to **Java > Compiler** and set **Compiler compliance level** to **1.8**, then click **Apply and Close**.

## How to Prove Your Studio Installation Is Healthy

Run three checks before starting integration work:

1.  Check the bottom status bar in Studio: the update arrow icon must be **green** (not red).
2.  Open **Cloud Explorer**, test a Sandbox tenant connection (using either saved credentials or an [OAuth 2.0 API client with PKCE](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password)), and confirm deployed collections list without an update-required block.
3.  Run a local build and one AUnit test case to confirm `JavaSE-1.8` starts cleanly without a `Debug Target` error.

If you drive Studio through [Kiweely Vine](https://kiweely.com/vine), Settings > This computer > Workday Studio checks your local Studio installation, verifies the workspace and Java 8 execution environment for AUnit, and launches Studio’s `eclipse` binary directly with the right workspace flags so startup dialogs never stall a build.

## Frequently asked questions

### Why does Workday Studio say Profile SDKProfile is not current during an update?

Workday Studio uses the Eclipse Equinox p2 provisioning engine, which tracks installed plugins inside a registry named SDKProfile. That error appears when two Studio processes touch the installation at once, a prior update aborted halfway, a generic Eclipse update site modified core bundles, or Windows User Account Control blocked writes under Program Files.

### Which exact Java versions does Workday Studio require on macOS and Windows?

Workday Studio requires two separate JDK installations at the same time: JDK 17 specifically to launch the Eclipse IDE shell, and JDK 8 specifically to compile assemblies and run the local Workday Studio runtime and AUnit tests. On Apple Silicon Macs, both JDK 17 and JDK 8 must be native ARM64 builds rather than x86\_64 builds.

### Will reinstalling Workday Studio delete my integration projects or CLAR files?

No, provided you kept your workspace outside the Workday Studio application folder as Workday recommends. Back up your workspace directory or export active collections as CLAR archives first, uninstall the broken Studio binary directory, install the latest Workday Studio package, and point File > Switch Workspace back to your workspace folder.

### Can I keep working in an older version of Workday Studio without updating?

You can edit local assembly files and run offline checks while the status bar shows a red update arrow, but Workday only supports one active Studio release at a time for tenant communication. Studio blocks connections, deployments, and launches against Sandbox and Production tenants until you install the current update.

## Sources checked

-   [Download and Install Workday Studio for macOS](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/download-and-install-workday-studio-for-macos.html)
-   [Update Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-management/studio-updates/wrm1499766213982.html)
-   [Setup Considerations: Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/setup-considerations--workday-studio.html)
-   [Getting Started with Workday Studio](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-studio/getting-started-with-workday-studio.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Authenticate Workday Studio and External Tools Using an OAuth API Client with PKCE (When SSO Blocks Passwords) When SSO leaves consultants without a Workday password, register an API Client with Authorization Code Grant and Support Proof Key for Code Exchange enabled, then use that client ID with Studio or Vine OAuth sign-in instead of username and password auth.](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password)
-   [### Inheriting a Workday Studio Integration You Didn’t Build Every team eventually inherits a Workday Studio integration built by someone who moved on. The assembly works — until it doesn’t. This guide walks through a structured approach to understanding an unfamiliar integration, identifying fragile points, and bringing it under control without regressions.](https://kiweely.com/guides/inheriting-workday-studio-integration)
-   [### Writing Your First AUnit Test for a Workday Studio Integration Most Workday Studio integrations ship without automated tests. AUnit, Studio’s built-in unit-testing framework, can change that. This guide walks through creating your first AUnit test: setting up test data, writing a test case, running it locally, and reading the results.](https://kiweely.com/guides/workday-studio-aunit-testing)
-   [### How to Debug a Failing Workday Studio Integration, Step by Step When a Workday Studio integration fails, the error message alone rarely tells you enough. This guide walks through a structured debugging process: reading Integration Events, isolating the failing step, using Studio’s breakpoint and message-inspection tools, and resolving common error patterns.](https://kiweely.com/guides/debug-workday-studio-integration)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Workday PECI vs. PICOF Payroll Connectors: How Effective-Dated Stack and Retro Changes Export](https://kiweely.com/guides/workday-peci-picof-payroll-connector-change-detection)
-   [Why does my Workday Accounting Journal EIB fail? Balancing, worktag and period errors](https://kiweely.com/guides/workday-financials-accounting-journal-eib-validation-errors)
-   [How to Find Every Domain and Web Service Permission an ISU Needs in Workday (Without Guesswork)](https://kiweely.com/guides/workday-isu-permissions-activate-pending-security-policy-changes)
-   [How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB](https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors)
-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)
-   [Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing](https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts)
-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)
-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)
-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
