Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
After updating 10.13 to 10.13.1 beta 1 I was unable to join wifi.

Tried restarting computer. That didn't work.

Tried tuning wifi off and on again. That didn't work.

What eventually worked was restarting the modem.

But I never had to do that before after a mac os update. I've had all the betas from 10.7.2 right up to 10.13 and after every update wifi connected automatically.

Something bad happened going from 10.13 to 10.13.1 requiring a modem restart. Don't know why. At least I got it working again. Otherwise I would have been downgrading to 10.13 again. No need now.

Anyone else experiencing wifi problems like this when going from 10.13 to 10.13.1?
 
I just finished installing it. Bigger and longer than I thought. It actually took two tries. First download was 2GB. On reboot, I got "about 2 minutes remaining". Then the screen went black, fans running for about two minutes, then a boot with no update. Second try download was 1.5GB download and it took about 30 minutes to install.

The 2GB unsuccessful first try and 1.5GB successful second try used to happen more than a few times when installing pre-release betas. I think it's weird that the size of the update changed.
 
We found a password change issue with High Sierra in our domain environment.l with Enterprise Connect. I’m hoping this fixes that.
No, please.

One "Kernel panic" and Apple is going to the dogs?

I have run the developer betas since Mountain Lion and have never had a "kernel panic."

I actually don't know what a "kernel panic" IS.
Wait so you don’t know what it is so how are you sure you haven’t had one? :confused: Having a kernel panic when you control the hardware and software is never a good thing. They are very rare in Solaris and HP-UX.
 
I just finished installing it. Bigger and longer than I thought. It actually took two tries. First download was 2GB. On reboot, I got "about 2 minutes remaining". Then the screen went black, fans running for about two minutes, then a boot with no update. Second try download was 1.5GB download and it took about 30 minutes to install.

The 2GB unsuccessful first try and 1.5GB successful second try used to happen more than a few times when installing pre-release betas. I think it's weird that the size of the update changed.

No. It's not weird.

What actually downloads are the following files:

macOSUpd10.13.1.RecoveryHDUpdate.pkg (492.6 MB)
macOSUpd10.13.1.pkg (1.17 GB)
EmbeddedOSFirmware.pkg (59.3 MB)
FullBundleUpdate.pkg (110.3 MB)
FirmwareUpdate.pkg (200.5 MB)

of which the latter 4 have to install together. The first one however can be installed independently.

So I think what probably happened was you got the lot at first (or at least most of it), but only the first one installed.

Then the second time around it didn't need to download the first one because that was already installed. It just got the rest of it and that would explain the change in size of the update the second time around.
 
No. It's not weird.

What actually downloads are the following files:

macOSUpd10.13.1.RecoveryHDUpdate.pkg (492.6 MB)
macOSUpd10.13.1.pkg (1.17 GB)
EmbeddedOSFirmware.pkg (59.3 MB)
FullBundleUpdate.pkg (110.3 MB)
FirmwareUpdate.pkg (200.5 MB)

of which the latter 4 have to install together. The first one however can be installed independently.

So I think what probably happened was you got the lot at first (or at least most of it), but only the first one installed.

Then the second time around it didn't need to download the first one because that was already installed. It just got the rest of it and that would explain the change in size of the update the second time around.
Ahh, thank you for the explanation. My updates seem to go this way more often lately.
 
Worked for me.....downloading now. I pray they fixed the issue where my USBC monitor doesn't work.

Edit: Nope still not working. Can't believe nobody else is having this issue, I must be the only person that bought the HP Envy USB-C monitor.
 
Last edited:
Of course not. But that *is* a feature that's coming in an update, and it's one that some people look forward to, so I can't avoid it. No new emoji in this update, though, and I can promise not to mention them again until they launch.

It’s ok, though it irritates us, it is irritating humor. Just like the launch of ‘watch bands’. :). Keeps it real.
 
Hmm...this is concerning. After all the Developer testing and the countless users running the Public Beta and then to still have so many issues to release an update within a week?
Don't count too much on public beta testers. Many of them only download the public betas because they're curious, and they don't ever report bugs to Apple. Some public beta testers do, but most don't.

Anyone else having problems with the updated Photos app? It's running really slow on my 2011 MacBook Air. The previous version ran fine.
I think there are new models for object recognition, so the new version of Photos scans all of your photo library to see if there are new stuff to index. That means it will be slow until it has reindexed all of your photos.
 
only issue i have had so far with high sierra is a work version of MS Outlook said it weren't compatible with high sierra and since i don't have the upgraded version i just hardly cared as i dropped it in the trash, garbage MS products always something wrong. in general high sierra is quite a bit faster at launching apps and all sorts of things like rendering web pages, booting, wake from sleep, ... it's a good upgrade so far for me.
 
