So it is clear.
Workaround for me should be to delete or rename vmwinst.exe before the initial boot.
I`ll try.
David
art yerkes wrote:
Again, it should not raise any kmode exception, it only performs a privilleged instruction which raises an umode exception on regular systems.
Best Regards, Thomas
Our kdbg handles *all* exceptions last time I looked. dwelch told me not to turn that off, because he wanted it that way.