- Swcdn apple com content downloads
- Michael Kuron’s Blog
- Troubleshooting Apple Software Update Server
- “Product file URL contains possible security violation.” in log
- “Product XXX-YYYY is no longer available and has no replacement” in log or “*** Missing version string for product XXX-YYYY” in log or “_productId Update” showing up in Server Admin
- Create a bootable Mac OS X Lion Server USB drive
- Question: Q: Issue in Downloading Windows Support Software
- All replies
- Big Sur 11.0.1 RC2 Installation Issue
- Answers
- Question: Q: Installation stuck at «Retrying http://swcdn.apple.com/. /InstallESDDmg.pkg after 1 failure(s)»
- Helpful answers
Swcdn apple com content downloads
Copy raw contents
A script to download the components for a macOS installer from Apple’s softwareupdate servers and then install those components as a working «Install macOS High Sierra.app» onto a disk image.
The install logic within Apple’s packages will be evaluated by Apple’s installer, so you must run this on hardware compatible with the version of macOS for which you are attempting to obtain an installer. In other words, this script will fail when run on hardware that does not support High Sierra, and should High Sierra be «forked» as it was when the iMac Pro was first shipped, you may only be able to successfully install a hardware-specific version of the installer on the hardware supported by that specific build.
You’ll need roughly twice the ultimate storage space; IOW if the High Sierra installer is 6GB you’ll need at least 12GB free. If you use the —compress option you may need up to three times the space.
This tool must be run as root or with sudo .
—catalogurl Software Update catalog URL used by the tool. Defaults to the default softwareupdate catalog for the current OS if you run this tool under macOS 10.13-10.15.x.
—seedprogram SEEDPROGRAMNAME Attempt to find and use the Seed catalog for the current OS. Use installinstallmacos.py —help to see the valid SeedProgram names for the current OS.
—workdir Path to working directory on a volume with over 10G of available space. Defaults to current working directory.
—compress Output a read-only compressed disk image with the Install macOS app at the root. This is slower and requires much more working disk space than the default, but the end product is more useful with tools like Munki and Imagr.
—ignore-cache Ignore any previously cached files. All needed files will be re-downloaded from the softwareupdate server.
Источник
Michael Kuron’s Blog
Troubleshooting Apple Software Update Server
We are currently in the process of migrating towards a thin imaging approach for the Macs I manage at my university. One of the things we needed was an Apple Software Update Server, which is pretty straight forward to set up using Server Admin. I used Snow Leopard Server 10.6.8 with Lion updates enabled as described in Apple’s KB article.
A command I found extremely useful:
This command enables all available updates. If you have set SUS to automatically mirror, but not automatically enable, this command saves you from having to click on every single one of the 600 updates to enable it.
A few days after I set up my SUS I was starting to see a bunch of error messages in /var/log/swupd/swupd_syncd_log after starting a sync run using the refresh button below the updates list in Server Admin. I’ll go over them here and explain my fixes:
“Product file URL contains possible security violation.” in log
A few Lion updates contain subfolders, which SUS does not create. Simply create those subfolders (mkdir /var/db/swupd/content/downloads/10/59/11D2515_ServerEssentials/xajda1v3ycqbtv75fiw5hvosaovu9to9hc/ServerEssentials.dst; chown _softwareupdate /var/db/swupd/content/downloads/10/59/11D2515_ServerEssentials/xajda1v3ycqbtv75fiw5hvosaovu9to9hc/ServerEssentials.dst) and have SUS recheck for available updates.
[EDIT: The original version of this blog post used curl to download the file, but forgot to chown the folder. Letting SUS download the file itself is the cleaner solution.]
[EDIT 2: This issue is really widespread with the ARD Client 3.6 update, where http://swcdn.apple.com/content/downloads/31/58/041-5433/xt9k9paj5zu8rx258rdccohk236ee77clh/RemoteDesktopClient.dst/041-5433.*.dist fails. This does solve this issue.]
“Product XXX-YYYY is no longer available and has no replacement” in log or “*** Missing version string for product XXX-YYYY” in log or “_productId Update” showing up in Server Admin
Your catalog is corrupted. Delete it to have it rebuilt automatically. The following commands help:
Create a bootable Mac OS X Lion Server USB drive
Источник
Question: Q: Issue in Downloading Windows Support Software
Hi, I’m trying to dual boot my macOS with windows using Boot Camp, I have an issue where the speed of the download is slow, as usual my internet speed is fine
How am I able to fix this?
Macbook Pro MD101 A1278 (13″ Mid-2012)
macOS Mojave 10.14.6
MacBook Pro 13″, macOS 10.14
Posted on Sep 24, 2020 5:33 PM
All replies
Loading page content
Page content loaded
Your connection to the Apple CDN is slow, not your Internet connection. You can try Brigadier (https://github.com/timsutton/brigadier).
Sep 25, 2020 8:30 AM
I’m not an expert in Git, can you show me how to build the package and run it?
Sep 25, 2020 6:25 PM
The GIT link provides scripts, which you can readily use. You do not need to ‘build’. Look at the description of the utility brigadier.
Sep 25, 2020 6:50 PM
I can’t tell where’s the utility brigadier, only found this in the readme
Sep 25, 2020 7:12 PM
Please explain like I’m five sir, this is stressing me out
Sep 26, 2020 4:58 AM
Please explain like I’m five sir, this is stressing me out
😂 Hopefully the following content is suitable material for a 5-year old.
In the attached sample, the brigadier package was downloaded to the Downloads folder.
After the download is complete, and you have uncompressed the ‘package’, your Downloads will have this structure.
Here is an example of downloading the Driver package.
Sep 26, 2020 8:04 AM
so I did this, what should I do after I fully download the .dmg?
Sep 27, 2020 6:25 AM
You should have a WindowsSupport.dmg. You can double-click on it. It should have all the drivers. Use a USB2 Flash drive, format it as FAT32 and select the top level files from the .dmg and drag them to the USB2. This USB2 will be your drivers installation USB. You can run setup.exe in the Bootcamp folder to install all the drivers. If you need to install individual drivers, check the individual vendor folders.
Sep 27, 2020 8:52 AM
Sorry, but I forgot to tell you that I don’t have a Windows installed yet, this problem happened when I tried to install the Boot Camp, I tried unchecking the boxes, but still ended up in the same spot
Sep 27, 2020 9:29 PM
Are you using a wired connection or wireless?
Sep 28, 2020 1:57 PM
I’ve tried both connection, different wifi’s, different places, yet it still the same, my thought is that this isn’t on me, but on Apple, since I could watch 720p60fps just fine on YT, I even managed to download the driver through brigadier
Источник
Big Sur 11.0.1 RC2 Installation Issue
Running into an issue installing Big Sur on top of Catalina 10.15.7 on 2019 Mac Pro.
Downloads the installer no problem, but after a bit running — runs into a very generic dialog with
From the console, I can see that it tries to go through some networking, and everything is successful up until bridgeOS update download.
Relevant lines seem to be:
(formatted for readability)
A bit of google searching got me thinking that there seems to be something hay-wire with T2 firmware update, but before I go nuking it on my dev machine, I am curious whether anyone else ran into this, or what likely is the culprit, when should we expect the required components be fully upgraded so the installer can download them?
Answers
I’m getting the same thing. I uninstalled everything and then repeated the steps again with the Console application open and saw this during the «C-R» in the software update pane of system settings:
A bit more context after trying the installation again after the above messages:
I’ll chime in with a ‘me too’ from multiple Mac systems (all with a T2). I was trying to go from MacOS 10.15.7 (19H15) to 11.0.1 RC2 on some test systems before GA on Thursday.
Multiple forums have users with the exact same problem, so it’s clearly something Apple needs to take care of. I’m certain they’re aware. 🙂
I did a quick analysis of the HTTP URLs present in my install error log. Of the 76 unique URLs listed, 11 of them gave a 404 response, meaning about 1 in 7 were not found. Example (edited for clarity) of one 404: http://swcdn.apple.com/content/downloads/06/41/***/***/MRTConfigData_10_15.pkg.
This could be unrelated and normal, or it could be that the a file required for the bridge update was not found, so it could not update, and the install failed.
Pure speculation, but a reasonable possibility. If so, apple could drop the missing bits in place on the CDN, and the installers would magically start to work, maybe?
Источник
Question: Q: Installation stuck at «Retrying http://swcdn.apple.com/. /InstallESDDmg.pkg after 1 failure(s)»
Spec
Hardware: MacBookPro12,1 @ 2.70 GHz (x 4), 8192 MB RAM
Running OS Build: Mac OS X 10.13 (17A365)
I’m using FileVault.
Backgrounds
I was using Sierra, tried to upgrade through Appstore, successfully downloaded, launched installer.
It seemed working fine. Installer required me to restart my macbook and I did. Black screen with apple logo appeared and the progress bar was telling me that everything was working fine at that time.
But then suddenly a message showed up. «something is wrong blabla . you should diagnose with holding D when booting up . or just restart.»
So I restarted it, now there’s a question mark folder in black screen. I tried Safe mode, same screen.
Now, I’m on probably 7th try to install it on Recovery mode but it’s keep failing.
Current State of The Problem
I know there are 3 different options for Recovery mode when you’re trying to reinstall your macOS. How to install macOS — Apple Support
- Command + R — Install the latest macOS that was installed on your Mac, without upgrading to a later version.
- Option + Command + R — Upgrade to the latest macOS that is compatible with your Mac.
- Shift + Option + Command + R — Install the macOS that came with your Mac, or the version closest to it that is still available.
First, I tried the first option. Apparently, at the time, the latest macOS that was installed on my macbook was High Sierra. Maybe because there are some progresses that were made even though it stopped due to error or crash or whatever. Anyway I tried reinstall, didn’t work. Here’s my recent logs.
And nothing after that line. It stuck. Saying «About 24 minutes remaining» for hours.
My trials
I tried the second option with Option + Command + R but the result is the same.
I check the disk utility, ran First Aid, it says my disks are OK.
45.97 GB / 120.47 GB are Free.
Note: it says my disk format is AFPS (Encrypted). don’t know why.
I was able to navigate the folder named «/macOS Install Data» in which all of «AppleDiagnostics.chunklist», «AppleDiagnostics.dmg» etc are located. No «InstallESDDmg.pkg» found but there was «InstallESDDmg.pkg.partial».
Thankfully I could navigate «/Users/myname» and all my files seem to be ok.
I’ve tried wating for 2 hours, nothing has changed so far.
I haven’t tried the third option because I’m afraid to lose my data while trying to downgrade to my old macOS.
Help me!!
I can’t figure out why it can not download «InstallESDDmg.pkg» when it seems like I can download it using Safari, Chrome in other laptop. Although it says it will take 50m to complete download. That’s why I tried to wait for 2 hours.
So I think it doesn’t make sense that there’s a network issue.
my next step should be «Starting SKDaemon. «.
But I’ve never seen that line showing up.
Please help me out.
MacBook Pro with Retina display, macOS High Sierra (10.13)
Posted on Sep 27, 2017 3:57 AM
Helpful answers
Specs:
- Running Mountain Lion (freshly installed), not yet using FileVault
- MBP Retina early 2015 (2.7Ghz, 8GB RAM)
Background:
- Unable to download installation files for High Sierra using small downloader/installer from App Store
- Always got stuck with the app unable to retry/continue; every new attempt started to download again and got always ended up the same:
- After trying different (faster) Internet connection and with the same failure, I went to download the files manually one by one and then served them locally to the downloader/installer
- I did NOT have to go into the recovery console, all has been done from normal run of Mountain Lion
- Now updated, but haven’t yet tested everything. Follow only at your own risk!
What worked for me:
- AppStore did download successfully the «Install High Sierra macOS»downloader/installation package (˜14MB)
- When started, opened Log and after failure exported it
- The Log pointed at the catalog (your results may vary, I was updating from Mountain Lion):
- The Log also pointed at the specific catalog part with all the necessary files (in my case InstallESDDmg.pkg)
- Looked up the rest of the critical files from the catalogue (according to the path ../30/55/091-36857/e08asjpjpbflt33p43ufqmuv6b39x8pa10/..) and ran cURL in Terminal (replace with the problematic files that you cannot download, for me it was the largest one):
- Every time the speed dropped to 0, I cancelled the download (Ctrl+C) and started the same again, which (thanks to «-C -» parameters) resumed the download instead of downloading it again from scratch.
- After getting all necessary files, I started simpleHTTPserver in my Downloads folder, by running the following command in Terminal
sudo python -m SimpleHTTPServer 80
- In the Downloads folder, I created the same folder structure as in /content/downloads/30/55/091-36857/e08asjpjpbflt33p43ufqmuv6b39x8pa10/
- Put all downloaded files into this folder, to be specific I downloaded all of the following into this folder
Then changed hosts file to point at my local http server (add this line under ‘su’ user and make sure to save it properly
- When all configured, started the small downloader/installation app «Install High Sierra macOS»
- Because all files were hosted locally, I went fairly quickly to reboot and finishing the installation
So am now updated with High Sierra. Still have to check whether there aren’t any issues during regular run.
Thanks to JinsungL for pointing me in the right direction. All it required was a bit of playing around 🙂. And I couldn’t agree more, that Apple using http-only to download the necessary packages only implies possible security risks (not sure if the app itself doesn’t check something inside the files, etc..).
Oct 10, 2017 11:43 PM
Nice on Jinsung!
A possibly less involved option for others that worked for me was to re-install High Sierra in another location — in my case it was from my workplace (rather than home). This was my 4th attempt, and had to manually set-up the Wifi connection in Recovery mode before using the re-install option.
Oct 10, 2017 11:43 PM
There’s more to the conversation
Loading page content
Page content loaded
I have the same problem:
After that, there is no indication of anything happening.
Sep 27, 2017 5:05 AM
Short Answer
I made instructions. Follow them if you’re experiencing the same problem.
Updates
After posting this discussion, another 5+ hours passed, nothing has changed.
So I tried different approach. Remember I could access to my Macintosh HD volume though Safari’s file navigator? I tried to find the exact location of ‘macOS Install Data’ on terminal so that I could inspect more information.
I found out that they are located at ‘/Volume/Macintosh HD/macOS Install Data’ and was able to confirm that all the essential files for OS update were located in there.
Then I thought I could just download ‘InstallESDDmg.pkg’ manually using curl then move it to the folder. I tried, didn’t work. There are two important notes here.
A. Downloading stops when it hits around 326MB. I don’t know why this is happening nor if I’m the only one who’s suffering from this issue.
B. Downloaded files get removed when you start the installation.
Fact A can be solved easily, you just try multiple times with curl’s -C option. You fail like 30 times but eventually you’ll get the complete download. Look carefully if the ‘current download speed’ drops to 0. Then you’ll have to cancel the process and restart it again.
Fact B was a huge problem since even if you could somehow place the complete file at the right location, it will be removed.
So my solution to resolve this situation was;
1. Create a server that contains and serves pre-downloaded files you need but when it doesn’t have one, it will stream the original file from Apple server ‘swcdn.apple.com’.
2. Download all the files at the right directory of your server. You have to match the path of urls.
3. Modify ‘/etc/hosts’ file of your macbook.
4. Update will work now.
I created #1 using flask, downloaded all files including ‘InstallESDDmg.pkg’. Also I configured my server to stream missing files from ‘swcdn.apple.com’ if it doesn’t contain one. Later, I missed some essential files and this feature saved the installation process from errors.
I uploaded the source code at github.
#3 Didn’t work. Apparently you can’t modify ‘/etc/hosts’ when you’re in Recovery Mode. I guess.
I tried every possible method I knew including chmod, chown, chflags but all of them didn’t work.
So I had to decide to create a DNS server to make this work without modifying ‘/etc/hosts’ file. I created one using dnsmasq on ubuntu. Then I configured it to redirect ‘swcdn.apple.com’ to my custom file server, except from its own.
I’ve actually done this by redirecting ‘swcdn.apple.com’ to with no exception, then making my server to use the ip address of ‘swcdn.apple.com’ with header ‘Host: swcdn.apple.com’. But you can do this either way. The key point is to make your mac to lookup your files server IP address instead of Apple’s one but your file server to lookup the original Apple Server’s IP.
Don’t forget to configure your router to use your DNS. Then you’re good to go.
Still I had to try this several times because you can’t figure out which files are needed to be downloaded unless you try the installation step. – So don’t forget to turn on the debug mode and check the log.
But eventually this method worked.
I made this process easier for someone who’s experiencing the same issue with me.
After the installation is done, you’re system will get rebooted. At this point it seems OK to turn off your file server and DNS server. But I wasn’t 100% sure so I just left it turned on.
After the reboot another serious problem occurred. I couldn’t unlock the disk using my password.
This problem seems quite common and I could find a working solution for my case.
Disk Password Error
But with some modifications.
My ‘Macintosh HD’ disk wasn’t mounted on ‘/’ instead ‘/Volume/Macintosh HD’. Also the directory ‘/var/db/dslocal/nodes/Default’ didn’t exist in ‘/Volume/Macintosh HD’. But I could find the same files in ‘/Volume/Macintosh HD/Recovered Items/private’
and it worked. Don’t forget to put ‘\’ before spaces.
After you see the line “overall error = 0” you’re OK to reboot. When you’re system gets rebooted the login screen will be present with your account profiles. Enter your password, then it will begin to unlock your disk.
Then it gets rebooted again. This time it will continue the installation progress. It took about 30 m to be completed in my case.
After the installation, there’s one final reboot and then you’re in the new macOS High Sierra!
Thoughts
I’ve never imagined that this kind of thing would ever happen to me while just upgrading macOS. Unbelievable. Still don’t know what caused the problem but only guess is unstable internet connectivity. So never have unstable internet connectivity while upgrading your macOS. But who knew that I had one? My internet works fine for everything except ‘swcdn.apple.com’. Odd. Maybe it’s an issue from Apple’s server status. Who knows.
I’m very impressed of the system stability of macOS. I thought macOS is so stable that I would never ever strike to this kind of problem. Well… surprise! Never say never. I just wasted my 2 days.
Also I don’t understand why Apple let me do this. Apparently installation process uses http protocol which can be easily spoofed like what I did there. Maybe the installer is verifying the validity of installation files? But if not, you can basically hack someone’s Mac using this method if you have control of your local network. So don’t upgrade your macOS on public network like Work, School if you concern about hacking. Although I’m pretty sure there’s some kind of protection.
Источник