Hello,
I'm trying to deploy Windows 11 on a detachable Dell Latitude 7350 with a Thunderbolt dock.
I downloaded the Windows 10 drivers for the dock and integrated them into WinPE, but at the end of the boot process, I get:
VerifCert: 0
No Valid IP
. The LAN is not detected.
However, at that point, if I manually load the driver
(drvload rtu53cx22x64sta.INF
wpeutil InitializeNetwork
ipconfig /all)
, it works; the network card loads and I can launch the WADS interface.
The question is: why doesn't it work automatically?
WADS: Dell Thunderbolt driver issue
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
It looks like a signature or auto-matching issue in WinPE.
The driver is fine since it works manually, but WinPE doesn't load it automatically at boot, often because it's not properly signed for Windows 11 or isn't recognized as a boot-critical driver.
Also check that the INF file is in the correct folder (network drivers) and injected with the exact index of the WinPE image being used.
Unfortunately, this is quite common on Dell Thunderbolt docks, especially with Windows 10 drivers modified for Windows 11.
The driver is fine since it works manually, but WinPE doesn't load it automatically at boot, often because it's not properly signed for Windows 11 or isn't recognized as a boot-critical driver.
Also check that the INF file is in the correct folder (network drivers) and injected with the exact index of the WinPE image being used.
Unfortunately, this is quite common on Dell Thunderbolt docks, especially with Windows 10 drivers modified for Windows 11.
Relevant questions.
I successfully downloaded the Windows 10 driver (since WinPE is based on Windows 10).
When creating the WADS WinPE image, I see in the DOS window that the driver integration is 'successful'.
That's why I don't understand what's happening.
I successfully downloaded the Windows 10 driver (since WinPE is based on Windows 10).
When creating the WADS WinPE image, I see in the DOS window that the driver integration is 'successful'.
That's why I don't understand what's happening.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
