jon wrote:
On Thu, 27 May 2021 20:22:37 +0100, gareth evans wrote:

Any known bugs here? ...

W10 with FireFox

Usually in the evening.

I'll look at both of my gmail accounts, but when signing out of the
second, the laptop freezes with the disk light on.

There's no keyboard response in FireFox, not even to Alt-F4, and no
mouse cursor.

There's no Internet activity indicated on the LEDs of the router.

The only recourse is to shut down by an extended pressing of the power
button.

It's only been happening in the last week or so.

TIA

Gareth download a trial application for 'Process Lasso' and run it. It
will identify any processor hogging applications that are running. You
will have the opportunity to terminate the troublesome app.

In a quiescent state your computer should look like this:
https://ibb.co/WfC205R

21H1 seems to be virtualized.

I notice that Task Manager no longer aligns with
machine state and CPU usage.

Hyper-V is an inverted hypervisor, and the "host" OS
runs as a "client" of Hyper-V.

In the "Era of Containerization", we will not be able
to figure anything out. I've already discovered this on
Linux, with Snaps. You can have software behaviors which
are a function of which security ring they run in.

Microsoft laughs at your Process Lasso now. You're screwed.

We need a lot more documentation to be dealing with
this era. If only Mark Russinovich was not being held
hostage in a cheese factory... (He's the Sysinternals guy
and used to write excellent tutorials on how stuff works.
He used to write and sell books about Windows Internals.)

*******

I think I'm going to have to install an "absolutely clean"
copy of 21H1, just to see what the baseline behavior is. And
go the reverse engineering route (add softwares, check
for weirdness and added items where they don't belong).

I suspect (but don't know for sure), that 21H1 uses Hyper-V,
even when Hyper-V is not switched on in
Programs and Features : Windows Features.

It would use that for WDAG, when it uses a 2.4GB "mini-OS"
as a container to run a copy of Office Excel. Or use it
in some way when WSL2 Bash shell is installed and running.

(They changed the name to MDAG, but the hardware requirements
to make it work, tell you what it's doing...)

https://docs.microsoft.com/en-us/win...s-md-app-guard

To get to Control Panels, to check, you can start : run
and use control.exe , then pin the item in the Taskbar
so it will always be available.

One part of this I couldn't figure out, is what
happens to machines not particularly set up to support
Hyper-V ? Do they switch it off ? Do they block your
upgrade to 21H1 ? No idea. I would have to run an
"absolutely clean" install on a Core2 (non-HyperV)
machine to see.

I'd much rather have some well-written articles on
the topic, than do this via reverse engineering.

You can also run Windows 10 in a virtual machine,
and then what happens to this container stuff ?
The test cases are endless.

Paul