Here we go again: a redo of Timeslips 2009; Timeslips 2017, more mediocrity from mediocre programmers and software engineers

Harkening back to the terrible, absolutely pitiful Timeslips 2009 product, Sage Timeslips and its programmers and software engineers have demonstrated yet once again that they are the most mediocre of the worst mediocrity. Here's my story: in the process of installing a completely new clean boot of Windows 10 Pro, I decided to upgrade my Quickbooks Pro 2013 to QuickBooks Pro 2016. Prior to making the upgrade I had successfully been using Timeslips 2015 with QuickBooks Pro 2013. No problems whatsoever. After installing QuickBooks Pro 2016, however, my Timeslips 2015 crashed every time I tried to open it when QuickBooks Pro 2016 was open. Being the somewhat gullible consumer that I am, I then decided that for $503 I would upgrade to Timeslips 2017. New product certainly ready to work with Windows 10 Pro, which after all, has now been around for quite a good while, right?  After installing Timeslips 2017, I then experienced exactly the same disastrous crashes every time I opened Timeslips 2017 when QuickBooks Pro 2016 was open. Now you have to believe me when I say I had all the switches and bells and whistles properly hooked up such that Timeslips 2017 and QuickBooks Pro 2016 should have easily connected. But Noooooo. Consequently, I contacted Sage Timeslips support and got an instant remedial solution.  The techie simply went into my registry and we went from Hkey local machine/software/Microsoft/Windows/current version/policies/system, then over on the right side, right clicked on EnableLUA, selected modify and changed the value from 1 to 0. Timeslips 2017 then had no problem connecting and linking with QuickBooks Pro 2016. Should have been the end of the story but nooooo. As is often the case I just happened to stumble on another Windows related problem which I would have never thought had anything to do with the fix solution that the Timeslips Techie provided for making Timeslips 2017 work with QuickBooks Pro 2016. What happened was I tried to open a JPG file and instead I got this error message “This app can't open - - photos can't be opened using the built-in administrator account.” After Googling the error message I found a solution. Although there are some other steps involved, the primary steps to fixing the error message that this app can't open require one to go to Hkey Llocal Machine/software/Microsoft/Windows/current version/policies/system, then right click on EnableLUA on the right side and change the value from 0 to 1.  What is now completely obvious to me is that Sage Timeslips and its programmers and software engineers have no idea whatsoever about how their product completely messes with Windows 10 Pro because in the process of solving the issue that Timeslips 2017 has with QuickBooks Pro 2016 the remedy screws up your usage of Windows 10 Pro where you need to have the EnableLUA value set to 1 in order to make Windows 10 Pro usable with numerous and various apps. Or put it another way: the Sage Timeslips programmers and engineers make it possible and only possible for you to use Timeslips 2017 with Quickbooks Pro 2016 if you are willing to continuously and consistently compromise the functionality of Windows 10 Pro. Idiots, total numbskull idiots. See what I mean, like they did with Timeslips 2009, a completely worthless product, they have sold us a Timeslips 2017 product that that is absolute mediocrity in all the most mediocre sense. It won’t do what it is supposed to do without one having to completely mess up the operating system in which the software is supposed to function without difficulties or conflicts. What is world is wrong with these people??!!