heh, neat. the .kdfiles windbg command can be used to remotely reload (inject) kernel drivers in a debugging target.

https://learn.microsoft.com/en-us/windows-hardware/d...

windbg kernel debugging drivers kernelspace

this can be useful if you have multiple versions of some driver that you're debugging on your client. that way you can swap the one in your target for one on your disk. you're also more likely to have symbols for drivers you have locally, so you can avoid having to copy drivers and symbol files around.