That’s right, it was actually a pun on Toshiba

There is no one in my circle of acquaintances who is as critical of a number of details as I am.

For example, running beta drivers/firmware and cheerfully updating Windows (yes, also with 11) and replacing them with older versions.
None of these people also use virtualization, iSCSI, RDP, and AD (enough); I of all people do.

For me, fasting applies; if it works properly on Windows 10, but not on Windows 11, I will not continue looking at the hardware; then it will be wrong with Win10 as well

It’s already costing me a lot of time to waste more time on it while there is already a (in my opinion better) solution; Win10.
So (in my opinion) it’s sad that the switch is actually forced by turning off security updates.

In fact, it is not strange; The entire Windows test file has been moved to the main side; Let’s just say you’re playing into the hands of as few people as possible using proprietary/weird or expendable configs, so I don’t actually think people trying to use their hardware to its full potential are expected to run into all kinds of things that it previously should have Real test section… but this is not part of the professional license.

If that confidence drops, it will only ensure that more people use the 30-day grace period, resulting in a smaller testing space. At least, I would have already gone to 30 days to expect reliability… I remember well that in the era of Windows 7 and 10 I was always part of the test groups/preview releases and only since Windows 11 has that actually been the case right away.

Trust comes on foot and lives on horseback, the last laptop I had that many issues was the Panther D900f, but that had to do with a weird configuration like 3 2.5″ 7200rpm drives in RAID0, Optane and two 280m drives In SLI, this relates to a fairly regular Dynabook Sattelite Pro C50D-B-10G with just the memory banks and NVME swapped (and yes, also with the standard configuration to 2x16GB and 1TB NVME).