# Cursor size issue when using ThinLinc. How to fix?

**URL:** <https://community.thinlinc.com/t/cursor-size-issue-when-using-thinlinc-how-to-fix/703>\
**Category:** Community Support\
**Tags:** thinlinc\
**Created:** [1 September 2023 10:26 UTC](https://community.thinlinc.com/t/cursor-size-issue-when-using-thinlinc-how-to-fix/703 "2023-09-01T10:26:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeanz](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/jeanz/32/25_2.png) [@jeanz](https://community.thinlinc.com/u/jeanz)\
**Post date:** [1 September 2023 10:26 UTC](https://community.thinlinc.com/t/cursor-size-issue-when-using-thinlinc-how-to-fix/703/1 "2023-09-01T10:26:29Z")

</div>

A visitor at ThinLinc’s website left the following message today.

Any advice is welcome. How can the user solve the issue?

====================================  
What is your main reason for visiting us today?

1. Problem with cursor size when using ThinLinc

Are you able to find the information you are looking for?

1. No (please tell us what’s missing) **“** a guide to resize the cursor

====================================

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/martin/32/41_2.png) [@martin](https://community.thinlinc.com/u/martin)\
**Post date:** [5 September 2023 07:20 UTC](https://community.thinlinc.com/t/cursor-size-issue-when-using-thinlinc-how-to-fix/703/2 "2023-09-05T07:20:32Z")

</div>

Sorry to say, but this is nothing I’ve heard of before.  
Is this in the native client or Webaccess?

Regards,  
Martin

---

<div class="post-metadata">

**Author:** ![jeanz](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/jeanz/32/25_2.png) [@jeanz](https://community.thinlinc.com/u/jeanz)\
**Post date:** [5 September 2023 08:53 UTC](https://community.thinlinc.com/t/cursor-size-issue-when-using-thinlinc-how-to-fix/703/3 "2023-09-05T08:53:31Z")

</div>

Thanks, @martin, for your answer. Unfortunately, the visitor did not leave any extra information.
