Having updated to Windows 10 Fall Creators (1709), the problem is still the same.

I use Fences 3.03 as the click delay is just tolerable (2/3 seconds), when in double click mode. I suspect that 3.05 will be back to 5 seconds as before.

As I posted before, the instant fix is to change the click behaviour in File (Windows) Explorer and choose "Single-click to open an item (point to select)". The other options in that section are:

"Underline icon titles consistent with my browser"  or "Underline icon titles only when I point at them".

This then gives instant response to a single left click. The only problem I have found is when trying to select a file/folder for moving or copying, one has to be careful not to just open the item, as everything becomes single click. 

For example, the method of selecting by clicking on one item and then holding Shift whilst clicking on the last for your list, has to  be done by just moving the cursor focus to the first item and then pressing Shift before clicking the last list item. Selecting items is easier if you turn on "item check boxes" in the main View Ribbon of File (Windows) Explorer.

The fact that this works with Fences loaded and gives instant click response should point Stardock to where their problem arises.

It is also good for people used to Apple Mac as this is the default behaviour on a Mac.

For the record, I have over 180 icons on my desktop spread over 2 screens and I run my desktop in extend display mode.

The point is this: If Stardock is really willing to fix this issue, known since month, the usual way would be asking the Godfather MS & draw an incident & ask for support  ...

what is not free or charge or at least they have a MSDN contract (MS Developer Net Work) what would help a lot  

 Sad this issue still has not been resolved. Just running 3.03 at the moment.

Dear Stardock's Developers and Supporters,

->[ I still waiting for an answer to my ticket. Please DON'T closed it again until you provide me a solution. ]<-

From September 7, 2017 and waiting for 2 months to solve the problem we encounter with your app, you still have not managed to find a solution and serve your customers ... that is, all of us supporting you by buying your apps.

So after so long, instead of giving us a meaningful solution to the problem we are face it, you blaming the Microsoft that is for constantly changing and upgrading its operating system.

I really feel very disappointed with your non-existent support as you have not yet solved this problem and even in an application that you sell and do not distribute for free.

I think it's obvious that Microsoft Windows will be upgrading continuously (for security and functionality reasons) and that you should constantly take care of the full compatibility of your applications you are selling to your customers.

Sincerely

Sorry, i don't understand you.

1). I use Windows 10 Pro (x64) (Version: 1709 -- 16299.19 -- Full Updated) and the latest (version 3.05) of your programm (Fences) Which of these is the BETA edition?

2). 2 months without having done anything to solve the problem, it's a long time. I think that is it time to tell us a possible date for resolving the problem.

Thank you.

Only since the release of Windows 10 has there been this public beta process forced upon everyone, including those who never wanted it and/or are incapable of tolerating inherent failures within Microsoft's Beta process.

Prior to Windows 10 there were 'early releases actually CALLED 'Beta' or 'Alpha' or finally 'RTM', and those really wanting/willing to experiment would engage in Technet and similar programs.

IN SPITE of pre 10 Windows versions being ostensibly 'Fit for use' they still were capable of breaking things, so give them a chance with on-going Betas and they are GUARANTEED to 'break things'.

Now,

A program which is closely aligned with the Windows SHELL and is not a comparatively isolated process [ie. Photoshop et al]  is exposed to the most innocuous variations of the Windows GUI and can be adversely affected where your Text Editor won't even notice or care and continue unfazed.

This has always been an issue with Shell enhancements at one time or another, but thanks to Microsoft suckering people into a 'free upgrade' to Win 10 they now wreak havoc on Joe Public with little recourse..... just as long as those with Corporate licences can put off THEIR updating until after the havoc abates and the OS ver is 'stable'.

All is well when Stardock resolves any issues pertaining to THAT build until MS messes around yet again.

This is excusable because you just don't know what has indeed been done.  To be clear, I have worked my tail off to try to figure out what the cause of this is - funneled prime candidates to the developers, set up remote connections, poured over countless support tool logs, tried every setting change under the sun, no doubt with many of you on this thread.

