Spoofing Virtual Apple Mac Model

[JoeH2510]

Could you please show me where the regen.sh file is located in the installation package and how I can use it? It seems that the file is not being recognized when I run it on macOS.

[DrDonk]

You run it on the host not inside the VM. The location is tool/host/<windows/linux/macOS>.

Tools are documented here https://github.com/DrDonk/OC4VM/wiki/OC4VM-Tools

[JoeH2510]

PS C:\WINDOWS\system32> cd "E:\oc4vm-2.0.0\tools\windows"
>>
PS E:\oc4vm-2.0.0\tools\windows> dir
>>


    Directory: E:\oc4vm-2.0.0\tools\windows


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        12/17/2025   3:16 AM         225792 cpuid.exe
-a----        12/17/2025   3:16 AM          38912 macguest.exe
-a----        12/17/2025   3:16 AM         376006 macserial.exe
-a----        12/17/2025   3:16 AM           3349 regen.ps1
-a----        12/17/2025   3:16 AM        2498560 vmxtool.exe


PS E:\oc4vm-2.0.0\tools\windows> .\regen.ps1 "E:\002 MACNEW15\GOC\intel\macos.vmx"
>>
.\regen.ps1 : File E:\oc4vm-2.0.0\tools\windows\regen.ps1 cannot be loaded. The file
E:\oc4vm-2.0.0\tools\windows\regen.ps1 is not digitally signed. You cannot run this script on the current system. For
more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\regen.ps1 "E:\002 MACNEW15\GOC\intel\macos.vmx"
+ ~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

I ran the command as instructed, but I received an error message. Could you help me resolve this issue?

[DrDonk]

Run this to allow your user to run unsigned scripts.

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

[DrDonk]

I am in the process of writing more docs and I will add this to the tools page.

[JoeH2510]

PS C:\WINDOWS\system32> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
>>
>>

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): Y
PS C:\WINDOWS\system32> cd "E:\oc4vm-2.0.0\tools\windows"
PS E:\oc4vm-2.0.0\tools\windows> dir


    Directory: E:\oc4vm-2.0.0\tools\windows


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        12/17/2025   3:16 AM         225792 cpuid.exe
-a----        12/17/2025   3:16 AM          38912 macguest.exe
-a----        12/17/2025   3:16 AM         376006 macserial.exe
-a----        12/17/2025   3:16 AM           3349 regen.ps1
-a----        12/17/2025   3:16 AM        2498560 vmxtool.exe


PS E:\oc4vm-2.0.0\tools\windows> .\regen.ps1 "E:\002 MACNEW15\GOC\intel\macos.vmx"
.\regen.ps1 : File E:\oc4vm-2.0.0\tools\windows\regen.ps1 cannot be loaded. The file
E:\oc4vm-2.0.0\tools\windows\regen.ps1 is not digitally signed. You cannot run this script on the current system. For
more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\regen.ps1 "E:\002 MACNEW15\GOC\intel\macos.vmx"
+ ~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

I also tried changing the Execution Policy earlier, but it didn’t work.

[DrDonk]

There are few issues that I was not aware of and I will have to see what is going wrong. To help you move forward I manually generated some values for you.

1. Close the VM down and exit VMware.
2. Open the VMX file of the VM in a text editor (if you used templates it will be macos.vmx)
3. Paste these lines into the file:

__Apple_Model_Start__ = "iMac 2019"
board-id = "Mac-63001698E7A34814"
hw.model = "iMac19,2"
serialNumber = "C02C10GGJWDW"
efi.nvram.var.MLB = "C02953270J9KGQGA8"
efi.nvram.var.ROM = "%63%B5%25%E3%6E%DA"
__Apple_Model_End__ = "iMac 2019"

4. Save the file
5. Boot up the VM

Hope that helps. I will be looking at fixes for 2.0.1.

[JoeH2510]

Thank you for your help. I manually pasted those lines into the .vmx file, and it worked for me. I am very much looking forward to the next version that fixes this issue. Have a great day.

[cvandeplas]

@DrDonk for your info.
I followed the instructions to install Sequoia with OC4VM 2.0.2 on a AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
Sequoia didn't want to install and reported the hardware was unsupported.
The above lines solved the issue. Using the regen.sh script too.

[DrDonk]

