Topic was locked for absolutely NO REASON and I want it unlocked NOW

"Again, I am not just going to "suck it up and accept it" due to lazy programing and some strangers loose interpretation of empirical evidence. I want to see the research that was done to prove that there is  NOTHING Stardock can do to mitigate this issue because it's a Microsoft problem and their hands are tied. That is what is being alleged here and I just want to see the non-anecdotal evidence that backs up that allegation so I know which company I need to proceed against going forward."

You need to 'proceed against' Microsoft, as it is their methodology [since after Win 7] to alter the boot sequence to give the impression the Desktop has loaded completely when in fact it has not finished background services loading, and they then require third party programs to load AFTER the sequence has completed.  That is why there APPEARS to be a delay with Fences.

There isn't.

What you see [with Fences] is the ACTUAL boot time.

By all means proceed against Microsoft as it would be great if they liberated 3rd party loading/booting order.

Reason for the locking of the thread?

Attitudes expressed, nothing more.

Continuance of attitude can see other threads locked too.

Again, where is the proof to backup your claims. Anyone can make any claim they want , but until they can prove it than its just hearsay.  What are you  afraid of by exposing your proof, which I  am certain you have  because of the  countless hours of research your world-class developers have painstakingly put into this very topic. 

Is there something wrong with requiring accountability from those whose whom you literally pay their  salary. Like it or not, your customers are your boss and I am not sure sure about you,  but when my boss ask me a question I  do not respond with  a patronizing  comment which is exactly  what  was done in the topic of discussion. Furthermore,  I  do not shut them down when they criticize my work because  that  just  enforces their point  further. You should know better. 

You know what they say  about assumptions....... The reason i called the devs lazy is because I  was a developer myself for over 11years with embarcadero  systems and I  can tell you first  hand that if i put forth a claim to a customer  about a product / service without  proof of said claim, I would be made redundant  with extreme prejudice. That being said,  I  think I "might" just  understand  what you  were sayIng if you spoke REALLY REALLY slowly and backed up what you were saying  with a little  thing called...EVIDENCE. Thank you for playing , you are dismissed now.

You said it best 

mtcellph, it's always curious how people who 'was a developer myself' presumes superior knowledge over 'lazy devs'.

Firstly, please do not denigrate Stardock's 'devs'.  It's uncalled-for.

If you really need to contest the issue, why not Google boot sequences for services in Windows 10 and the 'appearance' of faster load times.

It's not about anyone lying to you...it's about Microsoft wanting to give the impression that their newer OS versions are superior to their older ones.  Call that 'deception' if you must, but it's Microsoft's, not Stardock's.

If Microsoft allowed shell modifiers to be integrated into the boot sequence sooner, ie, when the desktop icons load then there'd be zero indication of an apparent longer boot...other than the milliseconds required to include Fences in the sequence.

Other than that, remember my prior reference to 'attitude' and the possible thread-locking that ensues.

You can lock all the threads you want it will not change the facts. Additionally, I do not appreciate you  insinuating that I am a liar. Unlike your company I can PROVE the claims I make. Further, why should I have to do ANYTHING to prove you wrong when YOU are doing NOTHING to prove you are right. I am not here to do your job for you, it's quite the opposite or do you not understand how commerce works.

Lastly, are you also going to blame Microsoft for the other (non-performance) issue I have with this application. Notice the lack of a question mark because it's a rhetorical question because I know you will.

You too are dismissed.

https://social.technet.microsoft.com/Forums/en-US/445ddb5e-16b4-4dca-ab89-c0d0ec728af5/boot-order-of-windows-services?forum=winservergen 

Start there... and follow all ensuing links.

A developer such as yourself is bound to be au fait with all that's discussed...;)

Maybe this can be consider as proof

Thank you,

Basj,

Stardock Community Assistant

You should know by now that you don't catch flies with vinegar.

As others have already told you multiple times, you can get all the proof you need all by yourself: just add any small application to your Startup group and see how long it takes for it to start AFTER a reboot and the desktop popping up.

Here is what is happening: in Windows 10 Microsoft is deliberately DELAYING the startup of 3rd party applications by several seconds. Whether it is to make Windows itself appear to boot faster at the expense of 3rd party applications or some other reason, that is something you will have to ask them.

Want to be mad at somebody? Be mad at Microsoft. They at least deserve it.

Sometimes people feel the need to rant when something isn't working properly/going their way.  Often times the wrong people are blamed, but that is irrelevant, so long as the rant gets out there and somebody cops the brunt.

In this case it's Stardock copping it when Microsoft is to blame.  That should be common knowledge among most hard-core users, and especially developers, but like I said, some people feel the need to rant, irrespective of whether they have the right target or not.

So mtcellph, hopefully you will realise that this is what you have done here and apologise for the poor attitude.

Not to mention unsubstantiated allegations of wrong doing on the part of Stardock. I have great respect for Stardock and all its employees. You claim to be a developer but your posts suggest otherwise. You should be ashamed of yourself.

My two cents.

Quoting basj, reply 12

Maybe this can be consider as proof

Reduced 90%

Original 1281 x 948

Thank you,

 

Basj,

Stardock Community Assistant

I guess that reads as 140 milliseconds .... the time it takes to load the Fences 'services'.

Dang that's a long time to add to a boot sequence....;)

Anyway, this is now a non-issue [other than yet another thread-closure] as the topic is moot....;)