How to Install macOS Big Sur on VirtualBox on Windows – PC

How to Install macOS Big Sur on VirtualBox on Windows – PC

Apple has announced the next major release of macOS at WWDC 2020. Available today in developer beta and coming to all users in fall 2020. macOS Big Sur will be a free software update later this year. In the meantime, the developer beta is available on and for public beta in July.

This OS has new features that include an all-new iOS inspired design, Control Center arriving for Mac, a revamped Safari with greater privacy controls, Apple’s new translation software that uses on-device processing, and more.

Macs compatible with macOS Big Sur (macOS 11):

  • 2015 and later MacBook
  • 2013 and later MacBook Air
  • Late 2013 and later MacBook Pro
  • 2014 and later iMac
  • 2017 and later iMac Pro
  • 2014 and later Mac mini
  • 2013 and later Mac Pro

And Accordingly, the following models capable of running macOS Catalina will not be able to be upgraded to macOS Big Sur:

  • 2012 and Early 2013 MacBook Pro
  • 2012 MacBook Air
  • 2012 and 2013 iMac
  • 2012 Mac mini

Tip: before reading the rest of the article, it’s recommended to navigate to the Required File section of this post and download macOS Big Sur then you’ve time to read the item until the downloading gets complete.

Steps to Install macOS Big Sur on VirtualBox on Windows

  • Install VirtualBox on Windows PC
  • Install/Update VirtualBox Extension
  • Create a New Virtual Machine & Customize it
  • Run VirtualBox Code to the Command Prompt
  • Start the Virtual Machine
  • Perform Clean Installation of macOS Big Sur
  • Summary

Important Note:

Before we get started, make sure your system can support Virtualization Technology (VT), and it is enabled from BIOS so that you should be able to run Virtualization software like Virtualbox or VMware. Also, you should have a 64-bit Windows operating system with at least 2 GB Ram and 20 GB of free storage, however, we recommend you at least 4 GB of RAM or higher so you can store more files and install more apps on macOS Big Sur.

Furthermore, if you have an SSD, it’s highly recommended to use it as storage because SSD is much faster then mechanical hard drive (HDD ) and macOS run on SSD very smooth. Anyway, it is not 100% compulsory but if you have, don’t hesitate to use it.

Required Files

Note: You can create macOS Big Sur ISO Image.

Recommendation: It’s highly recommended to create a new drive on your Windows PC and install macOS Big Sur on that drive.

Step 1: Install VirtualBox on Windows PC

From the “Required File” section of this post, you should have downloaded VirtualBox as well and if you didn’t, download VirtualBox’s latest version and install it on your Windows system. If you’ve already installed VirtualBox, then you can skip this step. Other than that, double click on VirtualBox Setup and click Next for a couple of times and you’re done with the installation.

This slideshow requires JavaScript.

Step 2: Install or Update VirtualBox Extension

This step is not 100% percent necessary but it’s highly recommended to do this step because macOS Big Sur might not be compatible with VirtualBox and for this reason, it will cause a problem during the installation. Download VirtualBox Extension and follow the steps below.

#1. Open up VirtualBox, navigate to Tools>Pereferences>Extensions.3

#2. Click on Plus icon and select VirtualBox extension which you’ve downloaded at the beginning of this section. Click Install or Upgrade and then click OK button.

#3. Finally, you should see something like the screenshot below.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Update Virtualbox Extension

Step 3: Create a New Virtual Machine & Customize it

Creating a virtual machine for macOS Big Sur is the same when you create a virtual machine for the Windows Operating system or Linux. We will use the ISO image of macOS Big Sur to do the installation process.

Note: We’ll make the VMDK as well if we receive lots of requests for that. Otherwise, there is no point because you can install macOS Big Sur with iso image as well.

#1. Open up your VirtualBox application and click New.

#2. Type a name for your Virtual Machine. Click Expert Mode and choose the following options then click Create.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Expert Mode

  • Name the VM
  • Virtual Machine Location (a separate drive is recommended)
  • Type (Mac OS X)
  • Version (Mac OS X 64-bit)
  • Memory 4 GB (recommended 8 GB or higher)
  • Create a virtual hard disk 
Your setting should look something like the screenshot below.
How to Install macOS Big Sur on VirtualBox on Windows - PC

Create New Virtual Machine

#3. Select where you want to save your virtual hard disk. Also, make sure to increase the size of the disk. From virtual hard disk, type make sure to select VHD. If you select dynamic allocated, your VM speed will not be good but it’s good that does not allocate the specified storage at once, unlike fixed-size type.
How to Install macOS Big Sur on VirtualBox on Windows - PC

Create Virtual Hard Disk

#3. It’s time to customize some of the settings according to your choice. Click Settings and from the pane choose System. On the Motherboard, tab uncheck Floppy disk and move it down. If you’re not happy with your memory setting still, you can change it.
#4. Click the Processor tab and select a minimum of two processors or higher.
How to Install macOS Big Sur on VirtualBox on Windows - PC

Increase the Processor

#5. Navigate to the Display menu then increase the Video memory to 128 MB.
How to Install macOS Big Sur on VirtualBox on Windows - PC

Increase Video Memory

It’s time to select your macOS Big Sur ISO file. Click Storage and then select on Empty. Click on DVD icon and choose your macOS Big Sur ISO file.
How to Install macOS Big Sur on VirtualBox on Windows - PC

Select ISO Image

Make sure your macOS Big Sur ISO file is on the top, not your Disk because if your disk is on the top, your VM might not boot. Just change the SATA port number to 0 for your iso image. It’s not 100% compulsory.
How to Install macOS Big Sur on VirtualBox on Windows - PC

ISO Image SATA 0

Step 4: Run VirtualBox Code to the Command Prompt

Once you’ve created and customized your virtual machine, it’s time to run some codes in order to install macOS Big Sur on VirtualBox.

First, you should notice your virtual machine name because later on, we will use it. Open the VirtualBox code which you should have downloaded from the Required File section of this post.

#1. When you opened VirtualBox code via notepad or any other text editor, use the replace function of the program to replace the VM Name to your virtual machine name. See the picture below to get an idea of how it’s done.

cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe modifyvm "VM Name" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "VM Name" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
VBoxManage setextradata "VM Name" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "VM Name" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95"
VBoxManage setextradata "VM Name" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "VM Name" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

Replace VM Name

Tip: It’s highly important that you should quit the VirtualBox program before executing the code. If you don’t do it, your virtual machine might not proceed to the installation step.

Exit VirtualBox

#2. Once you replaced the “VM Name” with your virtual machine name, then run the code one by one to the command prompt (CMD). You can open the command prompt by pressing Windows+X key in Windows 10 or click windows key and type CMD and run command prompt as administrator.

This slideshow requires JavaScript.

Step 5: Start the Virtual Machine

Starting macOS Big Sur with the older version of the Mac Operating system was a bit different, but with new macOS Big Sur still, it’s easy to set it up.

#1. Open the VirtualBox app then click the Start button. A black screen with a few yellow & white text will appear on the screen.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Start Virtual Machine

#2. Once you started the VM then you’ll see some code running in the background. Just wait until you see the Apple logo.

