> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/get-started/faq/registry-access-demo.md).

# Registry access in the demo version

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

While you try out Apryse SDK without a license key, it is running in demo mode. One side effect of this is that your application will need read/write access to the registry enabled. The licensed version does not have this requirement.

This is a problem in running the demo version in an environment with restricted permissions such as when developing a Windows service or a server application.

{% hint style="warning" %}
**No restrictions in the licensed version**

* The demo version is not intended for use on production environments.
* The licensed product does not require registry access to work.
  {% endhint %}

The demo version has been used on servers with tight security by modifying a config xml file that controls security settings or using a `Code Access Security Policy` tool. For more info please see:

* <http://msdn.microsoft.com/en-us/library/ff648243.aspx>
* <http://msdn.microsoft.com/en-us/library/cb6t8dtz(VS.80).aspx>
* <http://msdn.microsoft.com/en-us/library/a0ke3k86.aspx>

## Error: The evaluation version encountered an error in your system configuration. Please contact customer support at: <support@apryse.com>. No reg. write rights

When running in a server context, you may encounter the following error if registry access is not available to the application. Please [contact support](https://apryse.com/support) for more guidance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/core/get-started/faq/registry-access-demo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.