Yes, there is a 'lag' issue for some using 3.05 (started with 3.04 actually) - clicking an icon is delayed, dragging is sluggish, and overall desktop performance seems to suffer.  However, the cases are very very few.  With this post, and our internal tickets, I may have 100 people (examples).  When compared to how many copies of Fences 3.05 are in circulation and working (millions), it's not even a contest - the cases with the issue are statistically insignificant.

That said, no one with it is being ignored - while the afflicted numbers are low, they are consistent in their account of the issue and enough in numbers to warrant attention. 

The problems we have faced with solving this:

• Very few have reported the issue (somewhere around 100).
• Anyone with any troubleshooting experience knows, the first step to fixing any issues is being able to see it - to be able to reproduce it reliably.  We have no one here that can.
• For the people that can reproduce it - we need their full attention.  Many of the candidates I have worked with failed to actively participate to the degree we needed (time and effort). 
• Corporate clients with the issue generally don't allow remote connections - further limiting the pool of candidates.
• They need to be in the Western Hemisphere (preferably North America) - working with overseas clients has both time and language barriers.  

That said I am open to working with anyone on resolving this.  What would be wonderful is if someone had a solution - not on a code level of course - but a 'if I don't have this installed', 'if I don't have this setting on', etc, 'It works'.  Something is unique to you all - I need to know what that something is.  I'll toss out free OD subscriptions like frisbees to any that can bring me such examples.

A Fences 'Clean boot' is where most would want to start:

https://forums.stardock.com/486084/Fences-Support-FAQ#cleanboot

Again, I want to make clear that any with the issue are not being ignored - this issue is just one of the tougher ones we have had to deal with for the aforementioned reasons.

~Sean

This.

After not having used Stardock products for a couple of years (I have used Object Desktop for a long time years ago) I recently bought Fences. I read up on Windows 10 compatibility before installing it, found (among others) this thread and after reading your last comments (assuming you are some kind of Stardock representative judging from the forum badge) I will most likely not install Fences after all.

While I agree that is it alot harder writing software that tightly integrates with the OS than standard desktop software I don't think the way you are trying to blame Microsoft for an (assumed) error connected to an (assumed) public beta conspiracy is the right way to handle this problem - especially since it is quite obvious that this problem does _not_ only occur on the so called Windows 10 beta versions.

'Beta' Windows (alone) is not at likely at play here - what is most likely is a 3rd party app or a setting that these clients have.  Were Window's preview changes the core issue, everyone would see it. 

I have Fences installed and it works fine - I could bring the weight of many (millions of) clients where that is the case as well.  What is needed is to find the app or setting that they have - why are they different than everyone else? 

What we need is someone willing to go bare bones, installing / enabling to find what is causing this.  It won't get fixed without that. We want this fixed as much (way more actually) as you do.  We need some help is all.

out-file : Cannot perform operation because the wildcard path C:\Users\[YOUR did not resolve to a file.

At line:1 char:1

+ Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\Current ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : OpenError: (C:\Users\[YOUR:String) [Out-File], FileNotFoundException

    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

As curiosity value only [and for the exact same outcome] whilst on Windows 7 Ult 64 with a $10,000+ computer I find currently that sooner or later Skype will bring my machine to its knees.

By 'to its knees' I mean a lag that can be measured in minutes.  The cure is to ctrl/shift/esc and kill the process in Task Manager....[usually done in a few minutes or so] and then it's all honky-dory until you reload Skype again and wait a few days...

Wow, this thread started last April!?  Not promising...

Well, I've had this problem for a long time, and finally am trying to resolve it.  I just found this thread after posting a support ticket and getting no response, and then starting my own thread..  Now I'm glad I found this thread that says something about it.

I have tried the disable Intel r-click graphics menu fix since I have an on-board graphics on my mobo that I am using.  And I also have a nVidia 1080ti as well..  But that did not fix anything.

Has there been any resolution on this?  I am running v3.0.5.12 from Steam.  Should I revert back to some previous version somehow?