Apple Seeds First Beta of macOS High Sierra 10.13.4 to Developers

[tywebb13]

Build number is 17E139j.

You can disable the 32 bit apps like this in terminal:

Boot to Recovery OS by restarting your machine and holding down the Command and R keys at startup.

Now in terminal use this:

nvram boot-args="-no32exec"

Then restart computer.

You can re-enable them like this:

nvram boot-args=""

(again in Recovery OS)

Then restart computer.



Looks like there will cease to be separate special builds for the iMac Pro now. They can use the same installers (including combos) the other macs can use for 10.13.4. Previously for 10.13.3 betas and the final release of 10.13.3 the iMac Pro got their own special builds and no combo.

The 10.13.4 installer also now has a new component called Secure Boot:

EDIT: The commands for enabling and diabling 32 bit apps have been corrected thanks to GDP3.

 

[justperry]

Something new must have been added to this built, I'll explain

About a month or so I needed Windows and I couldn't use Parallels for it, had some external device not recognised/working under Parallels.
I have an SSD and a harddrive in my Mac Mini, I wanted to use bootcamp but I couldn't, so I installed it manually on the HD, I also installed a different bootloader, before I could choose the Windows install only by pressing the option key at startup, I could not see the Windows part in Startup Preferences.
I just installed this beta, saw 2 extra disks, one untitled which is the Windows disk, never saw that one before and the recovery partition (Named: System reserved), strange, the last must be a fluke.
I also can choose the Windows startup disk now, as I said before, it's not bootcamp.

Edit: Bolded part, it's not the recovery partition, seems like the Windows boot section.

Snip...The 10.13.4 installer also now has a new component called Secure Boot:

View attachment 748321

Yup, saw that one too.

 

[Pkavicky]

Why wouldn't you be able to boot RAID-0 volumes? What's your RAID setup? Which RAID controller are you using?

It’s my understanding the you still cannot boot from a RAID 0 drive in High Sierra. I have a Sonnet Tempo Pro Plus in a Mac Pro 5.1. I have two SSDs on it, one of which is the boot drive. I just want it for speed. I believe you can have a RAID drive in a High Sierra machine, it’s just not able to boot from it. I’m waiting on an update to fix that. I imagined it would come when APFS support for fusion drives came, but I’d be happy if RAID drive boot support came sooner.

 

[casperes1996]

Neither Spotlight returns the right file despite lots of rebuilding nor smart folders like Recents work fine. Also several commands using mdfind won't work since Yosemite. Do you actually use any of the stuff? On my iMac Finder hangs quite often. I have done lots of NVRAM and SMC resettings.

All of it in fact, yes. I constantly use Spotlight, both for finding files, launching apps, converting currencies, etc.
I don't have many smart folders, but the two I have work just fine, and, and I just tried a few quick mdfind queries with no issues in finding what I expected.
High Sierra 10.13.3 on my iMac, as well as my MacBook Pro, both work perfectly fine.
[doublepost=1516830735][/doublepost]

It’s my understanding the you still cannot boot from a RAID 0 drive in High Sierra. I have a Sonnet Tempo Pro Plus in a Mac Pro 5.1. I have two SSDs on it, one of which is the boot drive. I just want it for speed. I believe you can have a RAID drive in a High Sierra machine, it’s just not able to boot from it. I’m waiting on an update to fix that. I imagined it would come when APFS support for fusion drives came, but I’d be happy if RAID drive boot support came sooner.

Is this software RAID?
Addendum - are these RAID drives APFS? Cause if so that's a key part I didn't catch.
[doublepost=1516830838][/doublepost]

Looks like there will cease to be separate special builds for the iMac Pro now. They can use the same installers (including combos) the other macs can use for 10.13.4. Previously for 10.13.3 betas and the final release of 10.13.3 the iMac Pro got their own special builds and no combo.

Pretty sure the secure boot you mention is exactly for the iMac Pro, since the T2 chip is in there.

The 10.13.4 installer also now has a new component called Secure Boot:

[doublepost=1516830981][/doublepost]