This slideshow requires JavaScript.

#3. Select a Language and click Continue arrow.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Select Language

#4. Select Disk Utility and click Continue.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Select Disk Utility

#5. Select your main Virtual Disk and click the Erase button. Make sure to check the size of the disk and you should not erase the wrong disk.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Erase Virtual Disk

#6. Name your Disk that you want to install macOS Big Sur on it. I’ll name here macOS HD. Once typed a name then click the Erase button.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Name the Virtual Disk

#7. Close Disk utility.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Close Disk Utility

#8. Select Install macOS and click Continue.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Install macOS

#9. Click Continue.

How to Install macOS Big Sur on VirtualBox on Windows - PC

macOS Big Sur Beta

#10. Agree to terms and Conditions.

How to Install macOS Big Sur on VirtualBox on Windows - PC

Agree to the Terms & Conditions

#11. Select the installation disk and click Continue. Once you click continue it’ll take around 29 minutes to complete the first part of the installation.

NOTE: If you get the Operation Couldn’t be Completed BiErrorDomain Error 3 then follow this step by step guide below.

Fix the Operation Couldn’t be Completed BiErrorDomain Error 3

This is a very common error with macOS Big Sur beta version 1 that most people have faced.  Just use our VirtualBox code and it should work without any error.

How to Install macOS Big Sur on VirtualBox on Windows – PC

Installation Disk

Step 6: Perform Clean Installation of macOS Big Sur

  1. Once you hit enter, a whole bunch of code will run on the screen, but you should not worry about it. Wait for a few minutes, and you should see the macOS Big Sur installation window. Have a cup of coffee until the installation complete because it’s going to take around 29 minutes to finish.
  2. Once the installation part complete, your system will reboot, and after the restart, you should see macOS Big Sur Welcome page.
  3. Select the following options. You can change most of the settings later on, so don’t worry about that for now.
    1. Select your Country and click Continue.
    2. Choose a Keyboard Layout and click Continue. If you don’t agree with preset options then you customize it. Just click Customize Settings.
    3. You can turn on the Accessibility features now with macOS Big Sur. You’ve several options with accessibility like vision, motor, hearing, and cognitive. If you don’t want to set up right now just click Not Now button to skip them.
    4. Read Data & Privacy and click Continue.
    5. Now, you can transfer your data from your previous Mac or from your Windows PC. If you don’t want to transfer anything right now, just click the Not Now button to continue.
    6. Click on Set Up Later then Don’t Sign In. You can add your Apple ID later.
    7. Click Agree to the Terms and Conditions and click Continue.
    8. Fill out the Full name,  Account name, Password, and Hint then click Continue.
    9. If you want to customize Express Set Up, you can click on Customize Settings otherwise click on Continue.
    10. On the Analytics page click Continue.
    11. On-Screen Time, click Set up Later.
    12. Select an appearance theme and click Continue. Here you choose your dark mode if you want.
    13. Wait for a few seconds and you’ll see the login screen now.
  4. Well done 👍👌😮 you’ve installed macOS Big Sur on VirtualBox Successfully.
How to Install macOS Big Sur on VirtualBox on Windows – PC

Welcome to macOS Big Sur VBox

Click on the image below to see the full resolution

This slideshow requires JavaScript.


Basically, in this article, I’ve shown you the step by step pictorial guide on how to install macOS Big Sur on VirtualBox on Windows computer. After reading and following this guide, you should have done the following;

  • Downloaded VirtualBox with its Extension
  • Installed VirtualBox on your system
  • Installed & upgraded VirtualBox extension
  • Created a new virtual machine for macOS Big Sur
  • Customized macOS Big Sur VM
  • Executed the VirtualBox code to the CMD
  • And finally performed a clean installation of macOS Big Sur.

Related: How to install macOS Big Sur on VMware on Windows.

We are ready to keep receiving your feedback about this article, and other posts on wikigain. Your suggestion and feedback are highly appreciated.

Warning: All the content of this site is copyright protected, and no-one has the right to copy-paste our materials.


