I hope this will be helpful for others: Go to Windows Security -> Device Security -> Core Isolation -> Core Isolation Detais -> Turn off memory integrity and then restart your system. It will start working
I had to go down the list of profiles until the third one worked for me. Installing successfully now; going to do an xcode assignment for an apprenticeship pre-work
Please help, I can't install it. Please help me see what's wrong with it???? Now I have gone to the language selection section and then to the MACOS installation section and it only installs about 80% and then goes back to the operating system installation step.
Hi @homeroaddams3434, I'm glad you enjoyed the tutorials! 😊 Regarding VirtualBox Guest Additions on macOS Sonoma, it's a bit tricky. Officially, VirtualBox doesn't fully support Guest Additions for macOS guests, which means some features like shared folders and seamless mode might not work as expected¹. However, you can try the following steps to improve your experience: 1. *Enable File Sharing**: Use macOS's native file sharing to share files between your host and guest systems. Go to **System Preferences > Sharing* and enable **File Sharing**. 2. *Screen Sharing**: Similarly, enable **Screen Sharing* in the same menu to access your VM's desktop from your host system. 3. **Third-Party Tools**: Look for third-party tools or scripts that can enhance the VM's performance and usability. Some users have had success with these². I hope this helps! If you have any more questions or need further assistance, feel free to ask.
Hello! I'm trying to install macOS Sonoma using VirtualBox with a laptop with AMD CPU. I tried your install tutorial and this video to try to fix the errors, but I tried all the given CPU profiles and it gives me the same error (EXITBS:START). How can I fix this? I can give you the log files if you need it
The “EXITBS:START” error during macOS installation in VirtualBox, especially on AMD CPUs, can indeed be a bit pesky. But worry not; I’ve got a few tricks up my digital sleeve to help you out. Let’s dive in: 1. CPU Profiles: o You’ve already tried some CPU profiles, but let’s give it another shot. These profiles essentially tell VirtualBox how to emulate the CPU. Some users have reported success by setting a specific profile. o Open a terminal or command prompt and run the following command (replace "VM name" with the actual name of your virtual machine): o VBoxManage modifyvm "VM name" --cpu-profile "Intel Xeon X5482 3.20GHz" o Try booting your VM again and see if it gets past that pesky “EXITBS:START.” 2. Remove Existing CPU Configuration: o Sometimes remnants of previous CPU configurations can cause issues. Let’s clean house: o VBoxManage modifyvm "VM name" --cpuidremoveall o This command removes any existing CPU configuration from your VM. Give it a whirl and try booting again. 3. Nested Virtualization: o If you’re running VirtualBox within another virtualization environment (like VMware Workstation), nested virtualization might be causing trouble. o Check if nested virtualization is enabled in your host system’s BIOS/UEFI settings. If it is, try disabling it and see if that helps. 4. USB Port Mapping: o Sometimes USB port mapping can throw a wrench into the works. o In your VM’s configuration (usually in the config.plist file), try various USB port configurations. You might even disable USB port mapping altogether to see if that resolves the issue. 5. Community Wisdom: o Sometimes the best solutions come from fellow adventurers. Check out forums and community discussions related to your specific hardware (Ryzen 7 7700X, RX 6800, etc.). Others might have encountered similar issues and found workarounds. o For instance, this forum thread discusses a few additional steps that might help. Remember, virtualization can be a bit finicky, but persistence pays off! If one approach doesn’t work, try another. And hey, if your VM could talk, it’d probably say, “Thanks for not giving up on me!” 🤖🔧
@@EpidemicTutorials-qh6de Hi! Thanks for answering and trying to help me. - I'm not running VirtualBox inside VMware so I'm assuming I'm not using nested virtualization. It's running from a Windows 11 with an AMD Ryzen 7 5800H. - I tried all the CPU profiles again, tried the cpuidremoveall command and then tried getting all the CPU profiles but still the same error. I noticed that when using Intel Core i5-3570 the VM starts and keeps a black screen but all the others end with the EXITBS:START error. - I searched for USB port mapping settings but only found USB controller settings so I tried USB 1.0, 2.0, disabled it (doesn't save) but nothing changed. - Also, I searched some topic forums with my CPU but found topics where they use VMware or VirtuaBox forum topics saying hackintosh is illegal and won't help. If you have new ideas or tips to try I will be glad to test it
I am having issues with installing this as well. I have an AMD processor and have run the command to function as Intel. Everything looks fine, the VM boots and starts installing. It gets to this line and stops every time. #[EB.LD.LKCIR.2] . I am trying to install Sonoma.
@@EpidemicTutorials-qh6de Don't bother, i already got it installed with Vmware workstation player. Getting macOS to work with AMD Ryzen 7 pro and Virtualbox seems to require way too much effort
![Install macOS in VirtualBox on Windows PC [Intel & AMD]](http://i.ytimg.com/vi/vQJrM7HqezQ/mqdefault.jpg)
I hope this will be helpful for others: Go to Windows Security -> Device Security -> Core Isolation -> Core Isolation Detais -> Turn off memory integrity and then restart your system. It will start working
literally fixed it, thank youuu
Thank you for your contribution to the channel
thank you !
This worked for me after all else failed on my Ryzen 7950x
I had to go down the list of profiles until the third one worked for me. Installing successfully now; going to do an xcode assignment for an apprenticeship pre-work
Good Job Sir
Please help, I can't install it. Please help me see what's wrong with it????
Now I have gone to the language selection section and then to the MACOS installation section and it only installs about 80% and then goes back to the operating system installation step.
make sure you have enough storage, double-check the configuration to make sure it's correct and try again
Nice Tutorials, Thanks. But what about VBox guest Additions on MACOs Sonoma? 🤗
Hi @homeroaddams3434,
I'm glad you enjoyed the tutorials! 😊
Regarding VirtualBox Guest Additions on macOS Sonoma, it's a bit tricky. Officially, VirtualBox doesn't fully support Guest Additions for macOS guests, which means some features like shared folders and seamless mode might not work as expected¹. However, you can try the following steps to improve your experience:
1. *Enable File Sharing**: Use macOS's native file sharing to share files between your host and guest systems. Go to **System Preferences > Sharing* and enable **File Sharing**.
2. *Screen Sharing**: Similarly, enable **Screen Sharing* in the same menu to access your VM's desktop from your host system.
3. **Third-Party Tools**: Look for third-party tools or scripts that can enhance the VM's performance and usability. Some users have had success with these².
I hope this helps! If you have any more questions or need further assistance, feel free to ask.
Hello! I'm trying to install macOS Sonoma using VirtualBox with a laptop with AMD CPU. I tried your install tutorial and this video to try to fix the errors, but I tried all the given CPU profiles and it gives me the same error (EXITBS:START).
How can I fix this? I can give you the log files if you need it
The “EXITBS:START” error during macOS installation in VirtualBox, especially on AMD CPUs, can indeed be a bit pesky. But worry not; I’ve got a few tricks up my digital sleeve to help you out. Let’s dive in:
1. CPU Profiles:
o You’ve already tried some CPU profiles, but let’s give it another shot. These profiles essentially tell VirtualBox how to emulate the CPU. Some users have reported success by setting a specific profile.
o Open a terminal or command prompt and run the following command (replace "VM name" with the actual name of your virtual machine):
o VBoxManage modifyvm "VM name" --cpu-profile "Intel Xeon X5482 3.20GHz"
o Try booting your VM again and see if it gets past that pesky “EXITBS:START.”
2. Remove Existing CPU Configuration:
o Sometimes remnants of previous CPU configurations can cause issues. Let’s clean house:
o VBoxManage modifyvm "VM name" --cpuidremoveall
o This command removes any existing CPU configuration from your VM. Give it a whirl and try booting again.
3. Nested Virtualization:
o If you’re running VirtualBox within another virtualization environment (like VMware Workstation), nested virtualization might be causing trouble.
o Check if nested virtualization is enabled in your host system’s BIOS/UEFI settings. If it is, try disabling it and see if that helps.
4. USB Port Mapping:
o Sometimes USB port mapping can throw a wrench into the works.
o In your VM’s configuration (usually in the config.plist file), try various USB port configurations. You might even disable USB port mapping altogether to see if that resolves the issue.
5. Community Wisdom:
o Sometimes the best solutions come from fellow adventurers. Check out forums and community discussions related to your specific hardware (Ryzen 7 7700X, RX 6800, etc.). Others might have encountered similar issues and found workarounds.
o For instance, this forum thread discusses a few additional steps that might help.
Remember, virtualization can be a bit finicky, but persistence pays off! If one approach doesn’t work, try another. And hey, if your VM could talk, it’d probably say, “Thanks for not giving up on me!” 🤖🔧
@@EpidemicTutorials-qh6de Hi! Thanks for answering and trying to help me.
- I'm not running VirtualBox inside VMware so I'm assuming I'm not using nested virtualization. It's running from a Windows 11 with an AMD Ryzen 7 5800H.
- I tried all the CPU profiles again, tried the cpuidremoveall command and then tried getting all the CPU profiles but still the same error. I noticed that when using Intel Core i5-3570 the VM starts and keeps a black screen but all the others end with the EXITBS:START error.
- I searched for USB port mapping settings but only found USB controller settings so I tried USB 1.0, 2.0, disabled it (doesn't save) but nothing changed.
- Also, I searched some topic forums with my CPU but found topics where they use VMware or VirtuaBox forum topics saying hackintosh is illegal and won't help.
If you have new ideas or tips to try I will be glad to test it
@@Termindiego25 Hello , same problem here with ryzen 5 5600
worked thanks
Ur welcome
I am having issues with installing this as well. I have an AMD processor and have run the command to function as Intel. Everything looks fine, the VM boots and starts installing. It gets to this line and stops every time. #[EB.LD.LKCIR.2] . I am trying to install Sonoma.
Try using Installing it on VMware ruclips.net/video/Fq6j9CS7C5g/видео.html
Grand! Thx !
glad I could help you
I have AMD how to manage it pls?
if you are using AMD and this video didn't fix you might need to install an older version of MacOS such as Montary.
I got error in intel
Running in inherently Mac OS ?
check settings and config file and try again
@@EpidemicTutorials-qh6de worked after restart I’m using Mac OS for past 10 days
Glad to hear that , sorry for late reply I had an accident and couldn't work on my channel for like two weeks
@@EpidemicTutorials-qh6de it’s ok bro take care ❤️
@@sathiyaprince Same here, what did you do?
You're a god, how do you know all that
Thanks for all the positive words
GENIUS
Thanks for the possitive feedback
error remains 😭
Make sure configuration is correct, allocate only one cpu core to the machine
None of the profiles helped - AMD Ryzen 7 PRO 4750U
I'm sorry but this is all the profiles i got, ill look for more options and keep you updated, check video description in the next few days
@@EpidemicTutorials-qh6de Don't bother, i already got it installed with Vmware workstation player. Getting macOS to work with AMD Ryzen 7 pro and Virtualbox seems to require way too much effort
@taf130 yeah it's not as easy as older versions, glad you managed to install it