What this means
Windows prevents a normally running application from reliably controlling an application that is running as administrator. Offisen therefore stops recording instead of creating a sequence that could not be played back safely.
What to do
- Close the target application.
- Start the target application normally, without choosing “Run as administrator”, and try recording again.
- If the target must run as administrator, close Offisen and start Offisen as administrator too.
- Retry the recording after both applications are running at compatible permission levels.
Why this can happen
- The target application was started with “Run as administrator”.
- A launcher, installer, management tool, or company policy elevated the target automatically.
- The target changed to a higher-permission window during recording.
Example
If an accounting application is running as administrator while Offisen is running normally, Windows can block Offisen from interacting with it. Restart the accounting application normally, or run Offisen at the same elevated level when elevation is genuinely required.
Diagnostic details
| Code | OFS-1001 |
|---|---|
| Symbol | TargetIntegrityHigher |
| Domain | Permissions and security |
| Layer | Security and session |
| Phase | Recording |
| Severity | Blocking error |
| Retryable | Yes, after permission levels are aligned |
| Privacy | Safe support context |
| Safety policy | Block or stop recording |
If the problem continues
If both applications appear to use the same permission level and OFS-1001 continues, copy the support report and contact support. Include whether either application was started as administrator.
Include the error code, correlation ID, timestamp, Offisen version, target application when relevant, and a short description of what happened. Review the report before sharing it and remove anything you do not want to send.
Contact [email protected].