Mukhtar Jafari is the founder and CEO of He is CISCO CCENT & CCNA Certified and has got his diploma in IT Networking from North Metro TAFE PERTH. He is currently working as a Help Desk Technician at DEEPTECH Perth Western Australia. In addition, he loves helping other tech enthusiasts so he is working part-time on He shares his experience through this website for IT beginners.


  1. blankVasil Ts. Reply

    Just few tips for those, who still can not make it work:
    My setup:
    CPU: AMD Ryzen Threadripper 3970X , 32Gb RAM, VGA: RX5600XT
    VirtualBox configuration ( version: 6.1.26 ):
    — General: —
    Operating System: “Mac OS X (64-bit)”
    Base Memory: 8192MB
    Processors: 4
    Boot Order: Optical, Hard Disk
    Chipset Type: ICH9
    EFI: Enabled
    Acceleration: VT-x/AMD-V, PAE/NX
    — Display: —
    Video Memory: 128 MB
    Graphics Controller: VboxVGA
    Acceleration: 3D
    — Storage: —
    Controller: SATA
    Port 1: Optical Drive macOS Big Sur 11.0.1 ( 20B29 ).iso ( 16.00 GB )
    Port 2: MacOSBigSir.vhd ( Normal, 120Gb)
    — Everything else is default…
    ——– Virtual Box Code: ——
    cd “C:Program FilesOracleVirtualBox”
    VBoxManage.exe modifyvm “MacOSBigSir” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal/Devices/efi/0/Config/DmiSystemSerial” “CK1156I6DB6”
    VBoxManage setextradata “MacOSBigSir” “VBoxInternal2/EfiGraphicsResolution” “1920×1080”
    VBoxManage modifyvm “MacOSBigSir” -–cpu-profile “Intel Core i7-6700K”
    bcdedit.exe /set hypervisorlaunchtype off

    Installation tips:
    Disk: format as: Mac OS Extended ( Journaled ) / AFPS will not work

    This configuration works for me, good luck.

    1. blankSteve Reply

      Hey Vasil. Do these steps work with a Ryzen 5600x? I can’t seem to be able to install bigsur on Virtualbox, got it working somewhat yesterday in VMWare but its very slow, hoping it will be faster in VB

  2. blankScott Reply

    Thank you. I’ve worked on this too many times in the last 3 weeks. This was the only step-by-step instructions that actually worked.

  3. blankHum Reply

    I got the answer of Forcing cs_runtime for entitlement: stuck. Just wait for a long time.I solved this for 4.5 hours

  4. blankHum Reply

    I got the answer of Forcing cs_runtime for entitlement: stuck
    Just wait for a long time.
    I solved this for 4.5 hours

  5. blankAutistic Moshi Reply

    Well I Ran The codes through the windows command prompt (ADMIN MODE) and when i run the codes 1 by 1 through the command prompt i think something is wrong because when i started the VM it rebooted and did a kernal panic I Saw this message in the codes that i knew it was a kernal panic


    Isnt there a way to fix this

    1. blankFy Reply

      I had the same problem too. Left it like that for about 4 hours and finally sprang to life. It seriously tests your patience. For checking whether the installation is going well, go to libraries and click on my computer. you will see that the space in C drive will gradually decrease this indicates that your the installation is still in process.
      Just wait.

  6. blankshannon Reply

    I’ve had the sane problem for months no fix I can see, i installed it under VM Player 16 it works but cant connect to apple store etc

  7. blankMenna Helmy Reply

    First of all, thank you so much for this it’s really detailed and helpful
    after I ran VBox code, and started the virtual machine, This error appeared :
    VT-x is not available (VERR_VMX_NO_VMX).
    Can you please help?

  8. blankxberg Reply

    Thank you for this excellent guide!
    I have however the following problems:

    – SLOW: Big Sur runs incredibly slowly. 20 minutes to boot and 30-60 seconds to open Safari for instance. The installation itself took several hours.
    I dedicated 16GB of memory (my windows 10 host has 64gb). My system is a dual CPU Xeon E5 32-core machine.
    Reading Jordan’s recommendation above I checked and hyper-V is disabled on my machine. DeviceGuard and Core Isolation Details (Windows Defender) were also turned off.

    – Unable to use more than 2 cores. I tried defining 4 or 8 cores and the system will not boot. It will only boot when I define 2 cores.

    Running Virtualbox 6.1.20 on windows

  9. blankKyle Reply

    Whenever i try to install macOS Big Sur in the virtual machine i keep on getting the message “Installation cannot proceed because the installer is damaged. Re-download the installer and try again.” Any tips on how to fix this?

  10. blankSid Reply

    I did everything instructed. I have an ASUS x570-F motherboard with an AMD Ryzen 7 3700x processor and an NVIDIA RTX 2070 GPU. I get this error after the Big Sur installation is complete. Instead of getting a welcome page, it gets stuck here: PLEEEEASE HELPPP

  11. blankEduardo Reply

    After installing I get stuck on less than a minute remaing…can´t pass this step…I´ve waited more then 2 hours and nothing

    1. blankFlagging Dragons Reply

      From what I’ve heard, that step alone can take over 3 hours on some machines. It’s painful, but you’ll just have to wait it out.

    2. blankTudor Trifan Reply

      Try to install on the other hard drive, i had the same issue and I solved by installing VM at external SSD with more then 200Gb free space. Was successfully installed in around hour and a half. After installation works fine.

    1. blankHenry Reply

      I get this screen too and haven’t been able to get any further with installing macos on virtual box.

      1. blankalex

        anyone come up with a solve for this? i followed everything exactly and have no idea what the fuck this screen even is

    2. blankH3llR4iser Reply

      That drove me insane for hours. Turns out it’s VirtualBox being an idiot.

      Type “Exit” at that prompt, you’ll end up in the VM “BIOS”.
      Select the Boot Manager -> UEFI VBOX CDROM

      Now it should start properly. I have zero idea why the issue happens, btw.

  12. blankmike Reply

    it worked the first time i created a vm but then i had problems and needed to delete the vm and start again and now it will not work i do al the same steps but it just doesnt work the same any ideas

  13. blankJacob Reply

    Thanks for the manual, everything was installed and working. I also managed to change the screen resolution to the one I needed.
    The only thing is that the system is working very slowly, although I allocated 10GB of RAM and SSD of physical memory to it. Can you tell me how you can solve this problem.

    1. blankMick Baugh Reply

      Note: You should replace your “macos” with your own virtual Machine
      Code for Virtualbox 6.x:
      run all of these commands with VirtualBox app closed and as admin in windows 10

      cd “C:\Program Files\Oracle\VirtualBox\”
      VBoxManage.exe modifyvm “macos” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      VBoxManage setextradata “macos” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
      VBoxManage setextradata “macos” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
      VBoxManage setextradata “macos” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
      VBoxManage setextradata “macos” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “macos” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

      C:\Windows\System32\bcdedit.exe /set hypervisorlaunchtype off

      VBoxManage modifyvm “macos” -–cpu-profile “Intel Core i7-6700K”

  14. blankYM Reply

    I can no longer boot on a Ryzen 5 3600. This used to work about 3 months ago, which is when I last booted macOS Catalina. I get the following print at the end:


    I did the commands mentioned in addition to VBoxManage modifyvm “macOS” –cpu-profile “Intel Core i7-2635QM”

    I’m thinking some Windows 10 updates messed things up.

  15. blankLitos Reply

    Not sure if this will help anyone …

    Im running a Ryzen 5 3600 and i had to use the following to get to apple logo:

    VBoxManage modifyvm “VM_NAME_HERE” –cpu-profile “Intel Core i7-2635QM”

  16. blankRanj Reply

    Cant get to work in Ryzen:
    Ryzen 5 3500
    Virtualbox: 6.1.16 with extensions

    The initial boot exits with (Error image:
    [EB.LD.OFS|OPEN!] Err (0xE)
    Code Ran:
    VBoxManage.exe modifyvm “mac” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    VBoxManage setextradata “mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
    VBoxManage setextradata “mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
    VBoxManage setextradata “mac” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
    VBoxManage setextradata “mac” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata “mac” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1
    VBoxManage setextradata “mac” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-F22589C8”
    VBoxManage setextradata “mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemSerial” “CK1156I6DB6”
    VBoxManage modifyvm “mac” –cpu-profile “Intel Core i7-6700K”
    VBoxManage setextradata “mac” “VBoxInternal2/EfiGraphicsResolution” “1600×900”
    VBoxManage modifyvm “mac” –paravirtprovider default

    1. blankYoNevelt Reply

      On Windows you have to run this command and the rest should be fine in your additional config.

      C:\Windows\System32\bcdedit.exe /set hypervisorlaunchtype off

  17. blankHelp Reply

    Hello! I tried installing the OS in Virtualbox, but after the code that I had to input in the CMD, it just showed me the following:

    UEFI Interactive Shell v2.2
    EDK II
    UEFI v2.70 (EDK II, 0X00010000)
    Mapping Table
    FSO: Alias (s) :F0b65535a : ; BLK1:
    and so on…
    At the end it says:
    Press ESC in 6 seconds to skip startup.nsh or any other key to continue. (None of these buttons do anything) and that is it, it is not booting, NOTHING! Can you help me? Thanks

  18. blanksamuele Reply

    Hi, when I try to access my iCloud account it makes me mistake .. so I ask, within virtualization: is it possible to enter my Icloud account so as to use the services and synchronize my Apple data, as if I had an original Mac? For example the use of apps such as Photos, Notes, Mail, Calendar..ect.

    Also, despite a PC with i7-6700 2.60GHz with 16RAM and still 50GB free, using BigSur turned out to be very slow up to having simple mouse pointer delay, what could it be?

  19. blankLyubomir Kaludov Reply

    So I have been trying to install this for 5 days now with no success. I am trying to do in on a Dell XPS 9560 (i7-7700HQ, GTX 1050 4GB, 16GB RAM, 512GB NVMe SSD). Could it be because my VirtualBox is set to run with the nVidia GPU instead of the integrated one (Did that as a fix to the Ubuntu VM visual stuttering problem)?

    For additional info: I am trying to install with the latest BigSur from the link at the top of the post.

  20. blankmian muzammal Reply

    can anyone help me . when i was boot up from iso the mouse pointer stucks and do not moves please help me,

  21. blankMike Wheeler Reply

    Hello, Is there any way that I can make the sound work? My guest Mac is showing no output devices available and I don’t know how to solve this. Please help me with this if anyone knows the way out. Also, thanks a lot for giving such information, Big Sur worked for me : )

  22. blankNikola Mitrin Reply

    Hello! I tried installing the OS in Virtualbox, but after the code that I had to input in the CMD, it just showed me the following:

    UEFI Interactive Shell v2.2
    EDK II
    UEFI v2.70 (EDK II, 0X00010000)
    Mapping Table
    FSO: Alias (s) :F0b65535a : ; BLK1:
    and so on…
    At the end it says:
    Press ESC in 6 seconds to skip startup.nsh or any other key to continue. (None of these buttons do anything) and that is it, it is not booting, NOTHING! Can you help me? Thanks

  23. blankpch Reply

    I did everything you explained. But, when I started booting VM, it was stuck at #[EBILOG:EXITBS:START] (current date). What should I do?

  24. blankalpine Reply

    For those of you getting the error “LOG:EXITBS:START”, you need to be using the latest version of VirtualBox with the extensions. If you’re using Virtualbox <6.1, it wont launch.

    1. blankSleepybear Reply

      I have latest VirtualBox (6.1.16 r140961) and got the Extensions install today, so also newest. I did the –cpu-profile “Intel Core i7-6700K” as well, and still cannot get it to boot on my AMD Ryzen 5 3600XT PC.

  25. blanknanohaxor Reply

    Hi Mukhtar,

    Thanks for the nicely constructed instructions. Awesome work mate!

    For you and anyone else interested in trying this procedure with Linux/Ubuntu, here’s what I did, and after a bit of stuffing around, found a process that works, as follows.

    I used your exact process with Big Sur as a VirtualBox Client, but instead, used Ubuntu 20.4 LTS as the VirtualBox Host.

    I created the Big Sur VM client on an external USB3.0 drive.

    I also stored the Big Sur macOS ISO file on the same external USB3.0 drive in a separate folder.

    I named my Big Sur VM image: macOS Big Sur-20201217

    I followed your procedure quite closely except used the following linux commands in an ubuntu Terminal window:

    $ cd /bin

    $ VBoxManage modifyvm “macOS Big Sur-20201217” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff

    $ VBoxManage setextradata “VM Name” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1″^C

    $ VBoxManage setextradata “macOS Big Sur-20201217” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”

    $ VBoxManage setextradata “macOS Big Sur-20201217” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”

    $ VBoxManage setextradata “macOS Big Sur-20201217” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”

    $ VBoxManage setextradata “macOS Big Sur-20201217” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”

    $ VBoxManage setextradata “macOS Big Sur-20201217” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

    Then I created a snapshot of the VM using VirtualBox so that I can revert back to this snapshot if needed.

    Then I performed the disk erase process you explained, and named the virtual disk which was 128GB in size as: macOS HDD

    I also used a ‘MacOS Extended (Journaled) with case-sensitivity’ option for the erase process, and used the scheme: GUID Partition Map. Now, I’m not sure if selecting the case-sensitive alternative will be an issue down the track, but it’s a VM so I can always revert to a snapshot and try it again without case-sensitivity later if there are problems with this for the OS.

    Then when I installed the OS, the installer just hung after about 60 seconds. Well damn, that’s linux. Upon inspecting the error logs these said something about an (… isCSFusionDrive:] failed to get LVG for diskls3) and (… invalid LVGUID) and would not proceed with the install. I googled the error and could not find anything specifically useful on this error message to resolve the hang.

    So, I then erased the virtual disk again with the exactly the same process above, but then used the same disk management tool to perform a partition of the virtual disk volume. So what this means is that I split the original 128GB volume into 2 equal volumes of 64GB each. I named the second volume partition: macOS HDD2

    Now I effectively have 2 hard disks of 64GB each: macOS HDD, and, macOS HDD2.

    Then I exited the erase tool and ran the ‘Install macOS’ process as you described, then selected the 64GB disk volume named ‘macOS HDD’, continue, and you bloody ripper, it proceeded with the install just fine, but took about 45 minutes to complete. My external drive is an older spinning disk, not an SSD, so it’s very slow, but it means I can watch/read the Apple scripts used to install macOS which is super interesting.

    I’ve no idea why this split volume technique solved the logical volume GUID issue I hit originally, but this split volume process worked.

    I figure that I can go back and resize the macOS HDD volume back to 128GB later and blow away the macOS HDD2 volume in the process.

    I hope this helps others trying to do the same with Linux/Ubuntu as a host and installing on an external USB3.0 disk.



  26. blankMartin Reply

    Hi that all did the Job in some Way – Its now working :-).

    VBoxManage.exe modifyvm “Mac2” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-F22589C8”
    VBoxManage setextradata “Mac2” “VBoxInternal/Devices/efi/0/Config/DmiSystemSerial” “CK1156I6DB6”
    VBoxManage modifyvm “your VM name” –cpu-profile “Intel Core i7-6700K”
    VBoxManage setextradata “mac2” “VBoxInternal2/EfiGraphicsResolution” “3840×2160”

    VBoxManage modifyvm “Mac2” –paravirtprovider none
    after back to
    VBoxManage modifyvm “Mac2” –paravirtprovider default

  27. blankVB Reply

    Everything is OK. Big Sur was installed successfully following your instructions. But there is a problem with the audio. It is not enabled. I have ALC622, could you give me a solution pls ?

  28. blankSteve Reply

    How to get passed “ICLOUD_UNSUPPORTED_DEVICE”??

    Thanks. Following these instructions worked perfectly for me. However, previous MacOS installs on Virtualbox have always allowed me to log in to the Apple store. It’s the primary purpose for me to have MacOS on VM. Is there any way to get past the “ICLOUD_UNSUPPORTED_DEVICE” error when attempting to login into the Apple store? This error was also reported in a couple of other comments. This error will constantly block access to Apple Store and has been accessible via previous MacOS versions installed via Virtualbox. I realize the VM is not authentic Mac OS and/or Mac OS hardware. But this has worked in the past. I am only looking for a solution.

  29. blankLyner Reply

    Hello, I’m having an issue, and I’m not sure if I should just keep waiting or if there’s something wrong. I followed the guide to the letter, and also did that extra CPU ID code to get where I am. I tried adding the screen fixed resolution code and that didn’t do anything. Currently, I have 2 cores assigned to the VM as I have 4 cores in total, and 4 GB of RAM as I have 11.2 GB usable. My CPU is AMD A10-5750M APU with Radeon(tm) HD Graphics.

    Here’s the link to my VM:

    Despite it not seeming to be doing anything, the VM’s currently using 27-38% of my CPU, but I’ve waited almost 20 minutes now for it to do anything, as I write this it’s still in the background doing.. nothing.

    Any help would be much appreciated! Oh, I’m also trying to install Big Sur 11.0.1

  30. blankPhil Higdon Reply

    I have a acre i5 8th gen 8 gb ram, i have followed this guide to the letter.
    Setup VM with 3076mb ram 128mb gpu 128gb vhd, everything goes well upto the point where it is installing macOS to the less then a min remaining and it just sites there (been trying for over an 1.5hrs to get this setup.

  31. blankXavian Reply

    Now I am stuck on 5.2, it’s running code but is like is rebooting, and reloads the code, however is not moving to the Apple logo screen. Help needed. Thanks!

  32. blankXavian Reply

    Hello, after I run the code and open back VirtualBox and hit start I get a UEFI Interactive Shell v2.2. How can I fix this? Thanks in advance.

    1. blankJohn Harrington Reply

      Same – it took a while to workout that was the problem.
      Anyone know a way of upping processors beyond two?

  33. blankDonald D Joyce Reply

    To change the resolution use the following command:
    VBoxManage setextradata “VM Name” VBoxInternal2/EfiGraphicsResolution RES

    Where RES = one of the following:

  34. blankUgur H Reply

    thank you so much! Everything works till the installation of macos Big Sur. after a couple of minutes installation fails with message “installation cannot proceed because the installer is damaged”. I already re-downloaded the ISO file without help.

  35. blankkks Reply

    For display settings use following code(say for 1600×900)
    vboxmanage setextradata “bigsur” “VBoxInternal2/EfiGraphicsResolution” “1600×900”

  36. blankMiki Dora Reply

    My own experience, using macOS Big Sur 11.0.1 (20B29).iso, on a Linux Mint machine, running 19.3 Mate, on an older Dell XPS with an intel i7 and 24gigs total memory.

    Basically, everything is the same as it is with Windows, and the instructions are sterling, all the way through. One difference with Linux is that you open a terminal instead of a command prompt, and with VirtualBox already installed, simply typing in “VBoxManage” followed by whatever instruction(s) might be at hand on the very same input line and then hitting the ‘Enter’ key, works in exactly the same way. So that’s easy enough to deal with.

    In the beginning, things went really fast, and that kind of mislead me, and later on, when things slowed waaaaay down, it caused me to make a couple of mistakes, so give it time, ok? Be patient with it.

    My first stumbling block occurred when it was time to erase the “installation disk” with the Disk Utility, and almost immediately VirtualBox threw an error and the process froze up. Not knowing what the fuck to do, I did the wrong thing.

    Of course.

    I tried to figure out the freeze-up, but could not, and said “The hell with it,” to myself, and WIPED IT CLEAN.

    Fresh start. From dead scratch, creating an new VM.

    When I got to the “erase” point once again, if promptly locked back up, once again, same place. Prior to that, I noticed that it defaulted to a Format of APFS file system, with a GUID Partition Map Scheme instead of Format as Mac OS Extended (Journaled), which is what’s showing in the screenshot above, in the instructions, and I decided to leave that alone, but it froze anyway, and I was right back where I started, and this time, putzing around with things, I just kind of happened to notice that the machine state, in the VirtualBox Manager, was showing as “Pause” so I clicked that button, and low and behold, it lit right up, and kept on stroking, from there, as if nothing had ever happened.

    For a looooong time. And there was a lot of stuff, but it all went well enough without any alterations from my obedient little self, so we’re not gonna talk about it. Except for additional lockups with a VirtualBox Manager showing “Pause” so if you get any of that crap, be sure and give that one a look, ok?

    And when it got to where the Apple logo showed up, but before a cursor arrow could appear against the blackness of the install background, and the little bar was creeping along, I noticed that the damn bar only made it about a quarter of the way across, where it steadfastly refused to move from, even as the timer kept counting down, to “less than a minute” and from there….. nothing. I let it sit for fifteen minutes or so, and foolishly decided it was frozen, and killed the Virtual Machine without saving the state.

    Started it back up, and as a reward for being stupid, I got to once again watch the bar, and the countdown timer, do the exact same thing again, but this time I left it strictly alone, over there on my second monitor, and busied myself with other pursuits, and after a pretty good while, it suddenly lurched back into life, and proceeded to throw lots of white gobbledygook across the black background, gave me another status bar (which thankfully did not last as long), went back to gobbledygood, and the goddamned thing TOOK FOREVER. During which forever it would occasionally “hang” for interminable lengths of time, but finally it kicked all the way through.

    And a few more “Pause” events along the way, but it never stopped the process.

    And now it’s working, and I could not be happier.

    Altering the screen resolution was another weird item too, though, and I had to do a LOT of playing around with that, and for some reason, it would refuse to take a given resolution, boot into the default low resolution, and this annoyed me greatly, until, for reasons I do not know myself, i decided to slide the damn thing from one monitor to another (they’re different sizes, different resolutions), and in the process of sliding across, the VM jerked into the proper resolution, and I’m gonna leave it right where it is, lest I fuck it up further, by trying too hard with it.

    Gonna let it rest. It’s earned it, right?

    Most of a day, spent.

    Every minute of which was worth it.

    Cannot thank you enough, Mukhtar. Your work is The Best, and it is greatly appreciated.

    Again, my utmost praise and thanks, Mukhtar.

    You’re a credit to the force.

    1. blankKryz M Reply

      haha, man, you’re good!
      and actually thanks to the length of your story now I appreciate my own thoughtfulness of taking the snapshot titled “less than a minute”.
      yeah, it took forever, but it goes somewhere this time.

    2. blankValerij Reply

      God bless you, man! I spent 2 hours deleting, creating a new VM due to the fact that it did not “hang” when erasing the disk at the beginning of the installation. but i read your answer and hit that fu ** ing pause!
      be happy!

  37. blankbianser Reply

    me too :! less than a minute fpr several hours of wait than … it is already alocated 28.5 GB so it is proably done intalling but even after several tries always stuck there. please help asap. thanks win10 hp pavilion laptop

  38. blankAlonso Guzman Reply

    It seems that it takes a long time to install the image, so could you upload the same file but in zip to unzip it?

      1. blankKavindu Rashmin

        me too please 🙂 it says the downloaded file is corrupted when installing. thanks a bunch Faiz.

  39. blankAlonso Guzman Reply

    the image of big sur or the iso file will download very slowly you could upload the same file worse in zip because it is too heavy and it takes hours to download it is more I have been trying to do it for a month and it does not work because there is a network error when it takes so long It would be cut in half if you gave us the zip file for us to unzip

  40. blankClaudiu Reply


    I have an AMD Ryzen 7 3700X and I have ran all the commands:

    cd “C:\Program Files\Oracle\VirtualBox\”
    VBoxManage.exe modifyvm “macOS Big Sur Beta” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    VBoxManage setextradata “macOS Big Sur Beta” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
    VBoxManage setextradata “macOS Big Sur Beta” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
    VBoxManage setextradata “macOS Big Sur Beta” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
    VBoxManage setextradata “macOS Big Sur Beta” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata “macOS Big Sur Beta” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1
    VBoxManage modifyvm “macOS Big Sur Beta” –cpu-profile “Intel Core i7-6700K”

    But it gets stuck at “LOG:EXITBS:START” + timestamp. Check screenshot

      1. blankYes

        I’m also getting the same issue, even though I already set cpu-profile with the two hyphens. I have an AMD Ryzen 5 2600. Any suggestions?

  41. blankJohn Leonard Reply

    THANK YO SO MUCH! I’ve been trying for the last 4 hours with multiple images with no sucess and changing the cpu profile resolved the issue!

  42. blankStephen Reply

    Can the download links be saved onto something like Mega instead of Mediafire? MF is garbage. Even on premium I’m still getting 100Kbps like it’s 2001.


  43. blankMichel O. Reply

    When I do this, it works until the final stage of installation. The screen shows the Apple logo and the loading bar, but it is stuck on “Less than a minute remaining”. I must be doing something wrong, but what?

      1. blankHenry Wertz

        Not a problem. Just be patient. As far as I can tell (based on gkrellm showing my actual disk activity), it counts down while *just* reading the installer (probably doing a checksum on it), then does the ENTIRE install claiming “less than a minute remaining.” I quit waiting for it after like 20-30 minutes, checked quite a while later and it was done.

  44. blankkJ Reply


    lie to the public


    1. blankFAM Reply

      No you are not
      If you are a “DEVELOPER 4 APPLE” why would you come to this site seeking for installation

  45. blankVishal Raj Reply

    VBoxManage: error: Could not find a registered machine named ‘“MacOS”’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 547 of file VBoxManageModifyVM.cpp

    I found this error while running the commands in command prompt

    VBoxManage.exe modifyvm ”MacOS Big Sur” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    VBoxManage setextradata ”MacOS Big Sur” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1″
    VBoxManage setextradata ”MacOS Big Sur” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
    VBoxManage setextradata ”MacOS Big Sur” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95″
    VBoxManage setextradata ”MacOS Big Sur” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata ”MacOS Big Sur” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

      1. blankRL

        I get basically the same error. it tells me
        “C:\Program Files\Oracle\VirtualBox>VBoxManage.exe modifyvm “macOS BigSur” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
        VBoxManage.exe: error: Could not find a registered machine named ‘macOS BigSur’
        VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
        VBoxManage.exe: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 524 of file VBoxManageModifyVM.cpp

        I have checked that my vm name is exactly the same as it is in the command. Do you have any idea what I’m doing wrong, or where it thinks the vm should be so I can check if its not putting in in the right spot?

    1. blankSantiagobbboff Reply

      It’s because you’re not really using a Mac… It’s a Windows, so it’s not in the list of supported devices. I don’t know if exists any solution for this but you can search for it.

      1. blankMiles Prower

        There is a solution.

        You need to assign a valid mac’s serial number to your virtual machine.

        VBoxManage setextradata “MacOS Big Sur” VBoxInternal/Devices/efi/0/Config/DmiSystemSerial ““

        I have a Core Duo mac mini that I no longer use, and instead assign that serial number to my VM.

    2. blankDave Sousa Reply

      If you use the mac App Store you can sign in there. You still cannot use iCloud but your VM will be logged into your account so you can use the app store ect.

  46. blankShawn Wright Reply

    Ok, so followed all directions, but when i try to login to my account, i get an error. “ICLOUD_UNSUPPORTED_DEVICE” Now, i have reinstalled multiple times, a couple different ways and i continue to get this error. Any help to fix would be appreciated

  47. blankHaroon Reply

    Thanks so much Mukhtar. Followed your steps and have Big Sur Beta 11 up and running. However, that 30 minute wait at “Forcing CS_RUNTIME for entitlement” is a killer. Any way to get around this issue?

  48. blankMD HOSSAIN Reply

    Every time I tried to download Mac Big Sur on virtualBox, I got stuck here. Either way to downloads straightly Big Sur on virtualbox or upgrading from Catalina. Please help.

    It says on the last line “ Forcing CS_RUNTIME for entitlement:

  49. blankBenjamin B Reply

    Hey thanks so much for this guide. I tried it on my Ryzen machine (3970x) but I’m getting stuck at the EXITBS:START error like a few people above…I tried the VBoxManage modifyvm “macOS Big Sur” –cpu-profile “Intel Core i7-6700K” command (and did it with virtualbox closed), but it still stops the install…any ideas how to fix? Mobo is a TRX40 Creator, tried this with Hyper-V both on and off, same results…

    Thanks for the help and the guides!

      1. blankPratishthit

        Hi, I’m running into the same problem on the latest release 11.0.1
        Below is the code I executed:

        cd “C:\Program Files\Oracle\VirtualBox\”
        VBoxManage.exe modifyvm “MacOS Big Sur 11.0.1” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
        VBoxManage setextradata “MacOS Big Sur 11.0.1” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “iMac19,1”
        VBoxManage setextradata “MacOS Big Sur 11.0.1” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”
        VBoxManage setextradata “MacOS Big Sur 11.0.1” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-AA95B1DDAB278B95”
        VBoxManage setextradata “MacOS Big Sur 11.0.1” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
        VBoxManage setextradata “MacOS Big Sur 11.0.1” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1
        VBoxManage modifyvm “MacOS Big Sur 11.0.1” –cpu-profile “Intel Core i7-6700K”

  50. blankGanapathy MB Reply

    How long would it take for the initial “#2. Once you started the VM then you’ll see some code running in the background.” to complete.

    Mine seems to keep running for more than 20 minutes.
    its stuck at
    [EB|#LOG:EXITBS:START] 2020-08-22T01:21:00

    1. blankFaiz Reply

      Definitely not more than 5 minutes on my system. If you are doing this on AMD CPU then: if you have an AMD CPU then Add this code to your VM:

      cd "C:\Program Files\Oracle\VirtualBox\"
      VBoxManage modifyvm "your VM name" --cpu-profile "Intel Core i7-6700K"
      1. blankMuhammad Suleman

        first i was stuck on [EB|#LOG:EXITBS:START] error but your suggestion help to move some further steps.
        i am still stuck at similar screen but last string is following

      2. blankKavindu Rashmin

        Thanks man the background code was frozen, I added this code because i have an AMD Ryzen 9 3900x. It worked 😉

      3. blankDaniel

        This should definitely show up in the initial How-To guide! I search way to long for this solution, just because I use an AMD cpu.

        Still thanks for the help!

      1. blankTudor Trifan

        I wait here 15 minutes, i changed ram to 4gb but i can use 5gb processor 2 cores but can use 4 and video memory to 128mb.

  51. blankKen Spreitzer Reply

    Thank you for this! I just used these instructions to install macOS 11.0 Big Sur (beta 4) on a VirtualBox 6.1.12 virtual machine (using my MacBook Pro as a host). Here’s what went wrong and how I fixed it:

    1. You can use any SATA port numbers for your devices, just make sure the .iso file/drive is first. I ended up with BigSur.iso (SATA Port 5), macOS-11-beta.vdi (SATA Port 10), and a DVD (SATA 20) which ultimately ended up having the VBoxGuestAdditions.iso. (After I was all done I used VirtualBox Settings/System to change the boot order to boot from the hard drive before the BigSur.iso.)

    2. The instructions are written for Windows, so you’ll need to run the VBoxManage utility (as shown in the “VirtualBox Code” section) from a different location. So instead of:

    cd “C:\Program Files\Oracle\VirtualBox”

    use this:

    cd /Applications/

    and remove the “.exe” from the first VBoxManage command. So the commands I used were like this:

    cd /Applications/
    VBoxManage modifyvm “macOS-11-beta” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff

    3. After starting the virtual machine, I hit a huge problem where it booted into the UEFI “shell” and just left me at a prompt saying “Shell>”. FYI, look at the first lines of this screen and you’ll probably see that “FS0:” is an “alias” to a CD-ROM drive. I found instructions online about typing “fs0:” and then “edit startup.nsh” but this failed with an “Access denied” message because it was trying to edit a file on FS0: (which is a read-only CD-ROM .iso). I also found instructions online about installing an “APFS EIF Boot Image.iso”. But I found an easier workaround. When you get to the UEFI “Shell>” prompt, just type “exit”. (Extra tip: type “help -b” to see available UEFI commands.) Typing “exit” will get you to a BIOS startup screen. Choose “Boot Manager” and it should provide a list of available devices. Choose each of them in order until you find one that works. As I recall, my first device was “EFI (something)” and choosing it didn’t do anything. My second device was a SATA device (as I recall), and it was mapped to the BigSur.iso install image that I was trying to install; choosing it worked!

    4. Once I managed to choose the correct boot device image as discussed above, it started to install. You’ll see a ton of text scroll by. Just let it work.

    5. The entire installation process will need to reboot a bunch of times (5?), even after you’ve done the main 29-minute installation part.

    6. At one point I thought the installation was frozen because it was stuck on a line that read:

    Forcing CS_RUNTIME for entitlement

    It seemed to be stuck on this FOREVER, but it finally continued after about 30-45 minutes.

    7. When doing the initial Apple ID and iCloud setup, it got the error “ICLOUD_UNSUPPORTED_DEVICE”. I gave up on signing into iCloud for the time being. (I’ll try to figure it out later.)

    8. The machine seemed to not recognize the host MacBook Pro’s keyboard. It had me press Z and / to determine that it was a US ASCII keyboard.

    9. I couldn’t get the VirtualBox Guest Additions to install. The installer package seemed to run OK but at the end it gave an error message. The largest effect of this is that VirtualBox can’t capture the keyboard, so when I press Command-Q (for example) it gets passed through to the host. Also, the trackpad doesn’t seem to scroll; I assume it’s the same problem due to the missing Guest Additions.

    10. Since I didn’t want to update my MacBook to the Big Sur beta, I removed the “profile” described near the start of this article. To do so, go into System Preferences / Software Update. On the left side, underneath the gear, you’ll see a message that your computer is enrolled in the beta seed program. Click the link to get a little window which will let you confirm that you want to remove that profile and revert to your existing (non-beta) config.

    BTW, I created a 100GB hard drive (in VirtualBox), and there were 87GB free after I finished installing Big Sur, so macOS 11 took about 13GB to install.

    I hope this helps someone!

      1. blankJamal Ziyan

        If you do not want to get stuck at loading or anything it is strongly recommended to download the VirtualBox extension pack on their website.

  52. blankArnold Schwarzie Reply

    Hi ! Thanks a lot for this pretty useful guide, which helped me to install Big Sur on VirtualBox on Windows 10 (rel 1909). I’m however facing two issues, whose resolution got me into some trouble and i’m seeking advice to get back to a workable situation.

    1) Belgian French Keyboard is not recognized by Big Sur, which made me provide all setup inputs with a wrong keyboard, but I somehow got through it I guess.
    – I’m using in the meantime a French keyboard layout but all keys don’t match, sadly :'(
    – I hoped that adding the Guest Additions (Darwin) could help, but when I tried to install the dpkg file it failed at the end and I’m not even sure it caused a trouble or not :-O
    – When looking into the System Info I checked for Updates of Big Sur and see there is one pending… which I’m downloading now — hopefully the belgian keyboard has been added ?

    2) The actual performance is really poor in my opinion. The mouse pointer is stuttering all the time when moved and starting an application takes several seconds (3-10). So I’ve looked into that and I’m doing the following:
    – upgraded VM RAM from 4 GB to 8 GB, but kept the 2 processors only (my i5-4690system has only 4, but they are actual cores, and my PC is otherwise very smooth in games, other VM’s and anything)
    – I admit I selected as disk (70GB) the VDI type instead of VHD and it is of dynamic type… my bad. Q1: Firstly, there seem no option or process to convert a dynamic to fixed length format, supposedly faster ? Any hint or tip here ? Secondly, when I used VBox’s media manager to copy the VDI to VHD format, MacOS would not boot anymore : the VM would immediately display a screen full of status info with hex code and status values all over the place a stop with a “Shell >” prompt. When typing Exit, I’m entering a boot manager setup displaying 4 entries, none of which are working when leaving the boot manager (I’m back to the Shell prompt each time). Any pointers to what might be the issue here ? I still have the VHD disk (though I have reconnected to the VDI now, which is pretty slow but works at least)

    Thanks in advance for your advice !

    PS: I’ve read you’re recommending VMware instead of VBox but I’d really like to push it to the maximum of tuning before adding one more virtualisation software and having to learn its specificities.

    1. blankArnold Schwarzie Reply

      I’ve tried to install it right away to a VHD of fixed size but it fails the same way : it cannot start after installation and I’m left with a Shell prompt without knowing what is wrong or what to do next.
      When ‘exiting’ I’m reverted to the Boot manager with much more clues…
      Please help ?
      PS: see attached screenshot

      1. blankArnold Schwarzie

        I used your file. Did even the download twice in case it got corrupted but did a file compare by content and it was ok.

  53. blankMonica Reply

    Thx for writing this article.
    I actually get a problem that I did successfully installed the macOS Big Sur into Virtual Box, but after I created the Account and trying to login, the screen turns black for a while and then skip back to the login menu again. Is there any idea about this problem?
    I’m pretty sure that I had followed every steps being mentioned in the article. Also I’m using the latest version VirtualBox and the iso file in this post.

  54. blankFrancesco Adamo Reply

    Hello, sorry I do not speak English I am Italian, the guide and excellent is working for me, the only flaw and that you do not hear the audio, solutions? Thank you
    (translated with google)

    1. blankFaiz Reply

      What is your system specs? if you have an AMD CPU then Add this code to your VM:

      cd "C:\Program Files\Oracle\VirtualBox\"
      VBoxManage modifyvm "your VM name" --cpu-profile "Intel Core i7-6700K"

      P.S It’s highly important that you should quit the VirtualBox program before executing the code.

      If no then try the Fix the Operation Couldn’t be Completed BiErrorDomain Error 3 article.

      If no success then I highly recommend you to Install macOS Big Sur on VMware on Windows 10 because it works much better than VirtualBox.

  55. blankZR Reply

    Hi, im having issues downloading the MacOS Big Sur beta ISO, when it finish downloading it give an error saying the file is damaged, i tired downloading again but it keeps giving me the same error every time.

    if could help me out.

    1. blankFaiz Reply

      Hi, I am not sure but to double-check, Is your Virtualbox the latest version (6.1.10)? Have your installed the VirtualBox Extension?

  56. blankKai N. Reply

    Hi guys. Doesn’t work for me because i’ll always get an error “VBoxMana.exe: error: Could not find a registered machine name ‘Mac OS Big Sur’. I found out that my machine is in a different folder. It’s in my user folder. What to do right now?

    1. blankFaiz Reply

      When you opened VirtualBox code via notepad or any other text editor, use the replace function of the program to replace the VM Name to your virtual machine name (this should be exact).

      Also, make sure to use CMD (As admin) not Powershell.

      1. blankFaiz

        Did you CD to “Program Files\Oracle\VirtualBox\”?

        cd "C:\Program Files\Oracle\VirtualBox\"

        If you have installed Virtualbox in another folder then you may have to cd to that folder.

      1. blankTudor Trifan

        Asus Tuf FX 505 AMD Ryzen 5 3550H with integrated Radeon Vega 8 graphics+Nvidia GTX 1050 3Gb 8Gb RAM

      2. blankFaiz

        Add this code to your VM:

        cd "C:\Program Files\Oracle\VirtualBox\"
        VBoxManage modifyvm "your VM name" --cpu-profile "Intel Core i7-6700K"

        P.S It’s highly important that you should quit the VirtualBox program before executing the code.

  57. blankRodrigue Martin Reply

    a am to long boot blocking for ”” put how to repair boot ?
    thank you

    1. blankBlake T Reply

      Hi, I have the same error. After installing macOS and partitioning the drive on the recovery screen successfully, and then waiting 29 minutes on the apple logo code scrolls on the screen and seems to get stuck on:
      CS_RUNTIME for entitlement:

      I followed the steps exactly and it was working up until there, does anyone have any suggestions? I already tried deleting and re-doing the VM and it is still the same.

  58. blanklmao Reply

    Warning: All the content of this site is copyright protected, and no-one has the right to copy-paste our materials.
    What are you gonna do, sue someone?

    1. blankMukhtar Jafari Post author Reply

      There are other ways that can help the original creator to protect their works without a lawsuit. A lawsuit can be the last option as it might be an expensive and long process to go. I encourage you to read this article on how we can protect our content online.

      1. blankmavethee

        I have exact same problem, I installed it using your dmg file and converting it to iso.

      2. blankmavethee

        File is down now but before I had issues downloading it from Mediafire. Can you add link to some better hosting or torrent protocole for it?

  59. blankGabriel Reply

    is there any way i can fix the screens ratio, it stays at a 4:3 ratio and i cant change it to my monitors ratio, so it has 2 giant black bars on both sides

  60. blankGustavo Vilas Boas Reply

    I managed to get through the installation steps, but when the system boots, it gets stuck at this “Forcing CS_RUNTIME for entitlement:” message. Tried searching for it but couldnt find anything related to restricted-block-devices.

    1. blankGustavo Vilas Boas Reply

      Actually I just had to wait like 5 hours and then It worked. It is very laggy but Its usable. Thanks for the tutorial!

      1. blankJordan van Bergen

        Do you have the May 2004 version update of Windows 10?
        If yes read my comment on how to fix the laggy issue with this version. It will be fast as normal again.

  61. blankJordan van Bergen Reply

    After getting it to work with VMWare I tried booting my Catalina version on Virtualbox but this really doesn’t start at all and is very slow as well.

    I have the Windows10 May Update:

    Windows 10 – Version 2004 OS Build 19041.329

    So it could well be that everything depending on virtualbox doesn’t work as it should due to the Windows 10 may update. BlueStacks Android emulator doesn’t work any longer as well due to the May Update.

    So I found this as well:

    So a lot is not functioning 100% after Windows 10 – Version 2004 OS Build 19041.329 with virtualbox.

    1. blankMukhtar Jafari Post author Reply

      If you’ve followed our guide thoroughly, we’ve said the virtualbox doesn’t completely support the new macOS Big Sur at this time but we’ll update the post once everything works fine.
      Also, if you really need to up and running macOS Big Sur, we recommend you to use our Install macOS Big Sur on VMware guide because it’s working.

      1. blankJordan van Bergen

        Okay….. I do get this now after long waiting:

        But I don’t go passed the Disk Utility screen. Mouse is really not responding and screen is very slow with Virtualbox.

        So I got somewhat further but this takes too long.

        I don’t like VMware as i always get the 64bit remark that the hosts needs to be 64bit as well otherwise you can’t run a 64 bit virtual machine. But of course my host is 64bit and I set all settings correctly. It’s an i9 processor that won’t work together with VMware for now. I tried everything. That’s why I am sticking to virtualbox as this is working nicely on windows and with catalina for example.

      2. blankMukhtar Jafari Post author

        You’re totally right but at this point, we also looking for a better solution to get passed from selecting the disk. When you select the disk then you can’t actually select it because it won’t let us do that unless we change some code in the configuration file of the virtual machine. It’s quite challenging but we’re working on it to find a solution. We’ll update our guide as soon as we come up with a good solution.
        Btw VMware is working for us very well but I’m not sure why it’s not working for you?
        I’m using VMware 15.5. You can download VMware latest version from this website but the language is Persian. If you don’t trust them then you can download from its official website.

      3. blankJordan van Bergen

        It’s working 100% now, see:

        I had to do this: It’s due to the Windows 10 Version 2004 May Update !

        If you do the following if you have the same issues than it will work again:

        1. Control panel -> Programs and Features -> Turn Windows Features on or off -> Uncheck Hyper-V and Windows Hyper-Visor Platform

        Additional Notes for Windows Hosts

        2. To check the status of Hyper-v in Windows 10, | Run | OptionalFeatures.exe, and look for the “Hyper-V” option. The box should be empty, not checked or shaded. If you want to be absolutely sure that Hyper-v is gone then open an administrator command console and type “bcdedit /set hypervisorlaunchtype off”. Make sure to fully power down and reboot the host after changing the Hyper-v setting.

        3. On some Windows hosts with an EFI BIOS, DeviceGuard or CredentialGuard may be active by default, and interferes with OS level virtualization apps in the same way that Hyper-v does. These features need to be disabled. On Pro versions of Windows you can do this using gpedit.msc (set Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled. CredentialGuard is a subset of DeviceGuard, so disabling the former should be enough. If you cannot use gpedit for some reason then the equivalent registry hack is to find the key


        and set it to 0.

        4. On Win10 hosts, check Windows Defender > Device Security > Core Isolation Details and make sure settings in this panel are turned off, reboot the host from power down if you needed to make changes. “Core isolation [includes] security features available on your device that use virtualization-based security” …which is why they can interfere with VirtualBox.

      4. blankMukhtar Jafari Post author

        Thanks for you time for submitting this solution. We really appreciate your time Jordan.
        Also, you’ll be able to fix the slow performance of macOS Big Sur or any other version of macOS by giving it more RAM, and Processor and it’ll perform much better.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.