Install Windows 10 Virtual Machine in VirtualBox  

Hopefully, that's all it was and will be successful.

Brink,

Now that I have done things properly I have discovered that the correct procedure works. And I have yet again written out a hundred times, "I must pay attention to detaiil.".

I have posted these notes just in case anybody else wonders about the subject of
- the use of combined 64 bit & 32 bit Windows ISO files in VMs
- mixing 64 bit / 32 bit VMs with 64 bit / 32 bit OSes

I successfully used VirtualBox to create & run
- 32 bit VM into which a 32 bit OS was installed from a combined 64 bit & 32 bit Windows ISO file
- 64 bit VM into which a 32 bit OS was installed from a combined 64 bit & 32 bit Windows ISO file
{I ran out of time without trying a 64 bit VM into which a 64 bit OS was installed from a combined 64 bit & 32 bit Windows ISO file but, given the results obtained already, I no longer worry that it would be any problem at all.}

The common tests for identifying 32 bit / 64 bit hardware / OSes gave these results:

In the 32 bit VM & 32 bit OS,
- echo %PROCESSOR_ARCHITECTURE% responded x86
- the SystemInfo response, Processor(s) entry contained [01] x86 Family ...
- the Registry key HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0 - Identifier entry contained x86 Family ...
- the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment - PROCESSOR_ARCHITECTURE entry contained x86
- the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment - PROCESSOR_IDENTIFIER entry contained x86 Family ...

In the 64 bit VM & 32 bit OS,
- echo %PROCESSOR_ARCHITECTURE% responded x86
- the SystemInfo response, Processor(s) entry contained [01] x64 Family ...
- the Registry key HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0 - Identifier entry contained x86 Family ...
- the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment - PROCESSOR_ARCHITECTURE entry contained x86
- the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment - PROCESSOR_IDENTIFIER entry contained x86

So, as others had told me before, these tests are indeed tests of the installed OS and not of the machine itself except for the SystemInfo response which revealed the Type [32/64 bit] of the underlying VM.

I also looked around out of curiosity for a property that would reveal the true nature of the processor [64 bit] whichever OS I had installed but was unable to find one.
- I do suspect that, on real machines rather than in VMs, the SystemInfo response - Processor(s) entry might reveal the true Type [32/64] of the Processor rather than that of the OS
- If anybody else has tested for this already I would be interested in knowing the answer.

Denis

Hello Shawn so if I run a VM on my older Ivy Bridge will I be able to try to install Windows 11 even though I have no TPM and the 3rd Gen intel CPU.

If it doesn't work just how do you get rid of the VM??

ICIT2LOL said:

Hello Shawn so if I run a VM on my older Ivy Bridge will I be able to try to install Windows 11 even though I have no TPM and the 3rd Gen intel CPU.

If it doesn't work just how do you get rid of the VM??

Hello John,

If you enable secure boot and TPM for the VM, it may allow you to install W11. I haven't tested on VirtualBox though. I've always used Hyper-V.

You can delete the VM and it's folder to remove it.

Hello Shawn well mate I think I will give it a miss because I cannot find a TPM plug in module for my board and the CPU is apparently not compatible even though others have said they have 11 up and running on their Ivy Bridge machines with no TPM and that particular CPU.


But thanks once again for your help as I can always rely on you for the best advice.

I think my best option is to carry on with 10 until it runs out of support and then buy another prebuilt machine with 11 installed as am a little too old to be able to do an upgrade besides the hideous cost of buying new components for the case I have. Shame because it is in my opinion the best case ever designed

Brink said:

Hello John,

If you enable secure boot and TPM for the VM, it may allow you to install W11. I haven't tested on VirtualBox though. I've always used Hyper-V.

You can delete the VM and it's folder to remove it.

It certainly works for HyperV as I have done it.

Ok Shawn and cerebus I think I shall have to have a play around with the VM stuff until I get the hang of it. The main problem is I cannot access a TPM module for the board I have.