Comment

Comment on Windows 11’s 2025 problems are getting impossible to ignore

IchNichtenLichten@lemmy.wtf ⁨6⁩ ⁨days⁩ ago

I detest this company for many reasons, it’s like they go out of their way to make dealing with them as painful as possible.

Here’s just one example I discovered today. I have a Windows 10 VM I needed to upgrade to 11 but the “PC Health Check” app says no, the i5 processor isn’t supported.

I can, however, create a new VM and install 11 on the exact same hardware, so that’s what I did, along with a whole bunch of extra work to get the new VM set up the same as the old Windows 10 VM was.

Why? Because fuck you, that’s why.

Assholes.

source

Sort:hotnew top

bagsy@lemmy.world ⁨6⁩ ⁨days⁩ ago
This is how i feel about 98% of Azure. Its just so needlessly complicated, with incomprehensible defaults, and out of date documentation, and APIs that just fail silently.

source
- hdsrob@lemmy.world ⁨6⁩ ⁨days⁩ ago
  So much this. I actually pulled all of our servers from Azure and went back to a regular provider. Way cheaper as well.
  
  source
TBi@lemmy.world ⁨6⁩ ⁨days⁩ ago
There is a way to upgrade directly. I got this from Reddit

reddit.com/…/is_it_safe_to_install_windows_11_on_…

It works fine - you just won’t get the more advanced security features available in more recent laptops.

Boot up into Windows 10

ensure you have 30GB free space

Download the .iso: www.microsoft.com/software-download/windows11

right-click the .iso and select “mount” to create a virtual DVDROM

create a new folder on your main system drive and copy all the files from the virtual DVDROM

start a command-prompt

navigate to the folder where you copied all the files

run the following:

.\sources\setupprep.exe /product server

This will not actually install the server version of windows but will bypass the CPU check so that you can install Win11 on an unsupported CPU. The actual version of Windows installed will depend on the version of Win10 you have: Pro, Home, or Enterprise, for example.
source
- IchNichtenLichten@lemmy.wtf ⁨6⁩ ⁨days⁩ ago
  Thank you for this. I already did a fresh install but it’s interesting that your link is to the Surface subreddit just to rub some more salt in the wound. The processor is officially supported for upgrades only if it’s in Microsoft’s hardware. I hate them so much.
  
  source
  - TBi@lemmy.world ⁨5⁩ ⁨days⁩ ago
    The irony wasn’t lost on me. Since I was trying to update my surface. I’ve also installed Linux on it. Which runs a lot faster on the older Surface Nook 1 harder.
    
    source
- Valmond@lemmy.dbzer0.com ⁨5⁩ ⁨days⁩ ago
  You can also flash a usb stick with rufus, mint needs 4GB IIRC.
  
  /j
  
  source
  - TBi@lemmy.world ⁨5⁩ ⁨days⁩ ago
    I prefer Fedora. Tried mint and hated it.
    
    source
    Valmond@lemmy.dbzer0.com ⁨4⁩ ⁨days⁩ ago
    As a neophyte to all those distros out there but still curious, any specific reason?
    
    source
- TheBlackLounge@lemmy.zip ⁨5⁩ ⁨days⁩ ago
  Is that an upgrade or a fresh install?
  
  source
  - TBi@lemmy.world ⁨5⁩ ⁨days⁩ ago
    It will upgrade an existing install. I did it on my surface and all my files and settings were kept.
    
    source
the_crotch@sh.itjust.works ⁨5⁩ ⁨days⁩ ago
Have you tried creating a new VM and attaching your existing vhdx or whatever to it?

source
- IchNichtenLichten@lemmy.wtf ⁨5⁩ ⁨days⁩ ago
  I just went for a new installation. Why would that work? Just curious.
  
  source
  - the_crotch@sh.itjust.works ⁨5⁩ ⁨days⁩ ago
    It sounds like your VM config was presenting a COU or TPM config that the upgrade wasn’t comfortable with. If your new machine presented acceptable configs to a brand new VM, then making a new VM and feeding it the old .vhdx would be the same as pulling a storage device and putting it in a new motherboard that was win 11 compliant. After a reboot to install new drivers it probably would have upgraded happily.
    
    source
    IchNichtenLichten@lemmy.wtf ⁨5⁩ ⁨days⁩ ago
    Hmm, the only barrier to upgrading was that the i5 processor wasn’t supported, no complaints about TPM/motherboard compatibility and a fresh install worked fine on the exact same hardware. Oh well, it’s done anyway.
    
    source
    -> View More Comments