you could do license reset if you are owner of such licenses... But if you are in Europe, Thailand not there... License connected to your account, domain or policies... And vendor brand... If you have your license connected to your ms account or domain, something could happen like not valid certs keys in MS root certs on main/master/ slave office domain... Still issue in 2025... maybe certs valid make them suprispe shock... And bonus key donations on specialized servers got thei ban.
If version does not match and your key is for different product or version, harrassment there... Some products belongs to family of versions and their support era, version mismatch could vary on install or thereafter... MS is specific on its products, OEM is not same as PE options... and something long in bet-haloweeen, could be anything... like OEM product id missing from UEFI... or its invalidation... If making image(PE or not), then finalize image is also problem.
it could be some libs upgrade problem, check your winget list, maybe some SDKs and windows or app runtimes missing, redist packs switch and ... its editions and versions required...
winget search "Microsoft.Windows"; winget search "Microsoft.DotNet.SDK" winget ms repos
winget view Microsoft.SaRACmd , winget list could show some problems or there could be various office components from multiple office installs and their activation garbage. Office components could be upgraded, but that is not so friendly and could couse some trouble, active departments inclusion..., environments there