I have re-written it as a Windows batch file so no Powershell shenanigans needed. Feel free to try it. I have tested it and appears to work correctly. Save the code to the Windows tools folder as regen.cmd and give it a go.

@echo off
REM {{VERSION}}-{{COMMIT}}
REM SPDX-FileCopyrightText: © 2023-2026 David Parsons
REM SPDX-License-Identifier: MIT

REM Enable debug mode if DEBUG environment variable is set
if defined DEBUG echo on

REM Get script directory
set "SCRIPT_DIR=%~dp0"
set "MACSERIAL_BIN=macserial.exe"
set "MACSERIAL_PATH=%SCRIPT_DIR%%MACSERIAL_BIN%"
set "VMXTOOL_BIN=vmxtool.exe"
set "VMXTOOL_PATH=%SCRIPT_DIR%%VMXTOOL_BIN%"

REM Check if macserial binary exists
if not exist "%MACSERIAL_PATH%" (
    echo Error: %MACSERIAL_BIN% not found at %MACSERIAL_PATH% >&2
    echo Please ensure the macserial binary is in the same directory as this script >&2
    exit /b 1
)

REM Check if vmxtool binary exists
if not exist "%VMXTOOL_PATH%" (
    echo Error: %VMXTOOL_BIN% not found at %VMXTOOL_PATH% >&2
    echo Please ensure the vmxtool binary is in the same directory as this script >&2
    exit /b 1
)

REM Get VMX file from command line argument
set "VMXFILE=%~1"
if "%VMXFILE%"=="" (
    echo Error: No VMX file specified >&2
    exit /b 1
)

if not exist "%VMXFILE%" (
    echo Error: VMX file %VMXFILE% not found >&2
    exit /b 1
)

REM Generate random week number (1-53)
set /a "WEEK=%RANDOM% %% 53 + 1"

REM Generate serial and MLB
for /f "delims=" %%i in ('"%MACSERIAL_PATH%" -m iMac19^,2 -n 1 -w %WEEK% -y 2020') do set "input=%%i"

REM Check if macserial executed successfully
if errorlevel 1 (
    echo Error: Failed to execute %MACSERIAL_BIN% >&2
    echo Command output: %input% >&2
    exit /b 1
)

REM Split the output by pipe delimiter
for /f "tokens=1,2 delims=|" %%a in ("%input%") do (
    set "serial=%%a"
    set "mlb=%%b"
)

REM Trim whitespace
set "serial=%serial: =%"
set "mlb=%mlb: =%"

REM Validate the generated values are not empty
if "%serial%"=="" (
    echo Error: Generated serial is empty >&2
    echo Serial: '%serial%' >&2
    echo MLB: '%mlb%' >&2
    exit /b 1
)

if "%mlb%"=="" (
    echo Error: Generated MLB is empty >&2
    echo Serial: '%serial%' >&2
    echo MLB: '%mlb%' >&2
    exit /b 1
)

REM Generate ROM using pure batch - generate 6 random hex bytes
setlocal enabledelayedexpansion
set "hex=0123456789ABCDEF"
set "rom="
for /l %%i in (1,1,6) do (
    set /a "byte1=!RANDOM! %% 16"
    set /a "byte2=!RANDOM! %% 16"
    for %%a in (!byte1!) do for %%b in (!byte2!) do (
        set "rom=!rom!%%!hex:~%%a,1!!hex:~%%b,1!"
    )
)
endlocal & set "rom=%rom%"

REM Check if ROM generation succeeded
if "%rom%"=="" (
    echo Error: Failed to generate ROM value >&2
    exit /b 1
)

REM Display the changes
echo OC4VM regen
echo -----------
echo Regenerating Mac identifiers...
echo Adding these settings to VMX file:
echo.
echo __Apple_Model_Start__ = "iMac 2019"
echo board-id = "Mac-63001698E7A34814"
echo hw.model = "iMac19,2"
echo serialNumber = "%serial%"
echo efi.nvram.var.MLB = "%mlb%"
echo efi.nvram.var.ROM = "%rom%"
echo __Apple_Model_End__ = "iMac 2019"
echo.
echo Running vmxtool to update file...

