Boot speed - slow at home, fast at office? plus very laggy

giantbucket

Honorable
Nov 17, 2013
192
0
10,710
so i have this here laptop (Dell E6420 with a 240G SSD), and lately over the past few weeks i've noticed that when i boot it up at home, it's EASILY 80sec before i get a usable desktop and even then most operations are very laggy. when i get to the office and boot up, it's almost always up and running with no lag within 35sec.

in both cases, i use an AC adapter (different ones, though). at home, i use WiFi, and at the office i plug in a network cable so that i get better access to our file server.

does anyone have any ideas why it would ALWAYS be so slow at home, and always so much better at work? time of day (at home) doesn't seem to make any difference, and swapping AC adapters had no effect, and plugging in a network cable (or even turning off WiFi) at home had nearly no effect.

i'm using BootRacer to get my times, and it's atrocious. is there some program i can use to do a deeper dive into the booting process?
 
if it an office laptop it may be set to log onto the server with a fixed ip info. if it is it going to cause your wifi to be laggy as the laptop is goping to try and connect with the company server. use msconfig and 3 party tools to see what in start up tab. see if you can see any 3 party tools that log the laptop onto the company server. see if you turn it off if the laptop boots and run better.
 

giantbucket

Honorable
Nov 17, 2013
192
0
10,710
i'm using Win7 and the office (inside) is DHCP with the exception of a few things like the server, printer, and alarm. if i look at Start-Programs-Startup, the folder is empty cuz i already removed OneNote (i think). using MSConfig, i previously unselected a few things like Dropbox, so the only thing i have there on the startup tab is Intel Common User Interface (3 of these), IDT PC Audio, nwiz (???), Alps pointing device (trackpad), and Microsoft Security Client (MS Security Essentials)

as far as i can see or guess, the only thing that's different at home is that when it tries to map the server's d drive, it can't because it doesn't exist. but that shouldn't add 40sec of time to the whole start-up process. should it? i could delete the mapping and see if that reliably & consistently improves things...