windows 11

Page 8 of 8 FirstFirst ... 678

  1. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #71

    bobkn said:
    Seems like a pretty Lilliputian issue to me.
    "confusion by obfuscation" comes to mind.
      My Computer


  2. Posts : 4,453
    Win 11 Pro 22000.708
       #72

    steve108 said:
    "confusion by obfuscation" comes to mind.
    I wasn't trying to be obscure. I figured that people interested in computing might know about the origin of "enidianness" (Endianness - Wikipedia). See the reference to Jonathan Swift.

    Lilliputians were known for going to war over which end of a boiled egg they chose to break to eat it. If they were Windows users, it might be round vs. square window corners.
      My Computers


  3. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #73

    bobkn said:
    I wasn't trying to be obscure. I figured that people interested in computing might know about the origin of "enidianness" (Endianness - Wikipedia). See the reference to Jonathan Swift.

    Lilliputians were known for going to war over which end of a boiled egg they chose to break to eat it. If they were Windows users, it might be round vs. square window corners.
    I'm not interested in going to war over this ...... just proposed a "simple" solution that M$ could take.
      My Computer


  4. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
       #74

    I'll bite.

    1. Nonsensical hardware cuttoffs (Intel 8th gens OK; 1st Gen Ryzens... no??? WTF?! Cost us another $60 for a Zen+, that did; no wonder they were so much cheaper; considering ahead when we're pingeonholed to go to 11 on that one. Turns out it was Gen 2 1600AF, yet flagged incompatible. 2600 instead and don't like it as much, oh well).
    2. Enforcement of TPM 2.0 and Secure Boot (effectively locking in system to Windows-only unless of course you want to wipe it; not go back to Windows 11 and all your contents held hostage within {ya know, the PC poor}. Or feel free to correct me somebody if I've got the wrong end of the stick here. I've yet to wade into dual booting and other such. Pretty sure this would interfere for those wanting to...?).
    3. Took away the only really useful 7 vs 10 feature (at least I don't recall it in 7): grouped and named Start pins. Why?
    4. No more configuring Taskbar to suit atypical (e.g. sideways for documents reading) display arrays. Why?
    5. Truncated context menu and File Explorer (2-3 times more clicking to do everything in Win11. This one really chaps my cheeks. A pox, a pox I say, for this on the guilty decision-making party. Yes, yes, risky Regedit workarounds for now but... yeah). WHY?!
    6. Rounded corners... on square/rectangular bezel displays. Oooo!
    7++ Who in heck knows.

    That's from not even using the bedeviled 11 personally yet. Yeah.

    Oh! Wait... wait... I know: if we wanted the Crapple experience, we'd have bought into Crapple.

    Me myself and I have been of the longstanding (Win8/8.1 boycotted) opinion that M$ needs to officially fork Windows into a Desktop/Laptop and a Mobile Toys edition and leave the Desktop/Laptop edition (GUI, context, et cetera) ALONE. (And, more recently, stop trying to be what they're not {yet?}: Crapple).

    Me doth think M$ hadn't sufficiently learnt their lesson with the Win8/8.1 gaffe...

    ¯\_(ツ)_/¯
      My Computers


  5. Posts : 1,777
    Windows 11 [21H2]
       #75

    Mortiferon said:
    2. Enforcement of TPM 2.0 and Secure Boot (effectively locking in system to Windows-only unless of course you want to wipe it; not go back to Windows 11 and all your contents held hostage within {ya know, the PC poor}. Or feel free to correct me somebody if I've got the wrong end of the stick here. I've yet to wade into dual booting and other such. Pretty sure this would interfere for those wanting to...?).
    The SecureBoot On is not enforced, but Windows 11 requires a Secure Boot Capable motherboard, so you need to enable UEFI in the BIOS.

    Note that there is workarounds to Install Windows 11 on non compatible machine: See this thread in ElevenForum:
    Let's install Windows 11 on a incompatible hardware | Windows 11 Forum
      My Computers


  6. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #76

    Rarely mentioned when people describe how to install Windows 11 on unsupported hardware:

    "Installing Windows 11 on a device that does not meet Windows 11 minimum system requirements is not recommended. If you choose to install Windows 11 on ineligible hardware, you should be comfortable assuming the risk of running into compatibility issues.

    Your device might malfunction due to these compatibility or other issues. Devices that do not meet these system requirements will no longer be guaranteed to receive updates, including but not limited to security updates."

    https://support.microsoft.com/en-us/...9-ef0a331518f1
      My Computer


  7. Posts : 4,453
    Win 11 Pro 22000.708
       #77

    I wonder whether MS will ever carry through on their implied threat to stop updating 11 on unsupported hardware?

    I recently put 11 on my (cheap) Lenovo laptop. It meets all of the device security requirements (including core isolation, for enhanced security), but the CPU is Intel Gen6.

    I imaged things before running the upgrade, so I can always go back if necessary. I'd bet a small sum (5¢, maybe) that it never will be.
      My Computers


  8. Posts : 1,777
    Windows 11 [21H2]
       #78

    steve108 said:
    Rarely mentioned when people describe how to install Windows 11 on unsupported hardware:

    "Installing Windows 11 on a device that does not meet Windows 11 minimum system requirements is not recommended. If you choose to install Windows 11 on ineligible hardware, you should be comfortable assuming the risk of running into compatibility issues.

    Your device might malfunction due to these compatibility or other issues. Devices that do not meet these system requirements will no longer be guaranteed to receive updates, including but not limited to security updates."

    https://support.microsoft.com/en-us/...9-ef0a331518f1
    Yep. I also do not recommend installing Win11 on unsupported hardware
    so, if I have time, I will clean installing Windows 10 and not go to Windows 11 again (on my unsupported hardware.)
      My Computers


  9. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
       #79

    Reportedly it is a ~52% kernel crash experience on unsupported systems, so no more need be said. Old systems staying 10. Pop!_OS or something else for them assuming they’re even still operational by 2025, and that Linux-whatever will play nicely with aforesaid hardware. (I confess I don’t know a damn thing about that yet apart from it’s notoriously tricky to get Nvidia drivers working… remains to be seen if it’s as difficult to do as it would be to obtain an AMD equivalent or better-than today lmao).

    Don’t all flame me at once, but been on the verge of wanting to take the Linux plunge for years now. 11 might just be what finally forces me to go there… (no illusions of problem-free; not that). But, either way, I will ultimately be dealing with 11 (household Admin; nobody else wants to or can deal with this crap. So Linux for anybody else is haha likely not happening. Hard-won battle to oust crummy OEM systems as it was... HP got on my absolute last nerve).

    Anyway. My personal objections would mostly evaporate over 11 if they'd at least rectify 3, 4 and 5. I don't think that's unreasonable.

    [In case anybody wonders why I said I had preferred that 1600AF, the 2600 appears more sensitive to DOCP (effective I've left it JEDEC).]
      My Computers


  10. Posts : 31,682
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #80

    Mortiferon said:
    Reportedly it is a ~52% kernel crash experience on unsupported systems, so no more need be said.

    Actually a lot more needs to be said about that 52% figure, which is correct (we assume) as it came from Microsoft themselves. Microsoft have been a bit disingenuous in their use of statistics. First, lets look at the full statement from Microsoft:


    Reliability: Devices that do not meet the minimum system requirements had 52% more kernel mode crashes.
    Devices that do meet the minimum system requirements had a 99.8% crash free experience.

    Let's analyse that a bit more. 0.2% of supported systems crashed. Unsupported systems had 52% more crashes, therefore 0.304% crashed. So to re-write the MS statement in terms that no longer compares apples with oranges it now reads as:

    Reliability: Devices that do not meet the minimum system requirements had a 99.696% crash free experience.
    Devices that do meet the minimum system requirements had a 99.8% crash free experience.
      My Computers


 

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:15.
Find Us




Windows 10 Forums