I have an SSD and a harddrive in my Mac Mini, I wanted to use bootcamp but I couldn't, so I installed it manually on the HD, I also installed a different bootloader, before I could choose the Windows install only by pressing the option key at startup, I could not see the Windows part in Startup Preferences.

Why couldn't you use BootCamp?

I just installed this beta, saw 2 extra disks, one untitled which is the Windows disk, never saw that one before and the recovery partition (Named: System reserved), strange, the last must be a fluke.

Could be that the update just rebuilt the GPT or something.

 

[Chazzle]

I still use the ancient version of iStat Pro, so that's probably it

Funny how it shows the full Dashboard process and not just iStat Pro though. I mean, I get that a 32-bit widget probably needs the 32-bit Dashboard to run, but even then, it's all merged into a single visual Dashboard. So it's like the two Dashboard versions are sharing a viewport with different models

Same thing going on here, and I too am running an old version of iStat Pro haha. I hope that doesn't go way.

 

[casperes1996]

Same thing going on here, and I too am running an old version of iStat Pro haha. I hope that doesn't go way.

Yeah - I like having it in Dashboard, and I'm a cheapskate who doesn't want to pay for iStat Menus .
But if it goes I'll be fine. I'll just use htop for my quick system overview, and MacsFanControl for sensor readings.

 

[ikir]

Please tell what’s new in MacOS 10.13.4

Many eGPU changes!! Yeahhhh can’t wait for public beta
[doublepost=1516852923][/doublepost]

Neither Spotlight returns the right file despite lots of rebuilding nor smart folders like Recents work fine. Also several commands using mdfind won't work since Yosemite. Do you actually use any of the stuff? On my iMac Finder hangs quite often. I have done lots of NVRAM and SMC resettings.

Do you have a spinning hard drive? It could be broken, they don’t last forever

 

[TheTissot11]

Many eGPU changes!! Yeahhhh can’t wait for public beta
[doublepost=1516852923][/doublepost]
Do you have a spinning hard drive? It could be broken, they don’t last forever

No, both my iMac and rMBP have built-in SSDs.
[doublepost=1516868561][/doublepost]

All of it in fact, yes. I constantly use Spotlight, both for finding files, launching apps, converting currencies, etc.
I don't have many smart folders, but the two I have work just fine, and, and I just tried a few quick mdfind queries with no issues in finding what I expected.
High Sierra 10.13.3 on my iMac, as well as my MacBook Pro, both work perfectly fine.
[doublepost=1516830735][/doublepost]

I doubt you do much with Smart Folder and look for files using mdfind command. If you do then try opening files after searching through mdfind command by piping the command to open the searched file in an application (Preview for example). And for Recents, arrange the documents in Date Last Opened. And then try opening few files from Finder and see if the Finder updates the data about opening of these files. This isn't a problem specific to my iMac or rMBP, I have seen it on my friends Mac too and it exists since Yosemite. I also complained to Apple (when I was using Yosemite) and they acknowledge this problem but did nothing to fix it. So I'm not going to trust you on this!

 

[casperes1996]

No, both my iMac and rMBP have built-in SSDs.

I'm sorry, I don't know why Spotlight and smart folders aren't working for you, but it works for me. Spotlight finds everything across my Fusion Drive, network drive and directly attached drives.

 

[TheTissot11]

I'm sorry, I don't know why Spotlight and smart folders aren't working for you, but it works for me. Spotlight finds everything across my Fusion Drive, network drive and directly attached drives.

Thanks. Maybe I should clean-install HS on my iMac since I'm also having my Finder hanging quite often these days and I always upgraded the macOS after Yosemite. I can get correct results by using mdfind or mdls -name finename commands but I can't pipe the result to xargs -0 open and use preview to open these pdf files. This problem started after Yosemite and Apple acknowledged it too. With HS it looked in the beginning that it will be fixed and the new Recents will replace All My Files properly. The Recents seem to work better on my rMBP than iMac and this could be because I had clean installed Sierra last year and then upgraded to HS.

 

[casperes1996]

