Did you ever see bootext.dll?

WINDBG
1

Hi All,

Refer the output from WinDBG, it complained that failed to load an
extension DLL called bootext. I think such dll is defined in workspace
for NTLDR debugging so WinDBG is trying to load it at the beginning of
the debug session.
With a search in several versions of WinDBG and Internet, I didn’t find
such bootext.dll. So it is possible an internal DLL. If so, why public
version of WinDBG still loads it (a bug???)?

Anyone has information about this extension DLL?
______________________Output of WinDBG

BD: Boot Debugger Initialized
BD: osloader.exe base address 00400000
Connected to Windows Boot Debugger 2600 x86 compatible target, ptr64
FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Module List address is NULL - debugger not initialized properly.
WARNING: .reload failed, module list may be incomplete
KdDebuggerData.KernBase < SystemRangeStart
Windows Boot Debugger Kernel Version 2600 UP Checked x86 compatible
Primary image base = 0x00000000 Loaded module list = 0x00000000
System Uptime: not available
The call to LoadLibrary(bootext) failed, Win32 error 0n2
“The system cannot find the file specified.”
Please check your debugger configuration and/or network access.

BR, Raymond

2

I don’t know the answer to this, but I have never heard of it either.
WinDbg is all around a peculiar beast that is distributed not for
profit, so I personally would not stress too much about this error
message or the others that appear during a debugging session of ntldr,
although I don’t what it means exactly, and I can’t say that I recall
seeing this one before, but it’s been a good two years since I’ve
debugged ntldr.

Good luck,

mm

Zhang, Raymond wrote:

Hi All,

Refer the output from WinDBG, it complained that failed to load an
extension DLL called bootext. I think such dll is defined in workspace
for NTLDR debugging so WinDBG is trying to load it at the beginning of
the debug session.
With a search in several versions of WinDBG and Internet, I didn’t find
such bootext.dll. So it is possible an internal DLL. If so, why public
version of WinDBG still loads it (a bug???)?

Anyone has information about this extension DLL?
______________________Output of WinDBG

BD: Boot Debugger Initialized
BD: osloader.exe base address 00400000
Connected to Windows Boot Debugger 2600 x86 compatible target, ptr64
FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Module List address is NULL - debugger not initialized properly.
WARNING: .reload failed, module list may be incomplete
KdDebuggerData.KernBase < SystemRangeStart
Windows Boot Debugger Kernel Version 2600 UP Checked x86 compatible
Primary image base = 0x00000000 Loaded module list = 0x00000000
System Uptime: not available
The call to LoadLibrary(bootext) failed, Win32 error 0n2
“The system cannot find the file specified.”
Please check your debugger configuration and/or network access.

BR, Raymond

3

The reference to bootext.dll is a bug, although a harmless one.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Zhang, Raymond
Sent: Monday, November 12, 2007 6:46 PM
To: Kernel Debugging Interest List
Subject: [windbg] Did you ever see bootext.dll?

Hi All,

Refer the output from WinDBG, it complained that failed to load an
extension DLL called bootext. I think such dll is defined in workspace
for NTLDR debugging so WinDBG is trying to load it at the beginning of
the debug session.
With a search in several versions of WinDBG and Internet, I didn’t find
such bootext.dll. So it is possible an internal DLL. If so, why public
version of WinDBG still loads it (a bug???)?

Anyone has information about this extension DLL?
______________________Output of WinDBG

BD: Boot Debugger Initialized
BD: osloader.exe base address 00400000
Connected to Windows Boot Debugger 2600 x86 compatible target, ptr64
FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Module List address is NULL - debugger not initialized properly.
WARNING: .reload failed, module list may be incomplete
KdDebuggerData.KernBase < SystemRangeStart
Windows Boot Debugger Kernel Version 2600 UP Checked x86 compatible
Primary image base = 0x00000000 Loaded module list = 0x00000000
System Uptime: not available
The call to LoadLibrary(bootext) failed, Win32 error 0n2
“The system cannot find the file specified.”
Please check your debugger configuration and/or network access.

BR, Raymond

You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com