yo this is a good tip; I turned on my virtual box mac for the first time in 6+ months, and i did a system update. then i was stuck in a boot loop: ***the system was rebooted due to panic*** or some other error. all i did was switch my virtual box processors from 4 cores to 2 cores (like the video says) and it seems like my mac virtual box is no longer stuck in a boot loop. i just wanted to say that this worked for me and in case anyone else is scratching their head because they have the same problem, try to change processor cores from 4 down to 2 because it worked for me. ty Geek rar guides :)
Have to compile for IOS from Windows. You saved my day, too. The 2 core fix did not work, but 1 core as referenced by user Thiago worked. Much appreciated.
I have a loop on another point. Installation was going to about 25%, and now says 29 minutes left. Now, progress bar is not moving, estimated time is changing time to time (29...27...24...29...28...29), after 10-15 minutes it reboots, move back to this 25% like it remember where it was, but again not moving anymore and reboots in 10-15 minutes.
Sadly, this doesn't work for me. Even with 1 CPU. I once successfully installed and booted Monterey after 14 hours of trial and fails but with no other version. I suspect it has something to do with AMD CPUs on the host machine and / or the command with the "--cpuid-set", which seems to vary in tutorials sometimes.
Sorry to say this boys, but if you're using AMD, I think you are out of luck. I've tried the RealTSCOffset” command, and even switching to 1 core, then 2 cores etc... but I always get stuck on boot loop during the installation.
@@JoseMedina-qj4qp I was actually able to make it work. It works better with the older version of Mac. I got it to run on the newest version of Mac using VMware but it was still laggy.
I ran amd processor and it worked somehow I just had to use a lot of commands till it worked, but i definitely used 1 core for the processor and it worked for me. It’s possible but you need to mess around
This solution works for me. After configuring two cores, the virtual machine kept rebooting. Then i applied this command: VBoxManage setextradata "MacOS Ventura" "VBoxInternal/TM/TSCMode" "RealTSCOffset" and it work. Thanks for the tip
I will be… It's almost always the simplest things. It was a joy finally to see the Apple welcome/configuration screen because of your deep dive and demo of what you found. Great hack! Thanks.
Hello everyone, unfortunately, shortly before completing my installation of MacOS Ventura 13.0 v18.0.02.iso via Oracle VM VirtualBox (on Windows10), a boot loop occurs. This happens again and again, but only at the very end of my installation when everything is supposed to be completed. Does anyone have a similar problem? I followed the recommendations in this video, which has led to my system no longer crashing at the beginning or during the installation and not just at the end.
I'm still stuck in the bootloop no matter what i do, ive been at this for like 2 hours now and have yet to find a soltuion for this, can you give some insight into it? Anything would be much appreicated.
it crashed crashed... it was stuck on "a minute left" for a log bit then VM crashed lol I may try to toly restart with it but also anyone has an idea how to fix? Edit: I tried to redo it from scratch, it now continues but reboots after nd restarts back at the 29 min mark again helppp plzzz
So many comments and none asked so ..... 1.Is it mandatory at least for macOS installation the user to be admin for some reason? All other Vms installed under an active directory user with no problem at all. For mac os had to open cmd not in admin mode cause else couldnt find the VM path which was logical since admin and user have different paths 2.In case of AMD processors (my case 5500u) nothing seems to fix the not noly boot loop but after the installation it goes back to initial installation window to select restore /disk utility / install macos ..etc (No unchecking virtual cd rom from boot options doesn t fix the issue) Commands used (with no errors under simple user not admin) for macOS Ventura cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage.exe modifyvm "macOSventura" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1" VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95" VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 If you have AMD Cpu then run below else it will stuck at EXITBS:START VBoxManage.exe modifyvm "macOSventura" --cpu-profile "Intel Core i7-6700K" VBoxManage setextradata "macOSventura" VBoxInternal2/EfiGraphicsResolution 1920x1080 (not useful) Troubleshooting modes for install boot loops VBoxManage setextradata "macOSventura" "VBoxInternal/TM/TSCMode" "RealTSCOffset" VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 0
i still have the boot loop problem i changed it to 1 cpu and it installed. but when i get it set up and into the OS it just crashes after a min or so and restarts shows PANIC error
Bro, can you help me? I tried a loot of macos versions but no one installed, i tried two time Ventura macos and the two times it arrives at the final bar installing and get in panic loop, i tried with two processor and same happened
My virtual box says about 28 minutes remaining goes down to 14 minutes remaining restarts and starts at 28 minutes again it’s done this 5 times already
I'm having a similar issue with the Windows 10 .iso that I've downloaded. Might this be a solution, as well? I'm about to try it and then document my results
Im stuck in an installation loop, after installing it reboots the system. Have tried both ventura beta and sonoma beta. Same issue. Lowering cpus helps installation but starts from beginning when completed
I'm having the same issues. I have an and Ryzen x3900 and I think I've heard some say that you just can't run Mac OS on AMD. Has to be intel... I"m going to try the installation with just 1 core and see if that works. Basically my last shot lol
It got a bit farther than the last time, but once the time got down to 12 minutes it slowed down drastically then crashed. I noticed I didn't have USB set to 3.0 and I changed the processor value to 3. I am trying this again right now. Meanwhile, on my laptop computer it locked up once it got to 'less than 1 minute remaining' So, it appears your fix works for some computers, but not all.
Why so fuzz and panic about this situation, simple solution is, just keep your VM's processor to just one, go ahead with the installation, it will finish smoothly.. After the installation you can then increase VM's processors to 4. Don't try keeping it 2 or 3 it while installation it will just waste your valuable time.
![Install macOS in VirtualBox on Windows PC [Intel & AMD]](/img/1.gif)
yo this is a good tip; I turned on my virtual box mac for the first time in 6+ months, and i did a system update. then i was stuck in a boot loop: ***the system was rebooted due to panic*** or some other error.
all i did was switch my virtual box processors from 4 cores to 2 cores (like the video says) and it seems like my mac virtual box is no longer stuck in a boot loop.
i just wanted to say that this worked for me and in case anyone else is scratching their head because they have the same problem, try to change processor cores from 4 down to 2 because it worked for me.
ty Geek rar guides :)
Happy to hear this worked for you!
2 cores also dont work
it really help me to fix this , thank you very much
@@GEEKrarGuides same problem do you have a video??? It won't work
Fixed the issue at a critical time (I had to use 1 cpu but the fix still worked). You saved me time and a LOT of money.
this helped me a lot
Have to compile for IOS from Windows. You saved my day, too. The 2 core fix did not work, but 1 core as referenced by user Thiago worked. Much appreciated.
I have a loop on another point. Installation was going to about 25%, and now says 29 minutes left. Now, progress bar is not moving, estimated time is changing time to time (29...27...24...29...28...29), after 10-15 minutes it reboots, move back to this 25% like it remember where it was, but again not moving anymore and reboots in 10-15 minutes.
I have the same problem. Did you find a solution?
@@pogramadorcumcafe6953 found any fix for that?
@@wasifamin8074 Yes. I changed the CPU amount to 2. Before I was putting it to 4. For some reason that's what would make it crash.
@@pogramadorcumcafe6953 thanks
I am having the same problem I am trying the method right now to see if it would work
Sadly, this doesn't work for me. Even with 1 CPU. I once successfully installed and booted Monterey after 14 hours of trial and fails but with no other version. I suspect it has something to do with AMD CPUs on the host machine and / or the command with the "--cpuid-set", which seems to vary in tutorials sometimes.
Sorry to say this boys, but if you're using AMD, I think you are out of luck. I've tried the RealTSCOffset” command, and even switching to 1 core, then 2 cores etc... but I always get stuck on boot loop during the installation.
Real
@@JoseMedina-qj4qp I was actually able to make it work. It works better with the older version of Mac. I got it to run on the newest version of Mac using VMware but it was still laggy.
I ran amd processor and it worked somehow I just had to use a lot of commands till it worked, but i definitely used 1 core for the processor and it worked for me. It’s possible but you need to mess around
I gotta buy an Intel pc now
Ventura and Sonoma is not working...
Try with big sur.... It works
This solution works for me. After configuring two cores, the virtual machine kept rebooting. Then i applied this command: VBoxManage setextradata "MacOS Ventura" "VBoxInternal/TM/TSCMode" "RealTSCOffset" and it work. Thanks for the tip
I will be… It's almost always the simplest things. It was a joy finally to see the Apple welcome/configuration screen because of your deep dive and demo of what you found. Great hack! Thanks.
Hello everyone, unfortunately, shortly before completing my installation of MacOS Ventura 13.0 v18.0.02.iso via Oracle VM VirtualBox (on Windows10), a boot loop occurs. This happens again and again, but only at the very end of my installation when everything is supposed to be completed. Does anyone have a similar problem? I followed the recommendations in this video, which has led to my system no longer crashing at the beginning or during the installation and not just at the end.
Yes, this happens also to me. Did you found any fix? I'm getting too many bugs with Virtualbox, so i'll probably go for VMware
@@EmaBixD got the same problem if anyone fixes itd be appriciated
@@ogulcandursun1665 same bro got any solution? I´ve already tried with Vmware and all the commands for virtual box
@@JUANDIEGOAMADORCASTILLO i gave up and downloaded ubuntu lol 😂
Thank you so much - this just helped me solve my issue, after trying to get Monterey to install on VirtualBox the whole night :)
really happy to hear that
Great job! It fixed my problem. I had to decrease to 1 CPU though but still it helped me a lot! Thanks.
I'm still stuck in the bootloop no matter what i do, ive been at this for like 2 hours now and have yet to find a soltuion for this, can you give some insight into it? Anything would be much appreicated.
did you find anything?
I tried everything and it’s still stuck in a boot loop
For me only worked when I put 1 core. Thanks for the video
awesome!
it crashed crashed... it was stuck on "a minute left" for a log bit then VM crashed lol
I may try to toly restart with it but also anyone has an idea how to fix?
Edit: I tried to redo it from scratch, it now continues but reboots after nd restarts back at the 29 min mark again
helppp plzzz
Thx for a fix but also worked on 3 for me (I looked on other tutorial and they used 3)
great to know! thanks for the feedback
even after a year it still works, thx
Thanks men! YOu saved me! I had to decrease it to 1 core but it worked!
Another useful fix! thanks boss
So many comments and none asked so .....
1.Is it mandatory at least for macOS installation the user to be admin for some reason? All other Vms installed under an active directory user with no problem at all. For mac os had to open cmd not in admin mode cause else couldnt find the VM path which was logical since admin and user have different paths
2.In case of AMD processors (my case 5500u) nothing seems to fix the not noly boot loop but after the installation it goes back to initial installation window to select restore /disk utility / install macos ..etc (No unchecking virtual cd rom from boot options doesn t fix the issue)
Commands used (with no errors under simple user not admin) for macOS Ventura
cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe modifyvm "macOSventura" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95"
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
If you have AMD Cpu then run below else it will stuck at EXITBS:START
VBoxManage.exe modifyvm "macOSventura" --cpu-profile "Intel Core i7-6700K"
VBoxManage setextradata "macOSventura" VBoxInternal2/EfiGraphicsResolution 1920x1080 (not useful)
Troubleshooting modes for install boot loops
VBoxManage setextradata "macOSventura" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
VBoxManage setextradata "macOSventura" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 0
Thanks bro, you completely saved my life
so, im stuck on qa loop after it installs and then after a time, it starts all over again
It helped me get through the first phase of installation and after that ut did the same thing
oh my god! thanks a lot! i didnt knew that i was going through a boot loop. then i got to know and this helped me
fantastic!
Is there any videos for windows
I am on this loop on core 1 and 2 both, installation was complete but still taking me to the recovery loop.
when i did this and tried to boot it said "displaying boot failure for 10 seconds"
i still have the boot loop problem
i changed it to 1 cpu and it installed.
but when i get it set up and into the OS it just crashes after a min or so and restarts shows PANIC error
Same you find a solution?
Did you find the solution
Did you find the solution?
Bro, can you help me? I tried a loot of macos versions but no one installed, i tried two time Ventura macos and the two times it arrives at the final bar installing and get in panic loop, i tried with two processor and same happened
Same. This is a ridicules solution.
Thanks! It helped me get to the end of my install... Great tip
this fix just saved my life, thank you!
glad it helped
Welp, its downloading! Thanks so far!
My virtual box says about 28 minutes remaining goes down to 14 minutes remaining restarts and starts at 28 minutes again it’s done this 5 times already
vmware install loop, it hangs on 15 mins remaining then kernal panics
I only have 4 CPU do I put it at one. What do I do in this situation can you please help me?
Great Buddy still works
I have a different problem after updating my VM macOS, how would I reach you?
I'm having a similar issue with the Windows 10 .iso that I've downloaded. Might this be a solution, as well? I'm about to try it and then document my results
mine instead is grey and it keeps looping back to the grey screen saying about (insert minutes) remaning. I need help plz
my max cpu is 2, in the green space, and it doesn't fix it
ty so much this even helped me when it tried to boot loop windows 10
can you show solution for vmware workstation pro 17? i recently updated my macos catalina vm to sonoma beta and it ended with looped kernel panic
also had infinite loop, for all kind of installs,
only got macOS Big Sur 11.0.1 (20B29) iso up and managed to upgrade via the store to macOS Monterey
Im stuck in an installation loop, after installing it reboots the system. Have tried both ventura beta and sonoma beta. Same issue. Lowering cpus helps installation but starts from beginning when completed
I'm having the same issues. I have an and Ryzen x3900 and I think I've heard some say that you just can't run Mac OS on AMD. Has to be intel... I"m going to try the installation with just 1 core and see if that works. Basically my last shot lol
2024. IT WORKS
does not work on AMD Ryzen using ventura image
I had to reduce to 1 cpu to get it past the boot loop error
Worked for me at 1, after installing and setup was done 3 would NOT work 2 is the best your getting.
Edit: barely works on 2, so 1 is your best bet.
Great thanks! You saved my day!
Glad I could help!
This one didn't help me. It still restarting and won't continue the bootloop in finishing the OS installation
and update?
Excellent dear...
Does not work try & tryed
thank you!
Idk bro, my installation is successful it occurs while personal use. im try now. hopefully it stops. thanks.
WORKS..............!
thx so much ❤❤
no prb
Won’t work for me still
Thank you my good sir
You sound like Jm Halpert from The Office
thank you it's worked
work with one cpu Macos 13 beta
I have green line max at 2 processor. Should i make it to 1 then?
it doesnt hurt to try, it may just run extremely slow.
@@GEEKrarGuides getting the same loop again. Sad life🤕
@@GEEKrarGuides Bad idea it will hurt frequency to 3.0 GHZ keep doing it will break cpu to point cpu will run at 2.8 ghz to max
its working NOWWW thanks
First time I’ve heard anyone call macOS flaky.
when its running on something its not designed for, its flaky lol
Them's fightin' words!!
Had to turn mine down to 1 cpu.
Thank you
It got a bit farther than the last time, but once the time got down to 12 minutes it slowed down drastically then crashed. I noticed I didn't have USB set to 3.0 and I changed the processor value to 3. I am trying this again right now. Meanwhile, on my laptop computer it locked up once it got to 'less than 1 minute remaining' So, it appears your fix works for some computers, but not all.
yes it definitely isnt a fix that will work with all pcs, but it will hopefully help some users.
Tysm this really helped!!!
Thank you !!!
Welcome!
hero !
1 core works for me
awesome
RUclips deleting my comments like its trash
woooo.. it worked.. thx
fantastic!
thnak you so much bro
Im trying just now...
Dont work 😢
thats basically wrong i installed ventura dislike
Why so fuzz and panic about this situation, simple solution is, just keep your VM's processor to just one, go ahead with the installation, it will finish smoothly.. After the installation you can then increase VM's processors to 4. Don't try keeping it 2 or 3 it while installation it will just waste your valuable time.
I try to install bigSur but it still stuck in IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0*0
did not work for me
thank you it worked