Thanks. Maybe I should clean-install HS on my iMac since I'm also having my Finder hanging quite often these days and I always upgraded the macOS after Yosemite. I can get correct results by using mdfind or mdls -name finename commands but I can can't pipe the result to xargs -0 open and use preview to open these pdf files. This problem started after Yosemite and Apple acknowledged it too. With HS it looked in the beginning that it will be fixed and the new Recents will replace All My Files properly. The Recents seem to work better on my rMBP than iMac and this could be because I had clean installed Sierra last year and then upgraded to HS.

Interesting. That you get the correct results when just using mdfind, but piping it to xargs results in incorrect behaviour is very strange. If it can print properly to stdout, I see no reason it shouldn't be able to redirect it to another process, unless the issue is with xargs taking in the input.

I had an issue where the Finder would never ever show any toolbar or sidebar or anything (like when you open a DVD), no matter what I did. The issue just appeared one day on Sierra. Fixed itself when I upgraded to HS. Still curious as to why that happened. Anyways, point is that sometimes weird behaviours occur, and there are so many variables that it can be hard to tell why. A clean install might fix your issue indeed

Thanks. Maybe I should clean-install HS on my iMac since I'm also having my Finder hanging quite often these days and I always upgraded the macOS after Yosemite. I can get correct results by using mdfind or mdls -name finename commands but I can can't pipe the result to xargs -0 open and use preview to open these pdf files. This problem started after Yosemite and Apple acknowledged it too. With HS it looked in the beginning that it will be fixed and the new Recents will replace All My Files properly. The Recents seem to work better on my rMBP than iMac and this could be because I had clean installed Sierra last year and then upgraded to HS.

What exactly does it print when you try and pipe mdfind?

 

[leman]

Fixed some stuff for me. Most significantly: waking up from sleep when a monitor is attached now works properly and the windows are exactly where one left them.

 

[TheTissot11]

Interesting. That you get the correct results when just using mdfind, but piping it to xargs results in incorrect behaviour is very strange. If it can print properly to stdout, I see no reason it shouldn't be able to redirect it to another process, unless the issue is with xargs taking in the input.

I had an issue where the Finder would never ever show any toolbar or sidebar or anything (like when you open a DVD), no matter what I did. The issue just appeared one day on Sierra. Fixed itself when I upgraded to HS. Still curious as to why that happened. Anyways, point is that sometimes weird behaviours occur, and there are so many variables that it can be hard to tell why. A clean install might fix your issue indeed



What exactly does it print when you try and pipe mdfind?

It says the files, that I could find using mdfind command, don't exist when I'm piping though xargs. Also I have noticed that GUI version of Spotlight wouldn't show me the all the files (even after filtering the types of the documents) that mdfind gives. In Mavericks this wasn't the problem.

 

[JCsHands2]

Does the menu bar look different for anyone else? When in dark mode all of the icons are still dark, e.g. Spotlight, Notification Center, and Battery indicators are almost invisible. I haven't used Light mode for years, but it also seems to be a little different, maybe a different color grey?

 

[casperes1996]

It says the files, that I could find using mdfind command, don't exist when I'm piping though xargs. Also I have noticed that GUI version of Spotlight wouldn't show me the all the files (even after filtering the types of the documents) that mdfind gives. In Mavericks this wasn't the problem.

When i just tried piping mdfind, it says that the command I am trying to pipe it to doesn't exist, not matter what I try and pipe it to. Everything else works as it should, but for some reason, pipes don't play well with mdfind for some reason.... Although maybe... I'll just try something



OK. Problem figured out. It's specific to the Terminal app. If I run the Terminal that's in XQuartz, it works just fine (passing it to xargs, to grep, to anything). To check if it were a problem with Terminal the app, or just the specific shell Terminal spawned, I tried using a different version of Bash in Terminal, as well as csh, with no luck. Still "command not found" no matter what command I try and pipe to. But in XQuarts' Terminal, it works
[doublepost=1516914095][/doublepost]

Does the menu bar look different for anyone else? When in dark mode all of the icons are still dark, e.g. Spotlight, Notification Center, and Battery indicators are almost invisible. I haven't used Light mode for years, but it also seems to be a little different, maybe a different color grey?

The light version seems the same to me.