REM Run vmxtool to update the VMX file
"%VMXTOOL_PATH%" set "%VMXFILE%" __Apple_Model_Start__="iMac 2019"
"%VMXTOOL_PATH%" set "%VMXFILE%" board-id="Mac-63001698E7A34814"
"%VMXTOOL_PATH%" set "%VMXFILE%" hw.model="iMac19,2"
"%VMXTOOL_PATH%" set "%VMXFILE%" serialNumber="%serial%"
"%VMXTOOL_PATH%" set "%VMXFILE%" efi.nvram.var.MLB="%mlb%"
"%VMXTOOL_PATH%" set "%VMXFILE%" efi.nvram.var.ROM="%rom%"
"%VMXTOOL_PATH%" set "%VMXFILE%" __Apple_Model_End__="iMac 2019"

[JoeH2510]

Thanks. I was able to run the regen.cmd file, and it worked well.

However, there are a few issues I noticed, which may be limitations of version 2.0.0 compared to the previous version 1.0.4 that I used.

The OpenCore file used in version 2.0.0 is in .ISO format. I noticed that when I create a linked clone from the parent VM, the OpenCore component is not generated in the cloned child VM, which causes the child virtual machine to fail to boot.

I am also unable to use iCloud on the macOS virtual machines running on VMware. It appears that Apple has identified these as emulated devices and therefore rejected iCloud access (even though Serial, MLB, ROM, etc. have been added), resulting in many features being unavailable on these virtual machines.

[DrDonk]

I had several requests to make it an ISO file which is what happened in 2.0.0. I have a way to also use the ISO as a VMDK file added to 2.0.1. If you download https://raw.githubusercontent.com/DrDonk/OC4VM/refs/heads/main/vmware/opencore.vmdk into the VM folder and then edit the VMX file and find the hidden usb device near the top of the file. Replace this with:

__Hidden_USB_BOOT_Device__ = ""
usb_xhci:0.deviceType = "disk"
usb_xhci:0.fileName = "opencore.vmdk"
usb_xhci:0.mode = "independent-persistent"
usb_xhci:0.parent = "-1"
usb_xhci:0.port = "0"
usb_xhci:0.present = "TRUE"
usb_xhci:0.readonly = "TRUE"
usb_xhci:0.speed = "16"

If you want the disk to be writeable change this usb_xhci:0.readonly = "TRUE" to FALSE.

The new method for creating the Mac details was because of the ISO requests. One thing you can try is modifying the VMX line:

hypervisor.cpuid.v0 = "TRUE" # VMM bit is set

