Windows 11 no longer activated after bios upgrade

[Stefan.coussen15ac02dc]

EDIT
Alan J T
Global Moderator
A Fix has been provided
Please watch this Video

###############################################################

I updated my bios 3 days ago hoping it would fix some usb issues I was having. Now my windows install is no longer activated (OEM key). Any one else got this problem?
How do you fix it?
Trouble shoot windows activations does not help.
entering the same key also does not work.

So any idea how to fix this and is this a f**-up from MSI bios update?

 

[verickson153502d0]

I've had this issue even with a brand new license, bought direct from the Microsoft website.....something I'll never do again. They took the best part of 7 hours on chat going through all the normal tests (change of hardware, etc.) and still could/would not reactivate my license (even though they could clearly see that I'd got the transaction on my account purchase history, and had already gone through all their checks to verify who I was). They ended up basically asking me "what about this other PC on your account, do you still use that? No? Ok, we can transfer that old license to your current PC then"....that was their "solution"....ignore the £100+ license that I'd bought specifically for this build, and disable an old PC that wasn't being used anymore.

Next bios update, same thing happened, and I didn't fancy sitting through hours of chat with them again, only to find that they still can't/won't re-activate windows (as I don't have any OTHER old PC's that aren't being used. I really don't understand why they can't just look at the hardware that the license was activated on (e.g., 12700k, z690 MSI, etc....verify you are the owner of the license, then just de-activate the license and provide a new one in instances like this. The "service" I received from Microsoft has ensure that I'll never buy a license direct again.

My own fix for the last time this happened was to just buy a new license for about 3 quid on another website.....even if this eventually gets de-activated, it'll be cheaper to do this 30 times over than to buy direct from Microsoft, and at least it actually works.

Having said all this, it would seem that this is not an issue that "MSI need to fix", as it's not a problem exclusive to MSI boards. If you search online, you'll find cases like this from all motherboard manufacturers. The fact that disabling the tpm before updating the bios could prevent the error (this info was too late for me) suggests that this is just a symptom of modern security doing it's job....so not even a fault as such, just extremely annoying for the consumer.

If you ask me, if anyone needs to "fix" anything.....it's Microsoft. It's their software that is having the activation issue, and they are the ones providing the licenses. Unfortunately, they don't seem to care to address the problem.....which is bad for everyone, including them, as they now lose out from people like me who will never buy another license from them again. If they can't prevent the issue from occurring, then they should seriously consider changing how these cases are dealt with. In my case, they could clearly see that I'd purchased the license, so it should have been no issue at all for them to either re-activate windows, or deactivate that license completely and supply a new one.

Only other thing I'd add, is on the point of "you should use the product key provided with the license"....I bought my license direct from the Microsoft website. They never sent me any code or key. At all. It is all handled directly in windows. You go through the windows settings to buy the license, it re-directs you to the website and upon completing payment, takes you back to the windows settings where you can see that it's now activated. Only email I ever received was an order receipt. I've never been given and literal code. So while this advice might work for a license bought in a physical store, where you get a code on a piece of card in a box, it will not work for anyone that's paid directly in windows.

Great post.

I wasn't aware this was happening with other MB manufacturers. In any case, it's really unacceptable.

 

[verickson153502d0]

Ya I did a search on the problem and it goes on for quite a few several years at least back to 2015
Bios update kills win 10 install key

I updated the BIOS many times on ASUS and Gigabyte motherboards since 2015 without this happening.

EDIT: I might add I have never had a BIOS update destroy my RAID arrays until I installed this motherboard. A quick Google search confirmed that other people have had this problem. Fortunately, there's a free third-party app that detects the messed up partition structure and repairs it.

 

[BrotherBelial]

Yet I've replaced the motherboard three times and updated the BIOS many times with one retail copy of Windows 11, and I've never had this problem before.

I think it is an MSI problem.

I've had this problem, with Gigabyte motherboards in the past so it most defiantly a Microsoft problem. But I've only had this problem with Windows 10 and 11. All Windows OS before 10 and 11 would let me upgrade my BIOS with no issues. But back then my PC's were quite basic. Having 2 HDD at most, not the multi drives I have now.

 

[verickson153502d0]

I've had this problem, with Gigabyte motherboards in the past so it most defiantly a Microsoft problem. But I've only had this problem with Windows 10 and 11. All Windows OS before 10 and 11 would let me upgrade my BIOS with no issues. But back then my PC's were quite basic. Having 2 HDD at most, not the multi drives I have now.

OK, I accept that this isn't unique to MSI.

I confess I'm a little impatient with being told "this is just what happens when you update the BIOS". I've always stayed up to date with the BIOS on every motherboard I've used, and never once had this problem before. That includes machines using TPM.

 

[BrotherBelial]

OK, I accept that this isn't unique to MSI.

I confess I'm a little impatient with being told "this is just what happens when you update the BIOS". I've always stayed up to date with the BIOS on every motherboard I've used, and never once had this problem before. That includes machines using TPM.

The problem is, no matter how well you test things, giving how different PC's can configured(which is why they are awesome) software is never 100% compatible for everyone. Over the years I've read people having problems with drivers for Nvidia cards, windows updates, even parts to working together that shouldn't be an issue. I'm lucky that I've never had issued with drivers and Windows updates. But just because I've never had a problem, doesn't mean there are not issues for other people.

 

[plutomate]

I confess I'm a little impatient with being told "this is just what happens when you update the BIOS". I've always stayed up to date with the BIOS on every motherboard I've used, and never once had this problem before. That includes machines using TPM.

This is the best answer that the community can give it to you. A quick google search would tell you the problem occurs on every manufacturer's board and clearly it's not a "MSI" issue.
I personally would stay away from doing the BIOS update on regular basis or seek Microsoft for help.

Redirecting

The workaround works for many people so the question is have you tried it?

 

[pogoet154602d9]

This is the best answer that the community can give it to you. A quick google search would tell you the problem occurs on every manufacturer's board and clearly it's not a "MSI" issue.
I personally would stay away from doing the BIOS update on regular basis or seek Microsoft for help.

Redirecting

The workaround works for many people so the question is have you tried it?

Could not find that pesky squirrel but I did get the link!

 

[Tyreman]

Have updated bios 3 times on my board, Pro Z690 but never an issue so don't know what's about here.
The MS licence id is digitally registered with MS.\
Maybe I am just lucky

 

[verickson153502d0]

This is the best answer that the community can give it to you. A quick google search would tell you the problem occurs on every manufacturer's board and clearly it's not a "MSI" issue.
I personally would stay away from doing the BIOS update on regular basis or seek Microsoft for help.

Redirecting

The workaround works for many people so the question is have you tried it?

I have, up until about a month ago when I installed the MSI board, been updating my BIOS regularly on an ASUS board (and a number of boards before that), this has never happened to me before. As for seeking help from Microsoft, well, you haven't read my posts. I'll come back to that below.

It is simply not true that this happens on every manufacturer's board simply from changing the BIOS, unless it is only on Z790 boards or something else specific. I'm prepared to accept that this sometimes happens on other manufacturer's boards, but to suggest that de-activation is something that you can just expect if you update your BIOS is misinformation.

When you refer to a work-around, are you talking about the link in your post? There is no work-around there. It suggests a diagnostic tool that I wasn't familiar with - thanks for that - but the solution offered was "Contact Microsoft Technical Support". I spent at least six hours on phone calls and screen chats with 13 different Microsoft people and they were no help at all.

Also, the video you linked to (which is the one at the top of this thread) is not a solution to the problem. It may represent a way to prevent the problem, which would be nice. But it doesn't allow you activate once the problem occurs, and yes, I've tried it (if that's what you're referring to). But no one seems really sure if it really does prevent the problem. Is there anyone out there who has tried what it suggests in this video and no longer lost activation after updating the BIOS? I'd really like to know, because there is a new BIOS version out for my board (MAG Z790 Ace).

I am not trying to be unpleasant. But it is very unhelpful to offer misinformation when people are faced with a real problem.

 

[verickson153502d0]

Have updated bios 3 times on my board, Pro Z690 but never an issue so don't know what's about here.
The MS licence id is digitally registered with MS.\
Maybe I am just lucky

We really shouldn't have to consider it lucky when hardware / software works as it is designed to. It's great to hear that at least someone isn't having this issue.

I guess this proves that getting de-activated after updating the BIOS isn't just something we should expect as a matter of course!

 

[Tyreman]

I just did the most recent bios no issue at all
why is there issues I wouldn't know
Are the keys being used bought off keys sites? the keys do work but when an update is used they are determined was for unsold oem stuff
the keys taken off those units, some sites sell these keys
the original key is found to be non acceptable for a number of reasons
other changes who knows

 

[verickson153502d0]

I just did the most recent bios no issue at all
why is there issues I wouldn't know
Are the keys being used bought off keys sites? the keys do work but when an update is used they are determined was for unsold oem stuff
the keys taken off those units, some sites sell these keys
the original key is found to be non acceptable for a number of reasons
other changes who knows

I was certainly using a license bought from Microsoft, which has kept its activation through multiple motherboard changes and at least a dozen BIOS updates on different boards.

I can't speak for anyone else.

 

[glenntidbur156f02e4]

I just did the most recent bios no issue at all
why is there issues I wouldn't know
Are the keys being used bought off keys sites? the keys do work but when an update is used they are determined was for unsold oem stuff
the keys taken off those units, some sites sell these keys
the original key is found to be non acceptable for a number of reasons
other changes who knows

It happened to me with a license bought direct from within windows. So this is not the reason. In fact, the cheap keys you mention have worked better for me than the £100 license I bought direct from Microsoft.

 

[Tyreman]

was the licence digitally registered? that is done separately by the user?
when I did that it was separate step to take
Most dont do that extra step you receive a confirmation of that unless its changed
What version are you running there are a few.........
was the computer ever compromised and the key obtained?
Those cheaper keys eventually run their course

 

[glenntidbur156f02e4]

I feel like we're all just repeating the same information at this point and going round in circles.

I bought a license direct from within windows. Direct from Microsoft. I paid the full price of over £100. It's a genuine license. Windows still got deactivated and Microsoft could do absolutely nothing to reactivate it. They ended up transferring an old license from one of my unused PCs.... this then got deactivated on the next bios update. I then bought a cheap key for 3 quid online and, touch wood, this survived the most recent update.... if it doesn't survive the next, I could still buy another 30 of these licenses and still save money compared to the full price from Microsoft..... again, bearing in mind that even with an email receipt, and with the license listed on my Microsoft account purchase history....Microsoft could do NOTHING to reactivate it.

I'm not gonna keep arguing and going over the same points again and again.... but my experience has now taught me that this issue is categorically NOT caused by having a "fake", "stolen" or otherwise invalid license.... and Microsoft being totally unable to do anything with that 100 quid license I paid for has taught me never to buy from them again.

Solution seems to be doing this thing of disabling tpm before the update.... but this doesn't help anyone who has already been deactivated.... so for anyone in that situation (as I was) I would suggest buying a cheap key online, the cheapest you can find, and then using the disable tpm method going forward.

Maybe it's time to lock the thread? A solution to prevent it has been provided, and other than that we're all just going in circles repeating the same info and asking the same questions?

 

[verickson153502d0]

I feel like we're all just repeating the same information at this point and going round in circles.

I bought a license direct from within windows. Direct from Microsoft. I paid the full price of over £100. It's a genuine license. Windows still got deactivated and Microsoft could do absolutely nothing to reactivate it. They ended up transferring an old license from one of my unused PCs.... this then got deactivated on the next bios update. I then bought a cheap key for 3 quid online and, touch wood, this survived the most recent update.... if it doesn't survive the next, I could still buy another 30 of these licenses and still save money compared to the full price from Microsoft..... again, bearing in mind that even with an email receipt, and with the license listed on my Microsoft account purchase history....Microsoft could do NOTHING to reactivate it.

I'm not gonna keep arguing and going over the same points again and again.... but my experience has now taught me that this issue is categorically NOT caused by having a "fake", "stolen" or otherwise invalid license.... and Microsoft being totally unable to do anything with that 100 quid license I paid for has taught me never to buy from them again.

Solution seems to be doing this thing of disabling tpm before the update.... but this doesn't help anyone who has already been deactivated.... so for anyone in that situation (as I was) I would suggest buying a cheap key online, the cheapest you can find, and then using the disable tpm method going forward.

Maybe it's time to lock the thread? A solution to prevent it has been provided, and other than that we're all just going in circles repeating the same info and asking the same questions?

This.

Despite evidence to the contrary, people keep ignoring the facts presented and coming back to denial of the issue.

 

[doug.hogart153b02d9]

... we're all just going in circles repeating the same info and asking the same questions?

There are variations in details which can be too subtle to deal with in a user-to-user forum thread. We aren't MSI nor a BIOS vendor like AMI, so we can't say whether there is something they could do during BIOS flashing to make it more like Intel NUC which doesn't seem to deactivate after flashing BIOS, and whether such happenings are more common now due to something like TPM and/or Secure Boot (but we can point out that similar situations seem to have occurred on non-MSI motherboards). We aren't Microsoft, so we can't improve the ambiguity of the name "Microsoft Store" which offers two ways to purchase Windows license - the web site which gets you a Product Key (probably emailed) similar to Product Key you'd get when purchasing from some well known retailers (having such Product Key seems to be helpful during activation) - or the "App" which sells a "Digital License" without a key (which must be tied to a Microsoft Account). Nor can we do anything about if Microsoft chat or phone support does a poor job helping a user "transfer" such purchased digital license after the automated options don't work (the options where you are signed into the same Microsoft Account and say "I changed hardware" then list the previous machine name that you need to "transfer" the license from).

Experienced users can try to provide guidance about those subtle variations, such as trying to understand whether you bought from someplace which provided a Product Key, whether you have lost track of original Product Key (can't do much about that), whether you have a Digital License under your Microsoft Account and are trying the Activation steps which are supposed to eventually bring up a list of previous machine names (explaining that user is not alone in experiencing that BIOS flash is causing Microsoft to think you have a new machine and that you have to "transfer" your license rather than more simply re-activate), or whether you have reached the final step of Microsoft chat/phone support (can't control but might help point out things mentioned above such as using original Product Key when you have it rather than "generic" product key which might now be on the PC, or to clarify with support that the help you need might be with what Microsoft calls "transfer" instead of re-activation). Again, it is hard to cover all variations but one is whether your original Windows install was an earlier version which has gone through upgrades (key that might now be generic) or whether you entered an original Product Key recently enough that it has not yet become "generic." Another is whether your current install is "Local Account" (without being tied to "Microsoft Account"), or even if that was the situation before some later upgrade. Today we probably assume people are describing experiences with PCs in UEFI mode that had "clean" install of Windows 11 or 10, but it isn't much of a stretch for experienced users to realize that history can include non-UEFI installs and installs that have been brought forward from older PCs and/or older Windows 7 or 8.x. As with any user-to-user forum, it is always possible you'll see people make assumptions, perhaps getting it wrong attempting to simplify details without knowing lots of variations. I can say that my re-activations after BIOS flashing seem automatic for my situation of having entered a Product Key not too long ago during a clean install and having it tied to my single Microsoft account, but I realize that is just one particular variation so I don't dismiss other experiences.

Advise after-the-fact seems like it can still be useful to me. For someone like me with many licenses across many PCs, I learned the importance of keeping my original Product Keys and tracking exactly where I have used them. If someone is about to resort to purchasing a license, they may want to know that there seem to be difficulties with such purchase in the "App" rather than Microsoft's web store (or some other well-known retailer) which provides a Product Key, etc. We aren't pretending that somehow solves problem once it already occurs, but there may be other people reading who appreciate learning from such experience. Some user may have discovered/shared some useful hint such as toggling fTPM helping avoid the PIN reset, and maybe someday another user will share some similarly useful discovery like subtle detail of secure boot keys or whatever is causing the BIOS flash to be seen by Microsoft as a hardware change. Some of us may not be comfortable suggesting that ultra-cheap license keys might be an easy way out, while others may point that out as potential money/time saver/"solution."

 

[plutomate]

It may represent a way to prevent the problem, which would be nice. But it doesn't allow you activate once the problem occurs, and yes, I've tried it (if that's what you're referring to).

That's exactly my point. No one is denying there's a problem with losing windows activation key after BIOS update, and it seems to do with TPM mechanism that once you update BIOS, windows thinks it's a different machine so it disables the license. However, I've searched this problem on the internet and realize the problem is not exclusive to MSI. Hence, my conclusion would be using the workaround from the video. It's hard to say wut the problem is, I don't see everyone using MSI board is complaining about this, otherwise the thread would be much much longer tbh.
You probably know more than I do, but either you reach MSI, microsoft, AMI, switch to ASUS board etc, I don't know, people here are trying to help you resolve the problem in user-level.

 

[BrotherBelial]

I was certainly using a license bought from Microsoft, which has kept its activation through multiple motherboard changes and at least a dozen BIOS updates on different boards.

I can't speak for anyone else.

I think that is the answer right there. Sounds like because we've been using the same "key" and upgrading Windows and not buying a fresh OS, it could be tied to that. I've used the same "activation key" across 4 builds.

 

[pogoet154602d9]

We really shouldn't have to consider it lucky when hardware / software works as it is designed to. It's great to hear that at least someone isn't having this issue.

I guess this proves that getting de-activated after updating the BIOS isn't just something we should expect as a matter of course!

Great answer! It is also that squirrel's fault in the link. He is running loose in the systems.