Could you imagine Microsoft trying to get ordinary people to tinker around in the BIOS to turn on secure boot and TPM. This is a disaster in the making.
Agreed. Sometimes there's dormant code in a BIOS, and that code is turned off because the motherboard doesn't have the sub-assembly that the dormant code is designed to address. So you might have a generic BIOS for several different revs of a motherboard. Unless one knows that the hardware sub-assembly is actually present on the motherboard, then it could be a disaster turning on the dormant code to address the sub-assembly that is not there. So this could get dicey.
Here's an example of the Windows 11 interface with an Open-Shell workaround for the Start Menu. Instead of having the menu in the middle of the taskbar, you can dock it on the left, change the menu, and give it a new start button.
MS is telling home users, "You have 4 years to upgrade your hardware. After that F You" Corporate customers that won't refresh their hardware will be offered exorbitantly expensive extended support contracts on Windows 10.
Did you mean the "Taskbar" or "Start Menu"? The Windows 11 settings do not distinguish between these two very well. I have yet to be able to "unlock" the Taskbar so as to make it "vertical" and move it to the left of the screen. But you can move the "Start Menu" to the left per Sam-Rs instructions. The settings say "Taskbar" but I think they are actually the "Start Menu".
I have done this but the Start button and other icons disappear. You can do it in the registry. It proves to be useless though for the fore-mentioned reason.
I installed win11 on vhd and it went great ,fast but for workstation its bad ff crash all the time apps works weirdly and so on im sticking with server 2016
Installed to spare metal box Core i7 2600K 16gb memory 120gb Kingston ssd Working fine so far, Firefox default browser.
There are some incompatibilities with apps that have their own GUI. Samsung Magician wont open its main window correctly and instead you get a single vertical shadow. I have had one BSOD on the test system I'm letting run 24/7 on a 3D screen saver. Event log says it was RPC, SVHOST and DHCP related.
I was thinking earlier today... Why straight up block Insider computers which aren't officially supported? I mean they could do as they said... and give a warning that bugs and problems could appear... And just let everyone test the insider builds... But no... They are kicking the poor machines out of the Dev/Beta channels. And if they don't... they give a very concerning warning: "some features may not work properly". What are these features they are talking about? Is it possible they are planning to announce some killer feature which requires newer hardware?