Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Malwarebytes Anti-Malware scan screams foul when it encounters DosDude's patchupdater.plist file.
I reported it and hopefully we can get it whitelisted.
 
Captura de pantalla 2017-11-06 a las 18.01.06.png Captura de pantalla 2017-11-06 a las 18.01.18.png
It should be installed already in your /Applications/Utilities folder. If not, you can install it using the script found here.

Yeahhh is installed, sorry. But how can I Re-install patches??? Thanks and sorry.
 
I forgot to mention that I had to repatch the 10.13.1 (HFS+) Recovery Partition, but the main 10.13.1 boot partition did not need to be repatched. But it seems many of you don't even care about the Recovery Partition so if that Recovery Partition is not important to you, then no repatching (or full installer needed). Just the App Store 10.13.1 update was fine for me for updating the main boot partition.

You seem to have a corner case then where the software update installation doesn't report that certain installers failed to complete. This issue has been reported by many folks here as it results in Safari, AppStore, etc from having broken network access. Perhaps Apple has coded the firmware installers to not run on some, but not all, unsupported machines.
My main point was that, for those with the failing software updates, attempting to repair the resulting volumes may be a risky strategy as we really don't know how much of the installation process properly completed.
 
I noticed my menu bar (iMac 9,1) is no longer transparent after upgrading from 10.11. Is this how 10.13 is or is it a video driver issue that causes the loss of transparency?
 
You seem to have a corner case then where the software update installation doesn't report that certain installers failed to complete. This issue has been reported by many folks here as it results in Safari, AppStore, etc from having broken network access. Perhaps Apple has coded the firmware installers to not run on some, but not all, unsupported machines.
My main point was that, for those with the failing software updates, attempting to repair the resulting volumes may be a risky strategy as we really don't know how much of the installation process properly completed.
? I’m not sure my update success is a “corner case”. It seems a lot of people have had problems but I suspect most people have had successful updates. It’s just that those with problems would come back here to find help.

It may also depend upon the specific hardware and/or how clean the install is too.
 
I used the last Handbrake Nightly (Nov. 4) to transcode the LG Jazz TV 4K HEVC demo to 1080p h.264, using the "Super HQ 1080p30 Surround" preset, with no modifications (on my iMac). The resultant h.264 file plays perfectly in QuickTime on my 2.0 GHz MacBook5,1 with High Sierra 10.13.1.
Did some more testing as well (all with the same source, Pelham 123):

Handbrake 1.0.7:
"Apple 1080p30 Surround" -> distorted result
"Super HQ 1080p30 Surround" -> distorted result

Handbrake (latest nightly build) 20171104122632-9f9afec-master:
"Apple 1080p30 Surround" -> distorted result
"Super HQ 1080p30 Surround" -> distorted result

So it seems that certain source files reproducibly produce distorted results, regardless of the version of handbrake that I use (other sources work well with handbrake under macOS High Sierra). All of them (source and all results) play fine in VLC, though. So if only I could find out if there's a problem with the converted files or just QuickTime … any ideas on how to do that?
 
? I’m not sure my update success is a “corner case”. It seems a lot of people have had problems but I suspect most people have had successful updates. It’s just that those with problems would come back here to find help.

It may also depend upon the specific hardware and/or how clean the install is too.

A quick glance back over the past few weeks of postings on this thread show software update failures for 10.13.0 to 10.13.1 or 10.13.0/10.13.1 to 10.13.2 beta on...

mid2009 5,3 MacBook Pro
MBP4,1
Early 2009 24" iMac
Late 2009 Mac Mini with NVIDIA GeForce 9400 256MB
MacBook 5.1
Imac 9,1
MBP 5,5 with SSD(APFS)-13 inch, mid-2009 MacBook Pro
Mac Pro 3,1

I do see some of the same hardware also listed as working after system updates, It was also postulated earlier in this thread that software updates on APFS volumes always worked but we have reports going both way on that one with some users seeing failures on APFS for the same hardware. It would be nice to get to the bottom of these sporadic software update failures (which are unfortunately all too reproducible on certain machines).
 
The bit about it being perfectly safe to install system updates doesn't sound right. So far, for both the release 10.13.1 system update and the beta 10.13.2 system updates, the installation isn't cleanly completed due to the presence of firmware updates. IMHO, until Apple stabilizes the firmware and stops shoving out firmware updates with each successive Software Update release, users should be using the full installer.

@jhowarth You nailed it.
Anyone know, where to find a full installer for the latest macOS 10.13.2 dev beta 2?
 
