Comment Ed Dijkstra was right about BASIC. (Score 1) 107
TSIA.
TSIA.
Looks like that change is already in progress. Their website removed wording about open weights and the self-deployment bit just says CONTACT US. The smaller models are still up on HF though, would be pointless to remove them.
VBox KVM backend from Cyberus seems like a good step in the right direction for VMWare exit strategy. Way too much left to do, but a good step.
And aside from being a liar, you're a gigantic, filthy, gaping asshole. Fuck off and die in a fire.
The promises aren't worth the pixels they're printed on. Typically, five minutes after company looks halfway viable, someone will make an eye-watering offer for whatever they want from the company and it's done. Just, ya know, tell the users the absolute minimum you can get away with.
Might read the full article on that. Original provisioning for trains was one contract, ongoing service was another.
Original article:
https://zaufanatrzeciastrona.p...
English translation:
https://zaufanatrzeciastrona-p...
It's a couple if registry keys to allow Win11 to install without TPM or on an older CPU.
Lowest effort solution there is to download Win11 ISO from MS and use Rufus [ https://rufus.ie/ ] to make an installer thumb drive.
I've got a spare 2012-vintage ThinkPad x230 here that handles Win11 just fine. (i7-3520M, 16 GB DDR3, SATA SSD).
I've seen this installed, and I only have local logins. Microsoft is ignoring the customer's wishes anyway - I had to uninstall Edge from my mom's computer (which was confusing her greatly) and she does not even have an admin account and thus no way to ever have installed it herself. The half assed half wits in Redmond all claim that they know more than you do about what's good for their bottom line.
Grrreat... thanks again, Microsoft. Any rate, now that I've had a minute to look further, there's a per-user toggle to disable in gpedit.
gpedit -> User Configuration > Administrative Templates > Windows Components > Windows Copilot > Disable Windows Copilot
and the associated reg key,
reg add HKCU\Software\Policies\Microsoft\Windows\WindowsCopilot
(key via via https://learn.microsoft.com/en...)
Per link, it would apparently be asking FAR too much for an option to globally disable Copilot, but I guess that's what Enterprise/LTSC is for. Grrrr.
My one Win11 install does not currently have Copilot showing, so can't test. And, again, I believe it is not reasonable to expect MS documentation to be either complete or accurate anymore.
Oh, good. Now I know I'll be spending some time trying to dig this out at the roots. Perhaps that'll work, or perhaps I can just toggle it to an "off" state. And perhaps my choice will be utterly ignored in future updates. In any case: DO. NOT. WANT.
As of yesterday, my understanding is that you must use a Microsoft account login to get copilot functionality. Local login and you'll never see it.
Expect this to change without notice or documentation update
For now, this *should* do the trick if MS documentation isn't outdated or just plain lying again.
# Disallow login via MS account, require local login
# 1 = can't add MS account, 3 = can't add or log in with MS account
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
# Disallow switching from local to MS account
reg add HKLM\SOFTWARE\Microsoft\PolicyManager\default\Settings\AllowYourAccount
# Disable MS account sign-in assistant
reg add HKLM\ystem\CurrentControlSet\Services\wlidsvc
Reboot after.
Three years behind is plenty good enough, on raw performance, to work towards ending dependence on foreign tech. If so, long road ahead.
How many QA engineers does it take to screw in a lightbulb? 3: 1 to screw it in and 2 to say "I told you so" when it doesn't work.