to FALSE which hides the VMM hypervisor flag from macOS. I think Apple ignore the ROM versions and unfortunately I have not found a way to modify those settings easily using VMX settings. (And I've been using VMware since 1999 so have a long history with it.)

2.0.1 is not quite ready so it may be another week before I have time to release it. 2.0.0 was in effect a complete re-work of the earlier version. Of course feel free to use that if it better suits your needs. I just do not have time to support multiple versions and V2 is the way forward for me.

I will add that I do not use VMs with any Apple accounts and do not test iCloud etc. Only use my real Macs for that.

[DrDonk]

Update I can fix the BIOS details in the OC config file. The system version will be in Apple format but is set to 9999.999.999.999 which Opencore team recommend as stops firmware updates which would fail on a hackintosh or spoofed Mac.

[vprasinos]

Could you tell us how you did that? Is it going to be in 2.0.1?

I am trying to log into an apple ID but I get the "Unexpected Error". My machine AMD Ryzen 9 7940HS Radeon 780M, creates a kernel panic when trying to change:
hypervisor.cpuid.v0 = "TRUE" to FALSE

I created everything from OC4VM 2.0 so I tried to grab vmhide from 1.1.1 which run successfully but made no difference, still getting the "Unexpected Error".

I run your regen.cmd file successfuly and got the iMac 19,2 spoofed correctly but still getting the "Welcome to the virtual Machine" in Sequoia.

[DrDonk]

It is in 2.0.1. Got a bit of testing to do on some other changes I made recently. I would not depend on a VM for Apple account login. Apple have locked a lot of that down now. Even Apple Silicon VMs have limited Apple account access.

I have also seen panics if you try to hide the VMM flag. Never found why and have no answer on how to fix it.

[bellum07]

Initially, I wanted to wait with this until v2.0.1 has been released as with 2.0.1 r/w access for /Volumes/OPENCORE is much easier to configure than in v.2.0.0.

But anyway …

Here’s a patch for /Volumes/OPENCORE/EFI/OC/config.plist which enables Apple-ID in macOS VMs.
I’ve tested it successfully with Sequoia and Tahoe.

With this patch you don’t even have to spoof a real Mac but I recommend it.

hypervisor.cpuid.v0 = "FALSE" didn't work here as well and created a reboot loop.

Hope that helps …

Subject: [PATCH 01/01] Enable Apple ID login in macOS VMware VMs

Adapted from:
  https://forum.proxmox.com/threads/macos-sequoia-cant-log-apple-id-and-its-services.154328/post-711390
  https://forum.proxmox.com/threads/anyone-can-make-bluetooth-work-on-sonoma.153301/post-697832

Thanks! 
---

--- config.plist
+++ config.plist
@@ -230,6 +230,66 @@
 				<key>Skip</key>
 				<integer>0</integer>
 			</dict>
+			<dict>
+				<key>Arch</key>
+				<string>x86_64</string>
+				<key>Base</key>
+				<string></string>
+				<key>Comment</key>
+				<string>Sonoma VM BT Enabler - PART 1 of 2 - Patch kern.hv_vmm_present=0</string>
+				<key>Count</key>
+				<integer>1</integer>
+				<key>Enabled</key>
+				<true/>
+				<key>Find</key>
+				<data>aGliZXJuYXRlaGlkcmVhZHkAaGliZXJuYXRlY291bnQA</data>
+				<key>Identifier</key>
+				<string>kernel</string>
+				<key>Limit</key>
+				<integer>0</integer>
+				<key>Mask</key>
+				<data></data>
+				<key>MaxKernel</key>
+				<string></string>
+				<key>MinKernel</key>
+				<string>20.4.0</string>
+				<key>Replace</key>
+				<data>aGliZXJuYXRlaGlkcmVhZHkAaHZfdm1tX3ByZXNlbnQA</data>
+				<key>ReplaceMask</key>
+				<data></data>
+				<key>Skip</key>
+				<integer>0</integer>
+			</dict>
+			<dict>
+				<key>Arch</key>
+				<string>x86_64</string>
+				<key>Base</key>
+				<string></string>
+				<key>Comment</key>
+				<string>Sonoma VM BT Enabler - PART 2 of 2 - Patch kern.hv_vmm_present=0</string>
+				<key>Count</key>
+				<integer>1</integer>
+				<key>Enabled</key>
+				<true/>
+				<key>Find</key>
+				<data>Ym9vdCBzZXNzaW9uIFVVSUQAaHZfdm1tX3ByZXNlbnQA</data>
+				<key>Identifier</key>
+				<string>kernel</string>
+				<key>Limit</key>
+				<integer>0</integer>
+				<key>Mask</key>
+				<data></data>
+				<key>MaxKernel</key>
+				<string></string>
+				<key>MinKernel</key>
+				<string>22.0.0</string>
+				<key>Replace</key>
+				<data>Ym9vdCBzZXNzaW9uIFVVSUQAaGliZXJuYXRlY291bnQA</data>
+				<key>ReplaceMask</key>
+				<data></data>
+				<key>Skip</key>
+				<integer>0</integer>
+			</dict>
 		</array>
 		<key>Quirks</key>
 		<dict>

[DrDonk]

I would not use that. It can also panic and I explicitly pulled it out of version 2. I think you got lucky and I will not add it to OC4VM. Also VMMHide can also cause the crash and you are not allowed to redistribute it so that is also ruled out.

And I really don't recommend removing the VMM CPUID flag unless absolutely necessary as other issues can arise when upgrading a VM.

I have also returned to write only mode as a CD for the templates but will provide details on how to make the boot drive writeable via the wiki. It makes upgrading much easier if it has not been modified.

[bellum07]

and I will not add it to OC4VM

I don't wanted you to add it, just wanted to share it as it helped me ...

[DrDonk]

I am also going to be brutally honest here I would not spoof VMs anymore. When I first documented it over a decade ago on InsanelyMac it was reliable and allowed a VM to use Apple services. I honestly think that this is no longer a good idea. The days of these VMs are numbered and this project really is only for interest do NOT rely on it for work or anything important. At this stage a cheap second hand M1 Mac mini is really a much better option if you work or personal life depends on accessing iCloud, Messages etc. I am aware that this is controversial as it means spending £200-£300 in the UK but what is the cost of using something incredibly unsupported.

[DrDonk]

Please read #77