So I uninstalled cursorfx and reinstalled and tried leawh again and same result.  So I uninstalled and reinstalled again and deleted leawh from the folder and used another theme (position) from the program and it works fine.  Evidently leawh is flawed.

You are right. That theme crashes CursorFX. Go to this folder C:\Users\YOURUSERNAME\AppData\Local\Stardock\CursorFX and delete the file CurrentTheme.CursorFX. That should make you able to choose another theme.

You should also go here: C:\Users\Public\Documents\Stardock\CursorFX\Themes and delete the Leawh theme to prevent you from applying it again.

Edit: See you got it fixed already. Great.

Hi Janoscar,

Thanks but I don't have the folder you described for that current theme fix.  Not sure why but I don't have it on Win10

Hi again Janoscar,

I do have a folder labeled as "owner" without my name and it has all the subfolders you mentioned.  Is there any way to change it to my name?

But when I log into windows it is my name.  What gives?

Hello,
Sorry to hear you are having issues. Need to know.

1. Windows 11 full version number. Use Winver.exe to get that.
2. CursorFX full version number you trying to use.

Thanks
Basj,
Stardock Community Assistant.

Another cursor that crashes the program is penthouse.  Too bad because that is a nice cursor.

Picking back up on this as the issue has relied dormant for some time, Lightstar recently modernized the Penthouse WindowBlinds theme, so when I purchased it, then went to apply the Cursor for it, I had the same crash as others have described.  I also tried Leawh and had the same issue occur.

Allow me to get the preliminaries out of the way.  I am using Windows 11 Pro 22H2  OS Build 22621.1848.

I was having some degree of difficulty following along what the solution was in order to get these (and other CursorFX) to display properly.  I can see how to remove cursors that are broken, but I couldn't see a way to get them to display properly.

Was there something specific you had in mind for us to try to get these cursors to work?  Was there something we could disable, or something we could do?   These are some great cursors and it's my hope that we can somehow find a way to salvage them.  I especially feel this way as older WindowBlinds are being brought up to code to play nicely with the more modern versions of Windows.  The more people download the new versions of the WindowBlinds, the more they are going to try to download and install the CursorFX that are causing an unceremonious crash of the program.

In the even there is no plan from Stardock to create a solution that works out of the box, is there anything I can do to get these cursors to work; and if so what?

If there is some degree of mystery of what needs to be disabled by an end user in order to get these to work and you need someone to try things that you need to have tried in order to find a solution, I happily volunteer to try whatever you'd like to have tried out.  I'm no expert, but I'm willing to try to toggle different settings in order to hopefully come to a solution.

Thank you in advance.

The Problem is only occurring with certain cursor themes.  I don't know how many of the cursor themes that have the particular issue that myself and others have experienced, I know for a fact that Penthouse and Leawh themes are affected.   

In the case of the Leawh theme, I believe I had read by the author of it, or perhaps someone who had also made cursor themes around the time it originally came out (April 2012) said that themes made for the version of CursorFX didn't play well with the modern version of CursorFX.

I don't know if that they meant all cursor themes made at that time don't work anymore, or if they meant certain cursors that had some sort of property affixed within the theme were only affected.

I personally use many cursors going all the way back to the early 2000's, and all but at least the two I've mentioned work just fine.  So I can't believe that all cursors made in a certain era simply don't work at all.  If that were the case, many other cursors I use from that era would also no longer work.

So it's my non-expert opinion that some property somewhere on at least two cursors (maybe more) don't play well for whatever reason with the modern version of CursorFX.

Thank you.