The Prepared environment for kernel programming
 

Hello,
Is there a custom Windows operating system for kernel programming?
For example, the WDK package and the Visual Studio version related to it are installed And other settings for kernel programming and debugging It has been done
Like This (Windows 10 Pro [1607] (x86/x64) Reverser Edition ISOs) :

Enterprise grade Device Driver development is done with Standard OS images, debugging performed by running the driver in VirtualMachine (Kernel Development is rich of BSODs or worse scenarios with storage drivers that destroy Filesystem) and attaching in remote debug session with Windbg.

To setup the environment, you can use the following link:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/attaching-to-a-virtual-machine--kernel-mode-

Best Regards,
Evilcry

Seriously, man ? You are actually linking to content in the RECYCLE BIN/TRASH of another forum ? :D :D :D

Isn't it going a bit too far ? I've got my content deleted there, and now you link it in the Recycle Bin ... :eek:

Perhaps maybe a trimmed version of a checked windows build?

hxxps://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/checked-build-of-windows

I would beg to differ with EvilCry on this. The development and testing is BEST done on specialized build systems that have the LEAST bit of interferring services and software running on them.

For the development of complex (especially kernel-level) drivers, we use specialized trimmed builds of windows that are VERY lean.

The logic being, that when we want to develop drivers and ensure that the driver(s) themselves are running and performing their functions without issues, it is a LOT easier to debug them when very few services are running in parallel on that system.

Otherwise it becomes very tedious to debug at every stage and see as to whether the driver itself is faulty or whether compatibility with the running services is the issue.

Also, the debugging itself is VERY fast with a system running a minimal set of services on it.It of course goes without saying that for kernel level debugging we require two machines (virtual or real).

It is only when we have determined that the driver itself is functioning as expected, that we switch to debugging and testing on "real" systems that mimic the Retail Builds as closely as possible.

Regards

I am sure if you have good connections with MSFT, you can get something like the Shared Source Initiative which would allow such customizations to be made in detail for driver debugging.

Otherwise Microsoft seems to encourage using the Checked Windows builds as per RiRye above.

The question is in practice, what are the major companies out there doing?