So they made a feature, put it into testing and then said, hey, you probably shouldn't enable this feature because it's insecure and it could also open a door to malware.
What does that look like exactly? specifically, they say, hey, they warn in this document, only enable this feature if you understand security implications.
And not much else is said here about it, but one of the coders that contributes to the WinUtil, Coding Wonders, actually installed this version.
But the build Coding Wonders used on the dev channel was 26220.7262. And this is what it looks like.
Essentially what they're doing is it's going to be a sub-process of, I want to say SVC host, which we'll get into.
But SVC host is essentially a process that runs on every Windows system, and it's very prominent.
You'll have it running right now, but most average normal users won't be able to know that ISO environment broker is running in the background unless they use something like Process Explorer or from Sysinternals or something of the like to actually break down some of these processes that run on Windows.
However, this is kind of what they're doing, where they're putting it, and we're kind of just tracking down all these changes so we can strip them out, we can use tweaks and kind of fix the glitch that they're going to add.
Here's the entry in the component store and their actual official documentation saying the creation of agent accounts.
This provides agents their own separate account on your device acting on your behalf.
Windows is using a phased approach to add stricter rules to agent accounts in upcoming releases.
If you enable it, it can just do whatever it wants, which is scarier than it sounds.
The creation of the agent workspace is where agents can work in parallel to the human users.
Think of it as almost like a secondary account, enabling runtime isolation and scoped authorization.
This provides the agent with capabilities like its own desktop while limiting the visibility of and accessing the agent has to the user's desktop activity.
So essentially, it's like a secondary user that's logged into your desktop that can do all kinds of sort of things.
So they made a feature, put it into testing and then said, hey, you probably shouldn't enable this feature because it's insecure and it could also open a door to malware.
What does that look like exactly? specifically, they say, hey, they warn in this document, only enable this feature if you understand security implications.
And not much else is said here about it, but one of the coders that contributes to the WinUtil, Coding Wonders, actually installed this version.
But the build Coding Wonders used on the dev channel was 26220.7262. And this is what it looks like.
Essentially what they're doing is it's going to be a sub-process of, I want to say SVC host, which we'll get into.
But SVC host is essentially a process that runs on every Windows system, and it's very prominent.
You'll have it running right now, but most average normal users won't be able to know that ISO environment broker is running in the background unless they use something like Process Explorer or from Sysinternals or something of the like to actually break down some of these processes that run on Windows.
However, this is kind of what they're doing, where they're putting it, and we're kind of just tracking down all these changes so we can strip them out, we can use tweaks and kind of fix the glitch that they're going to add.
Here's the entry in the component store and their actual official documentation saying the creation of agent accounts.
This provides agents their own separate account on your device acting on your behalf.
Windows is using a phased approach to add stricter rules to agent accounts in upcoming releases.
If you enable it, it can just do whatever it wants, which is scarier than it sounds.
The creation of the agent workspace is where agents can work in parallel to the human users.
Think of it as almost like a secondary account, enabling runtime isolation and scoped authorization.
This provides the agent with capabilities like its own desktop while limiting the visibility of and accessing the agent has to the user's desktop activity.
So essentially, it's like a secondary user that's logged into your desktop that can do all kinds of sort of things.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