I am waiting to apply 10.13.1 to my 3,1 Mac Pro until the dust settles a bit. The High Sierra upgrade caused enough havoc with my graphics card that I'm content to keep things in a steady state a while longer.
 
A quick glance back over the past few weeks of postings on this thread show software update failures for 10.13.0 to 10.13.1 or 10.13.0/10.13.1 to 10.13.2 beta on...

mid2009 5,3 MacBook Pro
MBP4,1
Early 2009 24" iMac
Late 2009 Mac Mini with NVIDIA GeForce 9400 256MB
MacBook 5.1
Imac 9,1
MBP 5,5 with SSD(APFS)-13 inch, mid-2009 MacBook Pro
Mac Pro 3,1

I do see some of the same hardware also listed as working after system updates, It was also postulated earlier in this thread that software updates on APFS volumes always worked but we have reports going both way on that one with some users seeing failures on APFS for the same hardware. It would be nice to get to the bottom of these sporadic software update failures (which are unfortunately all too reproducible on certain machines).
I have the aforementioned MacBook5,1 and MacBookPro5,5, and both are HFS+. As mentioned, both updated just fine, but also as mentioned, both had clean installs of 10.13 (plus some software).

It should also be noted that some people with fully supported Macs have also had problems doing the update. This is not an issue that is restricted to those of us with unsupported Macs.
 
I have the aforementioned MacBook5,1 and MacBookPro5,5, and both are HFS+. As mentioned, both updated just fine, but also as mentioned, both had clean installs of 10.13 (plus some software).

It should also be noted that some people with fully supported Macs have also had problems doing the update. This is not an issue that is restricted to those of us with unsupported Macs.
It is quite ironic I am unable to even install High Sierra due to the 'error verifying firmware' bug on my iMac 10,1 which is supposedly supported but runs like a dream on my unsupported iMac 8,1
 
3,1 with r9 280x (flashed to Mac), Apricorn PCIe card w/SSD, fresh install. Been running this rock solid since the week the tool was released. Software update not available (tried re-applying this patch). I do see red flashes occasionally when resizing some apps etc, but that is the only issue I've experienced other than not seeing the update to 10.13.1.

Thank you, @dosdude1!
 

Attachments

  • Screen Shot 2017-11-06 at 9.29.41 PM.png
    Screen Shot 2017-11-06 at 9.29.41 PM.png
    105.5 KB · Views: 171
Last edited:
3,1 with r9 280x (flashed to Mac), Apricorn PCIe card w/SSD, fresh install. Been running this rock solid since the week the tool was released. Software update not available (tried re-applying this patch). I do see red flashes occasionally when resizing some apps etc, but that is the only issue I've experienced other than not seeing the update to 10.13.1.

Thank you, @dosdude1!
Try resetting software update catalog URL by running "sudo softwareupdate --clear-catalog" in Terminal, and see if the update shows then.
 
Just discovered that my High Sierra install craps out when waking from sleep.
System wakes up but screen stays black.
I'm pretty sure the problem is the 5770 GPU as it works OK with my old GT120.
So for now I'm back to running a rock solid Sierra 12.6
Oh, and yes I have all the latest patches installed.
 
The patch tool is working beautifully on my early 2009 iMac except for the screen brightness problem. Has anyone found a fix for it? The screen brightens momentarily if you adjust it and then goes back to being dull again. It does the same if adjusted using the brightness keys or the slider in system preferences.
 
Hey dosdude1,



thanks for you great patch tools. I am using them since Sierra and they work wonderful on my MBP5,5.



Just a few comments:



I messed around with the APFS partitions. Like restored one from an other and things like that. Then I got the „NO“ symbol. I tried to apply the patch again also did a reinstall but both didn’t work.

For me a PRAM reset worked. Maybe you can add it in you FAQ. I think it is not a problem doing a PRAM reset when you run ‚csrutil disableÄ afterwards.



I am using APFS with an SSD and FileVault on. Using the EFI patch it works fine for me. There is just a little problem for me. I can not add users to unlock the Volume in the settings. There always occurs an error. Maybe there is a fix for it?



When installing updates the screen goes black with white apple logo. I want that black boot screen too :)) Is there any possibility to do it?







PS After updating to 10.13.1 the night shift patch was disabled. But a reinstall helped.
 
The patch tool is working beautifully on my early 2009 iMac except for the screen brightness problem. Has anyone found a fix for it? The screen brightens momentarily if you adjust it and then goes back to being dull again. It does the same if adjusted using the brightness keys or the slider in system preferences.

I fixed it using the terminal tool "brightness" that I found here:

https://apple.stackexchange.com/que...e-the-brightness-on-a-computer-using-terminal
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.