Windows 7 boots too fast on SSD (Profile login occurs before network initialization)[Non-Domain, Home PC]

Question

Windows

Good afternoon! At home, I ran into such a problem: Windows 7, freshly installed on an SSD, loads so quickly that the profile with applications from “startup” is loaded even before the network is turned on (hence a bunch of “Could not connect” style errors at startup). Can you tell me how this problem can be solved by regular-non-standard means?

Ideally, of course, I would like to add a network availability condition before autoloading.
But in extreme cases, the classic is also suitable.

ping -n 20 127.0.0.1 > nul

I remind you that Windows is not in a domain, therefore the GPO parameters
* Always wait for the network at computer startup and logon
* Startup policy processing wait time
Do not plow.
The loading priority of the dhcp service and the e1express driver also does not help

UPD: I myself decided to an acceptable level for myself Link , I will not pick further

Answer 1

Get your hands on a utility with which you can change the load order of Windows 7 drivers.(How To Control Device Driver Load Order)

Answer 2

>I remind you that Windows is not in the domain, so the GPO parameters do not plow
Why do not they plow? But what about local group policies?

Answer 3

Set the network parameters with your hands, and not through DHCP, perhaps the interface simply does not have time to configure ...

Answer 4

It's strange, I have an SSD, it was win7, now w2008r2, (both with all updates, not a domain) in Skype, ICQ, gtalk and a bunch of other network-dependent trash, there are no such problems, although I have a password everywhere. Usually when I enter password and log in, everything is already running and online. Which of the p / o do you swear?
GPO… Actually, on local machines without a domain, local security policies work fine starting with w2k, yes, with a domain, GPO is added.

Answer 5

You can try utilities that autoload later. Or write one.

Answer 6

Start - run - gpedit.msc and your
* Always wait for the network at computer startup and logon
* Startup policy processing wait time
Do not plow.

Answer 7

yoyokarny babay! Now I understand why Steam and a couple of other progs often lose the network on the home computer immediately when turned on (for Steam, this ends with a noticeable dialog box stating that it has not connected and refuses to start).

Answer 8

Almost the same problem. Toko in the domain.
2 computers (out of 33) are connected via Wi-Fi.
Group policy is not being processed.
What do you advise?