I wish they would do a much better job of distinguishing corporate workstation versions of Windows and Home versions of Windows. Put all this MS ecosystem garbage on the workstation version, and make the Home version a stripped down to the essentials OS. Which is what most of us try to do with tools like ShutUp10, anyway.

How long before there’s a discovery request for all recall data for a time period and companies start screaming about the risks with recall?

Agreed - if I were evil, I would use this data to look for long periods of static/unchanging desktop screenshots to look for inactivity and employees lying about being there or away.

Honestly this is just an arms race. If the above happens (and if I can come up with that use case think about what will come up when someone actually smart thinks about it.)

The response? I’d make a tool that presses alt-tab every 15 seconds a random number of times - to both keep the computer alive and change the desktop view, maybe move the windows around a bit for variety. A usb rubber ducky would be perfect for this.

It's less bad for sure. And I can understand, theoretically, the value of "that one think I saw that one time". I've definitely spent way longer than I'd want looking for some random reference I'd seen in the past, and I'm in the process of trying to catalogue all the references in my past nonfiction reading after the fact, and it's definitely a lot of work.

But man, other users on your PC could trivially see everything you did on your system unless you used the dumpster fire that's edge in private browsing mode, and the people on the project thought that was OK. There's no way people with that level of lack of awareness managed to adapt the project to not be a sieve.

Why cachy?

I have a really basic one. Some caveats - I've also used Windows my whole life (up until about 2 weeks ago), but I'm comfortable getting into a command prompt and/or powershell to tweak stuff. Also, I had a spare SSD lying around and extra space on my installed HDD.

Step 0 (arguably the hardest): pick your distro.
I went with Arch - but if you want something Arch-based but a little less barebones, you might do fine with Manjaro or EndeavourOS. This is totally up to you though (I'm in the process of migrating my wife to openSUSE). "But Gaspar, you crazy old man," you may ask, "what all is out there?" Well.. there's a lot. Over 600 active distros, if you believe this random-ass tech blog, and countless other hundreds (or thousands) that are old, outdated, no longer supported, or were cooked up by one dude specifically for their own system and will never be uploaded. There are a couple of tools that can help narrow this down, but you're really just going to have to poke around and see what appeals to you.

Step 1: Test in a virtual machine first.
This is optional, but it may help you make up your mind: pick a few different distros and install them in virtual machines, using VirtualBox or something. You can poke around in there and see how things "feel" before you make up your mind, without worrying about messing something up.

Step 2: Load up a USB stick.
Ventoy. You don't HAVE to use this, strictly speaking. You can just get Etcher or Rufus or something, use them to write your chosen distro's ISO to a USB stick, and install that way. But Ventoy sets up a separate partition on your USB stick where you can grab a bunch of different ISOs and drag-and-drop in there, and load up whichever one you want. Pretty handy.

Step 3: Go into Disk Management and free up a partition for your chosen distro.
This is up to your taste (I just installed it into its own whole SSD) but I'd set aside at least 256GB for the OS and the packages you'll want to install once you get in there. Again, though, YMMV.

Step 4: Install that sucker!
OK, now boot into your ISO through the USB stick you prepared earlier and install the sucker on your new partition. Most distros will have you set up a root password and give you the option to create a user. YOU WANT TO DO THIS. You do not want to always access your system as root - that way lies madness (and it's wildly insecure). You may also get a choice of desktop environments. This is up to your taste but I went with KDE Plasma because I have a Steam Deck (which also runs on a variant of Arch) and I was already used to the interface.

Step 5: Migration start
After you've gotten set up and a little comfortable poking around (maybe you already figured out how you want to start setting up when you were testing VMs in Step 1 earlier), it's time to start partitioning. There are a few GUI partition managers you can use - I used KDE Partition Manager, but there's also Gparted and a few others.

Once you're in whichever program you've chosen to set up your partitions, you'll want to proceed in this basic order:

• Shrink your Windows partition(s) if they are taking up the entire drive, and you have the space to do so (if not, we'll get to that)
• Create new Linux partitions in the filesystem of your choice (again, will explain this shortly)
• Mount both your Windows and Linux partitions and copy from one to the other
• Once you're happy that everything's copied over, delete the Windows partition(s) (unless you're planning on dual-booting, in which case keep the partition with your Windows install)
• Finally, extend your new Linux partition(s) to cover the whole drive

Step 6: Wait what?
Well, maybe your Windows drive is full, or there isn't enough space on the new partition to copy everything over. This is why I mentioned the spare SSD. You can plug that in, if you have one, and use it as a placeholder to copy your files to while you reformat your drive and then copy everything back.

Also - filesystem of your choice? Well, Linux has a few options for partition types: ext4, btrfs, zfs, and a bunch of others. You'll have to check them out and see which makes the most sense for you. I personally just reformatted everything as btrfs. It may not have been the most efficient choice, but it's worked out for me so far. The main issue here is the standard Windows NTFS file system. Now - you CAN keep a lot of your data on an NTFS partition, especially if you want to dual boot Windows for a while and get used to things while still having that familiar lifeline (or, like me, if you have some games that still just don't play well with Linux yet). Here's the thing, though: thanks to a driver you can download, you can fairly easily get Windows to mount your btrfs partitions (I did it and even still have my drive letter associations). Plus, if you are a heavy Steam gamer, while you CAN get Steam on Linux to read your NTFS partitions.. it's a huge headache, and it isn't worth it IMO (and, in my experience, I couldn't get my NTFS partitions to STAY mounted as read/write). Better to just bite the bullet.

If you are planning on dual-booting, of course your Windows partition will still need to be NTFS. But if you have the disk storage to copy everything over, you can have everything else converted to whatever combination of Linux partitions you want in a few days (took me about 3, but I also had 10-ish TB to copy over and I had to do half of that twice).

Final Thoughts
Depending on whichever flavor of Linux you opted for, you may boot into GRUB, which is a bootloader that gives you some pretty neat configuration options - one of those options is the ability to boot into all your existing OS installs, including your Windows installation. Once you get a bit more familiar with Linux you may wish to make your Linux partition the default, secure in the knowledge that whenever you want, you can just hit down a couple of times, then Enter, and boom - you're in Windows. Just be careful, because Windows recently pushed an update that may have broken this currently. I think it's a nice touch, though.

I have rambled on long enough at this point and I'm sure someone else can point out several hundred things I missed - again, I am still a Linux newbie. But the best way to learn this stuff is just to do it, and depending on your comfort level and familiarity with Windows it shouldn't take you long to get up to speed. Good luck!

It's 1000%going to be used for corporate surveillance.

Features to do this from other vendors are already in use.