You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made sure the question is not listed in the FAQ.
Is this a general question and not a technical issue?
I am sure my question is not about a technical issue.
Question
The documentation of the project does not specify whether it is possible to activate Windows. I would like to ask if it is the expected behavior or if is a technical issue.
I have tried Windows 10 and 11 and in both cases the product key is refused by Windows. The product key was rejected (0xc004f050) both in case when using the option to "Change product key" while running on Windows with finished setup and in the case when I try to submit the key in manual installation mode. The used product key is the one contained in BIOS of the device on which I am running compose from this repository, and it does work when used in VM (GNOME Boxes).
EDIT: I should add that I have also tried Windows 11 installation image from Microsoft instead of the tiny version. However, this ends up with black screen instead of the installer, even if MANUAL: "Y".
EDIT 2: Think I made an error my not connecting the product code with MS account. I will try to fix it by first installing to a VM, connecting to MS account, then deactivating and finally activating here while reported new hardware to MS.
The text was updated successfully, but these errors were encountered:
My attempt at solving the issue was unsuccessful. I was able to install Windows 11 Home and activate it in Virtmanager QEMU/KVM VM (even though my product key was from Windows 10 Pro). Then I proceeded to log into Windows with Microsoft account. Upon shutting down the VM, I started the docker compose from this project setting VERSION to tiny11 and choosing custom iso. Then I was able to install and log in. Then I tried the activation option "my hardware changed" and the windows reports, that the Virtmanager VM has Windows license incompatible with the current (Docker) Windows installation, even though both were installed from the same Windows 11 Home iso. There has to be some setting being applied which assumes Windows 11 Pro.
I will give it another try, I will try to upgrade the Windows in the Virtmanager VM to Pro by reminding Windows that I have a key for Windows 10 Pro and then I will the tiny11 directly.
Is your question not already answered in the FAQ?
Is this a general question and not a technical issue?
Question
The documentation of the project does not specify whether it is possible to activate Windows. I would like to ask if it is the expected behavior or if is a technical issue.
I have tried Windows 10 and 11 and in both cases the product key is refused by Windows. The product key was rejected (
0xc004f050
) both in case when using the option to "Change product key" while running on Windows with finished setup and in the case when I try to submit the key in manual installation mode. The used product key is the one contained in BIOS of the device on which I am running compose from this repository, and it does work when used in VM (GNOME Boxes).EDIT: I should add that I have also tried Windows 11 installation image from Microsoft instead of the tiny version. However, this ends up with black screen instead of the installer, even if MANUAL: "Y".
EDIT 2: Think I made an error my not connecting the product code with MS account. I will try to fix it by first installing to a VM, connecting to MS account, then deactivating and finally activating here while reported new hardware to MS.
The text was updated successfully, but these errors were encountered: