Jump to content
fantomas

[pre-release] macOS Catalina

1,735 posts in this topic

Recommended Posts

1 minute ago, ricoc90 said:


 

Check your DSDT. Probably you need the H_EC to EC patch

I have put the H_EC to EC patch, EC0 to EC patch, and ECDV to EC patch, all in DSDT patches.

Best regards.

Share this post


Link to post
Share on other sites
Advertisement
3 minutes ago, asdesoso said:

I have put the H_EC to EC patch, EC0 to EC patch, and ECDV to EC patch, all in DSDT patches.

Best regards.


Can you post your DSDT?

Share this post


Link to post
Share on other sites
1 minute ago, ricoc90 said:


Can you post your DSDT?

I have put the values to replace it in config.plist via Clover Configurator > ACPI > DSDT Patches.

I attached the config.plist here without Serial Number.

Best regards.

config.plist

Share this post


Link to post
Share on other sites
26 minutes ago, asdesoso said:

I have put the values to replace it in config.plist via Clover Configurator > ACPI > DSDT Patches.

I attached the config.plist here without Serial Number.

Best regards.

config.plist

use only correct rename, only one, u need check ur tables or ioreg and rename only device with AppleACPIEC load

MaLd0n 2019-08-01 às 16.29.01 cópia.png

 

Share this post


Link to post
Share on other sites

Update went well for me. I just needed to add ethernet again to net works settings and re boot

12 hours ago, Tony Arnold said:

Those of you who are succeeding with this update - are you using Clover or OpenCore when you install the update?

Ozmosis modded bios

Share this post


Link to post
Share on other sites
19 minutes ago, chris1111 said:

Hi @MaLd0n do you have a patch.txt to do this rename AppleACPIE

thanks again

notebooks, this device have many entries in dsdt and dependencies with OEM SSDTs, let the bootloader work on it ;) 

 

desktop, have only EC0 in some asus mobos and others, we can use it without any problem

into_all device label EC0 set_label begin EC end

 

Share this post


Link to post
Share on other sites
1 hour ago, asdesoso said:

I have put the values to replace it in config.plist via Clover Configurator > ACPI > DSDT Patches.

I attached the config.plist here without Serial Number.

Best regards.

config.plist

try without -lilubeta and -alcbeta boot arguments

Share this post


Link to post
Share on other sites
19 minutes ago, MaLd0n said:

desktop, have only EC0 in some asus mobos and others, we can use it without any problem


into_all device label EC0 set_label begin EC end

 


my Dell Precision T1700 has H_EC, so for me that would be a problem :rofl:
 

2073717670_Schermafbeelding2019-08-01om22_28_45.png.525975cde056cb359284d189b2b3574b.png

Edited by ricoc90

Share this post


Link to post
Share on other sites
6 minutes ago, ricoc90 said:


my Dell Precision T1700 has H_EC, so for me that would be a problem :rofl:
 

2073717670_Schermafbeelding2019-08-01om22_28_45.png.525975cde056cb359284d189b2b3574b.png


No need to rename thing,, just add EC device if you don't have EC device in your system

SSDT-EC.dsl from here https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl can be a sampel.

If you used OpenCore bootloader then Renaming ACPI will affect in other OS too. Just add EC device with If _OSI method. No need combination of manual renaming, patch all OEM SSDT from Config.plist

Share this post


Link to post
Share on other sites

Remove all patch about renaming acpi of EC or H_EC,, revert all ACPI renaming in ACPI DSDT,

Just put this to EFI/CLOVER/ACPI/Patched or EFI/OC/ACPI.


Problem will be solved,, with if _OSI of Darwin, then if you used OpenCore bootloader and boot to Windoes then EC device from this custom SSDT will not be loaded. So no worry.

Renaming ACPI with OpenCore bootloader without if _OSI specific then it will appear in your device manager. I attached a sampel

SSDT-ECUSBX.aml

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
2 minutes ago, Andres ZeroCross said:


No need to rename thing,, just add EC device if you don't have EC device in your system

SSDT-EC.dsl from here https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl can be a sampel.

If you used OpenCore bootloader then Renaming ACPI will affect in other OS too. Just add EC device with If _OSI method. No need combination of manual renaming, patch all OEM SSDT from Config.plist


I renamed H_EC to EC through the Clover patch mentioned by MaLd0n a couple of posts earlier. I was just mentioning that his patch.txt for maciasl won't work in my case (simply because mine is not EC0 but H_EC)

1 minute ago, Andres ZeroCross said:

Remove all patch about renaming acpi of EC or H_EC,, revert all ACPI renaming in ACPI DSDT,

Just put this to EFI/CLOVER/ACPI/Patched or EFI/OC/ACPI.


Problem will be solved,, with if _OSI of Darwin, then if you used OpenCore bootloader EC device will not be loaded. So no worry.

Renaming ACPI with OpenCore bootloader without if _OSI specific then it will appear in your device manager.

