product ID ends in AA4360 (I don't know if this is useful or not, so only giving the last bit in case it is sensitive info.) The volume license I used from MSFT website is there and you can read the last 'octect' of data and it is correct.
"we can't activate windows because we can't connect to your organization's server." The product ID does say windows 10 pro. Now on the windows activation applet, i see this: Minecraft: Windows 10 Edition is already a step above the Java version of Minecraft when it comes to the burden on your PC. no KMS server present" more words in it, but that's the gist. So, everything is the same, except when I run the /ato command now, i get the message "error 0xc004f074, kms could not be contacted. I have done that now and am getting different errors. I believe I was forgetting to add the /ipk VLK to the mix. Using the principles above, we are confident that devices running on Intel 8th generation processors and AMD Zen 2 as.
It has the fundamentals of >1GHz, 2-core processors, 4GB memory, and 64GB of storage, aligning with our minimum system requirements for Office and Microsoft Teams. and then I'm able to ascertain what I don't know and look into those bits. Windows 11 is designed to be compatible with the apps you use. So usually what happens is that I start to create an issue and then fill in all of the questions I currently have. This is when I noticed the command would spit out the non-core edition message.
So I modded the bios with HP SLIC and when I tried to install the HP certificate (using slmgr). The error seems like something I would get while trying to activate the wrong version. However, between then and now Windows started to report 'not activated'. Has something changed? Did I miss a step? Is there a way to double check which version of windows I installed? I always install pro, but maybe I clicked the wrong one this time. when i run slmgr /xpr, it says "windows professional edition: windows is in notification mode." I downloaded the ISO directly from microsoft using the media creation tool. When I run slui.exe 0x803f7001, it doesn't appear to do anything. When i run slmgr /ato, it sends a pop window that says "error 0x803f7001 on a computer running Microsoft Windows non-core edition, run slui.exe 0x803f7001 to display the error text." According to this thread its either a time/region error or a volume media. When I set slmgr/skms to point to my server, i get a positive message saying that it was pointed properly. Error: 0xC004F069 On a computer running Microsoft Windows non-core edition 6. When I point my new win10 vm to vlmcsd running in a container on my server, I'm getting an odd error.Ĭ:\Windows\system32>ver Microsoft Windows