Unable to choose which version of windows 10 to install

[francescotissera1211]

When installing windows 10 via the: "quickget windows 10" command the Pro edition of the guest OS gets installed. If the user wanted to select the Home version, that is not possible at the moment. It would be beneficial to users to be able to choose which version of Windows 10 to install either via the quickget command or another method baked into quickemu.

[TuxVinyards]

The only difference between Pro and Home is the ability to install HyperV which is for Microsoft virtual machines.

In other words, if you don't install HyperV, then Home is the same as Pro ....

[francescotissera1211]

That is what I thought as well, except for a single, very strange fact: When I install a certain program, called Edico (a math editor and viewer for blind people) on a pro VM, it errors out. When I install it on a VM or physical device with Windows 10 home, it works just fine.

On Thu, Jan 4, 2024 at 1:34 PM Alex Genovese @.***> wrote:

The only difference between Pro and Home is the ability to install HyperV which is for Microsoft virtual machines.

In other words, if you don't install HyperV, then Home is the same as Pro ....

— Reply to this email directly, view it on GitHub https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1877026673, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAPVILXCOO6XCIV4DOLYM2OVRAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGAZDMNRXGM . You are receiving this because you authored the thread.Message ID: @.***>

[lj3954]

I do not think this is a feature worth adding, since almost no one needs a home edition of windows over a pro one and it would likely significantly hurt UX (especially alongside Windows languages, which I'm proposing to add back in PR 886). However, you can replace the generic KMS Windows Pro key with a home one manually in the unattended setup before running the VM. Here's a command that should do the job when run from the directory quickget was run in.

sed -i 's/W269N-WFGWX-YVC9B-4J6C9-T83GX/TX9XD-98N7V-6WMQ6-BX7FG-H8Q99/g' windows-10/unattended/autounattend.xml

[francescotissera1211]

I am afraid that didn't work, it still installed Win 10 Pro and errored out.

On Fri, Jan 5, 2024 at 8:28 AM Liam @.***> wrote:

I do not think this is a feature worth adding, since almost no one needs a home edition of windows over a pro one and it would likely significantly hurt UX (especially alongside Windows languages, which I'm proposing to add back in PR 886). However, you can replace the generic KMS Windows Pro key with a home one manually in the unattended setup before running the VM. Here's a command that should do the job when run from the directory quickget was run in.

sed -i 's/W269N-WFGWX-YVC9B-4J6C9-T83GX/TX9XD-98N7V-6WMQ6-BX7FG-H8Q99/g' windows-10/unattended/autounattend.xml

— Reply to this email directly, view it on GitHub https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1878244756, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLANBNKOLYPEIDQPJ6BDYM6TTTAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGI2DINZVGY . You are receiving this because you authored the thread.Message ID: @.***>

[TuxVinyards]

My recollection is that Microsoft only distribute the Pro version out to developers. The Pro can be set to Enterprise but not to Home.

Looks you are going to have check the dependency lists very carefully, or take things up with Edico.

[lj3954]

My recollection is that Microsoft only distribute the Pro version out to developers. The Pro can be set to Enterprise but not to Home.

Looks you are going to have check the dependency lists very carefully, or take things up with Edico.

Quickget downloads the consumer release of Windows directly from Microsoft. There is no "developer version" it has access to. It's completely possible to install the home edition, but the automated installation doesn't do that by default.

[francescotissera1211]

I didn't find a way to install the home edition in the main documentation on the github page. Could you please tell me how to try and do so? Thanks.

On Sat, Jan 13, 2024 at 4:43 AM Liam @.***> wrote:

My recollection is that Microsoft only distribute the Pro version out to developers. The Pro can be set to Enterprise but not to Home.

Looks you are going to have check the dependency lists very carefully, or take things up with Edico.

Quickget downloads the consumer release of Windows directly from Microsoft. There is no "developer version" it has access to. It's completely possible to install the home edition, but the automated installation doesn't do that by default.

— Reply to this email directly, view it on GitHub https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1890287502, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAO7ENS62BW6XIFFEUTYOH7HFAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI4DONJQGI . You are receiving this because you authored the thread.Message ID: @.***>

[TuxVinyards]

Perhaps @lj3954 had a recent look. But that is how it was last time I checked over the Microsoft pages, a year or so ago.

Quickemu had a revamp of the Windows downloader a month or so ago too. And it took a lot of time before that one happened.

I think the key point here is that if someone releases a piece of software for Windows then it should run on both the Home and the Pro versions. If not, it's the software, not the Windows version.

I don't think @lj3954 and I should even be spending time talking about this. Or even trying to fix it. We should both be working on other things.

I am still looking forward to a better MacOS experience with Quickemu although I'm still not sure if we are ready to go with that one yet. There have been so many changes to the new MacOS PR of late ....

[francescotissera1211]

I understand, thanks for all your clarifications, I'll take it up with the edico devs themselves. What do you mean about having a better experience with MacOS? I haven't' had any time or reason to try it yet. I wonder if Voiceover, the screen reader, would work as expected.

On Sat, Jan 13, 2024 at 9:04 AM Alex Genovese @.***> wrote:

Perhaps @lj3954 https://github.com/lj3954 had a recent look. But that is how it was last time I checked over the Microsoft pages, a year or so ago.

Quickemu had a revamp of the Windows downloader a month or so ago too. And it took a lot of time before that one happened.

I think the key point here is that if someone releases a piece of software for Windows then it should run on both the Home and the Pro versions. If not, it's the software, not the Windows version.

I don't think @lj3954 https://github.com/lj3954 and I should even be spending time taking about this. Or even trying to fix it. We should both be working on the things.

I am still looking forward to a better MacOS experience with Quickemu although I'm still not sure if we are ready to go with that one yet. There have been so many changes to the new MacOS PR of late ....

— Reply to this email directly, view it on GitHub https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1890371748, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAJOH55LMGJUKJVKO3TYOI5XXAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGM3TCNZUHA . You are receiving this because you authored the thread.Message ID: @.***>

[lj3954]

I understand, thanks for all your clarifications, I'll take it up with the edico devs themselves. What do you mean about having a better experience with MacOS? I haven't' had any time or reason to try it yet. I wonder if Voiceover, the screen reader, would work as expected. … On Sat, Jan 13, 2024 at 9:04 AM Alex Genovese @.> wrote: Perhaps @lj3954 https://github.com/lj3954 had a recent look. But that is how it was last time I checked over the Microsoft pages, a year or so ago. Quickemu had a revamp of the Windows downloader a month or so ago too. And it took a lot of time before that one happened. I think the key point here is that if someone releases a piece of software for Windows then it should run on both the Home and the Pro versions. If not, it's the software, not the Windows version. I don't think @lj3954 https://github.com/lj3954 and I should even be spending time taking about this. Or even trying to fix it. We should both be working on the things. I am still looking forward to a better MacOS experience with Quickemu although I'm still not sure if we are ready to go with that one yet. There have been so many changes to the new MacOS PR of late .... — Reply to this email directly, view it on GitHub <#896 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAJOH55LMGJUKJVKO3TYOI5XXAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGM3TCNZUHA . You are receiving this because you authored the thread.Message ID: @.>

The experience in actual macOS VMs won't be any better. Aside from macOS Sonoma being added, I don't remember changing anything in quickemu. It's just quickget, where my PR adds downloading using wget/aria2, rather than via the external macrecovery tool. macOS versions newer than Catalina (I believe) don't perform particularly well in VMs and I don't think it's a good idea to use them for anything other than testing certain software.

[lj3954]

I didn't find a way to install the home edition in the main documentation on the github page. Could you please tell me how to try and do so? Thanks. … On Sat, Jan 13, 2024 at 4:43 AM Liam @.> wrote: My recollection is that Microsoft only distribute the Pro version out to developers. The Pro can be set to Enterprise but not to Home. Looks you are going to have check the dependency lists very carefully, or take things up with Edico. Quickget downloads the consumer release of Windows directly from Microsoft. There is no "developer version" it has access to. It's completely possible to install the home edition, but the automated installation doesn't do that by default. — Reply to this email directly, view it on GitHub <#896 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAO7ENS62BW6XIFFEUTYOH7HFAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI4DONJQGI . You are receiving this because you authored the thread.Message ID: @.>

After running quickget (and before launching the VM), run this in order to modify the unattended ISO to use a Windows home key instead. Just changing the key in the XML file like I recommended previously won't work, since the unattended setup is contained within an ISO file (which is an archive).

rm windows-10/unattended.iso && sed -i 's/W269N-WFGWX-YVC9B-4J6C9-T83GX/TX9XD-98N7V-6WMQ6-BX7FG-H8Q99/g' windows-10/unattended/autounattend.xml && mkisofs -quiet -l -o windows-10/unattended.iso windows-10/unattended/

[francescotissera1211]

Thanks! Will the same command work for Win 11 if I change all the 10 to 11? Just wanna make sure.

On Sat, Jan 13, 2024 at 7:43 PM Liam @.***> wrote:

I didn't find a way to install the home edition in the main documentation on the github page. Could you please tell me how to try and do so? Thanks. … <#m5970880261111790021> On Sat, Jan 13, 2024 at 4:43 AM Liam @.> wrote: My recollection is that Microsoft only distribute the Pro version out to developers. The Pro can be set to Enterprise but not to Home. Looks you are going to have check the dependency lists very carefully, or take things up with Edico. Quickget downloads the consumer release of Windows directly from Microsoft. There is no "developer version" it has access to. It's completely possible to install the home edition, but the automated installation doesn't do that by default. — Reply to this email directly, view it on GitHub <#896 (comment) https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1890287502>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAO7ENS62BW6XIFFEUTYOH7HFAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI4DONJQGI https://github.com/notifications/unsubscribe-auth/BBEFLAO7ENS62BW6XIFFEUTYOH7HFAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI4DONJQGI . You are receiving this because you authored the thread.Message ID: @.>

After running quickget (and before launching the VM), run this in order to modify the unattended ISO to use a Windows home key instead. Just changing the key in the XML file like I recommended previously won't work, since the unattended setup is contained within an ISO file (which is an archive).

rm windows-10/unattended.iso && sed -i 's/W269N-WFGWX-YVC9B-4J6C9-T83GX/TX9XD-98N7V-6WMQ6-BX7FG-H8Q99/g' windows-10/unattended/autounattend.xml && mkisofs -quiet -l -o windows-10/unattended.iso windows-10/unattended/

— Reply to this email directly, view it on GitHub https://github.com/quickemu-project/quickemu/issues/896#issuecomment-1890690752, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBEFLAN27D6MLWPIJEPGQ3DYOLITZAVCNFSM6AAAAABBJGZVR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGY4TANZVGI . You are receiving this because you authored the thread.Message ID: @.***>

[lj3954]

Yes, it definitely should.