Hello,

I'm on Windows 8.1 x64 (fresh install) and since I installed DF, the startup (after logon) is very long. Looking at the startup manager, DF is on the High impact list. Disabling DF restore myself to a normal speed.

My computer is made to run fast, it's on an intel SSD, 4.2 ghz i7, 6gig of ram... Normally, I login and bam, ready to go. Now, I go to the desktop, I see the second taskbar haven't loaded and if I request an app (let's say firefox), it lag behind for the time DF start.

It make a huge difference

edit: oh wait the service, I was in the startup list, let me try again

It's better, but still slower then without DF in startup

The only thing I', using is taskbar, wallpaper and key combination. Everything else is not used (no icon, window management, nothing). My guess is the taskbar, I'll check

Uh, old thread, but the problem ist still existing on an Win10 x64 with nvidia-graphics (if that matters at all..)

Booting and logging in are dramatically reduced by 55 seconds after setting the displayfusionservice to "delayed start". It took me quite some time to find the culprit.

So I figure that on an NVME-ssd as systemdrive it maybe necessary to delay the start a bit..

Greetings,

Don

Hey Keith,

well it seems it delays the pre-login phase (circle dots on screen) AND the login itself (after sending the password). I could prove this on two separate Win10-installs on my machine.

Putting the service to delayed start solves this instantly.

I could send you a boot-trace if interested.

Greetings,
Don

Hey,

I've just made the traces ready for you. Analyzing them, yes, the service starts at about 11 sec trace time. (in Normal)
Password entry durance is about 4 seconds each and after logging in, I've waited until every autostart process finished successfully then stopped logging.

The only system difference of the two is the setting of the DF-service.

I've protected the attachments, please use with discretion.

Really this is not a real problem for me, because I know how to circumvent it. And if there is no reason for the service running that early, why not make the delayed start a standard?

I am experiencing the same... A delayed startup and I have nvidia graphics and Win 10... I also have a couple other problems too... Not sure if they are due to Display Fusion or not, I will try the disabling of the service... But one is on and off when using the DF screen saver, when stopping the screen saver with my mouse, it goes to a solid color and just hangs there as if it is frozen. I press Ctrl + Alt + Del and then Cancel and I can go back to my desktop.
Another thing, I've been bugging nvidia about and all they say is "update your drivers", "preform a clean install of drivers" and many other useless things... though I'm going to try maybe disabling Display Fusion for a couple of days and see if the issue persists... The issue is, when waking from a long like "all night" sleep of my computer, it won't play sound through HDMI... I can see the sound level move up and down, but no sound... I switch out hdmi ports so that I can make it another day without having to do a complete restart of my computer...
I will post back here with my results... Will be hard though to not have DF for a few days, I use it so much and enjoy it so much! Anyway, just thought I'd add to this a little...

So I've done some testing... Remembered shortly after this post one way to increase my startup speed is to go into msconfig and under Boot and then Advanced Options there is a setting to use all cores on startup... That helped a bit with the slow startup... However, after disabling DF from starting, I've found that my computer when waking from sleep, no longer loses sound. I tried running DF again hoping I wasn't right, but a few days of running it, I was getting the loss of sound after waking. Disabled it again and the issue went away...
I'm pretty certain it has to do with the new nvidia video cards, I used to have an AMD video card and never experienced this issue, until about when I put in the nvidia card...
I have an nvidia gtx 1060 6gb card... Hope this helps find the issue...

No, I don't have any monitor profiles... Should I?

No, I have to do a complete restart. I've switched the HDMI ports around and then can get sound until the next day... but it completely seems to cut out the sound, other than I can see the volume level go up in the sound settings, but no sound... Is really strange and then without DF running, I don't have that problem...

That's a myth. The option is only there for Windows debugging purposes.

Okay, so I see the msconfig is a myth... Actually timed it and seems to boot faster without the processors selected... Though what a frustrating day... I unselected the processors but left the max memory, which for some reason switches to 0... well my pc wouldn't boot... so after doing a system image restore and such... finally tested this all out... I'm not messing with msconfig settings again... what a headache...
Then with timing it, am surprised at how fast it actually does boot... about a minute and 20 seconds... just seems to hang a little right after landing on the desktop, but could be because I have things installed on both C and D... one is SSD and the other isn't... though hopefully over the weekend I'll get a new 1TB SSD with everything installed on it... Should speed it up some more...

As for the sound issue, that wouldn't help... but I think and should know probably by tomorrow if I've fixed the issue... I bought an optical cable because I had the issue happen again without DF running... So I was like heck with it, buy an optical cable and use my sound card... well, my home theatre won't put the sound through the optical cable, because I have 2 HDMI cables plugged into the back of my TV and it switches to ARC and plays the sound through the home theatre, even though the cable is plugged in the OUT... Now that I found fascinating and probably would have done it sooner if I had known it would do that... Anyway, so I will post back tomorrow or the next day to see if the sound happens again with DF...
I know not running DF did help, I did see an improvement...

Hopefully this isn't all too confusing...

So seems like with the change of putting the audio into the tv and letting it pass through to the home theatre has fixed the problem... I still think it's strange, but must actually be something with nvidia's card or something like that... I'm not too sure, just happy that it's working proper now...

Also now that I've installed the new hard drive and installing everything on my C, Windows is starting much faster... about 40 - 45 seconds and all loaded into Windows, though I haven't setup Skype and SkypefBus yet... Hopefully they won't slow me down, though now I'll know what might slow the startup...

Also I've now loaded my desktop background images onto the C (SSD) I'm hoping I won't get the freeze when stopping the screen saver issue, but will report on that later on if I experience any issues... If not, well then guess all was a false alarm... sorry about that...