DHCP Client / BSODs

[gilius]

Without this component enabled I get BSODs such as inaccessible boot device without ever getting to OOBE; does that sound right? Is DHCP Client something that always has to be present?
EDIT: booting up now without DHCP Client

 

[gilius]

Same question for this component:

Network > WLAN > Virtual WiFi

Windows doesn't seem to boot up without it?
EDIT: booting up now without Virtual WiFi.

 

[Kasual]

BSOD isn't related to these components removal.

BSOD error codes?

 

[gilius]

Sometimes the WIM files become corrupt - possibly after injecting a series of drivers after using NTLite.

How about these components? Would you expect to get to OOBE without any of them?
System > Boot Manager (EFI)
System > Device Experience
System > Windows Management Instrumentation (Service) > Windows Management Instrumentation (Core)

And as for OOBE would you expect to be able to get to the desktop without any of these?
Windows Apps > Appx Deployment Service
Windows Apps > Appx Deployment Service > App Readiness
Windows Apps > Capability Access
Windows Apps > System Apps > Out-of-box Experience (OOBE)
Remoting and Privacy > Autopilot
System > Encryption File System (EFS) – Service
System > Windows Setup and Deployment
System > OLE for Process Control (OPC) library
System > Windows Update Service > Client License Service (ClipSVC)
Remoting and Privacy > KMS Connection Broker
Remoting and Privacy > Web Account Manager
Network > Windows Firewall Service

 

[nuhi]

Hi gilius,

to have OOBE protected, use the Components - toolbar - Compatibility, enable OOBE.
Then you can analyze yourself what I think is needed for OOBE.

As for BSOD, if you have a preset demonstrating that and not disabling any services or removing drivers that your/vm machine may need, send me the preset for review.

Thanks.