Reversed of you, I very rarely use Dark mode, but it to me seems a tad brighter (though that may as well just be that my background picture is different to last I tried). However, Spotlight and all the other menu bar icons appear just as they should, white on black or black on white depending on setting

 

[TheTissot11]

When i just tried piping mdfind, it says that the command I am trying to pipe it to doesn't exist, not matter what I try and pipe it to. Everything else works as it should, but for some reason, pipes don't play well with mdfind for some reason.... Although maybe... I'll just try something



OK. Problem figured out. It's specific to the Terminal app. If I run the Terminal that's in XQuartz, it works just fine (passing it to xargs, to grep, to anything). To check if it were a problem with Terminal the app, or just the specific shell Terminal spawned, I tried using a different version of Bash in Terminal, as well as csh, with no luck. Still "command not found" no matter what command I try and pipe to. But in XQuarts' Terminal, it works
[doublepost=1516914095][/doublepost]

Then I should install X11? Also do you use tabs in Finder? When I use tabs and sometimes I go to these tabs after a day or two Finder wouldn't display the the files properly in some tabs. I have click on other tab and then come back to the previous tab, only then i see all the files in that tab.

 

[casperes1996]

Then I should install X11? Also do you use tabs in Finder? When I use tabs and sometimes I go to these tabs after a day or two Finder wouldn't display the the files properly in some tabs. I have click on other tab and then come back to the previous tab, only then i see all the files in that tab.

The X Terminal worked out my issues with piping mdfind anyways, so yeah, try it!

I generally don't use tabs, no. I just open up more windows.

 

[TheTissot11]

The X Terminal worked out my issues with piping mdfind anyways, so yeah, try it!

I generally don't use tabs, no. I just open up more windows.

Thanks for the tips!

 

[Milltek]

Can anyone tell me if the 32-bit warning means that 13.3.4 will definitely NOT run 32 bit apps when it is released??

 

[casperes1996]

Can anyone tell me if the 32-bit warning means that 13.3.4 will definitely NOT run 32 bit apps when it is released??

I can tell you it definitely does NOT mean that

Such a change would not be made to a point release. General consensus is it'll be dropped in 2015 (maybe partially, maybe entirely).

 

[Milltek]

I can tell you it definitely does NOT mean that

Such a change would not be made to a point release. General consensus is it'll be dropped in 2015 (maybe partially, maybe entirely).

That's a relief! I have an older version of MS Office that is 32 bit and although I don't use it that much, I'd hate to have to buy the latest just because of that.

Thank Casperes1996

 

[casperes1996]

That's a relief! I have an older version of MS Office that is 32 bit and although I don't use it that much, I'd hate to have to buy the latest just because of that.

You're welcome - Apple has said that High Sierra (and that's all versions of High Sierra) will be the last release to support 32-bit "without compromises". This likely just means that the next release will become more agressive with warnings though. I.e. now you get a warning the first time you start an app saying "it's hurting performance". New release you'll likely get a message every time you open a 32-bit app, saying not just that it may hurt performance, but also that it'll stop working in a future release

 

[macsba]

Can anyone tell me if the 32-bit warning means that 13.3.4 will definitely NOT run 32 bit apps when it is released??

The warning will still be in GM version of macOS 10.13.4. Apple is stating in a future release such as macOS 10.14 won't run 32 bit applications. Apple is giving the users a 'heads up' and making them aware of the future situation.

 

[tywebb13]

You don’t have to wait.

You can turn the 32 bit ones off yourself in terminal in Recovery OS

nvram boot-args="-no32exec"

Then restart computer.

If you don’t like it you can turn them back on with

nvram boot-args=""

(again in Recovery OS)

and then restart.

EDIT: The commands for enabling and diabling 32 bit apps have been corrected thanks to GDP3.

 

[casperes1996]

You don’t have to wait.

You can turn the 32 bit ones off yourself in terminal:

sudo nvram boot-args="-no32exec"

Then restart computer.

If you don’t like it you can turn them back on with

sudo nvram boot-args=""

and then restart.

The benefit to this is that you can see exactly how it'll impact you before the eventual update comes out, so you can make a more informed decision about whether or not to do the update then