Isolated User Mode in Windows 10 with Dave Probert

He is a GOOD teacher and I am glad you asked him valid questions.  I would love to see a series with Dave teaching "Operating systems". I am really looking forward to the other episodes.

Good job Dave !!

Thanks 

More low levels!

I hope you will give this gentlemen more time on Channel 9. Hoping for series on Windows Internals? ;)

Bring on part two - 3,4,5, and 6?? Please!!

Is it Going Deep show?

Fantastic information. Looking forward to the rest!

Awesome!

Welcome back, Dave. Excellent as usual! :)

Great job, Seth!

Looking forward to the next installments.

C

Where is part 2?????????????????????

This is the best description of I've seen of IUM so far. I wish Microsoft would not send the management/PM types out to conferences, please just send the engineers to give the correct description to begin with!

PARRRTTT TWWWOOOOOOO!!!!!

Nice info! Looking forwards for the next video.

Thank you for this video. That was very interesting.
I think IUM will be used for Windows Docker containers.
Docker on Linux uses similar kernel instructions to isolate the containers.

this is great. Looking forward for the next one. Love to see more videos from this man. 

More Dave Probert videos. Why not doing a series that teach us people more about Windows 10 Kernel stuff? It would be awesome and appreciated.

ONLY 30 MINS??!?!?!?!?!
loved it!!!

can't wait for part 2!

Thanks a lot!

this is the best explanation that i have seen in Channel9, it is possible the others use this metodolegie (Black Board) instead of Tablet

Thanks for the deep down explanation.

Excellent, after wasting many hours on MS Academy W10 series, this video is exceptional and tells the story from the bottom up, not top down as were expected to understand (and I never can), you both work very well together.

Is the marshalling act performed by the proxy Kernel the same as the mechanism called LPC which was mentioned in Helen Custer's Inside Windows NT book?

For those pressed for time, the short of this video is that the kernel team introduced the concept of secure kernel which is used by some secure application.
Both the secure kernel and secure application run in a different address space from the normal kernel and normal applications. This address space is managed and isolated by the hypervisor's "Virtual Secure Mode" feature (which is a form of address translation in the hypervisor). The secure kernel is not a full-fledged kernel, but rather a mediator/proxy for system calls to the kernel (via some shared memory).
The result is that the kernel does not have access to the in-memory data of the secure application.

This video did not explain how an application developer can run his application in this secure mode. This is presumably the topic of the next video.

Seth, you have an uncanny ability to ask the follow-up question I was just thinking.  And while that might not be particularly impressive from my wife's point of view, I certainly appreciate it.

so this is basically Microsoft's implementation of Jail from Linux?

I am deaf, where can I find the text version ?

Awesome... Nice explanation..

-Nambi