SSDT-ECUSBX.aml

 

I'l look into it later, thanks :D

Share this post


Link to post
Share on other sites
1 minute ago, ricoc90 said:


I renamed H_EC to EC through the Clover patch mentioned by MaLd0n a couple of posts earlier. I was just mentioning that his patch.txt for maciasl won't work in my case (simply because mine is not EC0 but H_EC)


No need to rename your DSDT device from Config.plist. Just use that SSDT. It will fix it

Share this post


Link to post
Share on other sites
51 minutes ago, chris1111 said:

Hi @MaLd0n do you have a patch.txt to do this rename AppleACPIE

thanks again


Most of device has only EC0, H_EC or ECDV in DSDT only, but in certain device you will found those device in OEM SSDT too. Just renaming DSDT can cause trouble. if you rename this device from DSDT only, and if you have another H_EC/ECDV/EC0 ini other SSDT then you will need patch it from bootloader too. Simple thing just add EC device, no negative effect.

Share this post


Link to post
Share on other sites

if u have a native device why create other? is a non-sense way

usbx is mandatory for skylake+, skylake- just need create or rename devices and kill EHCx devices, serie 8+

Share this post


Link to post
Share on other sites

Hello, mates!

I have a problem updating to Catalina public beta 4. (currently i'm on beta 3, updated from latest Mojave)

With verbose boot mode on, i'm stuck at "apfs module start 1682" message.

Any suggestions?

Thanks!

Edited by Dobry_Bodry

Share this post


Link to post
Share on other sites
Just now, Dobry_Bodry said:

Hello, mates!

I have a problem updating to Catalina public beta 4.

With verbose boot mode on, i'm stuck at "apfs module start 1682" message.

Any suggestions?

Thanks!


Look above :P

Share this post


Link to post
Share on other sites
2 minutes ago, Dobry_Bodry said:

Hello, mates!

I have a problem updating to Catalina public beta 4. (currently i'm on beta 3, updated from latest Mojave)

With verbose boot mode on, i'm stuck at "apfs module start 1682" message.

Any suggestions?

Thanks!

Try put that files in EFI/CLOVER/ACPI/patched,, reboot and check

Share this post


Link to post
Share on other sites
25 minutes ago, Andres ZeroCross said:

Try put that files in EFI/CLOVER/ACPI/patched,, reboot and check

I'm sorry, but i'm total noobie in ACPI and DSDT. What files i should move?

Share this post


Link to post
Share on other sites
1 minute ago, Dobry_Bodry said:

I'm sorry, but i'm total noobie in ACPI and DSDT. What files i should move?

This file SSDT-ECUSBX.aml.
Put that file in EFI/CLOVER/ACPI/Patched. MOunt your EFI partition first

Share this post


Link to post
Share on other sites
1 hour ago, Andres ZeroCross said:

Remove all patch about renaming acpi of EC or H_EC,, revert all ACPI renaming in ACPI DSDT,

Just put this to EFI/CLOVER/ACPI/Patched or EFI/OC/ACPI.


Problem will be solved,, with if _OSI of Darwin, then if you used OpenCore bootloader and boot to Windoes then EC device from this custom SSDT will not be loaded. So no worry.

Renaming ACPI with OpenCore bootloader without if _OSI specific then it will appear in your device manager. I attached a sampel

SSDT-ECUSBX.aml

 

Copied the above .aml and previous .dst files to /EFI/CLOVER/ACPI/patched and finally my Desktop build with Catalina DP5 boot-up again. :lol::lol:

Thanks for all people that helped me.

Here are some pictures.

Captura de pantalla 2019-08-01 a las 23.26.18.png

Captura de pantalla 2019-08-01 a las 23.26.25.png

Share this post


Link to post
Share on other sites
1 minute ago, asdesoso said:

 

Copied the above .aml and previous .dst files to /EFI/CLOVER/ACPI/patched and finally my Desktop build with Catalina DP5 boot-up again. :lol::lol:

Thanks for all people that helped me.

Here are some pictures.

Captura de pantalla 2019-08-01 a las 23.26.18.png

Captura de pantalla 2019-08-01 a las 23.26.25.png


Congratulations then :D

Just remove SSDT-EC.dsl., you don't need DSL files ini ACPI :D It's not used

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
9 hours ago, MaLd0n said:

check ur Embedded Controller Device, PNP0C09 and rename it to EC, Skylake+ need inject usbx with correct properties, skylake- just rename or create device(create only if u don't see AppleACPIEC load)

 

This was the issue for my X299 system. Thank you, @MaLd0n!

Share this post


Link to post
Share on other sites

Am I the only one where things just randomly crash?

 

Process:               cfprefsd [343]
Path:                  /usr/sbin/cfprefsd
Identifier:            cfprefsd
Version:               1665.10
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           cfprefsd [343]
User ID:               501

Date/Time:             2019-08-02 04:06:12.863 +0200
OS Version:            Mac OS X 10.15 (19A526h)
Report Version:        12
Anonymous UUID:        438D0464-9BF6-6BA3-827F-9635BCDA4904


Time Awake Since Boot: 61 seconds

 

Process:               Console [558]
Path:                  /System/Applications/Utilities/Console.app/Contents/MacOS/Console
Identifier:            com.apple.Console
Version:               1.1 (4.0.14)
Build Info:            Console2-4000014000000~74
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Console [558]
User ID:               501

Date/Time:             2019-08-02 04:06:25.665 +0200
OS Version:            Mac OS X 10.15 (19A526h)
Report Version:        12
Anonymous UUID:        438D0464-9BF6-6BA3-827F-9635BCDA4904


Time Awake Since Boot: 74 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note:        EXC_CORPSE_NOTIFY

 

Or even AppleUserHIDDrivers which forces me to reboot:

Process:               AppleUserHIDDrivers [288]
Path:                  /System/Library/DriverExtensions/AppleUserHIDDrivers.dext/AppleUserHIDDrivers
Identifier:            AppleUserHIDDrivers
Version:               1.0 (1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           AppleUserHIDDrivers [288]
User ID:               270

Date/Time:             2019-08-02 02:28:17.161 +0200
OS Version:            Mac OS X 10.15 (19A526h)
Report Version:        12
Anonymous UUID:        438D0464-9BF6-6BA3-827F-9635BCDA4904


Time Awake Since Boot: 28 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: AppleUserHIDEventDriver-Default

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
dyld2 mode

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Franklin_NGO
      Hello, does anyone here has experience on thinkpad P hackintoshing? I'm using vanilla guide (my EFI is here: https://www.mediafire.com/file/i3xzh9lnjpae9nj/EFI_Thinkpad_P53s.zip/file) Hackintosh: Catalina 10.15.2 Hardware: CPU: Intel Core i7-8665U Processor (1.90GHz GHz 8MB) GPU: NVIDIA Quadro P520 2 GB GDDR5/ intel UHD 620 RAM: 16.0GB PC4-19200 DDR4 Soldered 2400MHz SSD/ HDD: 1TB SSD Samsung PCIe Motherboard/Laptop model: Intel Coffee Lake-U/Y PCH rev. 30/ Thinkpad P53s BIOS: Lenovo version 1.60 (12/30/2019) Screen: 15.6 "FHD IPS AntiGlare LED Backlight 1920x1080 Ethernet Card: Intel I219-LM Wifi/BT Card: Wireless Intel AC adapter 9560 2x2ac with BT5.0   Status: disabled dGPU, patched HD620 (able to boot to the installation USB without fake ID)   Problem: I finished the first phase of installation (auto reboot at 2 minutes remaining); then I was able to boot to the new installed disk, but it keeps rebooting at "13 minutes remaining". The verbose as in the picture. Thank you and good day.
    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410 and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      If performing an upgrade from Mojave, backup your Mojave disk! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the *** MASKED *** parameters in the attached config.plist with your own values. Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 4-7. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  Be sure to replace the *** MASKED *** parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) If you are upgrading from Mojave that you installed using the instructions here: Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Update IntelMausiEthernet.kext Remove VoodooSDHC.kext from /Library/Extensions If you're manually installing kexts in /Library/Extensions, make sure that you 'sudo chown -R root:wheel *.kext' and 'sudo chmod -R 755 *.kext' the kexts in /Library/Extensions and you execute 'sudo kextcache -i /'.  After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your install is not complete. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys)  
      Version Info at the time of this writing:
      Catalina Installer 10.15.2 CLOVER v2.5k r5102 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.0 BrcmFirmwareRepo.kext 2.5.0 BrcmBluetoothInjector.kext 2.5.0 BrcmPatchRAM3.kext 2.5.0 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (legacy) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change *** MASKED *** values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @headkaze, @vit9696 and others I'm sure for maintaining the Brcm kexts.
       
       
      E6410-Catalina.zip


      AppleHWSensor.kext.zip
    • By Kaku
      Greetings!
       
      So I managed to get a Catalina 10.15 vm up and running in ESXi 6.7u2.
      When I try to install Catalina updates, however, it goes to the Apple logo, status bar moving ever so slightly, reboots again and this time hangs on the Apple logo.  To fix this, I either remove or disable "Mac OS" as an option in the bootloader. Is there a way to get these updates to install? 
       
      In the meantime...
       
      I instead of restarting Catalina after choosing to update it, I shutdown the guest.  After a restart it SEEMED to update with the time duration countdown.
       
      Prior to this I did run disk utility and checked Untitled and Untitled-Data for errors (I don't think it found any).
       
      So I just logged back onto the VM and the version is still 10.15 and NOT 10.15.2 as hoped. So weird.
       
      Any ideas?
       
×