[Autogenerated] Let's examine the project manager.
Namespace by running win be J, one of the CSS center channel tools,
and When you run win be J.
Initially, it runs with the standard user right.
That's not good enough.
To see everything there.
Is to see here.
So it's better.
To run this with admin privileges.
And Once we do that we can see everything there.
Is to see, in the object manager,
namespace and We've talked about some of these directories,
in the past, remember, these directories,
are in memory.
They have nothing.
To do with the file system at all.
These directories, are just container object,
which are also part of the object types supported by Windows Now,
in the example for the shutdown,
event we've seen that The name of the event wasn't really shut.
Down event but was In fact, something like sessions,
two based named objects, and then shut down,
event So what we see here, is that Every session has its own object.
Namespace which means that If I call a function such
as create event with the name a BC, the actual name of the event object,
is In fact, going to be sessions, the number of the session.
Based named objects, and then a BC.
This is the way it works by default.
So that every session has its own names.
And what we see here in this view.
Are the list of all the named objects created by processes.
That run in section number two.
So this view, is not view of handles.
It's the view of objects which is different than what we see in
cross explore which shows us view of handles.
Per process here, we can see the list of named objects, only only those objects.
That have names as by processes in session.
Two When you click the double-click one of these objects,
we can see the properties for that object which is fairly similar.
To What we've seen in process explore because in cross
explores properties for an handle, is actually properties for the object.
So it's essentially the same thing here.
So we can select any one of these objects,
and see what's going on with these objects.
Now, if we go back to our example for uh for working with named objects,
just to See what that looks like we can Go ahead.
And and see the that In fact,
if I go ahead and and do something like filter here,
something like shut down, I'll see everything.
That has the word shutdown as part of its name we can see there,
are a Few of those here already.
Let me make these always on top.
If I just run this process once.
Is enough, we should be seeing shutdown, event popping up.
And Indeed it does.
Here's the shutdown event event object because it is named
it is shown here for unnamed objects.
They will not be shown here.
What about session zero?
You can see that Session zero here seems to be like a normal session.
But in fact, it's kind of special you.
Can see based named object, is not here.
So session zero, is In fact here under the root.
So this is what we find here, all the objects created by processes.
That run in session zero,
such as services and various system processes such as cs services ms ss,
and so on.
So it's the same idea essentially.
But we have a separate directory which is laid out slightly
differently than for normal user console various sessions,
console sessions or terminal services sessions.
Another thing you can see here,
is this directory called app contain named objects this is
a directory that contains sub direct series which
represent various UWP applications, UWP processes,
UDP processes can only have objects, that have names if in fact,
they have names.
That reside in their own private like a super private,
namespace in the way, that They cannot really be shared with other processes.
Just trying.
To exemplify the fact.
That UDP processes can t really interfere with other processes
because they can't even create an object.
That has a name, that can can be shared with processes,
that are not part of its own package.
So for example, if this kind of process will try.
To create an object called shutdown,
event It's not going to be the same shutdown.
Event created by our app its going to be a private shutdown,
event which is only part of this particular namespace this seed you see here,
is something called an app app container seed,
this is a way, to identify a UWP package.
So an European application can only share objects with itself
or with other processes within its package.
Maybe it has a background task.
In this case, it can still share these things So this is where named objects,
are for UWP processes for all other processes,
normal processes.
So, to speak, they error part of based named objects right here.