this post was submitted on 02 Jan 2026
648 points (98.1% liked)

Technology

78435 readers
3860 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
648
Windows 11’s 2025 problems are getting impossible to ignore (www.windowscentral.com)
submitted 6 days ago by handnutaschnitte@feddit.org to c/technology@lemmy.world
245 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] the_crotch@sh.itjust.works 2 points 6 days ago (1 children)

Have you tried creating a new VM and attaching your existing vhdx or whatever to it?

[–] IchNichtenLichten@lemmy.wtf 3 points 6 days ago (1 children)

I just went for a new installation. Why would that work? Just curious.

[–] the_crotch@sh.itjust.works 4 points 6 days ago (1 children)

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.

[–] IchNichtenLichten@lemmy.wtf 2 points 6 days ago (1 children)

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.

[–] the_crotch@sh.itjust.works 2 points 5 days ago

The hypervisor doesn't necessarily present the guest the exact CPU you're running. Maybe it was presenting an older model, or something stripped down that didn't have the features win 11 was looking for. It's moot.now that you found a solution but I believe this is what happened and moving the disks to a new VM probably would have worked.