If you are running flowerSoft in more than one computer and you have to buy a new computer, do not get a computer running Wndows 10 for the time being!

There is a big problem with computers running Windows 10 that slows down flowerSoft to a crawl when more than one computer is accessing it.

If you have a server and Windows 10 computers accessing it, you are probably experiencing this problem.

Here is what I’ve found out from programmers of other systems experiencing the same problem in their applications…

Has anyone run across settings for Window10 clients that must be set or
changed to improve I/O speed when writing to a WinServer Drive?

We have a network which has and is working wonderful with Win7 clients
and they are trying to change to Win10 clients and the difference in
speed makes the Win10 clients non-functional for our software
I remember caching was an issue in earlier versions but I have no idea
what other data to provide or what to ask the hardware guy to help them
get the bottom of this.
All the computers are virtual, to the best of my knowledge.
It is certainly an I/O issue between win10 and the server but I need
some suggestions.

Hi George –
 The reason for the hardware slowdown is because of a serious hacker exploit that was discovered on Intel and AMD chipsets.  It is called Spectre and it has to do with the way the chips are able to do speculative execution of instructions by preloading a series of instructions in the instruction cache before it goes through the translation process.  It was discovered by hackers that you could dump the contents of the cache and use that to access privileged memory.  The solution by the chip makers is to disable the speculative execution functionality, which can be up to a 30% performance hit, depending on the type of application.  I don’t know how FlowerSoft fits into that realm, but it sounds like it is being affected.  The chip makers have tried different patches but most of them lead to BSOD situations, not good.
So, we’re stuck with what we got for now.  I tried the remote desktop access option a while back and saw that it was pretty fast .

So far the only solution to this problem that seems to work, is to run remote desktop connections from the Windows 10 computer to the server computer.  This makes the workstation run the programs as if it was running from the server itself.

More info on this problem when and if they become available.
For now, do not buy or upgrade any of your computer to Windows 10.
You can still get computers running Windows 7, which Microsoft will support until January 14th, 2020.

Here is what experts at ZNet have to say about the latest Windows 10 update:
Worst Windows Version 10 Ever!

Here is what the Microsoft Community has to say about it:
Is Windows 10 the Worst Operating System Ever?

Here are some links to outfits still selling Windows 7 computers:


NixSys Computers





1 thought on “Warning!

  1. Thank you, Jeff Bandle, for tracking down why flowerSoft under Windows 10 was slowing down to a crawl by the product entry area if more than one computer was accessing flowerSoft at the same time. A simple solution to the problem was found and now flowerSoft works just as fast as it does under Windows 7.
    If you are still having problems under Windows10, let me know and I will make sure that the fix was added to your system.

    Liked by 1 person

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s