This article discusses a workaround for an issue that affects network kernel (KDNET) debugging on target servers that have AMD processors and Cisco virtual interface card (VIC) adapters.
Applies to: Windows Server 2019, version 2004 and earlier versions, Windows Server 2016
Symptoms
You try to use KDNET network kernel debugging, and your target server meets all the following criteria:
- The operating system is Windows Server 2019, version 2004 or an earlier version, or Windows Server 2016.
- The server has an AMD processor installed.
- The server has a Cisco virtual interface card (VIC) adapter installed.
You set up the target and host servers, and turn on KDNET debugging (by using bcdedit /debug on). However, when you restart the target server, the startup process stops at the Windows logo screen.
Cause
This is a known issue for the specific configurations that are described in the "Symptoms" section. The issue has been fixed in Windows Server versions that are later than Windows Server 2019, version 2004.
Workaround
To work around this issue, open an administrative Command Prompt window on the target server, and then run the following commands:
bcdedit.exe /set {bootmgr} bootdebug true
bcdedit.exe /set {default} bootdebug true
After you run these commands, restart the target server as you typically do for KDNET debugging.
References
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
