


There is also a github page with links to previous versions. Microsoft provides premade virtual machinesfor browser testing. (And switched to Vmware Workstation while writing the -Exploitation- tutorials, because it offers virtualization of certain security features that Virtualbox doesn'tl) I used Virtualbox while writing this guide. Use it if you are tied into Vmware products or want to fight SMEP. It is built for a completely different purpose and feels very clunky if used for kernel debugging. Apart from that Virtualbox is the best pick in my opinion and Hyper-V should be avoided. Neither Virtualbox nor Hyper-V virtualize SMEP which is a downside if you start advancing into exploiting. Main choices are Vmware Workstation, Oracle Virtualbox and Microsoft Hyper-V. There are several hypervisor solutions to choose from. Open WinDbg Preview, select kernel debugging and put in the port and key from above.

