Just a tip: if you must use consumer editions of Windows regularly, consider adding an automatic provisioning tool like AME to your workflow.
The example above uses customizable “playbooks” to provision a system the way docker compose would a container image, so it can fill the role of a VM snapshot or PXE in non-virtualized local-only scenarios.
The most popular playbooks strip out AI components and services (there are many more than just Recall) but also disable all telemetry and cloud-based features, replace MS bloatware with preferred OSS, curtail a truckload of annoying Windows behaviors, setup more sensible group policies than the defaults, and so forth.
I have a few custom playbooks for recurring use cases so that, when one presents, I can spin up an instance quickly without the usual hassle and risk.
SaharaMaleikuhm@feddit.org 4 hours ago
This got me good. I just love how they try to make using .NET for making a windows application “not the easy path”.
Sounds kinda interesting though. If I’m ever so unlucky as to having to use Win11, I will give it a try.
Septimaeus@infosec.pub 4 hours ago
Lol I noticed the same. They evidently have some ongoing internal disagreement as to their target audience. Docs and functionality says “our audience is enterprise developers” but their marketing definitely says “our audience is end users.”
It may be explained by recent partnerships with former custom ISO devs (seeking legitimacy and offering a sizable user base in turn). I expect the plan is eventually to sell premium support for an enterprise toolset, but for now their target audience is the non-dev-but-tech-savvy end user. And those happen to be surprisingly opinionated re: java and electron.