Jump to content
fantomas1

Apple released macOS 10.13.4 Update

29 posts in this topic

Recommended Posts

macos_egpu.jpg

 

The macOS High Sierra 10.13.4 update improves the stability, performance, and security of your Mac, and it is recommended for all users.

 

This update:

  • Adds support for Business Chat conversations in Messages in the US
  • Adds support for external graphics processors (eGPUs)
  • Fixes graphics corruption issues affecting certain apps on iMac Pro
  • Allows jumping to the right-most open tab using Command+9 in Safari
  • Enables sorting Safari bookmarks by name or URL by right clicking and choosing "Sort by..."
  • Fixes an issue that may prevent web link previews from appearing in Messages
  • Helps protect privacy by only AutoFilling usernames and passwords after selecting them in a web form field in Safari
  • Displays warnings in the Safari Smart Search Field when interacting with password or credit card forms on non-encrypted web pages
  • Displays privacy icons and links to explain how your data will be used and protected when Apple features ask to use your personal information

 

View full article

 

Share this post


Link to post
Share on other sites
Advertisement

Running fine on my Optiplex 790, Macbook and Probook :P

Spoiler


MQWP0X7.png10ibhUk.pnglZ33CW0.png

 

 

Share this post


Link to post
Share on other sites
29 minutes ago, DSM2 said:

Could someone provide a working 10.13.4 port limit patch please?

            <dict>
                <key>Comment</key>
                <string>Disable USB Limit 10.13.4+</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>g32UDw+DlwQAAA==</data>
                <key>Name</key>
                <string>AppleUSBXHCI</string>
                <key>Replace</key>
                <data>g32UGpCQkJCQkA==</data>
            </dict>

Share this post


Link to post
Share on other sites
2 hours ago, Zenith432 said:

Anyone try 10.13.4 with Kabylake graphics (HD630, model 0x5912)?  I'm getting flicker and screen artifacts.

See my post here

Any help is appreciated.

I have the same issue. UHD630 (Cannon Lake) shows up twice in System Information. Screen flickers like hell. Worked fine under 10.13.3.

Edited by mulder77

Share this post


Link to post
Share on other sites
8 hours ago, Zenith432 said:

Anyone try 10.13.4 with Kabylake graphics (HD630, model 0x5912)?  I'm getting flicker and screen artifacts.

See my post here

Any help is appreciated.

I have 0x5916 and it shows twice in System Profile too but no other issues at least for now. Same kexts you have. 

Share this post


Link to post
Share on other sites

@mulder77, bluenote56: I changed SMBIOS Model ID from iMac18.2 to iMac 18.1 and it fixed the problem.  The solution is posted in the thread I linked.

Share this post


Link to post
Share on other sites

The solution is posted in the thread

  • DVMT pre-allocated to 192MB
  • DVMT max to MAX
  • SMBIOS 18,3 to 18,1

Share this post


Link to post
Share on other sites

After updated to 10.13.4 and nVidia Web driver...30.103 for my Gigabyte GTX 1050 ti, needed to patch AppleHDAController from <de10e90b> to <de10b90f> for getting audio via DP-HDMI adapter

            <dict>
                <key>Comment</key>
                <string>AppleHDAController Patch</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>3hDpCw==</data>
                <key>Name</key>
                <string>AppleHDAController</string>
                <key>Replace</key>
                <data>3hC5Dw==</data>
            </dict>
 

Previously didn't patch anything.

Share this post


Link to post
Share on other sites

It seems to be working well on my Z800.
Seems like the two Xeon X5690 are running a little bit cooler but I'm not sure.
No immediate problems noticed.

Share this post


Link to post
Share on other sites
On 3/30/2018 at 12:00 PM, maleorderbride said:

            <dict>
                <key>Comment</key>
                <string>Disable USB Limit 10.13.4+</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>g32UDw+DlwQAAA==</data>
                <key>Name</key>
                <string>AppleUSBXHCI</string>
                <key>Replace</key>
                <data>g32UGpCQkJCQkA==</data>
            </dict>

Hi. Already went to the update and lost some of my USB 3.0. 

Excuse my noobness but where in the config plist I put this code? Already had under >KextsToPatch< some code to change  the 15 por limit from before (you can find the codes below)

Should I delete them and replace with the new code? 

Thanks in advance

 

 

<dict>
				<key>Comment</key>
				<string>change 15 port limit</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g32MEA==
				</data>
				<key>MatchOS</key>
				<string>10.13.x</string>
				<key>Name</key>
				<string>com.apple.driver.usb.AppleUSBXHCIPCI</string>
				<key>Replace</key>
				<data>
				g32Mfw==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change 15 port limit</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g710////EA==
				</data>
				<key>MatchOS</key>
				<string>10.12.x</string>
				<key>Name</key>
				<string>com.apple.driver.usb.AppleUSBXHCIPCI</string>
				<key>Replace</key>
				<data>
				g710////Gw==
				</data>
</dict>
			<dict>
				<key>Comment</key>
				<string>change 15 port limit</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g72M/v//EA==
				</data>
				<key>MatchOS</key>
				<string>10.11.x</string>
				<key>Name</key>
				<string>com.apple.driver.usb.AppleUSBXHCIPCI</string>
				<key>Replace</key>
				<data>
				g72M/v//Gw==
				</data>

 

Share this post


Link to post
Share on other sites

Replaying to my own noob question...

just replace in config.plist here after the "KextsToPatch" key. Then it should work. I did not delete the older patch´s and still works. 

<key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>Disable USB Limit 10.13.4+</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g32UDw+DlwQAAA==
                </data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>MatchOS</key>
                <string>10.13.4+</string>
                <key>Name</key>
                <string>AppleUSBXHCI</string>
                <key>Replace</key>
                <data>
                g32UGpCQkJCQkA==
                </data>
            </dict>
 

Question for the mentors. Is still necessary to maintain in this new update the USBinjectALL.kext in "Other"? @MaLd0n

thxs.

Share this post


Link to post
Share on other sites

Clover 4411 or any other 3d party USB creators using 4411 is not showing the 10.13.4 USB installer at Clover boot menu, direct update went well but no way to fresh install from USB even if has been created successfully

Short: USB installer is showing in the BIOS just fine and it boots to it, but Clover 4411 boot menu is not showing the installer as it always did.. Clover 4411 and 10.13.3 no problem, Clover 4411 and 10.13.4 problem

Share this post


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

Clover 4411 or any other 3d party USB creators using 4411 is not showing the 10.13.4 USB installer at Clover boot menu, direct update went well but no way to fresh install from USB even if has been created successfully

Short: USB installer is showing in the BIOS just fine and it boots to it, but Clover 4411 boot menu is not showing the installer as it always did.. Clover 4411 and 10.13.3 no problem, Clover 4411 and 10.13.4 problem

Clover 4424

https://drive.google.com/file/d/1o1DLChbq9hpT_I9rnd-rSv8Pc7czpYfN/view?usp=sharing

Share this post


Link to post
Share on other sites

Is there a way of finding out why the update keeps coming up in my App Store after rebooting during the install? 

It seems as though it does not want to finish the update.

There is also a new clover entry, "mac OS install on Macintosh HD".

Do I boot from that one after initiating the install?

Share this post


Link to post
Share on other sites
5 hours ago, Careless said:

Is there a way of finding out why the update keeps coming up in my App Store after rebooting during the install? 

It seems as though it does not want to finish the update.

There is also a new clover entry, "mac OS install on Macintosh HD".

Do I boot from that one after initiating the install?

Yes. The update has 2 stages, you only went through the first stage. After the first stage the system will reboot and then will proceed the initial update process.

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 fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

×