High Sierra has been disastrous for my iMac to the point that I'm now considering the first clean install in 5 years. Not what I expected of an OS meant to fix underlying problems and improve the system. It did the opposite. Should've stayed on Sierra.

I'm looking forward to this point update. I mean, it can't get any worse... can it?
 
High Sierra has been disastrous for my iMac to the point that I'm now considering the first clean install in 5 years. Not what I expected of an OS meant to fix underlying problems and improve the system. It did the opposite. Should've stayed on Sierra.

I'm looking forward to this point update. I mean, it can't get any worse... can it?
No! don’t fresh install. I felt the same after updating. just wait for hours and you will change your mind. It was super slow and I regret to update but now I am very happy with the performance. And I compare it to another M ac which still has Sierra. I think it’s indexing now and this depends on the number of data you have on your Mac. so you just wait
 
High Sierra has been disastrous for my iMac to the point that I'm now considering the first clean install in 5 years. Not what I expected of an OS meant to fix underlying problems and improve the system. It did the opposite. Should've stayed on Sierra.

I'm looking forward to this point update. I mean, it can't get any worse... can it?

Yes. It can get worse. Apparently you can’t redownload Sierra anymore: https://www.macrumors.com/2017/09/26/macos-sierra-decoupled-from-apple-id/
 
Yeah I think I will sit out High Sierra until 10.13.5 or so... All this yearly changing of the OS is getting a bit ridiculous at this point. I really wish they would hold still on one for a few years and perfect the stability. I mean do we really need any "new" features? They seem to just be adding stuff for the sake of adding now. Not because it is making anything better. And with Apple this seems pointless seeing as their OS is free. It isn't as thought they have money to make by doing this. I miss the good ole' days when an OS stuck around for many many years.
I agree.
The new Photos could have been made available on Sierra (or El Cap), I'm sure.
Same goes for Metal 2.

APFS is something different. But I have two thoughts on that:
1. Ruhsed into releasing it.
Apple have backed out of supporting APFS on HDD just before the final release, and publicly have stated it will come later...

2. APFS was a "silent" upgrade on iOS.
Wouldn't it have been a possibility to "silently" upgrade macOS 10.13 (or whatever version...) with APFS later?

It's all marketing, of course.
But it feels that because of this "must announce at WWDC, must release in the fall" Apple are scrambling for new features and forcing them into a "new OS" that the user must upgrade to. That, in turn, sparks buggy releases.

For the majority of users, the decent thing to do is wait until the .2 update. Most bugs squashed, most apps updated.
 
Hmm...this is concerning. After all the Developer testing and the countless users running the Public Beta and then to still have so many issues to release an update within a week?

I honestly don't understand what is happening? I also wonder if it is related to the lack of follow through on support contacts. I know personally I have a number of unresolved issues that remain open that have gone to senior advisors or engineering of which I have never heard back with any feedback.
[doublepost=1506536153][/doublepost]I guess new is new.....



Welcome to the modern world - where everyone passes the buck.
 
I see a lot of complaints, and I feel bad for the affected users, but I feel like I should mention (so that it doesn't seem like this release is a disaster for everyone), that High Sierra seems to have breathed new life into my late 2013 MBP - it's faster than ever before, presumably due to APFS, and I appreciate all of the new features.
 
  • Like
Reactions: Agent2015
Hope they're working with Adobe (or Adobe with them rather), can't upgrade until the issues with InDesign and Illustrator are sorted.

Adobe software not being compatible with High Sierra is a joke! They've had literally months to get the software compatible. Thankfully I've only seen a couple of issues since upgrading - but they should have been ready with a day one patch. It's not like they didn't know it was coming and an exact date at that!
 
  • Like
Reactions: Agent2015
After updating 10.13 to 10.13.1 beta 1 I was unable to join wifi.

Tried restarting computer. That didn't work.

Tried tuning wifi off and on again. That didn't work.

What eventually worked was restarting the modem.

But I never had to do that before after a mac os update. I've had all the betas from 10.7.2 right up to 10.13 and after every update wifi connected automatically.

Something bad happened going from 10.13 to 10.13.1 requiring a modem restart. Don't know why. At least I got it working again. Otherwise I would have been downgrading to 10.13 again. No need now.

Anyone else experiencing wifi problems like this when going from 10.13 to 10.13.1?
[doublepost=1506583461][/doublepost]No such problem - straightforward update here.
 
Can anybody confirm it does solve it? I am waiting for the fix before I install High Sierra.
You do realize this issue affects versions of macOS before High Sierra right? Holding off on installing for that fix isn't much of a reason.

EDIT: I see others have beat me to this....
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.