windows 11 24h2

[winxpto10]

is it possible to run windows 11 24h2 in latest virtualbox?

[multiOS]

Yes

[winxpto10]

Yes

You said yes but I can't install Windows 11 24h2, after i power on, it just hangs
My PC specs:
Dell optiplex 5080 mini tower
AMD Radeon RX 640 graphics card
i7 10700
1 TB nvme SSD
Virtualization enabled in Firmware

[winxpto10]

bump still waiting for reply

[granada29]

bump still waiting for reply

No-one will be able to help until you post a log (zipped) of the failed session.

The Forum Posting Guide
Minimum information needed for assistance.

[winxpto10]

bump still waiting for reply

No-one will be able to help until you post a log (zipped) of the failed session.

The Forum Posting Guide
Minimum information needed for assistance.

How do I create the log and create zip file??

[granada29]

1. Open VirtualBox Manager
2. Run your VM from a cold start (i.e. not saved state)
3. Shutdown your VM, cleanly if possible. Use Power Off as a last resort.
4. Right click the VM name in VirtualBox Manager
5. Choose the "Show in FileManager" or whatever is appropriate for your host OS (I have no idea what you are running so cannot be specific)
6. Open the Logs folder
7. Compress VBox.log to a zip file. You may need to set your file manager to show all extensions. The files with the .1, .2 etc suffixes are not required - VBox.log is the log of your most recent session. The process for creating a zip file is dependent on your host OS. Google is your friend.
8. Use the Attachments tab to attach the compressed log file to a new post in this topic.

[winxpto10]

1. Open VirtualBox Manager
2. Run your VM from a cold start (i.e. not saved state)
3. Shutdown your VM, cleanly if possible. Use Power Off as a last resort.
4. Right click the VM name in VirtualBox Manager
5. Choose the "Show in FileManager" or whatever is appropriate for your host OS (I have no idea what you are running so cannot be specific)
6. Open the Logs folder
7. Compress VBox.log to a zip file. You may need to set your file manager to show all extensions. The files with the .1, .2 etc suffixes are not required - VBox.log is the log of your most recent session. The process for creating a zip file is dependent on your host OS. Google is your friend.
8. Use the Attachments tab to attach the compressed log file to a new post in this topic.

[granada29]

There are known problems with VirtualBox 7.0.16 on Windows. It's probably a good idea to back-off to VirtualBox 7.0.14. See the warning at https://www.virtualbox.org/wiki/Downloads

You can download VirtualBox 7.0.14 and its matching Extension Pack from https://www.virtualbox.org/wiki/Download_Old_Builds_7_0

Code: Select all

00:00:03.806419   NumCPUs           <integer> = 0x0000000000000008 (8)
00:00:04.929564 CPUM: Logical host processors: 16 present, 16 max, 16 online, online mask: 000000000000ffff
00:00:04.929565 CPUM: Physical host cores: 8

Also - probably not causing your immediate problems, but in your VM configuration you have assigned 8 CPUs - i.e. all your host physical CPUs - hyperthreaded processors don't count. It would be a good idea to reduce this to 4, or even 2 while you are getting the VM to work. You can always increase the CPU count later, but using all the physical processors in your VM is not a good idea.

[winxpto10]

i uninstalled 7.0.16, restarted pc, i installed 7.0.14 but still hangs. I want to fresh clean install Windows 11 24H2 insider preview

[granada29]

Your configuration looks OK to me but now I am out of my depth. Hopefully someone more knowledgable with windows than I am will be able to help from here.

I did note the following entry in your log but have no idea of the cause.

Code: Select all

00:00:09.210321 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0x7fffffff0000 P2=0xff P3=0x0 P4=0xfffff807ebe7a476

[multiOS]

I also don't see any particular problem with the basic configuration of the VM; and the only thing that stands out to me is:

00:00:03.716749 Path <string> = "D:\Windows11_InsiderPreview_Client_x64_en-us_26080.iso" (cb=55)

i.e the 24H2 'Beta Version'

Was the problem VM a 'clean installation', i.e. a completely new VM, carried out using the Windows Insider ISO; and was it successfully activated during installation or, was it a conversion of an existing Windows 11 VM after enrolling the device in the Windows Insider program? I only ask those questions because I know that Microsoft pays much closer attention these days to device enrolment in the Windows Insider program(s) and will only accept (enrol) devices that both pass the minimum Windows 11 spec.; and are running, or have a previously installed a licensed version of Windows 10/11, and so already have an embedded electronic license. AFAIK it is not possible to run an official Widows 11 Insider installation on a device that doesn't carry an embedded electronic activation, or a have retail license (physical activation code), but only Microsoft can provide a definitive answer.

There is a possibility that, as the VirtualBox Development Team does not chase compatibility with evolving 'BETA' Operating Systems, there can be issues with newer Windows Insider Builds.

Assuming that you don't have an already activated and working Windows 11 VM, the only test I can suggest is to use a Windows 23H2 ISO to install the mainstream version of Windows 11, apply all required updates and verify that the VM works correctly, or let us know if you hit the same (or any different) issue. - Assuming the base installation does work, and after verifying Windows activation, take a full backup of the working VM. You should then be able to enrol the device in the appropriate strand of the Windows Insider Program and test the Insider update process. The working VM backup should ensure you have an easy route back to a working installation should you still experience problems.

[nineASCII]

I found a solution that works for me.
I tried everything I could think of, I spent hours trying to figure it out.
I noticed that Windows 11 24H2 did work in VMWare but would hang in VirtualBox.
Only 24H2 was not working. Everything else does.

The Solution:
In VirtualBox go to your Windows 11 24H2 virtual Machine

»» Settings
»» System
»» Change the chipset to ICH9
»» Click OK

now run the virtual machine.
It worked for me.

[FST]

I found a solution that works for me.
»» Settings
»» System
»» Change the chipset to ICH9
»» Click OK
It worked for me.

Unfortunately, your solution does not work for me.
Here is my contribution in the German section

viewtopic.php?p=547778#p547778

[winxpto10]

nope. Still not working