Windows activation after bios update

I have the same activation problem here. My mobo is a MSI Pro Z690-A wifi ddr4 ATX LGA 1700. I built this pc in May 2022, and I've updated the BIOS several times. But back on March 8 2024, I updated for the first time in maybe 6 months using the files provided from MSI support. That's when this activation issue started up--on Windows 11 Home. I got onto the MS support chat and even gave them permission to screen share (I know I know..) while I had him on the phone. He decided that a reinstall was the way to go---so we did that, and it didn't work. He also said that MS was well aware of the issue and something should be coming out in a windows update in the next month. I'm going to hold off on doing the script thing until that time has passed, but I'm happy to read that so many have had success with it.

Similar here purchased Win10 Home license then upgrade to win 11 then this license got busted, decided to buy a full new Win 11Pro nothing to do with UPGRADE and this license got fckd too after second BIOS update however after hours spent on call and massive email exchange with MS Support team I was able to save this one.

let's add ...so far, for how long though????

About this article, apparently microsoft just stopped to let users upgrade from win7 or 8 to win 10/11, causing the issue we're all talking about in here.

BUT: I did purchase a win 10 pro license, full price, and still suffered this annoying issue, after the win 11 upgrade and the BIOS flash. My personal opinion is they do not have a clue where the problem is, this problem is far to be addressed :(

I smell BS, my friend. Many of us suffering this issue were told to buy another license, it's the panacea to cure em all, at least according to microsoft (lower case intended). Just stick with you completely legitimate license and use one of the workaround listed early in this thread: one of them will work for you.

My personal experience, after tried a lot of different workarounds, is that the script works. And it does it very fast.

Didn't find anything like that. Probably you meant some people find alternative solutions that worked for them, but the script just works. Even microsoft support team used it to some customers, like the article I linked a few pages back. The work around used by user mattp516 it's completely logical, and I thought about it (and used it). No success for me.

After that I spent (lost) more than a month trying to open support tickets, no response at all and the ticket were close one by one, with the tag resolved (what a clown joke). So the solutions, or better workarounds, are all in this thread. Use what works for you, but until now the script 'just works'.